The supplier has presented its monthly figures. Tickets have been handled, service measures look acceptable and the meeting finishes on time. Afterwards, the leadership team is still unsure what needs attention or whether last month's commitments were completed.
A service review should leave a clearer picture than that.
The detailed report has a purpose, but directors do not need to work through every operational measure. They need to understand where the service is falling short, what the consequences are and what needs to happen next.
#Agree What Deserves Leadership Attention
Start with the expectations already agreed for the service. An exception is a meaningful departure from those expectations, or a change that could affect the business. It is not simply an unusual number on a chart.
A recurring interruption to order processing may deserve attention even when overall availability looks acceptable. A minor issue that the support team has resolved within its remit may not.
Agree which matters should reach the leadership review, using business impact, recurrence and unresolved exposure as guides. Keep urgent escalation separate: a serious incident should not wait for the next scheduled meeting.
Retain access to the underlying measures. Reporting by exception should reduce unnecessary detail, not conceal an unfavourable trend.
#Ask for a Short, Usable Summary
A one-page summary is a useful starting point, supported by detail where needed. For each significant issue, ask for:
- The service affected and the consequence for the business.
- The evidence available, including its date and any limitations.
- The recommended next step and any decision required.
- The named action owner and proposed completion date.
The request should be specific. “Discuss resilience” is difficult to act on. “Approve time for a recovery exercise before the next review” gives the meeting a clear question to resolve.
If no leadership decision is needed, say so. Some items require visibility and continued monitoring rather than another approval.
#Distinguish Assurance From Assumption
Ask what supports the conclusion, not just whether the status is green. A completed task, a supplier statement and a tested outcome provide different kinds of evidence.
For a hypothetical example, a report might say that a recovery exercise was successful. The useful follow-up is which service was tested, when, against what agreed expectation, and whether anything remained unresolved. That gives directors a basis for judging what the result actually demonstrates.
Where information is missing, show the gap plainly. Record who will obtain it and by when. Avoid replacing an unknown position with a reassuring colour simply because no incident has been reported.
The review should make uncertainty manageable, rather than pretend it has disappeared.
#Leave With a Record That Can Be Used
Finish each significant item by recording the decision or next action. Include any accepted limitation and the date it will be reconsidered. If a decision is deferred, note what information is needed to bring it back.
Give each action one named owner, even when several people will contribute. Agree what evidence will demonstrate completion. “Investigate recurring access failures” is a starting task; it is not evidence that the underlying problem has been addressed.
Circulate a short record afterwards so that both the business and provider can correct misunderstandings before work proceeds.
#Begin the Next Review With Previous Commitments
Revisit outstanding actions before introducing new material. Check completed items against the agreed evidence, and make overdue work visible with a reason and a revised plan.
A repeatedly moved date deserves discussion. The answer may be additional capacity, a dependency that needs resolving or an unrealistic original commitment. Simply changing the date does not explain the problem.
A useful review is not a search for reasons to replace the provider. It is a regular opportunity to turn service information into understood risks, explicit decisions and work that is followed through.