The Unbilled Hour: Counting Management Time in UK Service Contracts

When a UK organisation compares service providers, the conversation usually starts with fees, scope and service levels. Those measures matter. They are also incomplete. Every service relationship consumes a second currency: management attention. That cost is rarely invoiced, rarely budgeted and frequently discovered only when senior people compare diaries and find that a supposedly routine contract has quietly become a standing item across the year.

The shorthand is the meeting tax. The phrase is useful because it captures something familiar: the recurring review that needs preparation, the approval that waits for a single signatory, the report that is rebuilt in a different format, the escalation that travels further up the organisation than it should. But the issue is broader than meetings. It is the governance load of the relationship — the time, latency and seniority required to keep the service working and to assure the board that it is working.

Why the invoice is an incomplete cost model

A service fee tells the buyer what the provider charges. It does not tell the buyer what the provider costs the buyer to manage. Those are different figures. The first appears in the contract and the management accounts. The second is spread across calendars, inboxes, approval queues and rework cycles. It competes directly with strategic work, customer attention and other governance priorities.

For UK leadership teams, this matters most at the point of renewal, tender or budget setting. A supplier that appears competitive on price may require disproportionate oversight. A supplier with a higher fee may absorb less management time and leave decision-makers free for other work. Neither outcome is automatically preferable. The point is that the comparison should include both sides of the cost equation.

The governance load also has a timing dimension. A contract can consume modest total hours while creating significant delay. If every variation requires a committee, or every reporting query takes a week to resolve, the cost is not only the meeting itself. It is the decision that waits, the project that slips and the management attention that remains tied up while the issue is routed.

Four places the load accumulates

Most governance load gathers in four predictable places. The first is the recurring forum: the monthly service review, the quarterly performance meeting, the pre-meeting, the minutes, the action log. Each may be justified. Together they can become a parallel management system.

The second is the decision bottleneck. Approvals may be concentrated in one role, or delegated authority may be unclear. When the contract does not specify who can decide what, routine choices migrate upwards. Senior time is then spent on matters that should have been settled at service level.

The third is reporting rework. Different templates, incompatible definitions and reconciliation cycles create work that adds no assurance. If the buyer and provider spend the first half of every review agreeing what the numbers mean, the reporting is not doing its job.

The fourth is escalation drag. An issue that cannot be resolved at the point of service will travel through account management and into senior governance. Some escalation is healthy. Persistent escalation of predictable issues is a design flaw. It consumes attention and signals that the operating model is not absorbing normal variation.

A practical audit: the engagement ledger

A useful audit does not need to become a time-sheet regime. It needs a proportionate sample and a consistent method. Select one significant service relationship. Over four weeks, or one quarter if the data is readily available, ask the contract owner, finance and service managers to categorise their time against five headings: meetings, approvals, reporting, escalations and assurance requests.

Use calendar data and ticket records where possible. Recollection alone will undercount the small interruptions and overcount the formal meetings. Then apply an internal cost rate by role — salary plus overhead, or the organisation’s standard charge-out rate. Aggregate by role, not by individual. The output should be two figures: an annualised estimate of management hours and cost, and an indication of decision latency, such as the average number of days from request to decision.

The ledger is not an audit of people. It is an audit of contract design. If a routine approval takes ten days because authority sits with one director, the problem is the decision architecture, not the director’s diligence.

Reading the result

There is no universal threshold at which governance load becomes excessive. A complex, high-risk service will legitimately require more oversight than a simple one. The useful comparisons are relative: against the fee, against alternative delivery models and against the trend over time.

Ask three questions. Is the load stable, rising or falling? Is it concentrated in a small number of roles? And is the work value-adding or corrective? Genuine oversight — challenge, assurance, strategic direction — has a cost worth paying. Rework — correcting avoidable errors, reconciling incompatible reports, chasing decisions that should have been delegated — is a symptom of poor service design.

The final test is whether a different model could reduce the load without reducing assurance. If the answer is yes, the current relationship is carrying avoidable cost. That cost may not appear in the contract, but it is real.

Putting the load into 2027 budget and supplier decisions

As UK organisations prepare 2027 budgets, governance load should be visible in the business case. For renewals and tenders, ask providers to describe their standard governance: meeting cadence, decision rights, reporting format, escalation routes and change control. Require those commitments to be scheduled in the contract rather than left to good intentions.

Include management time in the total cost of ownership. Allocate it explicitly in the budget, even if the allocation is approximate. If it is not allocated, it will be absorbed invisibly by the functions that can least afford it.

Add a governance-load indicator to the supplier scorecard: hours per month, decision days, rework rate and escalation frequency. Review it alongside service performance. A provider that consumes more senior attention is not necessarily failing, but the board should know why. A one-page governance-load statement, presented with the usual performance report, would give non-executives a clearer view of what the relationship actually demands.

The discipline of counting

The meeting tax is not a argument against governance. It is an argument for designing governance deliberately. Count the unbilled hour, compare it with the assurance it buys and ask whether the same assurance could be obtained with less drag. In 2027 budget papers, the question should be not only what the service costs, but what governing it costs. The second figure belongs in the board pack.