How to Allocate Risk in Construction Project Management Client Contracts in the UK

If you manage construction projects for clients, risk allocation is where deals often go wrong. A customer contract might say you are responsible for delays caused by third parties, design problems outside your scope, or cost overruns you cannot control. Founders also get caught by vague fitness for purpose promises, uncapped indemnities, and payment terms that leave them carrying project risk without matching protection.

That matters because a construction project manager usually sits in the middle of the job. You are coordinating consultants, contractors, timelines, budgets and reporting, but you may not be the designer, principal contractor, or specialist installer. If your contract does not clearly reflect that reality, you can end up taking on liabilities that do not match your fee or your actual role.

This guide explains how a risk allocation customer contract construction project manager should work in the UK, what to check before you sign, where businesses commonly make mistakes, and how to set fair limits that clients are more likely to accept.

Overview

A well-drafted construction project management contract should place each risk on the party best able to control it, insure it, and price it. The main job is to define your scope precisely, align liability with your actual responsibilities, and make sure the contract does not quietly turn a management role into a guarantee of project outcomes.

• Define exactly what services you are providing, and what is excluded.
• State which risks stay with the client, such as design adequacy, latent defects, planning approval, and contractor performance where you are not giving warranties.
• Limit liability with clear caps, exclusions for indirect loss, and realistic carve-outs.
• Match your obligations to reasonable skill and care, rather than broader outcome-based promises where possible.
• Check programme, delay and cost provisions so you do not underwrite matters outside your control.
• Align insurance obligations, indemnities, reporting duties and dispute procedures with the project structure.

What Risk Allocation Customer Contract Construction Project Manager Means For UK Businesses

Risk allocation in a client contract decides who carries the financial and legal consequences when the project does not go to plan. For a UK construction project manager, that usually means drawing a clear line between managing the process and guaranteeing the result.

Many SMEs assume that if they are “only” providing project management, the law will naturally protect them from design, contractor and site risks. It does not work that way. Your starting point is the contract you sign, read alongside the general law on services, negligence, and the reasonableness of some limitation clauses in business-to-business deals.

Your role needs to be described accurately

A client may use broad wording like “manage and deliver the project” or “ensure completion on time and within budget”. Those phrases sound commercial, but they can shift substantial risk onto you. If you are coordinating and monitoring, your contract should say that plainly.

In practice, a project manager's services often include:

• programme coordination and monitoring;
• budget tracking and reporting;
• administering meetings and records;
• liaison with consultants, contractors and the client team;
• procurement support;
• change control administration; and
• risk reporting and escalation.

That is different from promising that the contractor will finish on time, that the works will be defect-free, or that the design will comply with every technical standard. Unless you are separately engaged for those responsibilities, the contract should not imply them.

Reasonable skill and care is usually the right standard

For professional and consultancy-style services in construction, a reasonable skill and care obligation is often the more appropriate standard. It means you must perform to the standard expected of a competent professional in your field.

A higher obligation, such as fitness for purpose or an absolute warranty that a result will be achieved, can be much harder to satisfy and may go beyond your insurance cover. This is where founders often get caught before they accept the provider's standard terms or a client's heavily one-sided appointment.

Not every project risk belongs with the project manager

A fair contract separates the risks you can control from the risks you cannot. If the client retains design consultants, appoints the contractor directly, controls key decisions, or delays approvals, the contract should reflect that allocation.

Risks often retained by the client, or allocated elsewhere depending on the project structure, include:

• the adequacy of design by third-party designers;
• contractor workmanship and specialist subcontractor defaults;
• site conditions and latent defects, unless specifically investigated by you;
• planning permission and statutory approvals, unless expressly within your scope;
• client-caused delay, including slow instructions or late decisions;
• accuracy of client-supplied information; and
• force majeure-style events, where the contract uses that concept.

The aim is not to avoid all responsibility. The aim is to carry the risk that matches your role, fee and insurance, and to avoid becoming the fallback target whenever anyone else on the project makes a mistake.

Caps, exclusions and indemnities matter more than the headline fee

A modest fee can still create a major exposure if liability is uncapped. Many disputes start with a relatively small project management appointment and end with a claim tied to the overall value of the build, delay losses, financing costs or tenant claims.

Before you sign, focus on:

• an overall cap on liability, often linked to fees, insurance, or a negotiated project amount;
• carve-outs from that cap, which should be limited and clear;
• exclusions for indirect or consequential loss, loss of profit and similar remote losses where appropriate;
• net contribution wording, so you only pay your fair share where others also caused the loss; and
• time limits for bringing claims.

