How to Review a Milestone Holdback or Retention on a SOW

Arlo, Ops at a 16-person UK studio, is about to treat “ten percent (10%) holdback until the project is complete” as a tidy closeout. Knowing how to review a milestone holdback or retention on a sow is a 25-minute hunt: write percent, invoices, and a named event; split acceptance from go-live and P1s; calendar the release; limit set-off to defects on this SOW; then keep, shrink, or pay on acceptance.

September 2026. English law; exclusive courts of England and Wales. The PDF is an MSA — master services agreement, the frame this SOW hangs on. Line 7: “Customer shall retain ten percent (10%) holdback until the project is complete.”

Phase 2 waits until they “feel done.” Set-off: “Customer may set off any dispute against the holdback.” The AE calls it standard retainage. Friday is booked; the rush is the problem, and the hidden risk is a feeling, not a calendar.

Ten percent is a construction habit with a Victorian origin — it is not Arlo’s statute. Procore (updated 4 September 2026) still cites 1840s railway companies withholding 20%. Construction colour is typically 5–10% at a named milestone, not HGCRA 1996 s.104 colour for a portal rebuild. The Commercial Payments Bill (19 May 2026; Osborne Clarke, 18 June 2026) would, if enacted, ban construction retention — not law, not Arlo’s paper. MC Law (updated 15 August 2026): 10 to 15 percent of each milestone until final acceptance — only if the event is final acceptance, not “complete.”

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

Which percent is held, from which invoices, until which event?

Circle the percent, the invoices it hits, and the named release event. Ten percent of what — each milestone invoice, the last invoice only, or total fees? Until which written event? “Complete” has no owner. Do not treat “10% until complete” as standard retainage.

Freeze the packet — the MSA, this SOW, payment schedule and change-order form — dated today. Open the payment schedule exhibit — the appendix that carries line 7 — not only the heading Fees. If the fight is the whole SOW wrapper, that is a different hunt: statement of work review checklist. Stay here for percent, release, and set-off.

MC Law’s 10 to 15 percent until final acceptance is a customer ask, not a rule. Construction 5–10% is not Arlo’s statute. Treat 10% as colour when tied to final acceptance. Treat “10% until complete” with no event as a fail. For example, log “10% of each invoice until written final acceptance,” or “10% / complete — fail.”

What does acceptance mean versus go-live versus no open P1s?

Pick one named gate that releases, or steps down, the holdback. Go-live can sit on open P1s. “No open P1s” is a later freeze. Do log which sentence names the gate. Do not let “go-live” swallow written acceptance.

LedgerUp colour, not Arlo’s vendor: go-live can mean 48+ hours in production with no P1 incidents; stabilization is a later gate — no unresolved P1/P2 issues at 30 days. “Customer is satisfied” is not a criterion. Terrapin (2026): releasing “at completion” without substantial versus final produces a 60-to-90-day closeout fight. In practice, write which one event Arlo’s 10% waits on. Log the sentence, or “no named gate — fail.”

When to demand a release calendar, not “when we feel done”?

A feeling is not a date. Circle “feel done” and “next phase will not start.” Redline written notice of achievement, stated review days, then days-after-acceptance the cash is due. Do require a calendar plus deemed release if the reviewer goes silent. Do not gate Phase 2 on mood.

Ququ (16 September 2026) is blunt: “5% held until project completion” is the weakest wording. Worked maths: 5% on four £5,000 invoices leaves £1,000 sitting after £20,000 of work; a tighter path pays the rest within 7 days. Completion according to whom?

MC Law colour: objective tests, a review period (example: ten business days), written deficiencies, deemed acceptance only after a written reminder. Put the next-phase start on the same named event plus calendar. Log “feel done — fail.”

Why does set-off against the holdback have to be real defects only?

Withhold contests this invoice. Set-off nets a separate claim against cash that is otherwise due. Limit set-off against the holdback to notified, particularised defects on this SOW, in an amount no greater than the reasonable cost to cure, after written notice. Do not let “any dispute” eat the 10%.

Arlo’s sentence is the expensive miss: “Customer may set off any dispute against the holdback.” Vaquill: safer clauses limit set-off to amounts liquidated, undisputed, or finally determined. The error is treating a quarrel on another SOW as a licence to keep this 10%. Last month’s “any dispute” net is the costly pattern. Do: written notice before deduction. Don’t: self-determined speculative set-off.

How do you keep this hunt on cash timing, not a volume shortfall?

A holdback delays fees already earned against a named event. A volume shortfall invoices unused commit. If the fight is an unused-commit shortfall, that is a different hunt: minimum volume commitment shortfall and rollover. Do not mix the two fights.

How do you choose keep, shrink, or pay on acceptance?

Keep only if the log shows a stated percent, a stated invoice base, a named event, a days-after calendar, and set-off limited to defects on this SOW. Shrink the percent or step it down at the named event. Pay on acceptance when the certificate is signed or deemed. Walk Friday if “10% until complete” plus “feel done” plus “any dispute” remain.

Success bar: a one-page log plus one Friday pause sentence. Arlo already has three: “ten percent (10%) until the project is complete”; “feel done”; “any dispute.” Workflow: percent + invoices + named event → acceptance vs go-live vs no open P1s → release calendar not “feel done” → set-off for defects only → not a volume shortfall → keep / shrink / pay on acceptance.

Spend counsel — the England-and-Wales solicitor who opens line 7 — on that package. Escalate the AE’s “standard retainage” line under Friday pressure. Upload the same PDF to document analysis for a first-pass — a machine extract of clauses before a human reads every page — then a human still opens line 7 to verify every High flag — a severity-high extract a human still opens.