Change Control Clauses for UK Fixed Fee Contracts

Fixed fee projects can look profitable at proposal stage and become painful once the client starts asking for extra meetings, extra revisions, new features or different deliverables. The most common mistakes are pricing the job tightly, leaving the scope too vague and treating client requests as harmless until the team has already spent days on unpaid work.

A clear change control clause helps you keep the project commercially viable without damaging the client relationship. It gives you a fair way to say, "yes, we can do that, but it needs a change request, an adjusted fee and a revised timeline."

For UK service providers, the aim is not to make every small tweak difficult. The aim is to separate included work from out-of-scope work, record approvals properly and avoid arguments about whether a fixed fee covered more than you actually priced.

Fixed Fee Scope Checklist for Service Providers

A fixed fee project agreement should make the original bargain clear enough that both sides can tell when a requested change falls outside it.

Before you rely on a change control clause, your contract needs a well-defined baseline. If the original statement of work is vague, it becomes much harder to prove that the new request is really additional work. A clause that says "changes must be agreed in writing" will not save the margin if the statement of work simply says "provide marketing support" or "build a website" with no detail.

For a fixed fee project agreement in the UK, the commercial schedule or statement of work should usually cover:

• Deliverables: What you are actually producing, such as a report, campaign plan, website, design file, software feature, workshop or implementation plan.
• Assumptions: What you relied on when pricing, such as client content being provided on time, access to systems, a limited number of stakeholders or a fixed number of product categories.
• Exclusions: What is not included, such as copywriting, user testing, third party integrations, stock imagery, paid advertising spend, legal review, hosting or travel.
• Client responsibilities: What the client must do, including providing information, reviewing drafts, appointing a single decision-maker and giving approvals within agreed timeframes.
• Rounds of review: How many revision rounds are included and what counts as a revision rather than a new direction.
• Project timeline: Key dates, dependencies and the effect of delays in client feedback or approvals.
• Fees and payment milestones: What the fixed fee covers, when invoices are issued and whether extra work is charged on a time and materials basis, a quoted fixed fee or another model.
• Acceptance criteria: How the client confirms that a deliverable is complete, and what happens if they do not respond.

This scope detail is what makes a scope creep contract clause in the UK practical. It gives your account manager or project lead a reference point when a client says, "can you just add one more version?" or "can we include another department in the rollout?"

For example, a brand agency may quote a fixed fee for a logo, brand guidelines and two rounds of amendments. If the client later asks for packaging mock-ups, social templates and a third stakeholder workshop, those requests are easier to classify as additional work if the original contract lists what is included and what is excluded.

The same applies to consultants, software developers, recruiters, training providers, architects, engineers and other project-based service businesses. A fixed fee is not the same as an unlimited service. Your documents should make that visible from the start.

How a Change Control Clause Protects Your Margin

A change control clause protects your margin by stopping extra work from becoming part of the fixed fee unless you have agreed the price, timing and scope change.

In practice, fixed fee projects often fail commercially because extra work slips in informally. A client asks for a small change on a call. A team member agrees because they want to be helpful. The change creates knock-on work for design, development, compliance or project management. A week later, the client sees it as part of the original project because no one said otherwise.

A well-drafted variation clause in a service agreement creates a pause point. It lets your team respond positively while still protecting the commercial deal. Instead of refusing the request outright, the contract gives you a process for assessing impact and asking for approval before work starts.

The clause should deal with four core points:

1. What counts as a change: Any addition, deletion, substitution, acceleration, rework, extra meeting, new stakeholder requirement or change in assumptions that affects the services, deliverables, fees or timeline.
2. Who can request it: The people authorised to submit or approve changes, so a junior user or separate department cannot accidentally bind the project.
3. How it is approved: A written change request, email approval, signed variation or approved project management ticket, depending on your business model.
4. What happens after approval: The fixed fee, milestones, delivery dates and responsibilities are updated to reflect the change.

The legal effect is simple: the original contract stays in place, but the agreed variation modifies it. Under English contract law, businesses can vary a contract if they agree to do so. Your clause sets the agreed method for that variation, which reduces arguments later about whether a casual conversation or Slack message changed the deal.

