Milestone payments that hold up under pressure
Splitting a payment into stages only helps if each stage has a completion test someone else could apply.
Milestone payments are widely used and frequently useless. A schedule that says "40% at design, 40% at build, 20% at launch" reassures both parties until the first disagreement, at which point it turns out nobody defined design, build or launch.
The value is not in the split. It is in each stage carrying a test that can be applied without either party's cooperation.
One milestone, one transaction
In Covalt Work each milestone is a separate transaction with its own conditions. There is no partial release inside a milestone: the conditions are met or they are not.
That removes the most common source of stalemate — negotiating a percentage of a milestone as a compromise, which leaves both sides feeling shortchanged and the record ambiguous.
Ordering enforced by infrastructure
Milestones hold a sequence, and settlement of a later milestone is refused while an earlier one is incomplete. This is enforced by the transaction layer rather than by anyone remembering to check.
Sizing milestones
Two useful tests when drafting a schedule.
- The stranger test
- Could someone new to the project decide whether this milestone is complete, using only the conditions written on it?
- The proportion test
- If this milestone stalled, is the amount at stake one you could live with while it is resolved?
Common questions
Can a milestone be partially released?
No. Partial release inside a milestone reintroduces the ambiguity milestones exist to remove. Work that deserves separate payment deserves its own milestone.
Can milestones be created as the project goes?
Yes. Later milestones can be created as earlier ones complete, which suits engagements where later scope genuinely depends on earlier findings.
What if a milestone is abandoned mid-way?
Its conditions remain unsatisfied and it does not settle. Nothing is inferred from partial progress, and no payout timing is estimated.
Draft a milestone schedule
Set the sequence, the amounts and the conditions for each milestone, and see the whole schedule before anyone commits.
Related reading
- Cross-border workDistance does not break international work. Undefined completion does. This is how to define it, order it and settle it.
- International project paymentsProjects are not just larger engagements. Their risk lives in the dependencies between phases.
- Verified work paymentsFour distinct steps that most platforms collapse into one vague status — which is exactly where disputes come from.
- International agency paymentsAgency work fails differently: not one missing payment, but months of scope drift financed by the agency.