Milestone Billing Schedule

Why this template matters

On a long or expensive job, the danger is concentration: if all your billing waits until the end, all your risk waits until the end too. A milestone schedule spreads both. By agreeing in advance that defined chunks of payment fall due at defined points, you fund the work as you go and surface any payment problem early — while you still hold unfinished work as leverage.

The schedule also kills the most common stalling line, 'I'll pay when it's all finished'. When the customer agreed up front that 40% is due at design sign-off, that conversation is already settled. A milestone schedule turns one big, risky invoice into a series of small, expected ones.

The schedule

MILESTONE BILLING SCHEDULE

Project:      [Project name]   Total: $50,000 inc GST
Customer:     [Customer name]
Contract ref: C-0099

------------------------------------------------------------
Milestone                  Trigger              %      Amount
------------------------------------------------------------
1. Deposit / kick-off      On acceptance        20%   10,000
2. Design sign-off         Designs approved     20%   10,000
3. Build complete          Build delivered      30%   15,000
4. UAT / acceptance        Customer accepts     20%   10,000
5. Final / go-live         Go-live + handover   10%    5,000
------------------------------------------------------------
                                       TOTAL:  100%   50,000

Each milestone is invoiced when its trigger is met.
Payment terms: Net 14 from each milestone invoice.

How to use it

Define each milestone by an objective trigger — 'designs approved', 'build delivered', 'customer accepts' — not a vague sense of progress. Objective triggers prevent arguments about whether a stage is really complete. Make the percentages add to exactly 100% and the amounts to the agreed total, so the schedule is self-checking and the customer can see they are never paying more than the quoted price.

Agree and sign the schedule before work begins, ideally attached to the quote. Then, as each trigger is met, raise a progress claim for that milestone. The schedule is the plan; the claims are how you execute it. Front-loading a deposit milestone keeps your exposure lowest at the riskiest, earliest stage.

Designing milestones that hold

Good milestones share three traits: they are objectively verifiable, they are spaced so your outstanding exposure never grows too large, and they map to real value delivered. Avoid back-loading — a schedule that leaves 60% to the final payment recreates the very risk milestones are meant to remove. Keep the final milestone modest, so the amount still at risk at handover is small.

Build in the variation rule too: if scope changes mid-project, agree the new milestone or amount in writing before doing the work, and re-confirm the running total. A schedule that flexes by agreement stays accurate; one that is silently overrun becomes the source of the dispute it was meant to prevent.