Blog · Board and management reporting
An IT operations dashboard gives business managers a checked view of incident backlog, resolution times and support costs. Work through a monthly service review, including the ticket reconciliation and the limits of cost per resolution.
An IT operations dashboard compares incident backlog, resolution time and support costs so business managers can review service performance. Start with a ticket export and the costs assigned to the same period. The report should explain where work is accumulating and who owns the next action.
This dashboard serves an IT service manager, a finance partner and the departments using support. It answers practical questions: Is unresolved work growing? Which queue misses its agreed target? Is spending changing because demand changed, or because the work became harder to complete?
Keep incidents separate from routine requests unless the review explicitly includes both. An incident records a service problem; a request may be planned work with a different completion target. Mixing them can make a shift toward simpler requests look like faster incident resolution. The ticketing dashboard covers the wider queue view.
Write down the clock definition. Atlassian's incident metrics guide explains that MTTR can refer to different measures, including resolution and recovery. A column called resolution hours is more useful when its start, stop and pause rules are explicit. Covirage is not affiliated with Atlassian.
Take an opening snapshot, a closing snapshot and the period's incident changes. Keep one incident identifier throughout. Add the financial export only after agreeing which costs belong in the review.
| File | Minimum fields | Why it matters |
|---|---|---|
| Incident records | Incident ID, queue, priority, created date, resolved date, status | Counts work entering and leaving the review |
| Service measurement | Incident ID, measured resolution hours, agreed limit, eligible flag | Rebuilds time and target measures |
| Backlog snapshots | Snapshot date, incident ID, queue, status | Proves opening and closing unresolved work |
| Cost export | Period, cost center, expense amount, allocation category | Defines the spending boundary |
| Budget | Period, cost center, approved support budget | Supplies the comparable target |
For this example, resolution time means business hours from incident creation to resolution, after documented allowable pauses. This is elapsed service time, not the support employee's labor hours. Resolution and financial reporting both cover September 2026.
The service owner approves the target rules. NIST's service-level agreement definition describes responsibilities, expected performance and reporting requirements. Use the actual agreement for your business; do not impose a generic target simply because it fits a chart.
An illustrative US company reports incidents by the department receiving support. In this example there are no reopened cases, cancellations or transfers between queues.
Closing backlog = Opening backlog + New incidents − Resolved incidents
| Department | Opening backlog | New incidents | Resolved incidents | Closing backlog |
|---|---|---|---|---|
| Finance | 10 | 30 | 32 | 8 |
| Sales | 8 | 40 | 36 | 12 |
| Operations | 6 | 20 | 18 | 8 |
| Total | 24 | 90 | 86 | 28 |
The company bridge is 24 + 90 − 86 = 28 incidents. Closing backlog grew by 28 − 24 = 4 incidents. Finance reduced unresolved work, while Sales and Operations added to it.
Confirm that the closing snapshot contains those incident IDs. A matching total alone can hide a missing incident offset by a duplicate. In a real review, show reopened cases and canceled cases as explicit additions and removals. Queue transfers must cancel at company level.
The same resolved incidents supply the next table. Every resolved incident is eligible for the agreed target in this example. Hours and target-met flags come from the incident records, grouped by department.
Mean resolution hours = Total measured hours for resolved incidents / Resolved incidents
Target met = Eligible resolved incidents within target / Eligible resolved incidents × 100
| Department | Resolved incidents | Total resolution hours | Mean hours | Within target | Target met |
|---|---|---|---|---|---|
| Finance | 32 | 96 | 3.00 | 28 | 87.50% |
| Sales | 36 | 180 | 5.00 | 27 | 75.00% |
| Operations | 18 | 72 | 4.00 | 15 | 83.33% |
| Total | 86 | 348 | 4.05 | 70 | 81.40% |
Total resolution time is 96 + 180 + 72 = 348 hours. The company mean is 348 / 86 = 4.05 hours, rounded to two decimals. Target performance is (28 + 27 + 15) / 86 × 100 = 81.40%, also rounded to two decimals. Calculate from the underlying totals before rounding.
Do not average the departmental percentages. The incident counts provide the weights. Also inspect unresolved work separately: resolved incidents can become quicker while difficult open cases continue to age. A business review needs both perspectives.
Finance supplies the following costs assigned to incident support for the same month. These are period expenses, not costs individually traced to the resolved incidents.
| Department | Assigned support cost (USD) | Budget (USD) | Cost less budget (USD) | Cost / resolved incident (USD) |
|---|---|---|---|---|
| Finance | 6,400 | 6,000 | 400 | 200.00 |
| Sales | 9,000 | 8,500 | 500 | 250.00 |
| Operations | 3,600 | 4,000 | −400 | 200.00 |
| Total | 19,000 | 18,500 | 500 | 220.93 |
Total spending is 6,400 + 9,000 + 3,600 = $19,000. The variance is 19,000 − 18,500 = $500 above budget. Company cost per resolved incident is 19,000 / 86 = $220.93, rounded to cents. A cost dashboard can explain the expense categories behind that total.
Sales has the largest closing backlog, the longest mean resolution time and the highest period cost per resolution in these records. That makes it a review priority. It does not establish that the team is inefficient: incident complexity, priority mix and the work still open can explain the pattern.
The service manager should inspect Sales incidents by category and age, then agree an action with the department owner. That could mean clarifying intake information or reviewing a recurring business process issue. Finance should verify cost allocations before treating the spending variance as an operational problem.
Publish a refresh date and retain the reviewed export. Check blank queue labels, duplicate incident IDs and missing resolution timestamps before comparing periods; the data quality dashboard describes that wider discipline.
For presentation choices, see the tool-specific operations dashboard guide. A sales and operations planning dashboard addresses a separate demand-and-supply review, so keep that commercial process outside this incident report.
Bring an incident export, backlog snapshots and the matching support cost file or Google Sheet. Covirage maps the columns; its tools compute and check the service and cost measures, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.
See Covirage for self-service analytics for the business-file approach.
Include opening backlog, new incidents, resolved incidents, closing backlog, resolution time, service-target attainment and support spending. Separate priority groups and show missing records. Each measure should have an owner, a defined reporting period and a path back to the supplied export.
Add the measured resolution hours for incidents resolved during the reporting period, then divide by the number of those incidents. Define whether the clock uses business or calendar hours and how approved pauses work. Keep unresolved incidents out of that denominator and report their age separately.
It is a useful period comparison when the cost boundary and incident mix stay consistent. It does not show the precise cost of each incident. Costs may support unresolved work or other services, so read the ratio alongside backlog, complexity and service-target performance.