Data Freshness

Data freshness measures how recently a dataset was updated relative to expectations. A sales dashboard expected to refresh nightly is fresh at 7 a.m. if last night's load succeeded, and stale if the pipeline silently failed. Freshness is therefore two things at once: a metric (time since the last successful update) and a contract (how old the data is allowed to be before someone is alerted).

Stale data is among the most dangerous failure modes because nothing looks broken — the dashboard renders, the numbers are plausible, and decisions get made on yesterday's reality. Automated freshness checks compare actual update times against the expected schedule and raise an incident the moment a dataset misses its window.

For a Saudi Data Management Office, freshness corresponds to the timeliness dimension of data quality in the NDMO framework, and it is where executive trust is won or lost: a leadership dashboard or a submission to a national platform built on a stale table damages credibility far beyond the single failure. Defining expected freshness per dataset — daily, hourly, near-real-time — and monitoring it automatically converts an implicit assumption into an explicit, auditable commitment, and gives data teams the early warning they need before consumers notice.