Information freshness
The share of knowledge domains reviewed within their required cadence.
Formula
Freshness coverage
(sources updated within required freshness window / total sources assessed) * 100
Unit
percent
Direction
Higher is better
Cadence
Monthly for high-risk information; quarterly for baseline.
Numerator
Sources updated within required window
Denominator
Sources assessed
Worked Example
Review of key executive and AI context sources.
Key sources
35
Updated within required window
22
Calculation
22 / 35 * 100
Result
62.9%
Interpretation
Information is not fresh enough for reliable decisions in several domains.
Recommended action
Set refresh owners and windows by domain risk.
Why it matters
This metric helps leaders see whether the information layer is healthy enough to support execution and AI readiness.
What it reveals
Whether information is current enough to support decisions and AI use.
Manual assessment method
Review each source of truth and record when it was last validated against its required review cadence.
Lapemo calculation path
Live through freshness rules and audit dates on knowledge domains.
Interpretation Bands
Healthy
85-100%
Strong enough for normal operating review.
Watch
70-84%
Usable, but gaps should be assigned owners.
Risk
50-69%
Weak enough to slow execution or create risk.
Critical
<50%
Do not scale the related workflow without intervention.
Required inputs
- Source list
- Last updated date
- Required freshness window
- Domain risk
Data sources
- Data catalog
- Document metadata
- Dashboard metadata
- Source-of-Truth Map
Common pitfalls
- Using one freshness window for every domain
- Counting touched files as refreshed
Recommended actions
- Define freshness by risk
- Assign refresh owners
- Retire stale sources
Measure Before You Scale
Measure the operating model before AI amplifies it.
Use the Metrics Library to understand what to diagnose, what to monitor, and where Lapemo can turn framework metrics into operating intelligence.