Operations Dashboard Specification

Defines KPIs, data sources, refresh cadence, alerting thresholds, and ownership.

# Operations Dashboard Specification â [Dashboard name] **Owner:** [Team / individual] **Audience:** [Who reads this and what decisions they make from it] **Refresh cadence:** [Real-time | 5m | hourly | daily] ## Purpose Dashboards exist to drive decisions. Write the decisions this dashboard supports. If a metric on the dashboard doesn't tie to a decision, remove it. Decisions driven: - [Decision A] â supported by [KPI #1, #3] - [Decision B] â supported by [KPI #2, #4] ## KPI catalog For each KPI: ### KPI 1: [Name] - Definition: [precise math, including time window and segmentation] - Source: [system + table or query] - Refresh: [cadence] - Threshold green / amber / red: [values] - Owner: [who explains anomalies] (Repeat for KPIs 2 through N.) ## Visual layout Sketch / link to mock. Above-the-fold panels should answer "is everything ok right now?" â colour-coded, no scrolling required. Below the fold: trends, breakdowns, drill-downs. ## Alerting Some KPIs cross a threshold and should page rather than wait for human eyes. | KPI | Threshold | Action | Channel | Acknowledger | |---|---|---|---|---| | | | | | | ## Data quality - Known gaps: [list] - Latency budget: [target end-to-end latency from event to dashboard] - Backfill policy: [how stale data is corrected] ## Ownership and review - Primary owner: [name] - Secondary: [name] - Quarterly review cadence: which KPIs to keep, retire, or redefine. ## Change log | Date | Change | Author | |---|---|---| | | | |

Price: Free
State: approved