Small Extras, Large Leaks: Keeping Margin Under Control on UK Trade Projects

Small instructions rarely announce themselves as variations. They arrive as a moved socket, an extra coat of paint, a request to ‘just’ return on Saturday, or a client asking whether the team can ‘tidy up’ an area outside the quoted drawings. Each request sounds reasonable in isolation. Together they can consume the margin on an otherwise well-run job.

For UK trade firms, the commercial risk is rarely a single dramatic change order. It is the accumulation of informal extras that were never priced, never recorded and never approved. The client may believe the work was included; the contractor knows it was not. By the time the final account is prepared, the argument is harder to win because the evidence is thin.

This is not a case for refusing reasonable requests. It is a case for managing them properly.

Why small extras become a large problem

A thirty-minute favour is rarely just thirty minutes. It involves a return visit, a different sequence of work, a delay to another task, or a material order that was not in the original buy. Ten such favours can absorb a day. Twenty can absorb a week. On a tight programme, that lost time is not recovered; it is simply donated.

The margin damage is also cumulative in a less obvious way. Small extras train the client to expect flexibility without cost. When a larger change arrives, the contractor who suddenly raises a variation may appear unreasonable, even though the earlier extras were the real problem. The firm has taught the client the wrong lesson.

Goodwill matters. Repeat business matters. But goodwill bought by absorbing unpriced work is not a commercial strategy; it is a slow transfer of value from the trade firm to the client. The answer is not a confrontational approach. It is a clear, repeatable process that treats both sides fairly.

A verbal-to-written variation process

A practical process does not need to be bureaucratic. It needs to be consistent. For most UK trade firms, five steps are enough.

First, acknowledge the request. The client should feel heard, not managed. Second, restate the boundary: explain that the request sits outside the quoted scope, or that it needs checking against the drawings and specification. Third, give a provisional view of cost and time impact, even if the final figure needs a short calculation. Fourth, put the request into writing the same day. Fifth, record it in the variation log and do not start chargeable extra work until the client has confirmed.

Written confirmation can be an email. It does not need to be a formal contract amendment for every small item. What matters is that the record is clear: what is being added, why it is outside the original scope, what it will cost, how long it will take, and who has authorised it. If the client will not confirm in writing, that is useful information. It may be a sign that the request is not as settled as it first appeared.

Urgent safety work is the exception. If something must be made safe, do it. Then confirm the instruction and cost immediately afterwards. The exception should be narrow, not a convenient escape route.

A polite script for holding the line

Tone matters. The aim is to sound helpful, not defensive. A short script can carry most of the message:

‘Thanks for raising this. It is a sensible change, but it falls outside the priced scope. I can carry it out; I will send a short variation note today with the extra cost and time. Once you reply to confirm, we will book it in.’

If the client pushes back, keep the language factual:

‘I understand the urgency. To keep the accounts clean, I need an email confirming the additional cost and the revised date before the team starts. I can send a two-line note for you to reply to.’

This is not a refusal. It is an offer to proceed on clear terms. Most clients accept it because it removes ambiguity from both sides. The minority who object to paperwork are often the same clients who become difficult at final account. Better to discover that early.

The one-page variation log

A single sheet, whether paper or spreadsheet, should hold one row per instruction. Useful fields include the date, project, person who gave the instruction, description of the extra, reason for the change, labour and materials cost, time impact, agreed price, status, and the name and date of the person who authorised it. A final column can note whether the item has been included in an application for payment.

The log is not just an administrative record. It is a cashflow tool. Review it weekly and attach it to monthly applications. It shows the client exactly where extra costs have arisen and helps the firm invoice for work that might otherwise disappear into the general project history. It also protects the relationship, because the conversation is based on a shared record rather than memory or assumption.

What to do when the answer is no

Sometimes the client will not approve the extra cost. That is their right. The contractor then has to do only what is included in the agreed scope, or offer an alternative: defer the item, substitute a different solution, or ask the client to place it as a separate instruction. The important point is that the extra is not carried out as unpaid work without a deliberate commercial decision. A firm can choose to absorb a cost for a strategic reason, but it should be a decision, not a drift.

Making the process part of the contract

Even simple quotation terms should say that variations must be confirmed in writing before work starts. Where a formal contract is used, check how variations are to be instructed and priced. For smaller jobs, a clear line in the quotation is often enough; for larger projects, the variation procedure should be discussed at the outset so there are no surprises later.

P.F. Lynch & Co. takes the view that courtesy and commercial discipline are not opposites. The firm that records small extras properly is not being difficult; it is being fair to the client, fair to its team and fair to its own cashflow. Margin is rarely lost in one dramatic event. It leaks through a hundred small courtesies. A simple written process stops the leak.