Ioan Davies All articles
Operations

The Short Letter That Saves the Job: A Scope-Creep Playbook for Small UK Consultancies

Ioan Davies
The Short Letter That Saves the Job: A Scope-Creep Playbook for Small UK Consultancies

Photo: 国务院港澳事务办公室, Public domain, via Wikimedia Commons

Most scope creep does not arrive with a bang. It turns up as a friendly email: 'While you are in there, could you just...' Three weeks later, the job has doubled, the fee has not moved, and everyone is being terribly polite about a problem nobody wants to name.

For small UK consultancies, the answer is not a forty-page contract drafted by a City lawyer. It is a short letter of engagement that both sides can actually read, understand and find again when the brief starts to wobble. Two pages is usually enough. Sometimes one and a half.

Why a short letter beats a long contract

A long contract is often a substitute for a conversation. A short letter forces the useful conversation to happen early: what are we doing, what are we not doing, when will it be done, what does it cost, and what happens if the ground shifts?

Under the law of England and Wales, a binding contract generally needs offer, acceptance, consideration, an intention to create legal relations and enough certainty about the terms. You do not need Latin or a leather-bound folder. You need a clear record of what was agreed. A letter of engagement does that job neatly, and it gives both parties a sensible reference point if memories diverge.

It also protects the relationship. Clients rarely set out to exploit a consultancy. They simply forget that a 'quick tweak' has a cost. A short agreement lets you say no, or yes with a revised fee, without it feeling personal.

The clauses that earn their keep

1. Parties and purpose

Name the client, name your business, and say what the letter is for. Keep it human: 'This letter sets out the basis on which we will provide the services described below.' If the client is a company, get the legal entity name right. If there are two decision-makers, name them both.

2. Scope and deliverables

This is where most disputes are born. Write down what you will deliver, in plain nouns and verbs. 'A written pricing review of up to ten product lines, delivered as a PDF and a one-hour call' is useful. 'Support with pricing' is not.

Then add an exclusions line. It feels negative; it is actually kind. 'This does not include implementation, staff training, ongoing monitoring or work on overseas markets.' Clients appreciate knowing where the edges are.

3. Timetable and client responsibilities

State your assumed start date, key milestones and what you need from the client. Access to systems, a nominated contact, feedback within five working days, accurate data: these are not small details. They are the difference between a project that flows and one that stalls while you send polite chasers.

4. Fees and expenses

Be direct. Say whether the fee is fixed, day-rate or capped, what it includes, when invoices are issued and what payment terms apply. If expenses are recoverable, say what counts and whether pre-approval is needed. A simple line such as 'Fees are exclusive of VAT and travel agreed in advance' prevents a surprising invoice later.

5. Change control

This is the quiet gatekeeper. A short clause can say that any change to scope, timetable or deliverables will be agreed in writing before work begins, and that fees and dates may be adjusted accordingly. It does not need to be aggressive. Something like: 'If the brief changes, we will confirm the impact on fees and timing by email before proceeding.'

That single paragraph turns the awkward 'just one more thing' email into a normal business conversation.

6. Intellectual property, confidentiality and termination

Keep these proportionate. Say who owns what, how confidential information will be handled, and how either side can end the arrangement. A notice period and a clear statement about payment for work already done will save a lot of strain if the relationship goes off course.

7. Liability and governing law

You are not trying to write a insurance policy. A sensible line confirming the governing law, usually England and Wales or Scotland depending on your setup, and a cap on liability where appropriate, is enough for many small engagements. If the project is high-value or high-risk, that is the point to take proper legal advice.

A template you can adapt this week

Use this as a skeleton, not a straitjacket:

Keep it to two pages. Use headings. Avoid clauses copied from a template you do not understand. If a sentence would embarrass you in a client meeting, rewrite it.

When the client says it is only a small change

Do not argue about whether it is small. Ask what outcome the change is meant to achieve, then confirm the impact in writing. 'Happy to look at that. It adds roughly a day of analysis and moves the delivery date by three working days. I will send a short revised note.' That is calm, commercial and fair.

A two-page agreement will not eliminate every difficult conversation. It will make those conversations shorter, clearer and less personal. For a small consultancy, that is usually the point.

Keep it human

A letter of engagement is not a wall between you and the client. It is a shared map. Write it in the same voice you use in meetings, send it early, and keep a signed copy somewhere you can find it. Then get on with the work.

If you already have a long contract, do not panic. Add a one-page scope and change-control summary to the front. If you have nothing, start with a letter. Your future self, halfway through a 'quick extra', will thank you.

All Articles

Related Articles

Small Print, Big Opportunity: Getting Your Foot in the Council Door

Small Print, Big Opportunity: Getting Your Foot in the Council Door

The Cheapest Fix for a Wobbly Website: Five Customer Calls

The Cheapest Fix for a Wobbly Website: Five Customer Calls

Seven Quiet Hours: The Admin Audit You Can Finish Before Friday

Seven Quiet Hours: The Admin Audit You Can Finish Before Friday