These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Project Management
- Features
- Milestones
Milestones
Keep dated checkpoints tied to the project and the task that demonstrates completion.
OverviewUpcoming Milestones×
Project Management · Milestones
New
Upcoming Milestones
Approval conditions
| Milestone number | Name | Target date | Owner | Project | |
|---|---|---|---|---|---|
| MLS-17122 | Milestone 752 | 20 Oct | PRJ-22945 | ||
| MLS-27878 | Milestone 819 | 10 Oct | PRJ-30739 | ||
| MLS-41502 | Milestone 302 | 19 Oct | PRJ-83608 | ||
| MLS-52128 | Milestone 730 | 15 Oct | PRJ-63082 | ||
| MLS-13789 | Milestone 417 | 09 Oct | PRJ-52175 |
6 of 6 records
Milestone 752Milestones · MLS-17122
Target date20 Oct
ProjectPRJ-22945
What you can do
Mark the commitment
A milestone gives a project a dated checkpoint that can be read separately from the full task list. It has a target date, owner, status and optional completing task. That link matters when a milestone stands for a real delivery result. The Project Manager can see whether the corresponding task is ready and whether the checkpoint is upcoming, at risk, hit, missed or skipped. A completed date records when the result was achieved.
Imagine a rollout with a training-ready milestone. The project plan contains writing, review and publication tasks. Link the publication task as the completing task only if it is the evidence that training material is ready. If review is blocked, the milestone owner can see that the checkpoint needs attention before its target date. The team should use an at-risk state to call for a decision, then record hit or missed according to what actually happened.
How the work is organized
- Checkpoint. The milestone holds the name, target date, owner, current status and completed date.
- Evidence link. The completing task points to the work item that demonstrates the result.
- Context. The project link ties each checkpoint to the initiative that owns the commitment.
What to agree during setup
Decide what evidence qualifies a checkpoint as hit. A date crossing alone is not proof of completion. Agree on who may mark a milestone skipped and how that decision will be explained in the next project update. If a target date changes, keep the task plan and sponsor communication aligned. At-risk and missed states should lead to an explicit recovery decision, not merely a color on a dashboard.
Milestones are useful when they identify decisions, handoffs or externally visible results. Too many checkpoints make the project harder to read. Choose dates that the sponsor or receiving team will care about. The owner should be someone who can investigate a slip and bring the Project Manager a useful explanation.
Check the handoff on an actual case
Add a training-ready checkpoint with a target date and owner. Link the publication task, then move its predecessor into a blocked state. Open Upcoming Milestones and inspect the task chain in Project Gantt. The Project Manager can adjust the schedule or ask for a different delivery route. If the target arrives without the deliverable, record the milestone as missed and include the consequence in the status update. If the deliverable lands later, record the completed date accurately rather than rewriting the earlier target.
What your team sees
- Upcoming Milestones — Dated checkpoints approaching across permitted projects.
- Project Gantt — Tasks whose timing affects the checkpoint.
- Projects at Risk — Project context when overdue work and checkpoints accumulate.
Follow the work through
Plan and kickoff establishes dates. Review and close reconciles the checkpoint outcomes.
What it keeps track of
Data model- Milestones
- Dated project checkpoints tied optionally to a completing task.
- Tasks
- The unit of work, supporting phases, tasks and sub-tasks with dependencies.
- Projects
- The project container. Every task, milestone, status update and time entry attaches here.
Who uses it
Permissions- Project manager
- Reviews milestone changes; team member completes linked work; Viewer reads checkpoint outcomes.
Set up Project Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.