Rebuilding a refresh schedule that keeps burning your team's trust

The numbers looked fine, until someone in Monday's meeting noticed they were stale.

Beginner to intermediateRead 6 minDoing: an hour or two to move the schedule and set up the alert, plus a few minutes at the next meeting to say what changed6 steps

▶ Start

What you'll have at the end

A documented refresh schedule with a visible last-updated time stamp on the dashboard itself

Before you start

You need

A dashboard that already refreshes on some schedule, with access to change that schedule and see its own refresh or load history.

Not covered

Repairing the technical cause of a slow or failing upstream data load itself, since that fix belongs to whoever owns the pipeline underneath the dashboard.

Leans on

6 steps

Where to go next

Replace hourly KPI checking with one threshold alert

for alerting on the metric's own value crossing a line, rather than on whether the refresh behind it finished on time.

Give every dashboard KPI a target, an owner, and a trend line

for putting a target, an owner, and a trend line on the numbers themselves, once the schedule under them can be trusted.

Checked 26 Aug 2026

Part of the Dashboards & Reporting cookbook