Managing contract variations without starting from scratch

Why variations go wrong – and why a clause fixes it

Almost every freelance project or small business contract changes after it is signed. A client asks for an extra revision, a supplier misses a deadline, or a new deliverable appears. Without a clear way to record the change, you are left with two bad options: ignore it and hope, or tear up the original agreement and start again. Neither is good. A simple variation clause lets both parties agree changes in writing while keeping the original agreement intact and enforceable. The original signed contract remains the foundation; the variation is just a short, dated add-on.

What a good variation clause actually says

A variation clause does not need to be long. It needs to be clear. At minimum, it should cover the following:

• In writing: changes are only valid if recorded in a written document signed by both parties or their authorised representatives.
• No oral variations: a phone call or corridor chat does not change the contract, even if everyone agrees at the time.
• Specific details: the variation must identify the original contract, the date, and exactly what is changing.
• Impact: state the effect on fees, expenses, deadlines, deliverables, and any other affected terms.
• Everything else stays the same: all other terms of the original agreement continue in full force.
• Authority: name who can sign off variations, so a junior team member cannot accidentally commit the business.

If your original contract has no variation clause, you can still agree changes, but do it carefully. Put the change in a separate written agreement, reference the original, and get both parties to sign. For larger or higher-risk changes, take legal advice.

How to handle a change request step by step

When a change comes in, treat it as a process, not a favour. A repeatable routine keeps things calm and professional.

• Log the request: note the date, who asked, and what they want. Even a quick email to yourself creates a paper trail.
• Assess the impact: work out the extra time, cost, resources, and any effect on other deadlines. Do not guess; check.
• Send a written variation proposal: set out the change, the price, the new timeline, and any conditions. Give the client a clear yes/no decision.
• Get written acceptance: a signed variation document is best. If your clause allows email, keep the acceptance email safe and unambiguous.
• Attach it to the original: file the variation with the contract. If there are several, create a variation schedule that lists them in date order.
• Update your project plan and invoices: do not forget to change the payment schedule, milestones, or purchase order if needed.

A simple subject line such as “Variation to contract dated 1 March 2025 – extra training day” helps everyone find it later.

Keeping the original agreement intact

The whole point of a variation clause is that you do not rewrite the original contract. Rewriting creates risk. You might accidentally change a liability cap, an intellectual property term, a notice period, or a payment condition that was carefully negotiated. Instead, use a short variation document that says: “The parties agree to vary the contract dated [date] as follows…” Then set out the change and add: “All other terms remain unchanged.”

Keep a master copy of the original signed contract, plus every variation, in one folder. Use version numbers and dates. If a dispute ever arises, you can show exactly what was agreed and when. This is far stronger than a scattered email chain or a verbal promise. It also makes handovers easier if you bring in an accountant, a solicitor, or a new team member.

Common traps for freelancers and small businesses

Most variation problems are not caused by bad faith. They come from small, understandable shortcuts. Watch out for these:

• The verbal yes: “That’s fine, just do it” on a call is not a variation if your clause requires writing.
• Assuming email always counts: check your clause. It may require a signature, a specific form, or approval from a named person.
• Letting small changes pile up: five tiny favours can add up to a week of unpaid work. Record each one as it happens.
• Forgetting the knock-on effects: a new deliverable may change the deadline, the expense budget, or the VAT treatment.
• Ignoring authority: make sure the person approving the change can actually bind their business.
• Using “we’ll sort it later”: later rarely comes. A two-minute variation note now saves hours of argument later.

If you spot a trap after the event, fix it with a retrospective written variation. Both parties can sign to confirm what was agreed. It is not ideal, but it is much better than nothing.

Make variations routine, not a confrontation

Clients and suppliers usually appreciate a clear process. It shows you are organised and fair. At the start of a project, explain how changes will be handled. Agree who can request a variation, how it will be priced, and how long approval will take. If you build a small “change budget” into the project, everyone knows that extra work has a cost. Review variations at your regular project check-ins. Keep the tone collaborative: “We can absolutely do that. Here is the variation note so we both have it in writing.”

With a simple variation clause and a consistent routine, you can say yes to sensible changes without losing control of the contract. The original agreement stays intact, the paperwork stays manageable, and you get paid for the work you actually do.