Stages · Guide · For builders
How to create payment milestones customers can understand
A payment schedule can look perfectly clear to the contractor who wrote it and still be almost meaningless to the customer.
“Deposit, first fix, second fix, completion” may match how you run the job. It does not necessarily tell the customer what is included, what they should expect to see or what makes the payment ready for review.
That gap matters because payment requests arrive at moments of pressure. You have paid labour, committed to suppliers and planned the next stage. The customer sees disruption and unfinished rooms. If the milestone is vague, both parties reach for leverage instead of the agreement.
Good milestone design makes that conversation easier before it becomes urgent.
Start with how the work actually moves
Do not divide the price into arbitrary percentages and then invent labels. Map the real sequence of the job:
- what needs to happen first;
- what costs must be committed before visible progress;
- which groups of work produce a meaningful outcome;
- what will be concealed;
- which later work depends on the stage;
- where a customer, professional or inspector must act;
- when a payment is commercially needed.
Then create milestones around meaningful checkpoints.
A small decorating job might need a mobilisation amount, one progress stage and completion. A £250,000 extension may need separate procurement, structural, envelope, service, finish and handover stages. Proportionality is part of professionalism. More milestones are not automatically better.
Separate work from the completion test
The scope says what you have agreed to provide. The milestone groups the relevant work. The completion criteria explain what must be true before the stage reaches its agreed state.
For each milestone, write a plain-English outcome and ask:
Could a reasonable customer understand why this stage is ready for review without already knowing construction terminology?
“Roof watertight” might need to identify which roof areas, coverings, flashings or temporary elements are included. “First fix” might need separate descriptions for electrical and plumbing work. If an element is excluded or belongs to a later stage, say so.
Link evidence to a reason
Do not require photographs merely to make the project look controlled. Agree evidence that helps answer a foreseeable question:
- work before it is concealed;
- a specified product or material;
- a relevant inspection or test;
- delivery or procurement where a payment relates to committed cost;
- a corrected issue;
- a change from the original plan.
Ten labelled photographs linked to requirements may be more useful than one hundred images dumped into a gallery.
Avoid milestones that are too broad
A single £30,000 milestone containing fifteen unrelated work packages creates avoidable risk. If one meaningful item is questioned, it may be difficult to understand the value or consequence of the exception.
Ask:
- Does this stage represent one coherent project outcome?
- Can an incomplete item be identified without arguing about the entire job?
- Is the value commercially honest?
- Does the stage hide procurement or mobilisation cost inside “completed work”?
- Would a customer recognise why the payment is due?
Do not split the project into dozens of tiny approval events. The aim is controlled clarity, not customer micromanagement.
Define roles before the stage arrives
If an architect, engineer, contract administrator or other professional must certify or advise, record that when the milestone is agreed. If Building Control activity is relevant, state the specific event without implying that it decides contractual payment.
Do not wait until the customer asks, “How am I supposed to know whether this is right?”
Treat changes as changes
When accepted work, specification, criteria, value or timing changes, update the project through the variation or amendment process. Do not quietly move the finish line inside a progress note.
The agreed version should remain visible. That protects you when a customer later remembers a different scope, and it protects the customer when the submitted stage no longer matches what was agreed.
Submit a stage professionally
A useful submission should say:
- what milestone you are submitting;
- what work has reached the agreed state;
- which evidence is attached;
- which accepted variations affect it;
- whether anything remains outstanding;
- what review or payment action is requested;
- what work comes next.
Do not leave the customer to reverse-engineer the payment from an invoice total and a folder of photographs.
Respond to a query against the item
A query is not automatically an accusation or refusal to pay. Compare the question with the relevant scope, criterion and evidence. Explain, add evidence, offer correction, identify a variation or seek professional input as appropriate.
If the project supports partial review, keep any exception connected to the specific work and relevant amount. Do not promise a financial result the workflow does not support.
How Assurr helps
Assurr connects each milestone with its work, criteria, evidence, changes, decisions and payment state. It creates a common reference point for the submission and review without making Assurr the surveyor, certifier or dispute decision-maker.
For a good contractor, that is not a new standard of behaviour. It is a clearer way to show what you already agreed, delivered and documented.
The test before issue
Before asking the customer to accept the milestone plan, imagine you are looking at the site without your trade knowledge.
Can you tell what the stage includes, what completion means, what evidence matters, who decides, what it costs and what happens if one item is unclear?
If not, the payment schedule is not finished.