The Favour Ledger: Making Unbilled Scope Visible in UK Service Businesses

In UK service businesses, the most expensive request is rarely the one that arrives as a formal tender. It is the short email that begins, ‘Can you just…’. Can you just add one more report? Can you just join a fifteen-minute call? Can you just tweak the wording before Friday? Individually, these requests look like reasonable client care. Collectively, they form a quiet tax on margin.

For managing directors and finance leads, the difficulty is that unbilled scope does not announce itself. It arrives disguised as flexibility, responsiveness or relationship management. By the time it appears in the numbers, it has usually been absorbed across several months and several people. The task for 2026 is not to become rigid with clients. It is to make the invisible visible, price it honestly, and introduce a repeatable way to say yes — on terms that work for both sides.

The request that does not look like work

Scope creep in an SME rarely resembles a formal change of direction. It tends to be incremental: an extra revision round, a supplementary data request, a colleague copied into a project who then needs briefing, a ‘quick’ review that becomes a redraft. Because each item is small, no one feels entitled to raise an invoice. Because no one raises an invoice, no one records the cost. Because no one records the cost, the pattern remains a matter of anecdote rather than management information.

This is particularly pronounced in professional services, marketing agencies, consultancies, IT support and design studios, where the boundary between service and extra service is often cultural rather than contractual. The client is not acting in bad faith. They are responding to the incentives in front of them: if extra work is absorbed without comment, it appears to be included.

Why scope creep stays invisible

There are three common reasons why UK SMEs under-record unbilled scope. First, timesheets are often completed at project level rather than task level, so an extra half-day disappears into a broader code. Second, client-facing staff may feel that logging a favour is an admission of poor commercial discipline. Third, the statement of work may be written in language that is deliberately broad — ‘ongoing support’, ‘reasonable assistance’, ‘ad hoc advice’ — which makes it difficult to argue that anything has fallen outside it.

The result is a gap between what the business sells and what it actually delivers. That gap is a finance and risk issue, not merely an operational annoyance. It affects gross margin, capacity planning, staff wellbeing and the accuracy of future quotes. If a team is routinely absorbing ten per cent more work than it prices, every new proposal built on historical delivery data is likely to be under-costed.

Put a price on the pattern, not the incident

Calculating the cost of scope creep does not require a complex model. It requires a consistent method and a willingness to look at the aggregate rather than the individual request. A useful starting formula is:

Unbilled hours × charge-out rate + direct costs + management time

Take a six-person consultancy with an average charge-out rate of £95 per hour. Suppose it receives twelve informal requests a month, each taking an average of one and a half hours to absorb. That is eighteen hours a month, or £1,710 in lost billing. Over a year, the figure is £20,520 before any allowance for the account manager’s time spent coordinating the extra work. For a business with a ten per cent net margin, replacing that revenue would require more than £200,000 of additional sales.

That comparison is the point. Scope creep is not simply a missed invoice. It is a margin leak that has to be refilled through new business. Once leaders see the annualised figure, the conversation shifts from ‘it is only a small favour’ to ‘which small favours are we choosing to fund, and why?’

A ledger simple enough to keep

The first practical step is a favour ledger: a lightweight record of unbilled requests, kept by the people who receive them. It should capture the date, client, request, time taken, and whether the work was inside or outside the agreed scope. A shared spreadsheet is sufficient. The aim is not surveillance; it is evidence.

Keep the categories narrow. For example: additional revisions, extra meetings, new deliverables, expedited turnaround, additional reporting, or support for a client’s internal process. After four to six weeks, patterns will emerge. One client may account for a disproportionate share. One type of request may be routine enough to include in future proposals at a higher price. Another may be a genuine exception that warrants a conversation.

The ledger also supports capacity planning. If the same two people are absorbing most of the unbilled work, the business has a hidden dependency risk as well as a margin problem.

Change requests without the chill

Boundary-setting often fails because it is introduced as a restriction rather than a process. A better approach is to make change requests normal, simple and mutually useful. The client gets clarity on cost and timing; the business gets protection against uncontrolled scope.

A practical change-request routine has three elements. First, a short written scope summary in every proposal or statement of work, listing what is included and what is not. Second, a standard response for out-of-scope requests: ‘We can do that. It falls outside the current scope, so I will send a short note with the additional fee and revised timing.’ Third, a threshold below which small items are absorbed deliberately, not accidentally. For example, a business might allow up to thirty minutes of incidental support per client per month, recorded in the ledger but not invoiced. That is a commercial choice, not a leak.

The language matters. ‘We can do that’ preserves the relationship. ‘It falls outside the current scope’ introduces the boundary. ‘I will send a short note with the additional fee and revised timing’ makes the next step predictable. The client is not being refused; they are being given a clear choice.

Boundaries that protect the relationship

Some SME leaders worry that change requests will damage goodwill. In practice, the greater risk is resentment. When a team quietly absorbs repeated extras, the quality of service can suffer, deadlines slip, and client-facing staff become weary. A transparent process is usually less damaging than a slow erosion of enthusiasm.

It also helps to review scope at natural milestones rather than waiting for a crisis. A short monthly check-in can ask three questions: what has changed since the last review, what has been absorbed outside scope, and what should be priced differently next time. This turns scope management into a routine part of client care rather than a confrontation.

The monthly discipline

For 2026, the aim is not to eliminate every favour. It is to ensure that favours are visible, deliberate and priced where appropriate. A monthly review of the favour ledger, conducted alongside the usual finance and operations meeting, can produce three outputs: a list of clients or request types to address, a set of proposal adjustments, and a small number of conversations to have before the next project begins.

Scope creep is rarely a story of one bad client. It is a story of many small decisions made without a system. A favour ledger, a clear scope summary and a standard change-request response are modest tools, but they give UK SME leaders something more valuable than rigidity: the ability to be generous on purpose rather than leaky by default.