Project Management – Milestones

Purpose

Milestones represent key checkpoints, delivery targets, or decision points within a project.
They are used to track critical moments in the project lifecycle, such as major deliveries, approvals, contractual obligations, or billing triggers.

Milestones provide high-level visibility into project progress and are often used for governance, customer alignment, and financial coordination.

Access Path

Project Management → Projects → Open a Project → Milestones

💡The Milestones tab is available when enabled in the project’s assigned Process.

What Is a Milestone?

A Milestone is a non-effort-based project element that marks an important event or outcome.

Unlike work items:

Milestones do not represent execution work
They are not assigned effort
They are used to signal achievement, readiness, or approval

Milestones are typically associated with:

Delivery commitments
Go / No-Go decisions
Billing events
Contractual obligations

Milestones Tab Overview

The Milestones tab displays all milestones defined for the project in a list view.

For each milestone, users can track:

Name and description
Status and probability
Estimated and due dates
Responsible owner

This view provides a concise overview of project commitments.

Creating a Milestone

Select Add Milestone to create a new milestone.

Core Milestone Fields

Field	Description
Name*	Required name of the milestone.
Description	Optional description explaining the milestone objective.
Status	Current milestone status (configured in Control Center).
Probability	Likelihood of milestone completion, used for forecasting.
Estimated Date	Expected date for milestone completion.
Due Date	Contractual or committed completion date.
Responsible	User accountable for the milestone.

Available fields depend on system configuration.

Acceptance Criteria

The Acceptance Criteria section defines the conditions required for a milestone to be considered complete.

Acceptance criteria may include:

Validation requirements
Deliverable approvals
Quality thresholds
Formal sign-off conditions

This ensures milestones are closed based on objective criteria rather than assumptions.

Project Impacts

The Project Impacts section allows users to define actions or consequences associated with the milestone.

Impacts may be used to:

Trigger follow-up activities
Highlight risks or dependencies
Support decision-making
Link milestones to broader project outcomes

Impacts enhance milestone relevance beyond simple date tracking.

Milestones and Billing

Milestones are often closely linked to Billing Plans.

Typical use cases include:

Invoicing upon milestone completion
Partial billing based on milestone percentage
Holdbacks released after milestone acceptance

While billing is configured in the Billing Plan tab, milestones frequently act as the operational trigger.

Status Management

Milestone statuses are defined centrally in:

Control Center → Project Management → Status → Milestones

Status updates affect:

Project summaries
Reporting and dashboards
Billing readiness
Governance visibility

Only configured statuses are available for selection.

Best Practices

Define milestones early during project planning
Keep milestones focused on outcomes, not tasks
Use acceptance criteria to avoid ambiguity
Align milestone dates with contractual commitments
Regularly review milestone probability and status

What’s Next

After defining milestones, teams typically proceed to:

Billing Plan – Align milestones with invoicing
Risks – Identify risks related to key delivery points
Project Progress & KPIs – Monitor milestone completion impact

Project Management – Projects (Overview)
Project Management – Work Items
Project Management – Billing Plan
Project Management – Risks
Project Management – Track Project Progress & KPIs

Project Management – Milestones