Beyond the Organisational Boundary: Auditing How Suppliers Sit Inside Your Service Model

Open almost any service operating model diagram and you will find the same quiet fiction. The organisation sits in the middle, ringed by a dotted line. Outside the line, in smaller boxes, sit the outsourced provider, the managed service partner, the specialist subcontractor and the software vendor. The arrows point inward, as though value were delivered by the organisation and merely supplied by others.

In practice, many of the moments that decide whether a customer stays are owned outside that line. The telephony platform, the field engineering workforce, the payment reconciliation, the identity verification, the after-hours support: each may be delivered by a partner whose staff, incentives and measures are shaped by a contract rather than by the customer journey. Treating that as an external matter is not a governance gap. It is a design error.

The boundary is an accounting convenience

Organisational boundaries matter for accountability, employment and statutory reporting. They matter much less to the customer, who experiences one service and does not care who employs the person on the phone. The operating model should reflect the customer's view, which means drawing suppliers inside the system and describing them by the customer moments they own.

That shift in drawing style has consequences. Once a supplier appears inside the model, it acquires interfaces that need designing: shared measures, joint escalation, knowledge exchange, and governance that meets often enough to matter. The five-point audit below is a way of testing whether those interfaces exist in anything other than a contract schedule.

Point one: contract intent against operational reality

Start by reading the contract's service description and then watching the service being delivered. The distance between the two is the first finding.

Look for the assumptions embedded in the specification. A supplier contracted to answer calls within twenty seconds has been contracted for speed, not resolution, and will optimise accordingly. A supplier measured on cost per transaction will reduce transactions, which may be excellent and may simply displace work back into your own teams. Neither behaviour is a failure of good faith; both are the predictable result of what was written down.

Ask three questions. Which customer outcomes does this contract actually reward? Which of our internal targets does it unintentionally undermine? And what does the supplier believe we value most, in their own words? The third answer is usually the most informative and the least documented.

Point two: shared measures, not mirrored ones

Many organisations mirror their own internal metrics into supplier scorecards and assume alignment has been achieved. It rarely has. Mirrored measures create two parties optimising the same number in different ways, often at the seam between them.

A more robust approach is a small set of joint measures that neither party can move alone. End-to-end resolution time across the boundary. Repeat contact rate on cases the supplier handled. Handback quality, meaning the proportion of cases returned to your teams with sufficient context to act. Customer effort scores segmented by which party owned the moment.

Fewer measures, jointly owned, generally outperform long scorecards that are reviewed quarterly and argued over monthly. The test is simple: if a measure can be improved by the supplier while the customer's experience worsens, it belongs in a contract schedule, not in a governance pack.

Point three: escalation paths that survive contact

The escalation route is usually documented, tested at mobilisation and then quietly abandoned. Six months later the operational reality is a named individual on each side who knows each other's mobile numbers, which works well until one of them leaves.

Audit the escalation path by tracing three real incidents through it, including at least one that occurred out of hours. Note where it stalled, who was woken, and how long the customer waited while two organisations established which of them owned the problem. Then check whether the path has been exercised since the last contract change or personnel change.

Escalation that depends on goodwill between two managers is a single point of failure with a friendly face. The operating model should specify the route, the authority levels and the joint decision right for anything that crosses the boundary.

Point four: knowledge flow in both directions

Knowledge is where supplier interfaces most often fail quietly. Your teams hold customer history, policy exceptions and local intelligence. The supplier holds interaction data, failure patterns and the working knowledge of staff who handle your customers every day. Neither side sees the whole picture, and neither is usually paid to share.

Three practical checks. Can the supplier's frontline staff see the same customer record your own teams see, with the same permissions and the same caveats? Does product or policy change reach the supplier's staff before it reaches your customers, or after? And is there a scheduled mechanism for the supplier to tell you what they are seeing, in a form that reaches the people who can act on it?

Where the answer to any of these is no, the interface is relying on informal workarounds. Those workarounds are usually competent and usually invisible until the person inventing them moves on.

Point five: joint governance with teeth

Most supplier governance is a monthly meeting that reviews a pack nobody reads and escalates nothing. The test of joint governance is not its frequency but its decision rights.

A functioning forum should be able to change the measures, approve a change to the escalation route, commit resources on both sides and record decisions that are subsequently honoured. It should have a standing item on cross-boundary incidents and a mechanism for reviewing the contract's fit with the operating model as the service evolves. In the UK public sector, the expectations set out in the Cabinet Office's outsourcing guidance and the use of Crown Commercial Service frameworks provide a useful structure, but the discipline of decision-making is what makes the difference.

Where regulatory duties apply, the interface needs an additional layer. Under the FCA's Consumer Duty, for example, a firm cannot delegate responsibility for customer outcomes to an outsourcing partner; it can only delegate activity. The governance forum is where that distinction is made operational rather than theoretical.

Scoring and sequencing

Score each of the five interfaces on a simple three-point scale: designed, partially designed, or informal. The pattern of partial and informal scores tells you where to start. In most organisations, knowledge flow and escalation are the weakest, because they are the least contractual and the most dependent on individual relationships.

Sequence the work by customer impact rather than by contract value. A small specialist supplier owning a single high-stakes moment, such as identity verification or emergency response, can carry more customer risk than a large partner handling routine volume.

Redraw the diagram

The most useful outcome of this audit is a new diagram. Put the customer journey across the middle. Place every party that owns a moment on that journey, inside the same frame, with the interfaces between them named and owned. The dotted line around your organisation can stay, because it still matters for reporting. It should simply stop being mistaken for the edge of the service.