Blog · Board and management reporting
A progress dashboard compares accepted milestones with planned dates. This worked example separates completion, overdue milestones, late finishes, and forecast slippage, with clear owners and checks.
A progress dashboard shows which milestones are accepted, which planned dates have been missed, and which upcoming commitments are likely to slip. Build it around a fixed reporting cutoff and an approved baseline. A completion percentage becomes useful when the reader can see its denominator and the milestones behind it.
A milestone should describe a verifiable event: a survey accepted, an estimate approved, or a handover signed. Name the person who can accept it and record the evidence required. Work that is almost finished remains open until that acceptance condition is met.
For this view, record milestone ID, project, owner, approved baseline date, actual acceptance date, current forecast date, and a short blocker. Keep the export date alongside the reporting cutoff so reviewers know when the information was last confirmed.
The NASA Schedule Management Handbook explains why baseline and current schedules should be compared to identify variances and their causes. The same distinction makes a business milestone register useful: an updated expectation does not change what was originally promised.
A US operations team is preparing a facility handover. Its reporting cutoff is the end of October 23, 2026. All dates below are in 2026; an empty actual date means acceptance has not occurred. Calculations use calendar days, with milestones due on the cutoff date shown separately from overdue work.
| Milestone | Baseline date | Actual acceptance | Forecast if open | Status at cutoff |
|---|---|---|---|---|
| Scope accepted | October 2 | October 1 | — | Complete, on time |
| Site survey accepted | October 6 | October 8 | — | Complete, late |
| Concept approved | October 9 | October 9 | — | Complete, on time |
| Estimate approved | October 16 | October 20 | — | Complete, late |
| Vendor review accepted | October 20 | — | October 27 | Open, overdue |
| Safety signoff accepted | October 23 | — | October 26 | Open, due today |
| Training readiness accepted | October 28 | — | October 28 | Open, future |
| Handover accepted | October 30 | — | November 3 | Open, future |
The statuses are mutually exclusive. A completed milestone can have been late historically, but it is no longer open and overdue at the cutoff. Keeping those ideas separate prevents the same milestone appearing in conflicting totals.
Completion of due milestones = Accepted milestones due by cutoff / All milestones due by cutoff
Overall milestone completion = Accepted milestones / All eligible milestones
The first rate answers whether the team has delivered what should already be done. The second answers how many of the listed commitments have been accepted across the entire register.
| Measure | Calculation from the register | Result |
|---|---|---|
| Milestones due by cutoff | Scope, survey, concept, estimate, vendor, safety | 6 |
| Due milestones accepted | Scope, survey, concept, estimate | 4 |
| Completion of due milestones | 4 / 6 × 100 | 66.7% |
| All milestones accepted | 4 / 8 × 100 | 50.0% |
| On-time share of completed milestones | Scope and concept / 4 completed | 50.0% |
| Open overdue milestones | Vendor review | 1 |
| Open due today | Safety signoff | 1 |
| Open future milestones | Training readiness and handover | 2 |
Percentages are rounded to one decimal place after division. The population check is 4 completed + 1 overdue + 1 due today + 2 future = 8 milestones. Every eligible row appears exactly once.
Equal milestone counts do not measure effort. A handover and a concept approval each count as an event here, regardless of their workload. Use a broader project management report when the review also needs cost, effort, or overall schedule performance.
For completed milestones, subtract the baseline date from the actual acceptance date. The survey finished 2 days late and the estimate 4 days late. Their average lateness is (2 + 4) / 2 = 3 days; the denominator includes only late completed milestones.
For open overdue milestones, subtract baseline from cutoff. Vendor review is 3 days overdue on October 23. Its forecast is October 27, which is 7 days after baseline. Those figures describe elapsed lateness and expected total slip, respectively.
Handover has not reached its baseline date, yet its forecast is already 4 days late. Safety signoff has no elapsed overdue days under this date-only convention, but its forecast slips 3 days. Show these as forecast exceptions so the review can act before more commitments become overdue.
If checking the counts in Google Sheets, put baseline dates in B2:B9, actual dates in C2:C9, and the cutoff in H1. The open-overdue count is:
=COUNTIFS(B2:B9,"<"&$H$1,C2:C9,"")
Google's COUNTIFS documentation confirms that multiple criteria can be applied together. Use real date values rather than text labels, and leave the unfinished actual-date cells empty.
The milestone owner confirms the forecast and explains the blocker. The accepting owner confirms completion evidence. The project lead decides whether a missed commitment needs escalation or an approved change to the baseline.
Start the review with vendor acceptance, then the safety commitment due today, then the handover forecast. Record the next action and its owner beside each exception. If work is deliberately deferred, distinguish that decision from acceptance; the change backlog explains the separate queue of work still awaiting action.
Color can help scanning, but state the date rule behind it. See project management RAG status for status-rule calculations rather than assigning colors by judgment alone.
Covirage is not affiliated with Google.
Upload your milestone register or Google Sheet with baseline, acceptance, and forecast dates kept separate. Covirage maps the columns, its tools compute and check the figures, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own register.
See project cost control for the supporting business context.
A milestone progress view concentrates on whether agreed events happened by their planned dates. A broader project dashboard can include costs, resource use, risks, and dependencies. Use the milestone view when the immediate decision is which commitments need recovery or acceptance.
Divide accepted milestones by the eligible milestone count. State whether the denominator includes all milestones or only those due by the cutoff. Those rates answer different questions, and neither represents the percentage of total project effort performed unless you separately define effort weights.
That depends on the reporting convention. With date-only records, you can define overdue as an open milestone whose baseline date is before the cutoff date, and show today's commitments separately. State that rule so reviewers interpret the count consistently.
Keep them in separate columns. The approved baseline records the commitment, while the forecast records the current expectation. If an authorized change establishes a new baseline, retain the previous version and approval reference so the history of performance remains understandable.