The Words We Work By: A Service Lexicon for UK Client Teams
Photo: Stephen Sweeney, CC BY-SA 2.0, via Wikimedia Commons
Service work is full of words that appear settled until a deadline is missed. A client marks a request as urgent. A supplier treats same-day as a target. An approval arrives from someone who may not hold the budget. None of these gaps are unusual, and none are solved by email volume alone. They are solved by agreeing, in advance, what the words require. A one-page service lexicon gives UK client teams a shared reference point before pressure arrives.
A working document, not a legal instrument
The purpose of the lexicon is operational clarity. It does not replace the contract, the statement of work or the service schedule. Where a definition conflicts with those documents, the contract prevails. The lexicon simply translates contractual language into daily behaviour: who acknowledges a request, within what time, using which record, and with what authority.
That distinction matters. Teams can spend weeks turning a glossary into a drafting project, complete with clauses and caveats. The result is often too long to use. A better approach is a single page, six to ten terms, and plain examples drawn from live client work. The document should be short enough to read at a kickoff meeting and precise enough to settle a disagreement later.
The one-page layout
A practical layout uses five columns: term, working definition, response expectation, evidence or trigger, and exception owner. The evidence column is often overlooked, but it is what makes the glossary usable. If urgent means a call to the duty manager, the team needs to know where that call is logged. If approval means a named authority, the team needs to know where that approval is recorded.
The figures below are illustrative. They should be set against the service actually sold, not copied without thought.
| Term | Working definition | Response expectation | Evidence or trigger |
|---|---|---|---|
| Urgent | An issue that stops the client receiving a live service, or exposes people, data or property to immediate harm. | Acknowledged within 30 minutes during service hours; a named owner assigned within one hour. | Ticket marked urgent, plus a call to the duty manager. |
| Same-day | Work completed, or a substantive update issued, before 17:00 on the same UK business day, provided the request arrives before 14:00. | Requests after 14:00 move to the next business day unless the urgent criteria apply. | Timestamped acknowledgement and update in the shared log. |
| Approval | Written acceptance from the named client authority listed in the service schedule. | No change work proceeds until approval is recorded in the shared log. | Email or portal entry from the named approver. |
| Out-of-hours | Any time outside 08:00 to 18:00 Monday to Friday, excluding UK bank holidays. | Answered within 60 minutes only where out-of-hours cover is purchased; otherwise next business day. | Call routed to the on-call rota and logged. |
| Response | Acknowledgement of a request, with a named owner and next step. It is not resolution. | Within the time band agreed for the request type. | Ticket note naming the owner. |
| Resolution | Service restored, or work completed to the agreed standard. | According to priority and service schedule. | Closure note with supporting evidence. |
The distinction between response and resolution is worth preserving. Many client frustrations come from a team treating acknowledgement as progress, or from a client treating a response target as a completion target. The glossary should make clear which promise is being made.
The kickoff routine
Agreeing the lexicon takes less time than repairing the misunderstanding it prevents. A short routine of 30 to 45 minutes is usually enough.
- Send the draft lexicon to the client two working days before the kickoff. Ask them to mark any term that means something different in their organisation.
- Walk through each term in the meeting. Ask for one real example from the client and one from the delivery team. If the examples do not fit the definition, revise the definition.
- Confirm the named approver or approvers for change work. Confirm who can authorise urgent action outside normal governance.
- Confirm whether out-of-hours cover is included, excluded or purchased separately. Record the answer against the term.
- Add a version number and date to the page. Store it with the service schedule and the client contact list.
- Send a one-page summary to the client within one working day. Note any points that require contract confirmation.
The routine should not become a negotiation of the whole contract. If a definition would change the commercial agreement, flag it for the appropriate owner and leave the lexicon in draft until that point is resolved.
Exceptions and escalation
No glossary removes every exception. The difference is that exceptions become visible. A client may ask for same-day treatment after the 14:00 cut-off. A delivery team may need urgent cover when the formal cover has not been purchased. The lexicon should include a short exception route: request in writing, named owner, reason, expiry, and approval.
Exceptions should be logged separately from the glossary. If the same exception appears three times in a quarter, it is no longer an exception. It is a signal that the definition or the service level needs review. Quietly stretching the meaning of urgent to include client anxiety is not a service improvement; it is a route to burnout and disputed invoices.
Review after an incident
After a significant incident, review the lexicon within five working days. Keep the review short and factual. Ask three questions. Which term was interpreted differently by the two sides? Was the response expectation realistic for the service sold? Did the escalation route work in practice?
Update the page if needed, change the version number, and tell the client what changed. The review is not a blame exercise and should not become a legal drafting project. Its purpose is to make the next incident less ambiguous. A glossary that is never revised after an incident is usually a glossary that is not being used.
Keeping the lexicon in use
A one-page lexicon only earns its place if it appears in daily work. Use its terms in tickets, status reports, service reviews and onboarding packs. Give it to new starters and account managers. Review it quarterly, when the contract changes, and after any major incident. Keep it to one page. The value lies in shared use, not in storage.
