SLA dashboards in Power BI: what to track and how to show breaches
A good SLA dashboard in Power BI shows response and resolution compliance by priority, highlights breaches and incidents close to breaching, and compares performance with last year. Lead with compliance percentages, then show open items at risk, ranked by time left. Use one consistent colour per priority, explain how the SLA is calculated, and pair the dashboard with alerts so teams act before a breach rather than after.
What should an SLA dashboard answer?
Service-level agreements set how quickly teams must respond to and resolve requests, usually by priority. An SLA dashboard should answer three questions: are we meeting our agreements, what is about to breach, and why did we miss when we did? Many dashboards only answer the last question, at month end, when it is too late to act.
Which measures should you track?
| Measure | Definition to agree |
|---|---|
| Response compliance | Share of items first responded to within target, by priority |
| Resolution compliance | Share of items resolved within target, by priority |
| Breaches | Count of items that missed response or resolution targets |
| At risk | Open items with less than a set time left before breach |
| Average and median times | Median is less distorted by a few very old items |
| Paused time | How on-hold time is treated, for example while waiting for the customer |
Write down whether the clock runs on business hours or calendar hours, and how pauses work. Two teams calculating SLA differently will produce a dashboard nobody trusts. If you use AI to draft these measures, see AI-assisted DAX for how to test them.
How should the dashboard be laid out?
Put compliance at the top, the at-risk list next, and breach analysis below. A team lead checking at midday should see in seconds whether anything needs moving.
How should you show breaches and priorities?
- One colour per priority: Use the same colour for critical, high, medium and low on every page.
- Red only for breaches: Reserve red for actual breaches so it keeps its meaning.
- Amber for at risk: Show items near breach in amber with time left.
- Target lines on charts: Draw the SLA target on every compliance chart.
- Text as well as colour: Label status in words so colour-blind readers are not left out.
In the Omantel case study, five urgency levels from critical to informational each had their own colour, and that colour meant the same urgency on every report. Consistency like this is what lets people read a page quickly. For broader colour advice, see choosing UI design colours.
What should you compare against?
Telecom and retail services often have strong seasonal patterns, so comparing with the same period last year is usually more honest.
How do you alert teams before a breach?
- Set data alerts on key tiles: Notify leads when compliance drops below target.
- Use Activator for item-level rules: Trigger an email or Teams message when an item has under an hour left.
- Send to the right person: Route alerts to the team that owns the item, not everyone.
- Avoid alert fatigue: Start with a few rules and review them monthly.
- Link to the item: Every alert should open the record or report page that needs action.
Built-in anomaly detection helps readers spot unusual days but does not send alerts; see anomaly detection in Power BI.
What did this look like for Omantel?
Omantel’s team leads needed to compare response and resolution times against their service agreements during the day, not only at month end. The reporting suite we built puts SLA compliance, closure rate and response and resolution times on the overview, each compared with last year, and splits incidents by enterprise, consumer and VIP customers. Leads can now see slipping targets while there is still time to act.
What mistakes should you avoid?
Hiding the SLA definition, mixing business and calendar hours, showing only averages, using red for everything below perfect, and building a dashboard with no link to action. Each makes the report less useful on the busy days when it matters most. Our article on Power BI for telecom covers the wider service-reporting suite.
Who should own the SLA dashboard?
Give the dashboard a named business owner, usually the head of service, and a technical owner in the BI team. The business owner agrees definitions and targets and decides when they change. The technical owner keeps the model, refreshes and alerts working. Review the dashboard with team leads every quarter: remove visuals nobody uses, check that alert rules still make sense and confirm that targets match the current contracts. When an SLA changes, update the measure, the target line and the written definition on the same day, so readers never see an old target next to new data.
How UIUX Studio helps
We design and build SLA and service dashboards in Power BI that teams use during the day, not only at month end. See our Technology Advisory service or read about Power BI report design.
Frequently asked questions
What is SLA compliance?
The share of items responded to or resolved within the agreed time.
Should response and resolution be separate?
Yes. They measure different things and often have different targets.
How do I show items about to breach?
A list of open items ranked by time left, with owner and priority.
Can Power BI send SLA alerts?
Yes, through data alerts and Activator rules.
Should I use averages or medians?
Show both; medians are less affected by a few very old items.