Progress Claim Terms in the UK: What to Include in Your Contract

Cash flow problems often start with vague payment wording. A business agrees to staged invoices, the work moves quickly, and then the customer says the milestone was never met, the paperwork was incomplete, or the amount claimed is too high.

The result is familiar: delayed payment, arguments over scope, and pressure on your margins.

Three common mistakes cause most of the trouble. First, the contract does not clearly define when a progress claim can be made. Second, it does not say what evidence must support each claim. Third, it leaves timing, approvals, set-offs or retention too open ended. That is where founders and commercial teams get caught, especially before they sign a contract or accept the other side's standard terms.

Good progress claim terms do not need to be long, but they do need to be precise. This guide explains what progress claim terms mean for UK businesses, what to include in your contract, the legal issues to check before you sign, and the mistakes that most often lead to delayed or disputed payments.

Overview

Progress claim terms set the rules for staged payment during a project, rather than one payment at the end. They matter most in construction, manufacturing, technology projects, fit-outs, professional services and any contract where work is delivered in phases.

Well-drafted payment clauses reduce uncertainty, protect cash flow and make disputes easier to resolve if they arise.

• Define each milestone, stage or valuation method in clear objective terms.
• State when a progress claim can be issued and what documents must accompany it.
• Set payment deadlines, approval periods and what happens if the customer stays silent.
• Deal expressly with disputed amounts, set-off rights, retention and variations.
• Make sure the payment clause matches the scope of work, programme and acceptance process.
• Check whether sector-specific rules apply, especially in construction contracts.

What Progress Claim Terms Means For UK Businesses

Progress claim terms are the contract rules that let one party invoice in stages as work progresses. They turn the commercial deal into a payment process that can actually work on the ground.

In practice, a progress claim is usually a request for payment linked to one of three things:

• a completed milestone, such as design sign-off or delivery of a working prototype
• a percentage of work completed, often assessed by valuation
• costs incurred up to a stated stage, sometimes with supporting records attached

Many UK businesses use staged payments because they cannot carry the entire project cost until completion. That is especially true where there are upfront materials, subcontractor costs, long lead times or significant labour before the final handover.

Where these clauses usually appear

You will often see progress claim terms in:

• building and fit-out contracts
• software development agreements
• marketing, design and content retainers with project stages
• manufacturing and supply agreements for custom goods
• consultancy engagements with phased deliverables
• installation and equipment supply contracts

The exact drafting should match the type of project. A construction contract may refer to interim valuations, payment notices and retention. A software agreement may tie payment to testing, acceptance and deployment. A manufacturing contract may use factory milestones, procurement points and delivery dates.

Why the wording matters so much

The main risk is not usually the idea of staged payment itself. The main risk is that the contract uses loose labels such as “upon substantial completion”, “when phase two is finished” or “monthly in arrears” without saying what those terms mean.

That leaves room for the customer to argue that the stage was not reached, the work was defective, or more evidence was needed before payment fell due. If your team is relying on that payment to keep the project moving, the commercial impact can be immediate.

Clear progress claim terms also help where the relationship is still good. They create a routine for issuing claims, reviewing them and paying them. That can prevent avoidable friction between operations, finance and procurement teams on both sides.

Milestones versus time-based instalments

Not every staged payment clause is a true milestone clause. Some contracts simply split the price across dates, such as 30 per cent on signing, 30 per cent after 30 days and the balance on delivery. Others link payment to measurable progress.

The difference matters. A date-based instalment may be simpler to administer, but it can feel risky for the paying party if progress is hard to measure. A milestone-based claim can feel fairer, but it only works if each milestone is specific enough to avoid argument.

Before you sign, decide which model suits the project:

• fixed instalments on agreed dates
• claims on completion of defined milestones
• periodic valuations of work done
• a hybrid model, such as an upfront deposit plus milestone claims

How progress claims interact with acceptance

Businesses often confuse payment stages with acceptance stages. They are related, but they are not the same thing.

A customer may agree to pay when a milestone is achieved, while still retaining a limited right to report defects or request remediation. Equally, a contract may require formal acceptance before the invoice becomes payable. If the clause does not separate those ideas clearly, disputes become much more likely.

Before you rely on a verbal promise that “finance always pays on receipt”, check the written terms, acceptance and payment provisions side by side. If one clause says payment follows milestone completion but another says invoices are only payable after written acceptance, the customer may treat written acceptance as a condition for payment.