Many UK business contracts also include a "no oral variation" clause. This says that changes are only effective if made in writing and approved by authorised representatives. That can be useful, although courts may still look closely at the parties' conduct in some circumstances. For SMEs, the practical lesson is to keep your internal process consistent: do not rely on the clause in one dispute if your team regularly ignores it in daily project work.

The clause also protects the client. It gives them a written explanation of what the extra work will cost and whether it will delay other deliverables. That transparency can make the conversation feel less like an unexpected invoice and more like a normal commercial decision.

For example, a software studio may agree to build an onboarding flow for a fixed fee. During user testing, the client asks for a new analytics dashboard. The studio can issue a change request setting out the dashboard specification, extra development days, revised testing window and additional fee. The client can then decide whether to approve, defer or reject the extra feature.

What to Include in a Change Request Process

A good change request process should be simple enough for the project team to use and specific enough to create a reliable record if a dispute arises.

The best process depends on the size and speed of your projects. A creative studio may use email approvals for small changes. A SaaS implementation provider may use a ticketing system. A consultancy working with larger clients may use a formal change request form signed by both parties. The contract should match how your business actually operates.

A practical change request process contract clause, supported by clear clause drafting, should cover these elements:

• Trigger: A change request is required when the client asks for work outside the agreed scope, changes a deliverable, delays required input, adds stakeholders, changes priorities or asks for an accelerated timeline.
• Written request: The request must be recorded in writing, with enough detail for you to assess the impact.
• Impact assessment: You can assess the effect on fees, dates, resources, dependencies, third party costs, intellectual property, data protection and project risk.
• Quote or estimate: You can provide a fixed price, day rate estimate, hourly estimate, revised milestone fee or confirmation that the change cannot be accommodated within the current project.
• Approval authority: Only named contacts, directors, project sponsors or authorised representatives can approve the change.
• No obligation before approval: You do not have to start out-of-scope work until the change is approved and any required deposit or milestone payment is made.
• Effect on timeline: Delivery dates move to the extent reasonably required by the change or any delay in approval.
• Priority of documents: If there is inconsistency, the approved change request updates the relevant parts of the original statement of work.

For small projects, the process can be light-touch. A clause might say that an approved email is enough, provided it describes the change, extra fee and timeline effect. For larger projects, especially technology, engineering, training rollouts or multi-site implementation work, a formal change request form can reduce ambiguity.

A change request form often includes:

• Project name and original contract or statement of work reference.
• Description of the requested change.
• Reason for the change.
• Impact on deliverables and exclusions.
• Additional fees, rates or third party costs.
• Revised milestones or delivery dates.
• Any effect on support, warranties, licences or service levels.
• Approval signatures, email approvals or platform acceptance records.

Your contract should also say what happens when a change is urgent. Some businesses allow emergency work to proceed if an authorised client contact approves it by email, with the formal paperwork to follow. That can be sensible, but the wording should not leave a gap where urgent work becomes unpaid work.

Record keeping matters. If a client later disputes an invoice, your strongest evidence is usually the original scope, the written request, the approved quote and the delivery record. A messy chain of calls and informal messages makes it harder to show that the client accepted the extra fee.

Where the change involves personal data, intellectual property or regulated content, the process should also flag the legal impact. For example, adding a new CRM integration may require a review of UK GDPR roles, processor terms, security measures and data flows. Creating extra design assets may require clarity about when copyright transfers or what licence the client receives.

Common Scope Creep Triggers and Contract Fixes

Scope creep usually comes from predictable project moments, so your contract should address the triggers that repeatedly affect your type of work.

Many businesses only add a variation clause after a bad project. A better approach is to build the clause around the situations your team already recognises. These are some common examples.

Extra Revisions and New Creative Direction

Creative, branding, copywriting, web design and marketing projects often become unprofitable when revisions are not controlled. A client may provide consolidated feedback in round one, then introduce new decision-makers in round two, then ask for a completely different concept.

The contract fix is to define the number of included revision rounds and what a revision means. A revision should usually be an adjustment to an existing deliverable, not a new concept, new strategy or new set of source materials. The clause can say that additional revisions, changes in creative direction or feedback received after approval are chargeable changes.

Client Delays and Missing Information

Fixed fee projects depend on assumptions about client input. If the client takes three weeks to provide access, content, product data or stakeholder feedback, your team may need to reallocate resources and restart work later.

