Pay for Progress, Not Promises: Milestone Payments Done Right and Done Wrong
Tying payments to milestones is one of the oldest ideas in project delivery, and one of the easiest to get wrong. Done well, milestone payments keep a project honest: money moves only when verifiable progress arrives, and both sides share a clear picture of where things stand. Done poorly, they become a source of constant friction, cash-flow strain on the supplier, and disputes that drain the very goodwill a project needs to finish. The difference is rarely the percentages. It is the definitions.
The past year sharpened the stakes. With materials delayed and crews working in shifts to keep distance, the gap between "the supplier is behind" and "the supplier delivered, but later" matters enormously. A well-built milestone schedule tells you which one you are looking at.
What good looks like
A healthy milestone-payment structure shares a few traits. None of them is exotic; together they remove most of the arguments before they start.
Each milestone has an objective, checkable completion test — a deliverable accepted, a system passing a defined test, an inspection signed off — not a calendar date alone.
Payment sizes roughly track the work and cost incurred to reach that point, so neither party is badly out of pocket between milestones.
Acceptance criteria and the review window are written down before work starts, with a named person responsible for sign-off.
A modest retention or holdback is released at genuine completion, giving a real incentive to close out the last details.
What bad looks like
Troubled milestone schedules tend to fail in recognizable ways. If you see these, expect disputes.
Date-only milestones. "50% on June 1" with no definition of what must exist by June 1 invites payment for time elapsed rather than value delivered.
Front-loaded payments. Large early instalments before substantial work is done strip away the leverage you need if the supplier stumbles, and tempt the unscrupulous.
Vague acceptance. "To the client's satisfaction" with no criteria turns every sign-off into a negotiation and every delay into a finger-pointing exercise.
No one owns approval. If approval drifts between people, invoices stall, the supplier's cash dries up, and a solvable cash-flow problem becomes a schedule problem.
Closing the gap
Moving from bad to good is mostly editing, not reinvention. Walk each milestone and ask one question: how exactly will we prove this is done? If the answer is a date, you have a problem; if it is a test, a deliverable, or an inspection, you have a milestone. Then check that the payment attached to it is proportionate to the effort behind it, name the person who signs off, and fix the review window in writing. On remote or hybrid jobs, agree in advance how evidence will be submitted and reviewed when people are not in the same room. These edits cost a meeting or two and prevent the disputes that cost months.
Milestone payments work when they pay for proof of progress. The moment they start paying for the passage of time, they stop protecting anyone.
If you want milestone schedules that hold up when a project gets hard, XNM's program & project delivery advisory can help you structure payments around real, verifiable progress.