Data Freshness SLA Audit Builder

Audit dashboard and pipeline freshness expectations with SLA definitions, stakeholder impact, alert thresholds, and remediation actions.

Prompt Template

You are a data reliability analyst. Create a data freshness SLA audit for analytics tables, dashboards, or pipelines.

**Business area:** [sales, finance, product, support, operations]
**Critical dashboards/tables:** [list assets]
**Expected refresh cadence:** [hourly, daily, weekly, real-time]
**Current known issues:** [stale dashboards, delayed ETL, unclear ownership]
**Stakeholders:** [teams and decisions affected]
**Data stack:** [warehouse, BI tool, orchestration, dbt, spreadsheets, etc.]
**Tolerance for delay:** [minutes/hours/days by use case]

Deliver:

1. **Freshness Inventory** — asset, owner, source, expected cadence, current freshness
2. **Business Impact Tiering** — critical, important, informational
3. **SLA Definitions** — freshness target, warning threshold, breach threshold
4. **Monitoring Plan** — checks, alert channels, escalation owner, weekend/holiday rules
5. **Root Cause Categories** — upstream source delay, transformation failure, BI cache, manual upload, permissions
6. **Remediation Backlog** — quick fixes, structural fixes, and documentation updates
7. **Stakeholder Communication Template** — what to say when data is stale

Focus on restoring trust in analytics, not blaming pipeline owners.

Example Output

# Data Freshness SLA Audit: Revenue Dashboards

Freshness Inventory

| Asset | Owner | Expected | Current | Tier |

|---|---|---:|---:|---|

| ARR Executive Dashboard | RevOps | 7:00 AM daily | 9:40 AM daily | Critical |

| Expansion Pipeline Table | Sales Ops | Hourly | 3-5 hour lag | Important |

| Win/Loss Notes Sheet | Sales Enablement | Weekly | Manual, inconsistent | Informational |

SLA Definition

For the ARR Executive Dashboard, data must be refreshed by 7:15 AM on business days. Warn at 7:20 AM, breach at 8:00 AM, and post a stakeholder update by 8:15 AM.

Remediation Backlog

1. Move manual currency-rate upload to scheduled API import.

2. Add freshness tests for invoice, subscription, and account dimension tables.

3. Display last refresh time directly on the dashboard header.

Tips for Best Results

  • 💡Define freshness based on business decisions, not just technical job schedules.
  • 💡Put last refresh timestamps where users can see them.
  • 💡Separate critical dashboards from nice-to-have reports so alerts stay meaningful.
  • 💡Use calm incident language; stale data already makes people twitchy enough.