The Fifteen Patterns Behind Every Service

I remember the moment the grammar became visible.

I was reviewing a set of service designs from across a large public sector organisation: a planning enforcement team, a safeguarding unit, a benefits fraud reporting function, and an environmental health service. Four teams, four directorates, four histories. No shared technology, no shared management, and as far as anyone knew, no shared anything.

I was looking for duplication. What I found was something more interesting. At the structural level, three of the four services began with an identical interaction. Someone contacted the organisation to report something. The contact was received, validated, classified, and routed to the appropriate team for handling. The content was entirely different. The logic was identical.

That interaction has a name. It is called Capture and Triage. And once you have named it, you see it everywhere.

This article introduces fifteen patterns that, in my experience and in the cross-government pattern work published by MOJ, DWP and Defra in 2025, underpin the service estate of any large public sector organisation. This is not an exhaustive taxonomy: organisations working in specific domains may identify additional patterns relevant to their context. But these fifteen recur most reliably, across the widest range of domains, in the organisations I have worked with and studied. Taken together, they constitute a grammar: a set of structural units from which services are built, whether or not the people building them know it.

Rather than treating each pattern in isolation, this article groups them into five natural families. The family a pattern belongs to reflects its function in the service lifecycle, not its domain or its frequency of use.

The intake patterns: how services receive people and requests

Every service begins with an intake moment, the point at which a person or organisation first enters into a relationship with the service. Three patterns govern this moment.

Register and Express Interest describes the interaction in which someone signals intent before a formal process begins. A citizen registers interest in a social housing allocation. A contractor registers on a pre-approved supplier list. A patient registers with a GP practice. The interaction is lightweight by design: its purpose is to establish a record of intent and initiate the relationship, not to gather all the information that will eventually be needed.

Apply and Submit is the pattern that follows when a formal request must be made. An application for a benefit, a licence, a permit, or a place in a scheme. The interaction involves structured information gathering, evidence submission, and the creation of a formal record that a downstream process can act on. The complexity of the application varies enormously by domain. The structural logic does not.

Capture and Triage is the pattern for inbound contacts that are not applications: reports, complaints, referrals, notifications. Someone reports a pothole. Someone refers a vulnerable adult. Someone notifies the organisation of a change in circumstance. The contact arrives, its nature is established, and it is directed to the right place. In high-volume service environments, this is often the highest-frequency pattern in the estate, and the one whose failure, a contact that is lost, misclassified, or routed to the wrong team, has the most immediate consequence for the person who made it.

The processing patterns: how services evaluate and determine outcomes

Once a service has received a request or contact, it must do something with it. Two patterns govern the core processing work.

Check and Assess is the pattern in which the organisation evaluates a person's circumstances, a property's condition, a risk level, or an application against defined criteria. A social worker assesses the needs of a vulnerable adult. A planning officer assesses a development application against policy. An environmental health inspector assesses a food premises against hygiene standards. The pattern has a consistent internal structure: evidence gathering, structured evaluation, documented outcome, and a handoff to a decision process.

Get a Decision is the pattern in which a formal outcome is produced and communicated: an approval, a refusal, an offer, an award, or an enforcement action. Where Check and Assess is the work of evaluation, Get a Decision is the act of commitment. The organisation formally concludes its assessment, authorises its outcome, and communicates it to the person it affects. In regulated public services, this pattern carries the highest governance burden of any in the taxonomy: the decision must be documented, authorised at the appropriate level, and capable of surviving challenge, appeal, or judicial review. It is the moment at which the organisation stands behind what it has concluded.

The coordination patterns: how services manage operational mechanics

Running beneath every service interaction is a set of coordination activities that manage the operational mechanics of delivery rather than its substantive content: arranging time, exchanging information, exchanging money. Three patterns govern these.

Book and Schedule is the pattern that coordinates the allocation of a specific time, operative, resource, or appointment. A repair is booked. An inspection is scheduled. A medical appointment is arranged. A planning site visit is confirmed. This pattern appears in almost every service that involves a physical or real-time element, and its failure mode is almost always the same: the appointment system and the capacity system are not reconciled, and the booking does not reflect what can actually be delivered.

Notify and Communicate is the pattern through which the organisation informs people of status changes, decisions, appointments, or required actions. It is the most cross-cutting pattern in the taxonomy: every other pattern triggers it at some point. An acknowledgement of a registration. A decision letter. A reminder about an upcoming appointment. A notification that further information is required. The structural logic is consistent even when the content and channel vary entirely. The failure mode is also consistent: notification sent via the wrong channel, at the wrong time, or containing insufficient information for the recipient to act on it.

