How it is run
A good QBR is built from the three monthly service reports for the quarter, not from scratch. A typical agenda:
- What changed in the client's business this quarter
- Results: tickets, SLA, backups, patching and security, with trends
- Issues and how they were fixed
- Risks: unsupported devices, accounts without MFA, expiring warranties
- Roadmap: recommended projects with cost and timing
- Decisions and next steps, with owners and dates
The audience is usually the client's owner or manager, so the language should be business, not technical.
Worked example
| Month | Tickets | Responded within SLA | Attainment |
|---|---|---|---|
| July | 52 | 48 | 92% |
| August | 47 | 45 | 96% |
| September | 41 | 40 | 98% |
| Quarter | 140 | 133 | 95% |
Tickets fell from 52 to 41 a month, about 21%, after the old laptops were replaced. That is the story for the meeting: the project paid off, and the next one on the roadmap is the same fix for the remaining desktops.
Common mistakes
- Reading the monthly reports aloud. Show trends and what they mean.
- No decisions. A QBR that ends without agreed next steps is a status update.
- Turning it into a sales pitch. Tie every recommendation to a risk or result from the quarter.
- No follow-up. Start each QBR with what was agreed last time.
Related terms
- SLA (service level agreement): A service level agreement (SLA) is the part of a service contract that sets measurable targets, such as how quickly the provider will respond to and resolve an issue.
- Month over month (MoM): Month over month (MoM) compares a figure for one month with the same figure for the month before, as a dollar change and a percentage change.
Further reading
- An MSP QBR checklist
- What to put in a monthly IT service report
- Monthly Service Report: the nvisin tool built around this