Milestone

A milestone is a defined, observable checkpoint in an engagement that marks the completion of a meaningful phase, a key deliverable, or a client decision point, often tied to a payment trigger or client acceptance event.

Milestones vs. tasks

Tasks are the granular work items inside a delivery plan. A milestone sits above tasks: it is the gate that determines whether enough work is complete to move to the next phase, trigger a client review, or issue an invoice. A well-structured engagement has four to eight milestones; a task list may have hundreds of items.

How to define a milestone

Every milestone should have:

• A name that describes the outcome, not the activity (“Discovery report delivered” not “Complete discovery”)
• Acceptance criteria stating exactly what the client reviews and how they approve it
• A due date with dependencies documented
• A billing trigger (in milestone-based fee arrangements)

A milestone is either complete or not complete. Vague milestones such as “phase one complete” without defined acceptance criteria create billing disputes and client disagreements about delivery status.

Milestone-based billing

In fixed-fee and phased time-and-materials engagements, milestones serve as the billing schedule. When the client accepts a milestone, the corresponding invoice is released. This structure protects the firm’s cash flow and gives the client clear visibility into what they are paying for at each stage.

The payment schedule embedded in a milestone plan is typically set in the statement of work. Common distributions are 20% at kickoff, equal tranches at each interim milestone, and a final payment on project completion. Front-loading payment reduces the firm’s exposure if the engagement is terminated early.

Milestone gates and go/no-go decisions

A milestone is also a natural decision point. After a discovery or design milestone, the client and firm can evaluate whether to proceed to implementation, adjust scope, or pause. Making this decision explicit at the milestone rather than mid-phase prevents cost overruns and misaligned expectations. The steering committee or engagement sponsor typically owns the go/no-go call.

Common mistakes

• Defining milestones by date rather than outcome (“End of month 2” carries no completion signal)
• Not obtaining written client acceptance before moving to the next phase
• Stacking too many milestones at the back of the engagement, creating a revenue cliff
• Using milestones as checkpoints but not as billing triggers, forfeiting the cash-flow benefit

A change order is the appropriate mechanism when a milestone’s scope expands or when an accepted milestone needs to be reopened.