Project Milestones

What milestones are actually for

On an unstaged project somebody is exposed for the whole thing. Pay everything up front and the client carries the entire risk. Pay everything on completion and the contractor does, having funded weeks of work against a promise.

Milestones cut that exposure into pieces. At any moment, the most either party stands to lose is one stage rather than the whole engagement. That is the mechanism, and every practical rule about milestones is downstream of it.

The secondary benefit matters nearly as much: milestones force the project to produce something checkable on a regular rhythm, which means problems surface at week three instead of week twelve.

What makes a good milestone

It delivers something real. "Design phase complete" is a status. "Approved wireframes for the six screens listed in the scope" is a milestone. If nothing changes hands, there is nothing to accept.

It is checkable against the scope. The acceptance criteria for the milestone should already exist in the scope of work. Inventing them at the moment of delivery is how a milestone becomes a negotiation.

It is independently useful, where possible. A milestone that leaves you with something you could take elsewhere if the engagement ended is worth more than one that only makes sense as part of the whole.

It is proportionate. If one milestone is 70 percent of the project value, the staging is decorative. Aim for pieces small enough that losing one is survivable and large enough to be worth the administration.

Tying payment to milestones

Payment on acceptance, not on the date. A calendar date arriving tells you time has passed, which is not the thing you are buying.

Two details are worth agreeing in advance. First, how long you have to review a delivery: without a review window, a contractor can be left waiting indefinitely for a decision they cannot make themselves. A week is common. Second, what happens when a delivery is partially accepted, because that is more usual than either full acceptance or outright rejection. Naming a partial-payment or fix-and-resubmit route stops the whole milestone stalling over a small defect.

An upfront payment before the first milestone is normal, particularly with contractors you have not worked with. It is a commitment signal, not a milestone, and it should be modest.

Where milestone projects go wrong

Milestones invented after the project starts. They end up drawn around whatever has already been built, which defeats the purpose.

Too many. A milestone every few days turns the engagement into a series of approval gates and slows the work more than it protects it.

The last one is too big. A final milestone worth half the project recreates exactly the exposure the staging was supposed to remove.

No review window. Delivery is met with silence, the contractor cannot proceed or invoice, and goodwill drains away over something nobody decided to do.