Logo_Color
PPDS

Milestone data under the new standard: the three rules most teams miss

Milestone data under the new standard: the three rules most teams miss
7:32

Milestones are the most visible data in any project. Boards track them, SROs are measured against them and portfolio offices combine them to judge portfolio health. They are also where teams most often underestimate the gap between what they record and what the Programme and Project Data Standard (PPDS) requires.

The standard sets out 12 attributes for the milestone entity. It locks the baseline date, sorts milestones into three categories and applies validation rules to what each date field can hold.

This post covers the three rules teams most often miss, how the date fields work together and where the common gaps are.

The three rules most teams miss

1. The planned date is locked once set

The planned date is the baseline. Once you set it, it does not change. To re-baseline, you create a new milestone.

This is deliberate: the planned date is the fixed point against which all slippage is measured. If teams move it every time the forecast slips, nobody can track cumulative slippage over the life of the project, and cross-government analysis of schedule performance loses its value.

Most project tools let you edit baseline dates, and many teams do. Sometimes there is a genuine re-baseline, after a change in scope or a restructured plan. Sometimes updating the planned date simply looks tidier than showing slippage. Under the standard, the second is not acceptable. The first needs careful handling: mark the original milestone as Superseded and create a new one with the revised planned date. That way, the slippage history survives.

2. An actual date can never be in the future

An actual date records when a milestone was completed, so it must be on or before today's date. The standard will not accept a future actual date.

This sounds obvious, but it catches teams out in practice. It happens when teams mark milestones complete ahead of formal sign-off, or pre-populate data for a reporting deadline.

3. Superseded milestones are never deleted

When a revised milestone replaces an original, you keep the original. Set its status to Superseded and use the comment field to record the ID of the milestone that replaced it.

This matters for audit and long-term analysis. A project with several superseded milestones shows how its schedule has changed over time. Deleting them erases that history and breaks the traceability the standard is designed to support.

How the three date fields work together

Each milestone has three dates, and each does a different job:

  • Planned date: the baseline, set once

  • Forecast date: when you now expect completion, updated as the project progresses

  • Actual date: when the milestone was completed, recorded once

A worked example

Take a milestone called Service Go Live. Here is how its record changes over the project:

Point in project Planned Forecast Actual Status
Baseline set 2026-09-30 2026-09-30 – On track
Supplier delay 2026-09-30 2026-11-14 – Off track
Completed 2026-09-30 2026-11-06 2026-11-06 Completed

The planned date never moves, so the record shows the milestone finished 37 days late. If the team had updated the planned date when the delay emerged, that slippage would have disappeared from the data.

The three milestone categories

You must assign every milestone to one of three categories. The category decides how the milestone is read in any cross-portfolio analysis.

  • Assurance: formal reviews and gates, usually run by a body outside the project team. This covers NISTA Gate reviews (Gate 0 at programme level, Gates 1 to 5 at project level) and GRIP milestones.

  • Delivery: substantive delivery events. This covers the project start and end dates, which must match those in the project features entity, plus the business case end date, operational end date and any other milestone on the critical path.

  • Business case: submissions and approvals of HM Treasury business cases. This covers Strategic Outline Cases, Outline Business Cases and Full Business Cases, plus revisions and programme-level business cases. Each formal submission or approval is a separate milestone.

A simple test: if it is a review, it is Assurance; if it is a Treasury approval, it is Business case; if it is progress, it is Delivery.

Critical, restricted and protected status

These three Yes/No fields are missing from most milestone trackers. They exist because milestone data is used beyond the project team's own planning.

  • Critical status: marks whether the milestone is on the critical path. This lets portfolio-level systems spot schedule risk without someone reading each project plan.

  • Restricted status: marks whether the milestone should be treated as Official Sensitive. This is likely to apply to projects involving security, defence or commercially sensitive procurement.

  • Protected status: marks whether the milestone should be prioritised for protection in centralised reporting. Accurate information may still be unsuitable for cross-government dashboards or publication, and this flag allows the reporting layer to handle it differently.

The 12 attributes at a glance

Attribute What it holds Updated
Milestone ID Unique code, prefixed with the Project ID (for example, HMT_PROJ0001_M001) Once
Milestone title A short name for the milestone Once
Planned date The baseline completion date (YYYY-MM-DD), locked once set Once
Forecast date The current expected completion date, matching the date used internally On change
Actual date The completion date, on or before today Once
Category Assurance, Delivery or Business case Once
Status On track, Off track, Completed or Superseded On change
Description What completing the milestone means in practice Once
Critical status Yes/No: on the critical path On change
Restricted status Yes/No: Official Sensitive On change
Protected status Yes/No: prioritised for protection in centralised reporting On change
Comment Context, supersession history or significant forecast changes On change

Five common gaps in milestone trackers

When we review milestone data against the standard, the same five gaps come up most often:

  • No baseline lock: the planned date is editable and has changed during the project, erasing slippage history

  • One date field: teams track a single date instead of separate planned, forecast and actual dates

  • No category: milestones are not classified as Assurance, Delivery or Business case

  • Critical path not recorded: the team knows which milestones are critical, but the milestone record does not say so

  • Superseded milestones deleted: old records are removed instead of being marked Superseded

Where to start

If any of these gaps apply to your tracker, start there. Lock your planned dates and split out the three date fields first, because slippage reporting depends on them. Then assign categories, add the three status flags and agree a process for superseding milestones instead of deleting them.

For the full milestone attribute list, with definitions, formats and examples, see the full standard.

Next in this series, we look at cost data: the entity with the most attributes in the standard and the most complex categories.

Verto Newsletter

Insights That Move Public Services Forward

Discover tools, stories, and insights that help leaders deliver meaningful change across their organisations.