Milestones & Deadlines
While the critical path manages the flow of work, milestones and deadlines represent the "hard points" of your project—the non-negotiable dates that stakeholders care about most.
Milestones: The Pulse of the Project
A milestone is a task with zero duration. It doesn't represent work; it represents an achievement.
Why use Milestones?
- Simplifying the View: Instead of showing 50 tasks to a client, you can show a a high-level timeline of 5 key milestones.
- Anchor Points: Milestones act as synchronization points. You can link multiple tasks to a single milestone to ensure everything is ready for a "Go-Live" or "Design Review."
- Progress Tracking: Measuring progress by "Milestones achieved" is more meaningful to stakeholders than "Percentage of tasks complete."
Deadlines: The Hard Constraints
A deadline is a constraint placed on a task that specifies the latest possible date it can finish without triggering a warning.
Deadline-Aware Scheduling
In MSP Planner, deadlines are not just visual markers; they are integrated into the scheduling engine:
- Warning Indicators: When a task's calculated finish date exceeds its deadline, the app provides a visual warning.
- Impact Analysis: Because the deadline is linked to the task, you can instantly see how a deadline constraint on a late-stage task affects the start dates of all preceding tasks on the critical path.
Pro Workflow: Combining Milestones and Deadlines
The most effective project managers use a combined approach:
- Set the Milestone: Create a milestone for "Client Approval of Phase 1."
- Set the Deadline: Apply a hard deadline to that milestone based on the contract.
- Link the Work: Link all necessary development tasks to that milestone.
- Monitor the Drift: Use the critical path and baseline overlays to see if the "Development" work is pushing the "Client Approval" milestone past its "Deadline."
This creates a closed-loop system where you can move from the most granular task to the highest-level commitment in a single view.