Client Delay Clauses in UK Service Contracts

A client misses the deadline for feedback, sends incomplete files, or gives you access to the wrong system. Your team is ready, but the project stalls and the delivery date starts to look unrealistic.

The usual mistakes are agreeing to fixed dates without naming client dependencies, absorbing extra project management time, and apologising for a delay that the client caused. A clear client delay clause in your contract helps you protect the timeline, recover extra costs, and avoid being blamed for missed milestones.

For service providers, the aim is not to be difficult. The aim is to make the project workable. With the right project delay contract terms, you can decide when dates move, when fees change, when work pauses, and when it is reasonable to walk away.

Client Dependencies Need to Be Built Into the Project Plan

A client dependency clause turns vague cooperation into specific client obligations that your timetable can rely on.

Most service projects depend on the client doing something before you can do your job. A brand designer may need existing style guides, product photos and stakeholder feedback. A software developer may need access to code repositories, test users and technical documentation. A consultant may need staff interviews, management accounts or decisions from the leadership team.

If those inputs are not clearly listed, the client may see them as minor admin tasks rather than critical project requirements.

That creates a risky mismatch: you are treating the input as a condition of delivery, while the client thinks the deadline is still fixed regardless of their own delay.

A practical contract should connect the project plan to the client's responsibilities. It should identify the materials, approvals, access, information and decisions the client must provide, as well as when they are due.

Common client dependencies include:

• Content and materials: copy, images, brand assets, product descriptions, policies, reports, data sets or design references.
• Technical access: logins, admin permissions, API keys, hosting details, analytics access, staging environments or software licences.
• Approvals: sign-off on wireframes, scripts, prototypes, budgets, campaigns, legal wording or creative concepts.
• Feedback: consolidated comments, issue lists, acceptance testing results or amendment requests.
• People availability: access to decision-makers, subject matter experts, staff for workshops, or client-side project managers.
• Third party inputs: supplier files, regulator approvals, payment provider details, platform approvals or materials from another agency.
• Data protection inputs: instructions about personal data processing, security requirements, retention periods and UK GDPR contact details where the project involves personal data.

The more specific you are, the easier it is to manage expectations. A clause saying the client must provide assistance is weaker than a clause saying the client must provide website copy, product images and written feedback within five business days of request.

The client dependency clause should also say the client is responsible for the accuracy, completeness and legality of the materials they provide. For example, if a client supplies images without the right copyright permissions, or customer data without a clear lawful basis under the UK GDPR and Data Protection Act 2018, your contract should not leave you carrying the legal or commercial risk for that input.

For founder-led and SME service businesses, this is where a statement of work becomes useful. The main services agreement can set the legal rules, while each statement of work lists the project-specific inputs, milestones and assumptions. That lets you reuse your legal terms across projects without rewriting the whole contract each time.

A sensible dependency checklist for each new project is:

1. What must the client give you before work can start?
2. What must the client provide before each milestone?
3. Who on the client side can approve deliverables?
4. How quickly must the client respond to requests?
5. What happens if the client gives unclear, incomplete or contradictory instructions?
6. Which dates are fixed, and which dates depend on client cooperation?
7. Will extra work, rework or waiting time be chargeable?

Once these answers are in the contract, delays become easier to discuss. You can point to the agreed process rather than negotiating from scratch during a stressful project.

What a Client Delay Clause Should Say

A good services agreement delay clause should state that delivery dates extend when the client is late, incomplete or unavailable.

The clause does not need to be aggressive. It should be clear and commercially fair. It should recognise that the supplier cannot be responsible for delays caused by the client's acts, omissions, late instructions, incomplete materials, delayed approvals or changes in scope.

The key protection is causation. If the client caused the delay, your liability for missing the affected deadline should be excluded or reduced. The project timetable should also move by a reasonable period, rather than leaving your team expected to compress the remaining work into fewer days.

A well-drafted client caused delay clause usually deals with four points:

• Trigger: what counts as a client delay, such as late materials, missed meetings, delayed approval, unavailable systems or unclear instructions.
• Notice: how you tell the client the project is delayed and what you need from them.
• Time extension: how milestone dates and final delivery dates are adjusted.
• Cost impact: when extra time, remobilisation, waiting time or rework can be charged.

For example, your agreement might say that if the client does not provide required information by the due date, any affected deadlines will be extended by at least the period of delay plus any reasonable time needed to reschedule personnel or restart work. That matters because a two-day delay from a client can create more than a two-day impact if your team has already been booked onto another project.

Some contracts make the mistake of saying deadlines will only extend by the exact number of delayed days. That can be too narrow for service businesses with scheduled teams, contractors or studio capacity. A better approach allows a reasonable extension that reflects the actual project impact.

Notice requirements also matter. If your contract says you must notify the client of a delay, build an internal habit of doing it quickly and in writing. A short email can be enough if the contract allows email notices for project communications. It should record the missing item, why it affects delivery, what date was missed, and what the revised date will be or when you will confirm it.

