Turning franchise brand promises into service standards you can measure locally

A service standard should describe what the customer receives, how the operator measures delivery and what happens when the promise is missed. It should not be a slogan such as "excellent service" or an internal target presented as a limit on customer rights. For an England franchise, align the brand promise, local capacity, customer terms and evidence before opening.

What to take away

Write the promise in observable terms

Choose the few moments that matter to the proposition: response, booking, arrival, fulfilment, correction and complaint. For each, record the starting event, expected outcome, any stated time, permitted exception and evidence source. If staff cannot identify when the clock starts, the measure will not be consistent.

Separate three layers. A contractual promise is what the customer is told they will receive. An operational target helps the team manage work. A diagnostic measure, such as queue age or repeat contact, reveals causes. Do not quietly replace the customer promise with a more convenient internal average.

Check the words customers see

The CMA's guidance on fair customer contracts says terms and notices must be fair and transparent, and important wording should be prominent and understandable. It warns businesses not to use clauses that take away statutory protections when service is poor. Have a qualified lawyer check the actual contract, booking flow and site notices.

GOV.UK summarises implied service rights, including reasonable care and skill, and reasonable timing or charging where those matters were not agreed. An internal service-level number does not define all legal obligations. Treat it as an operating control and a trigger to investigate or recover service.

Design the evidence before setting a target

Use records generated by the work where possible: booking timestamp, acceptance, completion, correction, refund and complaint. Define exclusions openly and preserve the original record when a mistake is corrected. Sample the full journey, because an apparently fast completion can hide repeated contacts or missing information.

Combine measures rather than chasing one number. Look at timely completion, first-time accuracy, cancellations attributable to the operator, complaint themes and unresolved cases. Segment by site, service and day only where the volume supports a useful interpretation. Tiny samples should be read as cases, not converted into a confident league table.

Prepare service recovery

Give frontline staff a clear authority band: what they can correct immediately, what needs a manager and what requires legal, safety or data escalation. The customer should receive a plain explanation, the proposed remedy and a contact point. Internally, record the underlying failure and whether other customers may be affected.

The CMA's current unfair-commercial-practices guidance covers misleading actions, omissions and conduct that falls below professional diligence. Do not let a recovery script conceal a repeated failure or overstate what the operator has done.

Keep customer records proportionate

Complaint and quality evidence may include personal information. Limit access, define retention and avoid copying sensitive details into broad performance dashboards. The ICO's accountability guide links compliance to responsibility, contracts, policies and demonstrable measures.

Review a small sample each week after launch. Ask what the customer expected, where the process departed and whether the standard or workflow needs changing. Head office can compare methods across the network, but local teams should not be ranked from unlike volumes or undocumented exclusions. A useful standard makes the promise testable, the failure visible and the recovery owned.

Before you act

Common questions

What should a service standard describe?

A service standard should describe what the customer receives, how the operator measures delivery and what happens when the promise is missed. It should not be a slogan such as excellent service or an internal target presented as a limit on customer rights.

Why should an internal service-level number not be treated as defining all legal obligations?

GOV.UK summarises implied service rights, including reasonable care and skill, and reasonable timing or charging where those matters were not agreed. An internal service-level number does not define all legal obligations. Treat it as an operating control and a trigger to investigate or recover service.

How should customer records be handled when collecting complaint and quality evidence?

Complaint and quality evidence may include personal information. Limit access, define retention and avoid copying sensitive details into broad performance dashboards. The ICO's accountability guide links compliance to responsibility, contracts, policies and demonstrable measures.