0. Cover and period
Operator brand or contracted slice, the calendar month or incident window, and the local busy-hour definition. The cover names the reviewer who froze the dictionary.
What’s in a pack
The folder we bind for a service-quality review
This page is the contents list. If you already know you need a monthly cadence, start with the flagship pack. If you are heading into a named enterprise review, use the SLA evidence commission instead.
1. KPI dictionary
Each figure: source extract, formula, aggregation, exclusions. Retainability is not silently relabelled as drop-call rate. Probe samples sit on a separate page when they appear at all.
2. Time series
Daily or busy-hour lines for the agreed set — typically availability, retainability, latency, packet loss or congestion. Axes use the same units as the SLA schedule.
3. Exception list
Worst cells, cabinets or exchanges, printed with traffic where we have it. A hilltop sector with forty calls is not presented as the equal of a four-thousand-call neighbour.
4. Missing-file appendix
Dates and network elements that did not report. If more than a fifth of contracted elements are silent, the narrative refuses a month-on-month comparison for that KPI.
5. Two-page narrative
Written for the review chair: what moved, what the files cannot support, and which planned engineering you told us about. No vendor-console captures.