Your clause should also deal with partial or poor-quality inputs. A client might provide copy on time, but it may be unusable because it is incomplete, off-brand, legally risky or inconsistent with the brief. In that case, the delay should not be treated as solved just because something was sent. The contract can say that materials are only treated as provided when they are complete, accurate and suitable for the agreed purpose.

For regulated, clinical or public-facing projects, approvals can be especially sensitive. A marketing agency may need client confirmation that financial promotions, environmental claims or health claims have been approved internally. An IT services supplier may need the client to confirm user acceptance testing outcomes. A training provider may need the client to approve course content before rollout. If the client delays those approvals, the project timetable should move accordingly.

A client delay clause should sit alongside, not replace, your wider project documents. The service agreement, proposal, scope of work and project plan should all tell the same story. If your proposal promises a launch by a fixed date but your contract says all dates depend on timely client inputs, the documents should state which one takes priority if there is a conflict.

How to Protect Fees When Client Inputs Are Late

Fee protection should make clear that client delay can lead to extra charges, revised instalments, or payment becoming due even if the project is paused.

Many suppliers lose money on delayed projects because they only protect time, not fees. The deadline moves, but the team still spends extra hours chasing, rescheduling, rechecking old work and holding availability. If your agreement is silent, the client may expect all of that to be included in the original fixed fee.

A fixed fee is usually priced on assumptions. Those assumptions might include timely feedback, one round of revisions, access by a certain date, or a launch window that matches your team's availability. If the client changes those assumptions through delay, your fees should be able to change too.

Common fee protections include:

• Variation fees: extra charges for additional work, rework or scope changes caused by late or changed client instructions.
• Waiting time fees: charges where your personnel or contractors are kept available but cannot progress the project.
• Remobilisation fees: a fee for restarting work after a project has been paused due to client delay.
• Extended project management fees: charges for extra meetings, chasing, status reports and replanning caused by delay.
• Instalment protection: payment milestones that remain due on dates or on completion of supplier work, even if the client has delayed later stages.
• Storage or hosting fees: ongoing costs for holding files, running environments, maintaining subscriptions or preserving project materials during a pause.

There is a big difference between charging for genuine delay impacts and using fees as a penalty. Under English contract law, clauses that impose excessive sums for breach can be challenged if they are out of proportion to the legitimate business interest being protected. Your fees should be framed as reasonable charges for actual costs, lost capacity, rescheduling or additional services.

The payment structure should also match the project risk. For longer projects, stage payments are usually safer than a large final payment on completion. If completion depends on client approval, a final-payment-only structure gives the client too much control over your cash flow. A better structure may involve an upfront fee, milestone payments and a final amount payable when deliverables are made available for review, rather than only when the client gets around to approving them.

Late payment rules can also support your position in business-to-business contracts. The Late Payment of Commercial Debts (Interest) Act 1998 allows businesses to claim statutory interest and fixed compensation in many commercial debt situations, unless the contract has a substantial alternative remedy. Your payment clause can still set out your own invoicing dates, interest, suspension rights and recovery costs, provided the terms are properly drafted.

Where you deal with consumers or micro-businesses, fairness becomes especially relevant. The Consumer Rights Act 2015 applies to consumer contracts and controls unfair terms. Even in SME relationships, clear and balanced wording reduces disputes. Avoid hidden charges and vague statements that anything late will attract any fee you choose. Say what types of costs can be charged, when they arise, and how they will be calculated.

Your contract should also cover cancellation or indefinite pause. A client may disappear for several weeks and then expect the project to restart immediately. A pause clause can say that, after a defined period of client inactivity, you may invoice for work completed, charge reasonable pause or remobilisation fees, revise the timetable, and require a new start date based on availability.

For creative, design, technology and consulting businesses, intellectual property clauses also connect to fees. You may want IP ownership to transfer only after full payment. If a client delays feedback but still wants to use draft work, designs, copy, strategy documents or code, your agreement should state what rights they have before payment and final approval.

Practical Workflow for Managing Client-Caused Delay

A contract works best when your project workflow creates the evidence needed to rely on it.

Even a strong client delay clause can become hard to use if the facts are messy. If requests were made by phone, deadlines were unclear, and feedback was scattered across messages, it may be difficult to show that the client caused the delay. A simple workflow helps your team keep the project on track and preserve your contractual position.

Start with a kickoff email that confirms the key dependencies. This should be a practical project note listing what you need, who is responsible, and the due dates. When a due date is approaching, send a reminder that connects the input to the timeline. Rather than saying please send the files, say the files are needed by Friday to keep the prototype review on schedule.

If the client misses the deadline, send a delay notice promptly. The notice should be polite but specific. It should identify the missing item, the original due date, the affected milestone, and the likely consequence. If you need to revise the timetable later once you know the impact, say that.

A practical delay notice might cover:

• the client input that was due;
• the date it was due;
• the part of the project that cannot progress without it;
• the contract clause or project assumption being relied on;
• the revised deadline for the client to provide the input;
• whether fees, availability or milestone dates may change; and
• what will happen if the input remains outstanding.

