Promises With Capacity: Auditing Whether Your Service Charter Can Be Kept

Service charters are often treated as a communications asset. They appear on websites, in onboarding packs and in tender responses. Yet a published response time is an operational commitment. It tells customers what the organisation has decided its processes, rota and decision rights can reliably deliver. When those elements do not align, the charter becomes a source of avoidable failure demand, complaints and internal friction.

The task is not to rewrite the charter until it sounds better. It is to find out where the promise and the operating reality diverge, and then make a deliberate choice about which one should move.

Begin with a promise inventory

Start by sampling the promises rather than reviewing every statement. A workable sample includes high-volume commitments, high-risk commitments and promises that are rarely invoked but carry significant consequences. For each one, record the exact wording, the channel through which it is published, any conditions attached and the internal owner. This matters because vague wording often hides a more precise operational expectation. A promise to respond within two working days may mean acknowledgement, a substantive answer or a resolution plan, depending on who is reading it.

Classify each promise by type: response, resolution, availability, outcome or conduct. Response promises depend on triage and queue management. Resolution promises depend on end-to-end process capability. Availability promises depend on rota cover and channel design. Outcome promises depend on factors that may sit outside the service team. Conduct promises depend on training, supervision and escalation. The classification quickly shows which parts of the operation are being asked to carry the most weight.

Trace each promise to a delivery chain

A promise is only credible if there is a delivery chain behind it. For each sampled commitment, identify the process steps that must occur, the owner accountable for the end-to-end result, the capacity required and the decision rights needed at each stage. Capacity is not simply headcount. It is available hours after meetings, training, absence and peak demand are accounted for. Decision rights matter because a promise that depends on a manager who is unavailable for two days is not a two-day promise in practice.

Test the chain against evidence rather than intention. Use historical performance, queue data, rota records, absence patterns and demand variation. Ask whether the process is designed to meet the promise and whether it actually does so under normal pressure. A promise that holds only in a quiet month is not a service standard. It is a best-case scenario.

Where possible, walk one or two real cases through the chain. This often reveals handoffs, system delays or approval points that no process map shows. It also exposes where teams are quietly absorbing demand through informal workarounds. Those workarounds may be keeping the promise alive, but they are also a sign that the formal operation is not carrying it.

Separate definition gaps from delivery gaps

Not every gap is a failure of effort. Some are definition gaps. The promise says five days, the process measures five days from a different starting point, and the customer counts from the moment they pressed send. Some are measurement gaps. The team reports against a median while the customer experiences the tail. Some are authority gaps. The promise requires a decision that the front line cannot make. Others are genuine capacity or process gaps.

This distinction is important because the remedy differs. A definition gap needs clearer wording and a single measurement rule. A measurement gap needs reporting that reflects the customer experience, not just the average. An authority gap needs delegated decision rights or a faster escalation route. A capacity gap needs resourcing, demand management or a revised promise. Treating all four as a performance problem will usually lead to pressure on the front line without changing the outcome.

Decide whether to fix, revise or route

Once the gap is located, make an explicit decision. There are three credible options. The first is to fix the operation: change the process, add capacity, redesign the rota, delegate authority or improve the handoff. This is the right choice where the promise is important to customers, commercially necessary and achievable at reasonable cost. The second is to revise the promise: narrow the commitment, clarify the conditions, change the measurement point or distinguish between acknowledgement and resolution. This is not an admission of failure. It is an honest alignment of what the organisation can sustain. The third is to introduce an exception route where the standard promise cannot be met for a defined group of cases.

Use clear tests for the decision. Consider customer harm, regulatory exposure, contractual obligation, volume, cost to serve and the credibility of the published statement. A promise that is rarely invoked but legally significant should not be quietly revised. A promise that is widely published but operationally unachievable should not be left in place to generate repeated failure.

Make the exception route explicit

The exception route is often where service charters fail quietly. Teams create informal exemptions, customers are told different things by different advisers, and no one can see the pattern. A controlled exception route should state who is eligible, who can approve the exception, what the customer will be told, how long the exception lasts and how it is logged. It should also have a review point. Exceptions are not a substitute for fixing the operation. They are a pressure valve that must be measured.

If exceptions are rising, that is evidence. It may show that demand has changed, that capacity has eroded or that the promise was never realistic. Review exception logs alongside complaints, missed commitments and repeat contacts. These are the signals that tell you whether the charter is still a fair description of the service.

Keep the audit connected to operations

A service charter audit should not become a branding review. Its output is not a new tone of voice. It is a set of decisions about process, capacity, authority and measurement, with named owners and dates. Assign a promise owner for each commitment, link the review to operational improvement planning and revisit the sample at a sensible interval. When the operation changes, the promise should change with it, or the gap will simply reopen in a different place.

The test is straightforward. Can the organisation show, with evidence, how each published promise is delivered, by whom and with what capacity? Where it cannot, the charter is describing an aspiration rather than a service. Closing that gap is operational work, and it deserves operational governance.