Change Request Clauses for UK Agency Contracts

Scope creep often starts politely: one extra round of amends, a new landing page, a last-minute stakeholder review or a request to repurpose campaign assets for another channel. For digital, creative and consulting agencies, the problem is rarely the first small favour. The problem is a project where extra work becomes expected, deadlines slide, margins disappear and nobody can agree what the original fee covered.

Common mistakes include describing deliverables too broadly, accepting changes over Slack without approval rules, and waiting until the final invoice to mention extra charges. A well-drafted change request clause in an agency contract gives you a clear process for approving new work, pricing it, adjusting timelines and pausing disputed extras before they become a relationship problem.

The goal is not to make your client experience difficult. It is to make commercial decisions visible at the right time, so your team can say yes to valuable changes without absorbing unlimited additional work.

A Practical Change Control Checklist for Agency Projects

A change request clause should tell both parties what counts as a change, who can approve it, how fees and timelines are adjusted, and what happens if the client asks for extra work without following the process.

For an agency, change control works best when it appears in both the contract and the day-to-day project workflow. Your agency master services agreement, statement of work, proposal or order form should set the legal rules. Your project management tools and client communications should then make those rules easy to follow.

A useful agency change control process usually deals with:

• Scope: what deliverables, assumptions, inclusions and exclusions were agreed at the start.
• Trigger events: what types of client requests or project events become a change request.
• Approval: who has authority to approve changes for the client and the agency.
• Price: whether extra work is charged at day rates, hourly rates, fixed fees or agreed estimates.
• Timing: how milestones, delivery dates, review periods and launch dates move when work changes.
• Dependencies: what happens if the client delays feedback, content, access, approvals or materials.
• Evidence: how a change is recorded, such as by written variation, email approval, signed change order or project management approval.
• Disputes: whether the agency can pause out-of-scope work until the parties agree on fees and timing.

For example, a branding agency might agree to create a logo suite, visual identity guidelines and two rounds of revisions. Halfway through, the client asks for packaging mock-ups, social media templates and a third board presentation. Those may be sensible additions, but they should not be treated as free unless the agency has decided to include them commercially.

A change request clause is different from a general variation clause in a service agreement. A standard variation clause often says the contract can only be changed in writing and signed by both parties. That is useful, but it can be too slow or formal for agency projects where clients make practical requests throughout delivery. Project change request terms bridge that gap by setting a clear operational process for day-to-day scope changes.

For UK agencies, the contract should also sit consistently with other legal obligations. If the project involves personal data, UK GDPR and the Data Protection Act 2018 may affect new data uses, new platforms or new processors introduced during a change. If the project creates copyright works, the change should be clear about who owns or can use the additional deliverables. If your client is a consumer-facing business, the Consumer Rights Act 2015 may influence their trading terms, marketing promises and website compliance, which can affect what they ask you to build.

What Your Clause Should Treat as a Change

Your clause should treat a request as a change whenever it alters the agreed deliverables, assumptions, timeline, working method, technical environment, content requirements or level of responsibility.

Agencies often lose margin because the contract only defines the final deliverable, not the assumptions behind it. A website build is not just a website build. The price may assume a certain number of page templates, integrations, content migrations, design concepts, browser support requirements, accessibility work, stakeholder reviews and testing cycles.

A scope creep clause should be specific enough to capture the kinds of changes your agency actually sees. Common examples include:

• extra deliverables, such as new pages, new ad variants, new reports, new design assets or additional strategy workshops;
• extra rounds of revisions beyond the agreed number;
• changes to signed-off work, including redesigning approved layouts, rewriting approved copy or rebuilding approved functionality;
• new stakeholders joining the project and requesting a different direction;
• changes to brand, product, pricing, messaging or business strategy after work has started;
• new technology requirements, platforms, integrations, plugins, analytics tools or hosting requirements;
• additional meetings, presentations, training sessions or internal approval support;
• faster turnaround, weekend work or reprioritisation to meet a new launch date;
• client delays that require rescheduling, rework or team remobilisation;
• extra compliance work, such as cookie consent adjustments, privacy wording, accessibility remediation or customer journey changes.

The clause should also say what is not a change. This protects clients and helps your team avoid overcharging for normal delivery work. For instance, reasonable corrections to agency errors, agreed minor amends within an included revision round and routine project management updates may stay within scope.

