The useful question is not whether the data loaded. It is whether the data is current enough for the decision in front of the team. A good dashboard makes that answer visible before the conversation starts.
Freshness is more than a timestamp
A timestamp tells you when a job finished. It does not tell you whether the number is safe to use.
Good freshness design compares the data to the pace of the business process it describes. Hourly lead routing and monthly recurring revenue should not share the same stale-data rule.
SignalLake treats freshness as a contract between the metric owner and the reader: how late the source may be, what warning should appear, and when the metric should be held back from a published review.
Freshness tiers
Metric class
Typical window
What happens when stale
Routing and support queues
15 minutes
Show warning and notify the operations owner
Pipeline and campaign spend
1 hour
Keep visible, but mark decisions that depend on it
Revenue recognition
24 hours
Hold published board views until finance confirms the load
Monthly reporting
3 days
Show close status and expected finalization date
SignalLake in practice
Set freshness rules around real decisions
See how SignalLake turns source timing, warnings, and publication holds into a clear operating contract.