Billing structure guide
Milestone billing based on events a client can recognize
Turn a project total into payment stages connected to signature, approval, delivery, or another objective engagement event.
A milestone is useful when both parties can tell whether it happened. Strong milestone billing replaces vague percentages of completion with observable commercial events.
01
Use observable events
Name what the client receives or approves at each stage. Avoid labels such as phase two, 70% complete, or ongoing work unless the agreement defines exactly what they mean.
- —Agreement signed and project deposit due
- —Prototype or staging build approved
- —Workshop completed and decision record delivered
- —Production handover or final files delivered
02
Make amounts and payment timing reconcile
The milestone amounts must add up to the engagement total. State when each invoice is issued and its payment deadline. If tax or a discount changes the final amount, show that calculation separately rather than hiding the difference.
03
Handle delayed approval
Set a reasonable review window and explain what happens when the client does not respond. Do not rely on silence as approval unless that rule is written clearly and is appropriate for the engagement.
Separate client-caused schedule movement from the freelancer’s delivery obligations so one missed review does not make every later date ambiguous.
04
Separate project milestones from changes and retainers
Use a change order for additional project scope. Use a retainer for genuinely recurring access or service. Mixing both into the original project milestones makes it difficult to see what the client has already approved and what remains payable.
Put this into the agreement
A practical final check
- 01Give every milestone an observable trigger.
- 02Make all milestone amounts reconcile to the agreement total.
- 03Set invoice issue dates and payment deadlines.
- 04Define the client review and approval window.
- 05Keep additional scope and recurring support in separate records.
Editorial standard
Written from the workflow the product actually supports.
- Prepared by
- The Censiq product team, which designs and maintains the agreement, invoicing, retainer, and reminder workflows described in this guide.
- Review method
- Product-specific statements were checked against the current Censiq workflow. No customer outcome, legal result, or payment-speed claim is inferred.
- Dates
- Published August 13, 2026. Last reviewed August 17, 2026.
- Corrections
- Found something inaccurate? Email support@getcensiq.com.
Continue with a related guide
Developers
Developer deposit structures that protect the start of a project
Read guideProduct designers
Design revision clauses that keep feedback inside the agreed scope
Read guideProduct consultants
Consultant workshop agreements that make the work around the meeting visible
Read guideAll independent professionals
A contract-to-invoice workflow for tech freelancers
Read guideGeneral operational information only. This guide is not a substitute for legal, tax, or financial advice.