Legal Issues To Check Before You Sign

The safest payment clause is one that leaves as little room for subjective debate as possible. Before you sign, make sure the contract answers the practical questions your finance and delivery teams will face during the project.

1. What exactly triggers each progress claim?

Your contract should say precisely when a claim can be made. Avoid broad wording that depends on opinion unless there is a clear mechanism for who decides and on what basis.

Useful trigger wording often includes:

• named milestones with objective deliverables
• dates for instalments
• measured percentages of completion
• valuation by a specified person or method
• delivery, installation or testing events

If you are using milestones, define each one. “Completion of phase 1” is not enough on its own. Spell out the outputs, standard required, and whether any customer action is needed to confirm completion.

2. What must be included in a claim?

If the contract is silent, parties often argue about whether the invoice was valid. A simple clause can avoid that.

Set out the required supporting material, such as:

• an invoice in the agreed format
• a milestone completion statement
• timesheets, records or valuation sheets where relevant
• delivery notes, test results or sign-off documents
• evidence of approved variations affecting the amount claimed

Keep this realistic. If the claim process becomes too burdensome, your team may miss steps and create arguments about technical non-compliance.

3. When is payment due?

The contract should state the payment period clearly, for example 7, 14 or 30 days from receipt of a valid progress claim. It should also say when a claim counts as received and whether there is a cut-off time for submission.

Founders often focus on the number of days but miss the definition of “valid invoice” or “valid claim”. If the customer can reject a claim for minor formatting issues, the payment clock may never really start.

4. Is there an approval or notice process?

A good contract says what the customer must do after receiving a progress claim. Silence should not leave your business stuck indefinitely.

Consider whether the contract should require the customer to:

• approve or dispute the claim within a fixed number of days
• identify reasons for any dispute in writing
• pay any undisputed amount on time even if part is challenged
• be treated as having accepted the claim if no notice is given within time

That last point needs careful drafting and may not suit every deal, but it can be very helpful where delays in internal approvals are common.

5. Can the customer set off other amounts?

Set-off clauses are often overlooked. A broad set-off right may let the customer deduct alleged losses, credits or back charges from a progress claim, even where those amounts are disputed.

If you are the supplier, you may want to limit deductions to sums that are agreed, finally determined or expressly permitted under the contract. If you are the customer, you may want enough flexibility to protect against overpayment where defects or delays are real.

This is one of the clauses that can materially affect cash flow long before any final dispute is resolved.

6. How do variations affect staged payments?

Projects change. If the contract does not explain how variations alter milestones, prices or timing, the payment mechanism can stop working as soon as the scope moves.

Your variation clause should deal with:

• who can request a variation
• what approval is needed
• how the price impact is calculated
• whether milestones move or new ones are created
• whether work can proceed before the variation is formally agreed

This is where founders often get caught. The team does extra work to keep the client happy, then the client says the milestone was not reached because the scope changed.

7. Is retention being withheld?

Some contracts allow the customer to keep back a percentage from each progress claim until practical completion, final completion or the end of a defects period. That is common in parts of the construction sector and can appear in other project work too.

If retention applies, the contract should say:

• the percentage withheld
• the maximum total retention
• when each part is released
• what conditions must be met for release
• whether retention can be replaced by another security arrangement

Retention that is vague or open-ended can become a hidden hit to project margin.

8. Do construction payment rules apply?

For many construction contracts in the UK, statutory rules can affect how payment and adjudication operate. The Housing Grants, Construction and Regeneration Act 1996, as amended, may apply depending on the arrangement.

If it does, the contract may need to fit specific requirements around payment notices, pay less notices and adjudication rights. This area is technical, and standard wording copied from a non-construction contract can cause real problems.

If your project involves building, engineering, fit-out or installation work, do not assume a general services agreement or template will be enough.

9. What happens if work is defective or incomplete?

The contract should say whether defects allow the customer to withhold the whole claim, only the disputed portion, or a reasonable amount reflecting the issue. Without that detail, minor complaints can turn into total non-payment.

You should also check whether there is a cure process. For example, does the supplier get a set period to fix defects before payment can be reduced or withheld?

10. Does the clause match the rest of the contract?

Payment wording cannot be read in isolation. It needs to line up with the scope, specification, programme, acceptance testing, variation mechanism and termination rights.

