Difference Between Milestones and Target Dates

Introduction

Milestones are used in project management to mark specific points along a project timeline. They show you key achievements or decision points throughout your project’s lifecycle.

The milestone itself carries no duration, but in many instances it will impact the total project duration.

In Proggio, setting milestones as Target Dates will visually stand out on the project map and will not impact the project duration as is normally acceptable in project management.

Understanding Milestones vs. Target Dates

Milestones mark the end of a project phase and directly impact your project timeline.

They create natural checkpoints where deliverables converge.

Target Dates are reference points that don’t affect project duration.

They’re useful for tracking important dates (like review meetings or external deadlines) without constraining your timeline.

How to Create a Milestone

To add a milestone, double-click on the timeline area at the top of your project map:

Milestones appear as flags, Target Dates appear as diamond flags

Configuring Milestone Properties

Click on the milestone to open the milestone properties panel.

From here you can:

  • Milestone name: Give your milestone a clear, descriptive name
  • Phase name: Associate the milestone with a project phase
  • Date: Set when this milestone should occur
  • Description: Add context or requirements
  • Tags: Organize milestones with custom tags
  • Mark as target date: Toggle this to convert between milestone and target date
  • Exclude from Project Portfolio: Hide from high-level portfolio views if needed
  • Color: Customize the milestone color for better visibility
Configure milestone properties including the “Mark as target date” toggle

How Should Milestones Be Used in a Project?

Milestones work best when they represent the convergence of multiple activities or the completion of a major phase.

Here’s an example from an application development project where tasks across multiple workstreams (Management, UX/UI Design, Development, QA, DevOps) all converge into a milestone.

Notice how the milestone sits at a natural decision point in the project – after key development work is complete but before moving to production.

Multiple workstreams converging into a milestone before the next phase

Milestones in Portfolio View

When viewing your project in the portfolio view, milestones and target dates display differently:

Milestones appear as arrows showing the phase duration in portfolio view

Regular Milestones: Display as arrows across the timeline, indicating the duration of the milestone phase. The sharp point of the arrow marks the exact milestone date.

Target Dates: Appear as flag markers on the timeline without affecting the project duration or creating phase boundaries.

When to Use Milestones vs. Target Dates

Use Milestones when:

  • Multiple tasks must complete before moving to the next phase
  • You need a formal approval or review point
  • The date marks a critical dependency for subsequent work
  • You want the project timeline to reflect this checkpoint

Use Target Dates when:

  • Tracking an external deadline that doesn’t constrain your work
  • Marking a review meeting or stakeholder presentation
  • Highlighting an important reference date without affecting project duration
  • Showing aspirational goals that don’t create hard dependencies

Impact on Project Duration

Important: Adding a milestone will extend your project duration even if there are no tasks associated with it.

This is because milestones mark the end of a phase and create a new timeline segment.

If you want to mark an important date without impacting project duration, toggle the “Mark as target date” option in the milestone properties.

This converts the milestone to a visual reference point only.

Best Practices

  • Keep milestones meaningful: Don’t create too many – focus on major phase completions
  • Use clear naming: Make it obvious what the milestone represents (e.g., “Design Complete” or “UAT Approval”)
  • Align with deliverables: Connect milestones to specific deliverables or approval points
  • Consider your audience: Use “Exclude from Project Portfolio” for internal milestones that don’t need executive visibility
  • Color code strategically: Use consistent colors to indicate milestone types (e.g., blue for reviews, green for go-live)

Quick Reference

FeatureMilestoneTarget Date
Impacts project durationYes ✓No ✗
Creates phase boundaryYes ✓No ✗
Visual indicatorFlagDiamond flag
Portfolio view displayArrow showing phaseFlag marker
Best forPhase completions, dependenciesReference dates, external deadlines

Want to learn more about project management best practices? Check out our other resources in the Proggio Basics section.