Indemnities need special attention. An indemnity can require you to reimburse loss on a broader basis than an ordinary breach of contract claim. If a client asks for a wide indemnity for all project losses, that can shift risk significantly and should be narrowed to losses you directly cause within your agreed scope.

Legal Issues To Check Before You Sign

Before you sign a construction project management contract, the key legal question is whether the words on the page match how the project will actually be run. If they do not, the contract can impose liabilities you neither intended nor priced.

1. Scope of services and express exclusions

Your scope should spell out what you will do, how often, and at what decision level. General wording creates room for argument later.

Useful points to cover include:

• which stages of the project you are involved in;
• whether you are advising, managing, monitoring, certifying, or approving;
• whether you have authority to issue instructions on the client's behalf;
• what reporting you will provide, and to whom;
• which meetings, procurement tasks and contract administration functions are included; and
• what is expressly excluded, such as design responsibility, quantity surveying, principal designer duties, contractor supervision, or health and safety roles unless separately agreed.

If the client expects site attendance, inspections or sign-offs, say how often and for what purpose. “Attendance as reasonably required” can lead to disagreement. A set number of visits or a clear attendance protocol is safer.

2. Duty of care and reliance

Your contract should usually say you will exercise reasonable skill and care in performing the services. It should also be clear who can rely on your work.

Without careful wording, third parties may later argue that reports, programmes or recommendations were prepared for wider reliance. That is a bigger issue on projects involving funders, purchasers, tenants or group companies. If the client wants collateral warranties or third-party rights, deal with that expressly and make sure it aligns with your insurance and liability cap.

3. Programme, delay and cost risk

Project managers are often blamed for late completion and overspend, even when the underlying causes sit elsewhere. The contract should distinguish between:

• providing estimates, forecasts and reporting;
• administering a programme and escalating risks;
• advising on mitigation; and
• guaranteeing completion dates or final costs.

If you cannot control contractor resources, supply chain failures, planning timelines or client variations, you should not guarantee the outcome. A better formulation is to require you to monitor and report material risks, use reasonable endeavours within your role, and promptly escalate issues requiring client decisions.

4. Payment structure and suspension rights

Risk allocation is not just about liability clauses. Payment terms also shift risk.

If your invoices are tied to disputed milestones, broad client satisfaction wording, or certification by someone with no timetable, cash flow becomes uncertain while your obligations continue. A better structure usually includes clear payment dates, interest on late payment, reimbursement of approved expenses, and a right to suspend services for material non-payment after notice, where commercially appropriate.

5. Client responsibilities

A project manager can only manage with timely information and decisions. The contract should state what the client must do.

Client obligations often include:

• providing accurate project information;
• appointing consultants and contractors on time;
• giving prompt instructions and approvals;
• ensuring access to the site and relevant records;
• maintaining project funding where applicable; and
• making key decisions within agreed timescales.

If the client fails to do those things, the contract should allow for extensions to your programme, revised fees where scope increases, and protection against resulting delay or cost consequences.

6. Insurance and consistency with your cover

Contract obligations should be checked against your professional indemnity and other insurance policies. Some clauses can create liabilities that are wider than your cover.

Points worth checking are:

• whether fitness for purpose wording appears anywhere;
• whether indemnities go beyond negligent acts or omissions;
• whether there are unusual obligations to insure project-wide risks you do not control; and
• whether the liability cap is realistic compared with your available cover.

Insurance is not a substitute for a balanced contract. It is one layer of protection, not the whole answer.

7. Variation, scope creep and change control

Construction projects rarely stay static. If your contract does not deal with change, you may end up doing extra work without extra fee, while also taking on extra risk.

Include a practical change control mechanism covering:

• how additional services are requested;
• when revised fees apply;
• who must approve the change;
• what happens if urgent work is needed before paperwork catches up; and
• how programme adjustments are recorded.

8. Termination and handover

Termination rights should protect both sides without leaving a messy project transition. If the appointment ends mid-project, you need clarity on payment for work done, delivery up of records, and any ongoing termination rights or duty to assist with handover.

Watch for clauses that allow termination for convenience without fair payment, or that require broad post-termination assistance with no time limit or fee.

Common Mistakes With Risk Allocation Customer Contract Construction Project Manager

The most common mistake is signing a client contract that uses attractive commercial language but quietly turns a project management role into responsibility for the whole project. That mismatch usually appears only when something goes wrong.

Accepting vague “deliver the project” wording

