What is a Milestone?

Common Project Milestones

Milestones vary by project type, but these appear in most professional service engagements:

• Project kickoff — formal start of work, kickoff meeting complete, access and credentials delivered
• Requirements sign-off — client has approved the scope document, no further changes without a change order
• Design approval — wireframes or visual designs approved by stakeholder
• Development complete — all features built and passing internal testing
• Client review — client has tested and approved, feedback incorporated
• Launch — product or deliverable is live in production
• Project close — all deliverables handed over, retrospective complete, final invoice sent

Milestones vs Deliverables vs Tasks

These three terms have distinct meanings that often get conflated:

How to Track Milestones Effectively

A milestone without a date and an owner is just a wish. Each milestone needs:

A specific date — not "end of Q3" but "September 15" An owner — the person responsible for confirming it's complete A clear definition of done — what has to be true for this milestone to count as hit? A dependency list — what tasks or external inputs must complete first?

Milestone tracking works best when it's visible to the whole team. A project board with milestones called out, a weekly status email that includes milestone status, or a dashboard that flags upcoming and missed milestones all work. The risk of milestone tracking in a spreadsheet: it becomes stale within days and nobody trusts it.

Setting Milestones for a 3-Month Agency Project

A 3-month agency project needs 4-6 milestones. Fewer and you lose visibility between kickoff and launch. More and you're tracking tasks dressed as milestones.

A reasonable milestone structure for a 12-week website project:

Week 2: Discovery complete. Project brief approved, content inventory done, technical requirements signed off.

Week 4: Design direction approved. Two to three concept directions presented, one selected by client.

Week 7: Design complete. All pages designed and client-approved.

Week 10: Development complete. All pages built, reviewed internally.

Week 11: Client review complete. Client feedback incorporated.

Week 12: Launch. Site live, handoff documentation delivered.

Set milestone dates in the contract. If the client delays approval at week 4, the week 12 launch date moves accordingly. Put this in writing before the project starts.

Milestone Reviews: How to Run Them with Clients

A milestone review is a structured meeting where you show the client what's complete, get their approval, and confirm next steps. It's a decision point — not a status update.

Preparation: Verify that everything supposed to be complete by this milestone is actually done. Send agenda 24 hours in advance.

Opening (5 min): State the milestone and completion criteria. 'Today we're reviewing the completed design phase. The goal is your approval on all 8 page designs so we can move to development.'

Presentation (15-20 min): Walk through the deliverables live — show, don't tell.

Feedback (10-15 min): Ask specific questions. 'Does this match the brand guidelines?' Specific questions get useful feedback. Open-ended questions get 'I'll need to think about it.'

Decision (5 min): Is this milestone approved? If yes, confirm in writing within an hour. If no, agree on exactly what changes are needed.

Send written summary within 24 hours: what was approved, what changes are needed, any revised dates.

• Agenda to client 24 hours before — surprises in a milestone review slow the decision
• Specific questions get specific feedback
• Written confirmation of approval within 1 hour of the call
• If approval is not given, document exactly what changes are needed

When Milestones Slip: How to Communicate and Recover

Milestones slip. The goal is to catch them early and respond without damaging the client relationship.

If you see a slip coming 2 weeks out, you have options: add hours, reduce scope for this milestone, or move the date. Two weeks out, all three are on the table. Two days out, only the last option remains.

When a milestone slips, contact the client before the milestone date — not after. An email that says 'We need to move the design review from Thursday to Tuesday next week' is professional. An email on Thursday saying 'we're not ready' is a failure.

The communication structure: (1) What slipped and by how much. (2) Why — one sentence, factual. (3) The new date. (4) Whether the final project deadline is affected. (5) What you're doing to prevent further slippage.

If the final deadline is affected, say so explicitly in this message. Clients handle bad news. They don't handle surprises on launch day.

• Proactive communication before the missed date preserves the relationship
• One sentence on the cause — factual and direct
• Always state whether the final deadline moves — clients assume the worst if you don't say
• Fix the cause before the next milestone, not at the retrospective 6 weeks later