Although milestones in Primavera P6 have zero duration and limited attributes, they play a vital role in tracking, controlling and communicating a project’s progress.
Milestones are somewhat like trail markers on a hiking trail; they tell where you’ve been or where you are headed. In Primavera P6, milestones are tasks that have zero duration. While they don’t reveal much about an ongoing process, they signal its start or completion.
They also mark key points in the schedule, such as a decision made, a phase completed, a deliverable handed over, a gate passed or an approval received. In P6, there are two types of milestones:
- Start Milestone: This marks the beginning of a phase or key event
- Finish Milestone: This marks the completion of something significant
Because they are zero duration, they cannot be assigned resources, do work or carry costs. They are purely scheduling markers, but as you’ll see, they can be extremely powerful communication tools within a project plan.
Here we explore the practical utility of milestones in Primavera P6 and how they enhance project scheduling despite their limited attributes.
1. They Make Your Schedule Easier to Read
A Gantt chart full of hundreds or thousands of activities can be overwhelming. Milestones act as visual anchors. Those little diamond shapes on the chart immediately tell folks (your client, your boss, your project board) where the important moments are. No one wants to read through 800 activity rows to figure out when Phase 2 kicks off. The milestone clearly marks that event like a signpost.
2. They’re Perfect for Reporting
When preparing a progress report or presenting to stakeholders, milestones can be your best friend. By filtering your view to show only milestones, you get an instant, high-level snapshot of the project’s status, often more insightful than pages of text or a cluttered Gantt chart.
3. They Help You Manage Interfaces and Dependencies
When multiple contractors or subcontractors are working on the same project, milestones can define clear interface handover points. For example, when Contractor A finishes their scope and hands it off to Contractor B, a milestone captures that interface precisely. It provides everyone a shared, definitive reference point, eliminating vague or conflicting assessments of when something was “done.”
4. They Keep You Contractually Covered
On many contracts, milestone dates are tied directly to payments. Getting this right in P6 means your schedule reflects your contractual obligations. And, you’ve always got an audit trail to refer back to.
Practical Tips
Creating milestones in P6 is very straightforward, but there are a few tips worth knowing.
Adding a Milestone
In your Activity Table, add a new activity and set its Activity Type to either Start Milestone or Finish Milestone. The duration will automatically default to zero; don’t try to change it. Give the milestone a clear, descriptive name, something apparently meaningful. For example, “Design Complete” conveys meaning at a glance, while “M1″ is cryptic.
Using Constraints with Milestones
You can apply a constraint to a milestone, such as a Must Finish On date, to lock it to a specific contractual date. But use constraints sparingly. They can disrupt the continuity along your critical path. Most scheduling guidelines limit their use, requiring constraints to be written explicitly in the contract.
As a rule, constrain only those milestones that are truly fixed by contract or external conditions. Let the scheduling software automatically calculate the start and finish times of other activities.
Baseline Your Milestones
Once you’ve got your schedule approved, assign a baseline. This gives you a reference point to compare against as the project progresses. In P6, you can track Baseline Finish vs. Actual/Forecast Finish for each milestone. This can make your variance reporting easier and more meaningful.
Codes and UDFs
Consider assigning Activity Codes to your milestones to classify them. For example, you might have codes like:
- CONTRACT — contractually required milestone
- INTERFACE — handover between parties
- INTERNAL — internal team checkpoint
- CLIENT — client-facing deliverable date
Activity Codes assigned to milestones simplify reporting. You can pull up either the contract milestones for your client dashboard or the interface milestones for your coordination meetings.
Common Mistakes to Avoid
Empirical project data shows several recurring issues with milestone usage:
- Too many milestones – if everything is a milestone, nothing is. Be selective. Reserve milestones for genuinely significant events.
- Orphaned milestones – milestones with no logic ties (no predecessors or successors) are meaningless in CPM scheduling. Every milestone should be connected within the network.
- Confusing start and finish milestones – use Start Milestones to trigger the beginning of work and Finish Milestones to mark completion. Mixing them up can create logic problems. (Good logic is the backbone of a healthy schedule.)
- Failing to update milestones – if a milestone slips, update it! The schedule must always reflect the current reality of the project.
A Simple Example
Say you’re running a construction project with three main phases: Design, Procurement and Construction. Here’s how you might use milestones:
- Project Start – Start Milestone, constrained to contract commencement date
- Design Complete – Finish Milestone, driven by the end of all design activities
- Equipment on Site – Start Milestone, tied to procurement delivery
- Practical Completion – Finish Milestone, contractual date with a constraint
- Final Completion – Finish Milestone, end of defects liability period
With these in place, you’ve got a clear project overview that anyone can understand at a glance.
Summary
The utility of milestones in P6 comes from their limited but definitive nature. And planners who understand their purpose can use them effectively as communication tools, contract anchors and reporting shortcuts, all in one.
When developing a schedule, identify the major milestones from the start. Doing so highlights truly significant events, keeps them logically connected and up to date and allows easy classification using Activity Codes.
As a result, your communication with stakeholders will become more focused, efficient and impactful.