This is one of the biggest traps. A founder may assume everyone understands they are coordinating the job, not guaranteeing every aspect of delivery. Later, the client points to the wording and says the project manager accepted responsibility for completion, budget or compliance.

Clear contract drafting is better than relying on industry assumptions or verbal explanations.

Letting the contract make you responsible for third parties

If consultants and contractors are appointed directly by the client, you should be careful about clauses that make you liable for their defaults. You can take responsibility for coordination and reporting, but that is different from warranting their performance.

Before you rely on a verbal promise that “we would never read it that way”, ask for the written terms to be changed. The written contract is what matters most if there is a later dispute.

Using an uncapped indemnity

Some customer contracts include a broad indemnity for all losses arising out of the project manager's services. That can be much wider than a standard liability clause.

A better approach is to limit any indemnity to specific, identified risks that are genuinely within your control, and to align it with the overall cap where possible. If a clause sits outside the cap, you should know that before you sign.

Failing to define assumptions behind budgets and programmes

Clients often want early certainty. Project managers often provide preliminary budgets and programmes to help decision-making. Problems start when assumptions are not recorded.

If your cost plan assumes a certain procurement route, design stage, or approval timetable, say so. If your programme depends on client sign-off within five working days, say that too. Otherwise, an indicative forecast may later be treated as a commitment.

Ignoring net contribution and limitation wording

Construction losses usually have multiple causes. A delay could involve the client, the designer, the contractor, and the project manager. Without a net contribution clause, one party may try to recover the full loss from you even where others were partly responsible.

This is where founders often get caught because the clause does not look dramatic, but it can make a major difference to exposure.

Taking on statutory or specialist roles by accident

Modern projects can involve separate obligations around design coordination, building safety, planning conditions, and health and safety management. If your contract uses labels loosely, you can drift into duties you did not intend to accept.

Make sure specialist roles are either expressly included with proper pricing and insurance alignment, or expressly excluded.

Not dealing with client delay and decision-making

Many project management disputes are really client management disputes. The client may delay instructions, change priorities, or approve key steps late, then still expect the original completion date and fee.

Your contract should give you a route to document delay events, seek revised timescales, and charge for additional work caused by prolonged decision cycles or repeated changes.

Relying on a proposal instead of a full contract

A short fee proposal can be enough for a straightforward engagement, but complex construction projects usually need more detail. If the proposal is accepted by email and the parties start work, assumptions can harden into disagreement later.

A fuller contract review helps allocate risk on purpose rather than by accident.

FAQs

Can a construction project manager be liable for contractor delays in the UK?

Yes, but usually only to the extent the delay was caused by the project manager's own breach of contract or negligence within its agreed role. A well-drafted contract should not make the project manager automatically responsible for contractor defaults it does not control.

Should a project manager accept a fitness for purpose obligation?

Often no. For construction project management services, a reasonable skill and care standard is usually more appropriate. Fitness for purpose wording can create a much higher risk and may not align with professional indemnity cover.

What is a reasonable liability cap in a project management contract?

There is no single rule. Caps are commonly linked to the fee, a multiple of the fee, available insurance, or a negotiated sum based on the project and scope. The right figure depends on the work, the likely losses, and the parties' bargaining position.

Do indemnities matter if there is already a liability cap?

Yes. Some indemnities are drafted to sit outside the cap, or to operate on a broader basis than normal breach of contract claims. You need to check the interaction between the indemnity, the cap, and any exclusions very carefully.

Can a client rely on verbal promises if the contract says something different?

That will depend on the facts and the drafting, but relying on verbal assurances is risky. Before you sign, any important understanding about scope, programme assumptions, exclusions or liability should be written into the contract itself.

Key Takeaways

• A construction project management contract should allocate each risk to the party best able to control and insure it.
• Your scope of services needs to be precise, with clear exclusions so a management role is not treated as a guarantee of project delivery.
• Reasonable skill and care is usually the safer standard for project management services than fitness for purpose or absolute outcome promises.
• Liability caps, exclusions, net contribution wording, claim time limits and carefully limited indemnities are central to managing exposure.
• Programme, cost and delay clauses should distinguish between reporting and coordination duties, and guarantees of result.
• Client responsibilities, change control, payment rights, insurance alignment and termination terms should all support the intended risk allocation.
• Before you sign, make sure the written contract matches the reality of how the project will be run, rather than relying on assumptions or verbal comfort.

If you want help with scope drafting, liability caps, indemnities, and consultant and contractor risk allocation, you can reach us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.