Before you accept the provider's standard terms or issue your own draft, compare these provisions carefully. A well-worded milestone clause can still fail in practice if another clause gives one party a broad right to delay sign-off.

Common Mistakes With Progress Claim Terms

Most payment disputes start with drafting that seemed harmless at the time. The biggest mistakes are usually practical rather than exotic.

Using vague milestone language

Terms such as “substantial completion”, “ready for use” or “phase delivered” can work if they are defined. If they are not, each side may apply its own commercial expectations.

A better approach is to list the exact deliverables, test criteria, documents or outcomes required for that stage.

Leaving acceptance entirely to the customer's discretion

If the customer can delay sign-off without objective criteria or a time limit, the payment trigger is weak. This often happens in software and creative projects where approval wording is copied from a procurement template.

The contract should say what counts as acceptance, the review period, and the grounds on which approval can reasonably be withheld.

Failing to separate disputed and undisputed amounts

If there is no clause requiring payment of the undisputed portion, a small disagreement can stall the entire invoice. That creates unnecessary pressure and usually makes the commercial relationship worse.

It is often better to require prompt payment of the undisputed amount while the balance is dealt with through the agreed dispute process.

Ignoring the paperwork needed for a valid claim

Your team may know what the customer expects, but if the contract does not say so clearly, routine admin issues become legal arguments. The other side may say the invoice was premature, unsupported or invalid.

A short schedule setting out claim documents and submission contacts can save a lot of time.

Agreeing to broad set-off rights without realising the impact

Broad deduction wording can let the customer reduce payment for almost any allegation. That may be acceptable in some deals, but many suppliers agree to it without appreciating how much leverage it gives the other side.

Before you sign, think about what deductions are fair and what should require agreement first.

Not linking variations to payment stages

When project scope changes, the original milestones may stop making sense. If the contract does not update the payment mechanism, invoices become harder to justify and easier to dispute.

This is especially common where founders rely on emails and informal approvals rather than the variation procedure in the contract.

Overlooking sector-specific rules

A clause that works for design services may be unsuitable for construction work. Where statutory payment rules apply, generic drafting can create compliance issues and make enforcement harder.

If the project sits near the construction boundary, get the payment wording checked through a contract review before you sign.

Relying on verbal assurances

Commercial teams often hear statements such as “we always pay milestones promptly” or “that clause is never enforced”. If the written contract says something different, the written wording usually matters most.

Before you spend money on setup or commit resources, ask for the contract to reflect the actual commercial understanding.

Using one template for every project

A supplier might use the same staged payment wording for consultancy, custom manufacture and installation work. That usually creates a mismatch between the clause and the real delivery process.

Payment terms should reflect how value is actually delivered in that project, not just what appeared in the last contract.

FAQs

What is a progress claim in a UK contract?

A progress claim is a request for payment made during the life of a project, usually after a milestone, valuation point or agreed stage has been reached. It is common where work is delivered over time rather than in one final handover.

Do progress claim terms need to be in writing?

They do not always have to be in a standalone written clause to exist as a matter of contract, but putting them in clear written terms is strongly advisable. Written wording reduces disputes about timing, amounts and evidence.

Can a customer refuse to pay a progress claim because of a minor defect?

That depends on the contract. A well-drafted clause often allows the customer to dispute only the affected portion or require remediation, rather than withholding the entire amount for a small issue.

Are progress claim terms different in construction contracts?

Often, yes. Construction contracts may be affected by statutory payment and adjudication rules, and the notice requirements can be stricter than in a general services agreement.

Should milestones be tied to acceptance?

Sometimes, but only if the acceptance process is clearly defined. If acceptance is subjective or has no deadline, tying payment to acceptance can create unnecessary delay and uncertainty.

Key Takeaways

• Progress claim terms should state exactly when staged payment can be claimed and how the amount is calculated.
• Each milestone or valuation point should be objective, measurable and aligned with the scope of work.
• Your contract should set out what documents support a valid claim, when payment is due and how disputes must be raised.
• Set-off, retention, defects, variations and acceptance wording can all affect whether a progress claim is paid on time.
• Construction and fit-out projects may require extra care because statutory payment rules can apply.
• The best time to fix weak payment wording is before you sign, not after work has started and cash flow is under pressure.

If you want help with payment milestones, variation clauses, set-off rights, retention wording, you can reach us on 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.