Keep your tone calm. The best notices sound like project management, not a threat. They create a written record while giving the client a clear way to get the project moving again.

For repeated delays, escalation is useful. A single missed date may only need a reminder. Repeated missed dates may justify a formal pause, revised fees or a senior-level meeting. Your contract can set out a staged process: reminder, delay notice, pause notice, revised quotation, and termination if the delay continues.

Suspension rights can be powerful for service providers. If the client has not paid invoices or has not provided essential materials, the contract can allow you to suspend services until the issue is resolved. Suspension wording should say when suspension is allowed, whether fees continue, what happens to delivery dates, and whether you are responsible for consequences caused by the suspension.

Termination is the backstop. It should be available where the client delay is serious, repeated or continues after notice. A termination clause can let you end the contract if the client fails to provide required inputs or approvals within a stated cure period. It should also say what the client must pay on termination, including fees for work performed, committed costs, non-cancellable third party expenses, and any agreed termination charges.

For software and digital projects, client delay can also affect security and data protection. Access credentials may expire, test data may become outdated, or personal data processing instructions may be missing. If you act as a processor for a client under the UK GDPR, your data processing terms should require the client, as controller, to provide lawful and documented instructions. If the client fails to give those instructions, your contract should allow you to pause the affected work rather than guessing what is permitted.

Internal records matter too. Use one system for approvals where possible. Keep version histories, meeting notes and sign-off emails. If the project later becomes disputed, these records can show that your team was ready to perform and that the delay flowed from the client's missing input or late decision.

Clauses That Work Together to Avoid Blame

A client delay clause is strongest when it works with the scope, change control, acceptance, payment, IP and termination clauses.

Scope and assumptions. The scope should define what is included and what is excluded. It should also state the assumptions behind the price and timetable. If the quote assumes that the client will provide final copy, two rounds of feedback and access to key systems, say so. If those assumptions change, the contract should allow a variation.

Change control. Change control prevents late client instructions from being treated as part of the original job. A client may delay for two weeks, then return with a new idea, different stakeholders or extra requirements. Your change control process should allow you to assess the impact on time and fees before doing the work.

Acceptance and deemed approval. Approval delays are one of the most common causes of project drift. An acceptance clause can say the client must review deliverables within a set period and provide specific reasons for rejection. If the client does not respond within that period, the deliverable may be treated as accepted.

Payment, IP and suspension. Payment clauses should avoid making all fees dependent on final completion if the client controls completion. IP wording should say who owns pre-existing materials, who owns new deliverables, and when rights transfer or licences begin. Suspension rights should allow you to stop work for non-payment or missing inputs without being responsible for resulting delay.

Liability and termination. If the client caused the delay, you should not be liable for losses arising from the missed date. The contract can exclude liability for delays caused by the client's failure to perform its obligations, third party suppliers controlled by the client, or inaccurate information supplied by the client. Liability clauses under English law need careful drafting because some liabilities cannot be excluded, and unreasonable exclusions may be challenged under the Unfair Contract Terms Act 1977 or the Consumer Rights Act 2015.

These clauses create a consistent commercial position. The client remains responsible for their side of the project, you remain responsible for your services, and the contract explains what happens when one side's delay affects the other.

FAQs

Can I Extend a Deadline if the Client Sends Materials Late?

Yes, if your contract allows the timetable to move when the client misses a dependency. The clearest approach is to state that affected milestones and delivery dates extend by a reasonable period where the client is late, incomplete or unavailable.

Can I Charge Extra for Client-Caused Delay?

Yes, if the charges are properly set out and reflect real commercial impacts such as extra project management, rescheduling, waiting time, remobilisation or rework. Hidden or excessive charges are more likely to cause disputes.

What if the Client Says the Delay Is Still My Fault?

Written records are critical. Keep the project plan, dependency list, reminders, delay notices, feedback logs and approval emails. These records help show that your team was ready and that the missed date flowed from the client's delay.

Should My Contract Include a Deemed Approval Clause?

For many B2B service projects, yes. A deemed approval clause can stop deliverables sitting unapproved indefinitely. It should give the client a fair review period and require specific reasons if they reject or request changes.

Can I Terminate if the Client Disappears?

Your contract can give you that right after a defined period of inactivity or after the client fails to remedy the delay following notice. It should also state what fees and costs are payable when the contract ends.

Key Takeaways

• A client dependency clause should list the materials, approvals, access and decisions the client must provide, and when they are due.
• A services agreement delay clause should extend affected deadlines where the client causes delay through late, incomplete or unclear inputs.
• Fee clauses should protect you against extra project management, waiting time, rework, remobilisation and delayed payment.
• Delay notices, approval records and clear project communications make it easier to rely on your contract if the timetable slips.
• Scope, change control, acceptance, payment, IP and termination clauses should all support the same position on client-caused delay.

If client delays are putting pressure on your timelines or fees, Sprintlaw UK's legal team can help with your services agreement, client delay clauses, change control process and IP ownership wording. Contact us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.