The best clause drafting starts with a tight statement of work. If the original scope is vague, the change request process has less to measure against. Instead of saying the agency will deliver a new website, list the agreed page types, features, content responsibilities, integrations, number of revision rounds and launch support. Instead of saying the agency will manage paid media, identify platforms, campaign types, reporting cadence, creative responsibilities, landing page responsibilities and budget assumptions.

A worked example shows the difference. A consulting agency agrees to produce a market entry report for a SaaS founder. The statement of work includes competitor analysis, customer interviews with up to 10 participants and a written report. The client later asks for investor pitch deck slides, additional customer interviews and a board presentation. Those additions are not bad requests, but they are separate outputs with separate time and commercial value. The change request clause lets the agency price them before starting.

Some changes are not client requests at all. They arise because the project reality is different from the agreed assumptions. A client may provide poor-quality data, incomplete brand assets or website access that does not support the planned build. A clause can state that a change request is required where client materials, systems or instructions are inaccurate, incomplete or inconsistent with the project assumptions.

For creative and digital work, intellectual property should not be left behind. If extra concepts, draft designs or unused routes are created as part of a changed scope, the contract should say whether the client receives rights only in final approved deliverables or also in unused materials. UK copyright generally arises automatically when original works are created, and ownership does not automatically transfer to the client just because the client paid an invoice. Clear licensing and assignment wording helps avoid confusion.

Approvals, Timelines and Evidence That Stop Scope Creep

Your contract should require an authorised written approval before the agency starts out-of-scope work, and it should allow delivery dates to move where the change affects effort, sequencing or dependencies.

Many agency disputes happen because the person requesting extra work is not the person who controls the budget. A marketing manager might approve extra creative options, while procurement later rejects the invoice. A founder might ask for weekend work, while the finance team expects the original fixed fee to stand. Your project change request terms should name the roles or individuals who can approve changes, or state that approvals must come from an authorised client representative identified in the statement of work.

Written approval does not always need to mean a wet ink signature. For practical agency projects, it can include email approval, e-signature, an approved change order, a statement of work amendment, or approval inside an agreed project management tool. The contract should make clear which methods count and which do not. If Slack, Teams or WhatsApp messages are part of your workflow, decide whether they can approve paid changes or whether they only flag a request for a formal approval step.

A simple change control process can work like this:

1. The client or agency identifies a potential change.
2. The agency confirms whether the request is outside the agreed scope.
3. The agency provides a change note or estimate setting out additional work, fees, timing impact and assumptions.
4. The authorised client representative approves the change in writing.
5. The agency schedules the work and updates the project plan.
6. The approved change becomes part of the contract or statement of work.

The timeline language matters as much as the fee language. If the client adds work, delays content or requests new approvals, the agency may need to move milestone dates. The clause should say that delivery dates are adjusted by a reasonable period, or by the period agreed in the approved change request. For larger projects, the agency may also need to adjust resource allocation, because the original team may no longer be available if the project drifts.

Client dependencies should be documented plainly. If you need brand files, product feeds, logins, data exports, legal sign-off, content or access to third-party suppliers, list them. Then state that delays or deficiencies in those inputs may affect delivery dates and may create additional charges. This is especially useful for website, CRM, automation and analytics projects, where delays are often caused by missing access or incomplete technical information.

Evidence is your best friend when emotions run high. Keep a clean record of the original scope, meeting notes, approval emails, version history, estimates and invoices. The contract can require both parties to use a nominated communication channel for approvals. That reduces the risk of crucial instructions being buried in informal messages.

Be careful with conduct that undermines your clause. If your contract says written approval is required, but your team repeatedly starts extra work after informal verbal requests, it becomes harder to rely on the process commercially. Train account managers and project leads to use consistent language, such as: That looks outside the current scope. We can price it as a change request and confirm the effect on timing before we start.

Where a project involves multiple stakeholders, consider a single client-side decision maker. This prevents a situation where the sales director approves one direction, the CEO later changes it, and the agency is expected to absorb the rework. A clear approval structure is not just legal protection. It makes the project easier for everyone to manage.

Fees, Payment and Disputed Extras

Your clause should say how extra work is priced, when it is invoiced, whether the agency can require upfront payment, and what happens if the client disputes whether the work was out of scope.

Charging for changes is easier when the pricing method is set before the project starts. Different agencies use different models, including project fees and agency retainer arrangements, and the contract should match your commercial reality. Options include:

• Hourly or daily rates: useful for uncertain or open-ended changes, especially consulting, development and technical support.
• Fixed fees: useful for defined additions, such as a new landing page, extra design template or additional workshop.
• Rate cards: useful where clients regularly request similar extras, such as creative resizing, copy variants or reporting packs.
• Retainer drawdown: useful where extra work is deducted from a monthly allocation, provided unused or excess time is clearly handled.
• Estimate plus approval: useful where discovery is needed before a precise quote can be given.

A change request clause should also address whether estimates are binding. If you provide an estimate, state whether the agency must seek further approval once time or cost is likely to exceed it. This prevents an argument where the client treats an estimate as a cap and the agency treats it as a guide.

Payment timing is another practical lever. For small changes, you might add the fee to the next invoice. For larger changes, you might require a deposit or full payment before work starts. For urgent work, you might charge premium rates if the client requests work outside normal business hours or asks you to deprioritise other scheduled work.

Disputed extras need careful drafting. A strong clause does not force a client to pay any invoice the agency labels as a change. It creates a fair mechanism for dealing with disagreement. For example, the contract can say the client must promptly identify the disputed amount and reasons, pay undisputed amounts on time, and the parties must discuss the disputed item with reference to the statement of work and approved change records.

The agency may also want the right to pause only the disputed out-of-scope work while continuing agreed in-scope work where practical. This is often better for the relationship than stopping the whole project. For serious non-payment, your wider service agreement should contain payment default, suspension and termination rights.

Late payment wording should be consistent with UK commercial practice. Many business-to-business contracts include interest and recovery cost wording aligned with the Late Payment of Commercial Debts (Interest) Act 1998, although the exact commercial position should be considered for your business. If you contract with very small businesses or individuals acting as consumers, additional fairness rules may apply under consumer protection law, so avoid one-sided terms that are difficult to justify.

Agencies should also think about purchase orders. Some clients, especially larger companies, refuse to pay invoices unless a purchase order was raised. Your change control wording can state that the client is responsible for raising any internal purchase order promptly and that failure to do so does not remove liability for properly approved changes. In practice, however, your account team should still collect the purchase order before starting substantial extra work.

There is a difference between a genuine extra and an agency mistake. If your developer builds the wrong feature because they misread the agreed specification, charging the client for correction will damage trust. If the client approved a feature and later wants it rebuilt for a different business reason, that is more likely to be a chargeable change. Your internal project notes should help make that distinction.

Data protection can also affect fees. If a change introduces a new analytics platform, CRM, email tool or AI service that processes personal data, the agency may need to review data processing terms, security measures or client instructions under UK GDPR. That compliance work should not be invisible. If it is outside the original scope, the change request should say so.

For intellectual property, extra fees and rights should align. If the client has not paid for a change, the contract can state that rights in the additional deliverables are not assigned or licensed for use until payment is received, subject to any agreed exceptions. For UK companies, make sure the contracting party is correctly named, particularly where the client trades under a brand name but is registered at Companies House under a different company name.

FAQs

What Is a Change Request Clause in an Agency Contract?

A change request clause is a contract term that sets the process for handling work outside the agreed scope. It usually covers how changes are requested, priced, approved, scheduled and documented.

Is a Scope Creep Clause the Same as a Variation Clause?

They overlap, but they are not always the same. A variation clause service agreement term usually controls formal contract amendments, while a scope creep or change control clause gives a practical process for project-level changes.

Can We Charge for Extra Work If the Client Approved It by Email?

Yes, if your contract allows email approval and the approval came from someone with authority. If the contract requires a signed change order, you should follow that process or update the contract to reflect how your agency actually works.

What If the Client Says the Extra Work Was Included?

Refer back to the statement of work, exclusions, assumptions, revision limits and approval records. If the work was not included, your clause should let you price it and pause that extra work until the client approves the change.

Should Change Requests Affect Deadlines?

Yes, where the change affects effort, sequencing, resources or dependencies. Your contract should say that approved changes may adjust milestones and launch dates, rather than leaving your team to deliver more work in the same time.

Key Takeaways

• A change request clause in an agency contract helps control scope creep without stopping clients from making useful project changes.
• The original statement of work should define deliverables, assumptions, exclusions, revision rounds, dependencies and client responsibilities.
• Project change request terms should cover approval authority, written evidence, pricing method, payment timing and timeline adjustments.
• Extra work should not start until the client has approved the fee and timing impact through the agreed agency change control process.
• Copyright, data protection, purchase orders and disputed invoices should be handled consistently with the wider service agreement.

If your agency needs clearer project change request terms, a tighter statement of work, client service agreement wording or IP and data protection clauses for digital projects, Sprintlaw UK's online legal team can help. Contact us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.