Stage payments split a construction project's cost into instalments tied to work actually completed, rather than one lump sum at the end. The safest structure links each payment to a verifiable milestone, backed by a modest deposit and clearly defined retention terms written into the contract before work starts. Get those three elements right and most payment disputes never happen.
TL;DR:
- Linking each stage payment to objectively verifiable milestones reduces disputes, with milestones like foundations or roof completion being most reliable.
- Construction contracts in the UK require clear mechanisms for interim payments, including proper notices and agreed valuation methods, to avoid payment delays.
- Vague payment clauses lead to disagreements; precise definitions, including scope, retention, and valuation dates, are essential to prevent arguments.
- Regular submission of detailed valuation claims with evidence accelerates payment, while effective record-keeping helps when withholding payments becomes necessary.
- Using integrated management tools that log milestones, photos, and invoices in one system keeps cash flow steady and minimizes admin gaps.
Table of Contents
- What are typical stage payment splits by project size?
- What legal rights do you have to interim payments?
- What should a stage payment clause actually say?
- How do you protect cash flow without over-frontloading?
- How does a payment application differ from an invoice?
- What can you do when payment is withheld unfairly?
- What does a sample stage payment schedule look like?
- Why stage payments protect both sides more than people assume
- Key actions to put in place now
- Sources
What are typical stage payment splits by project size?
The right split depends entirely on scale. A small job doesn't need the same scaffolding as a six-figure extension, and forcing one template onto both creates friction rather than clarity.
For very short jobs (a day's plumbing repair, a small electrical rewire), a simple two-stage structure works: a deposit to cover materials, then the balance on completion. Anything more elaborate is overkill.
For small to medium residential work, most contractors use three to six draws tied to physical progress. A typical run looks like this:
- Deposit on signing (covers initial materials and scheduling)
- Payment on completion of groundworks or foundations
- Payment when the structure is watertight (roof on, windows in)
- Payment on completion of first fix (wiring, plumbing carcassing)
- Payment on completion of second fix (fittings, finishes)
- Final payment on handover, after snagging is resolved
Larger commercial or new-build projects tend to move away from fixed milestones and towards monthly valuations against a schedule of values, where a surveyor or contract administrator assesses the percentage of work complete each period. That approach suits long timelines where a rigid five or six stage split would leave too much cash exposed on either side for too long.
The trigger matters more than the percentage. "Foundations poured," "roof watertight," and "first fix complete" are objective and checkable on site. "Halfway done" is not, and it's the wording that causes arguments six weeks later.
What legal rights do you have to interim payments?
Anyone working under a construction contract in the UK has a statutory right to stage, interim, or periodic payments under the Housing Grants, Construction and Regeneration Act 1996. This applies to most construction contracts running longer than 45 days, and it exists precisely because lump-sum-on-completion terms used to leave contractors financing entire projects out of pocket.
The Act requires the contract itself to state how payment amounts and due dates are worked out — it doesn't set the amounts, but it forces both parties to agree the mechanism upfront rather than arguing about it later.
Two notices matter here. A payment notice states what's due and when. A pay less notice, issued within a set window before the final date for payment, is the only lawful way to withhold or reduce a sum without breaching the contract. Miss that window, and the notified sum typically becomes payable in full regardless of any quality dispute.
What should a stage payment clause actually say?
A vague clause is worse than no clause, because it gives both sides room to argue that their reading is the correct one. Every stage payment clause should nail down:
- Milestone definitions with an objective completion test, not a subjective description ("roof structure complete and felted" rather than "roof stage")
- Deposit amount and what it covers, stated as a fixed sum or percentage with its purpose spelled out
- Retention percentage and release triggers, including whether retention splits between practical completion and the end of a defects period
- Valuation dates and payment-notice deadlines, matching the timings required under the Construction Act
- Change order handling, setting out how variations get priced and slotted into the existing schedule rather than left to argue about at handover
Ambiguity in any one of these tends to surface at the worst possible moment: right before a payment is due.
Pro Tip: Attach a one-page milestone description to the contract as a schedule, with a photo or diagram of what "complete" looks like for each stage. It removes the argument before it starts.
If you're building out a fuller set of clauses beyond payment terms, a construction contract management guide covers the wider checklist worth having in place.
How do you protect cash flow without over-frontloading?
Retention is typically a small percentage of the contract value, held back from each payment and released in two parts: some at practical completion, and the remainder at the end of the defects liability period. That second release is where cash quietly goes missing on smaller jobs, simply because nobody chases it once the client has moved back in.

Deposits deserve the same discipline. A large upfront deposit looks appealing when you need working capital, but it hands away your main leverage for ensuring the rest of the schedule gets paid on time. Keep mobilisation sums proportionate to actual upfront costs, not padded for comfort.
Practical ways to keep money moving:
- Submit monthly valuations even on projects with milestone-based stages. This way, cash flow doesn't stall during long phases
- Claim for materials delivered to site but not yet fixed, where the contract allows it
- Negotiate partial retention release at practical completion rather than waiting for the full defects period to end
- Track labour costs against draws closely, since payroll timing rarely lines up neatly with payment dates
How does a payment application differ from an invoice?
A payment application (or valuation) is a claim: "here's what I've completed, here's what I'm owed." An invoice is the formal demand for a specific sum, usually issued once the application has been agreed or the notice period has passed. Confusing the two is a common reason payments stall.
A solid pay application, built from a schedule of values, should include:
- A sequential valuation number, so cumulative amounts are easy to check against previous claims
- The percentage or value of work complete against each line item
- Materials on site, where claimable
- Less retention, showing the net amount actually due
- Supporting evidence: dated photos, sign-off sheets, or a site diary entry confirming the milestone
Clear numbering and photo evidence attached at submission cut approval time significantly, because the person checking the claim doesn't have to chase you for proof before they'll sign it off.
What can you do when payment is withheld unfairly?
Withheld payment isn't automatically unlawful, but the process for doing it lawfully is strict. A pay less notice must state the sum considered due and the basis for that calculation, issued within the timeframe set by the contract or the Construction Act's default provisions. Get the timing wrong, and the original notified sum usually stands.
- Suspend work lawfully only after giving the contractually or statutorily required notice period, and keep a written record of that notice
- Use adjudication for a faster, cheaper route to a binding decision than court litigation, particularly suited to payment disputes rather than complex technical ones
- Keep a dated record of every milestone: photos, sign-off sheets, and site diary entries build the evidence base that makes an adjudication claim strong rather than speculative
- Resolve snagging items promptly, since unresolved defects are the most common excuse cited for withholding final payment; a documented snagging process closes that door early
What does a sample stage payment schedule look like?
A workable schedule doesn't need to be complicated. It needs the trigger, the basis for the amount, and a due date, with supporting evidence attached at each stage.
| Milestone | Basis | Typical timing |
|---|---|---|
| Contract signed | Deposit, fixed sum or % | On signing |
| Foundations/groundworks complete | % of contract value | Within X days of sign off |
| Watertight shell | % of contract value | Within X days of sign off |
| First fix complete | % of contract value | Within X days of sign off |
| Second fix and finishes | % of contract value | Within X days of sign off |
| Practical completion | Balance, less retention | On handover |
| Defects period ends | Retention release | 3 months after handover |
Attach photos, a signed milestone checklist, and (where relevant) building control or architect sign-off to each request. Note change orders separately from the base schedule, so a variation doesn't muddy the cumulative valuation figure.
What operational credibility looks like in practice
Tradewisehq works with trades businesses that live inside exactly this problem: proving a milestone happened, invoicing it fast, and not losing track of retention six months down the line.
The gap between finishing a milestone and getting paid for it is almost always an admin gap, not a dispute. Photo evidence, a signed sheet, and an invoice sent the same day close that gap faster than any clause can.
An operational system that links job scheduling, photo logs, and invoice generation removes the lag between "we finished first fix" and "we've been paid for it."
A trades author's note on payment friction
Most disputes start the same way: nobody photographed the milestone before covering it up. A dated photo log, signed off on-site, prevents most of it.

Why stage payments protect both sides more than people assume
Contractors treat stage payments as a cash-flow tool. Clients often treat them as a control mechanism. Both views are half right, and the tension between them is exactly why so many disputes happen at the "he said the wall was finished, I say it wasn't" stage rather than over the big, obvious problems.
The real value of a well-drafted schedule isn't the money itself. It's that it forces both parties to agree, in writing, what "done" looks like before anyone's emotionally invested in the answer. Contractors who skip that step because a client seems trustworthy are the ones who end up chasing a final payment for months. Clients who refuse any deposit at all are often the ones who end up with a contractor who's financing their job on a credit card, which rarely ends well for build quality.
What's underrated is how much of this comes down to boring admin, not legal cleverness. The contractors who get paid on time aren't the ones with the sharpest solicitors. They're the ones who photograph everything, invoice the same day a milestone completes, and never let a valuation sit unsubmitted for two weeks because they were busy on the next job.
— Mateusz
How Tradewisehq keeps milestone payments on track
Tradewisehq gives you one place to schedule the job, log photo evidence against each milestone, and generate the invoice the moment a stage completes, so payment applications stop sitting in a drawer while retention quietly slips out of view.

Instead of chasing paperwork across three different apps, you get job scheduling, milestone photo logs, and invoice tracking in one mobile-first system built for how trades businesses actually work. If you're managing several jobs at different stages at once, that visibility is what keeps cash moving instead of stalling behind an unsent invoice. Start a free trial with Tradewise and set up your next project's milestone schedule before work even begins.
Key actions to put in place now
- Write milestone definitions with an objective completion test, not a vague description
- Set a fair deposit, a clear retention percentage, and named release points
- Use payment-notice and pay less notice language correctly, and track every application
| Action | Why it matters |
|---|---|
| Define milestones objectively | Removes room for dispute over "done" |
| Set deposit and retention terms upfront | Protects cash flow on both sides |
| Track payment notices carefully | Preserves your right to be paid on time |
Sources
- Housing Grants, Construction and Regeneration Act 1996 (Part II — Payment)
- Staged payments in construction | Experi – progress billing guide
- Guide to progress payments on construction projects | Procore
- Progress payments in construction: process and protections | LegalClarity