Pay and Account is the pattern that manages financial transactions between the organisation and the people or entities it serves. A charge is calculated. A payment is collected or made. An account is maintained. A debt is recorded. In public services, this pattern sits at the intersection of service delivery and financial governance, and its failure modes, incorrect charging, missed payments, unreconciled accounts, tend to have consequences that extend well beyond the service itself.

The sustained management patterns: how services maintain ongoing obligations

Many public services are not transactional. They involve ongoing relationships, recurring obligations, and continuous oversight that may span months or years. Three patterns govern this sustained dimension of service delivery.

Manage a Case is the pattern that provides a structured, ongoing management process for a relationship, contract, or regulatory matter that unfolds over time. A complex benefits case. A planning enforcement matter. A long-term contract with a supplier. The pattern involves regular review, documented progress, escalation triggers, and a clear thread of accountability from opening to closure. Without it, ongoing matters drift: nobody owns them, nothing moves, and the organisation discovers the gap only when the person affected complains loudly enough to be noticed.

Inspect and Record is the pattern through which the organisation conducts a structured assessment of a physical space, asset, or piece of work: a property inspection, an operational audit, a quality check on completed work. The pattern produces a documented record that serves as both evidence and accountability. In regulated environments, it is often the primary mechanism through which compliance is established and maintained, and the quality of the record is as important as the quality of the inspection.

Comply and Certify is the pattern that plans, executes, records, and certifies statutory compliance obligations. Gas safety checks. Fire risk assessments. Food hygiene inspections. Electrical safety testing. This pattern is characterised by fixed periodicity, mandatory documentation, and legal consequence if the obligation is not met on time. It is one of the most process-critical patterns in any organisation with a significant physical estate or regulated operational environment, and one of the patterns where the gap between the process design and the actual practice tends to be widest.

The resolution patterns: how services conclude, transfer, or escalate

Every service interaction reaches a point of resolution: a successful conclusion, a referral to a different service, a formal escalation, or a transfer to a new relationship. Four patterns govern these endpoints.

Refer and Support is the pattern through which the organisation connects a person with specialist internal or external support: financial advice, welfare assistance, health services, legal support, safeguarding intervention. It is triggered when the presenting need exceeds what the originating service can address, and its quality is determined almost entirely by the clarity of the handoff: what information transfers, to whom, in what form, and with what follow-up to confirm the person has been reached.

Enforce and Escalate is the pattern that initiates and manages formal action when an obligation has not been met: a debt escalation, a planning enforcement notice, a licensing breach. This pattern is governed by legal process, documented carefully, and subject to review. Its failure mode is escalation without adequate prior intervention, which tends to produce outcomes that are costly for the organisation and damaging for the person it is dealing with.

Handover and Onboard is the pattern that manages the formal transfer of a property, contract, or relationship from one party or state to another. A new tenant moves in. A contract transfers to a new supplier. A case moves between teams at a programme boundary. The pattern is defined by a documented point of transfer, stated conditions, and an onboarding process that establishes the new relationship on a clear footing from the start.

Close and Complete is the pattern that formally concludes a case, transaction, or relationship: confirming all actions are complete, all parties are informed, all records are updated, and the service interaction is properly ended. This pattern is more consistently neglected than any other in the taxonomy. Organisations invest heavily in intake and processing. They rarely have a systematic approach to closure, which means cases drift, records remain open long after the underlying matter has resolved, and resources are consumed by interactions that have functionally ended but have never been formally concluded.

The grammar beneath the services

Fifteen patterns. Five families. In every large public sector organisation I have worked with or studied, these structural units appear, in various combinations, across virtually every service in the estate.

What differs between services is the domain: the data, the roles, the business rules, the legal framework, the user population. What recurs is the structural logic: the intake moment, the assessment and decision, the operational coordination, the management of ongoing obligations, and the resolution of the interaction.

A planning application is Register, Apply, Check and Assess, Get a Decision, Notify and Communicate, with Book and Schedule for the site visit and Enforce and Escalate as a branch if planning conditions are subsequently breached. A social care referral is Capture and Triage, Check and Assess, Get a Decision, Refer and Support, Manage a Case. A supplier contract is Apply, Check and Assess, Get a Decision, Handover and Onboard, Inspect and Record, Pay and Account, Close and Complete.

The services are different. The grammar is the same.

The next article in this series examines how these patterns combine in practice: the logic of pattern chaining, the transition conditions between patterns, and what it means for programme planning and system design when you can see not just individual patterns but the sequences that services are built from.