The contract fix is to state the client's responsibilities and the impact of delay. You might say that timelines are extended for client delays, that idle time or remobilisation may be chargeable, and that missed approval deadlines can move milestone dates. This is especially useful for consultants and implementation providers whose teams are booked weeks in advance.

Additional Stakeholders and Approval Layers

A project priced for one decision-maker can change significantly when legal, finance, IT, senior leadership or external advisers join halfway through. Extra stakeholders often mean extra meetings, rewritten requirements and slower decisions.

The contract fix is to identify the authorised client representative and approval process. If additional stakeholders require workshops, calls, rework or new materials, those items can trigger a change request. This keeps stakeholder management from silently absorbing your project budget.

New Features, Integrations or Technical Dependencies

Software, IT, automation and platform projects, especially under an IT services agreement, are particularly vulnerable to hidden technical work. A client may ask for a new integration, data migration, user role, API connection, analytics dashboard or security feature after the fixed fee has been agreed.

The contract fix is to list technical assumptions and exclusions in the statement of work. The change control clause should then capture new functionality, altered acceptance criteria, extra testing, third party platform issues and delays caused by client systems. It should also clarify whether third party licence fees or vendor costs are passed through to the client.

Regulatory, Data Protection or Brand Compliance Changes

A project can expand when the client asks you to meet requirements that were not part of the original scope. For example, a training provider may be asked to tailor materials for a regulated audience, or a digital agency may be asked to add cookie consent work, privacy notices or accessibility testing.

The contract fix is to treat new compliance requirements as potential variations unless they were expressly included. Where personal data is involved, UK GDPR and the Data Protection Act 2018 may require clear processor terms, security obligations and instructions. If those obligations expand during the project, the commercial terms should be revisited too.

Small Favours That Become a Pattern

One extra call or small file change may not justify a formal change request. The problem is repetition. Ten small favours can become a material drain on a fixed fee.

The contract fix is to create a sensible threshold. You might allow minor administrative adjustments at your discretion but reserve the right to require a change request once cumulative changes affect cost, timing or resources. This gives the project manager room to be commercially sensible without waiving your position.

UK businesses should also think about fairness and clarity in standard terms. If your customer is a business, the Unfair Contract Terms Act 1977 can affect certain exclusions and limitations, particularly where standard terms are used. If you sell services to consumers, the Consumer Rights Act 2015 may also be relevant. For most SME service providers, clear drafting, transparent pricing and a fair process are the safest foundations.

FAQs

Can a Fixed Fee Contract Still Charge for Extra Work?

Yes. A fixed fee normally covers the agreed scope, not every possible request connected to the project. Your contract should state that out-of-scope work requires approval under the change control process and may attract extra fees.

Is an Email Enough to Approve a Change Request?

An email can be enough if your contract allows changes to be approved by email and the email clearly records the change, fee, timing impact and authorised approver. For higher value or higher risk changes, a signed variation or formal change request is usually safer.

What if the Client Says the Extra Work Was Implied?

The answer depends on the contract wording, the project context and the parties' conduct. A detailed scope, exclusions list and change control clause make it easier to show that the work was not included in the fixed fee.

Should Small Changes Always Go Through a Formal Process?

Not always. Many providers allow minor changes at their discretion to keep the relationship moving. The contract should still let you require a formal change request where small changes become repeated, costly or likely to affect the timeline.

Can We Pause Work Until a Change Is Approved?

Yes, if the contract gives you that right. A useful clause says you are not required to start or continue out-of-scope work until the client approves the change and pays any agreed upfront amount or milestone invoice.

Key Takeaways

• A change control clause for a fixed fee contract works best when the original scope, assumptions, exclusions and client responsibilities are clearly written.
• The clause should define out-of-scope work and require written approval before extra fees, revised milestones or new deliverables become part of the project.
• A practical change request process should record the requested change, impact on price, timeline effect, authorised approval and any legal issues such as IP or data protection.
• Common scope creep triggers include extra revisions, client delays, new stakeholders, technical changes, compliance requirements and repeated small favours.
• Your internal project habits should match the contract, so your team consistently flags changes before doing unpaid work.

If fixed fee projects are putting pressure on your margins, Sprintlaw can help with your service agreement, statement of work, variation wording and change request process. Contact us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.