Milestone (project)

A milestone is a marker for a significant point in a project — the end of a phase, an approval, a go-live, a client sign-off. Unlike a task, a milestone has no duration and consumes no effort; it's a checkpoint that records that something meaningful has been reached. On a timeline it usually appears as a diamond rather than a bar.

Milestones give a project its skeleton. Between them sit the tasks that do the work; the milestones themselves are the moments you actually report on, invoice against, or celebrate. "Discovery complete," "migration cutover," and "project accepted" are milestones — the tasks under each are how you get there.

Why it matters for MSPs

MSP projects are naturally phased — discovery, build, migration, cutover, handoff — and each phase boundary is a decision point where a client should be informed and, often, a payment or acceptance is due. Milestones make those boundaries explicit and trackable instead of buried in a task list.

• Anchor client communication: a status update against five milestones is clearer than one against fifty tasks.
• Tie to billing and acceptance moments on phased or fixed-fee engagements.
• Provide the early-warning line — a milestone at risk flags the phase, not just one task.

How it works in Current

Current supports milestones alongside phases and tasks, and they render on the Gantt timeline and dependency map so a slipped predecessor visibly threatens the milestone that depends on it. Because the partner portal enforces financial isolation at the database layer, you can share milestone progress and timeline with a client without ever exposing the cost or margin behind it — they see that discovery is complete, not what it cost you to get there.