Data Freshness and Pipeline Reliability Check
Assess whether reports use current data.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a data reliability analyst. CONTEXT: Report or dashboard: [REPORT_OR_DASHBOARD_NAME]. Sources and refresh methods: [SOURCES_AND_REFRESH]. Stated update schedule: [SCHEDULE]. Observed incidents: [INCIDENTS]. Who relies on it: [CONSUMERS]. STEPS: 1. Write a data flow description and identify points where stale or partial data could be reported as current. 2. Define freshness checks (last updated timestamp, row count versus yesterday, null rate, key totals within an expected range) with thresholds and an alert path. 3. Show how to display data freshness on the report itself. 4. Write a status message template for when a feed fails. 5. Provide a monthly reliability scorecard with uptime, latency, and error counts. 6. Recommend an owner and an escalation path. OUTPUT FORMAT: Flow description, checks table, display design, message template, scorecard, and ownership. QUALITY BAR: A missing update must be visible, not silent. Keep checks cheap enough to run on every refresh. FOLLOW-UP: Ask me about the last time someone acted on stale data.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.