Schedule health
Schedule health is whether a project schedule can be trusted to forecast its own finish date, judged by checks on its logic, constraints, float, durations, resources and progress such as the DCMA 14-point assessment.
Updated .
The rule
A healthy schedule is not the same as a project on time. A late project can have a healthy schedule that shows exactly how late it is; a project on time can have an unhealthy one whose dates nobody can trust, because they are typed in or pinned rather than driven by the links.
The DCMA 14-point assessment is the common yardstick. Each check counts one kind of problem and fails when the count passes its limit: open tasks missing a link, leads, lags, links that are not finish to start, hard constraints, high and negative float, long tasks, dates that contradict the status date, tasks without resources, tasks the baseline said would be done, a critical path that does not carry a delay to the finish, and two indexes of progress against the baseline (CPLI and BEI).
Some checks need a baseline or a status date in the file. Without them those checks cannot be assessed, which is itself a finding.
Worked example
The office move example from the example schedules (26 open tasks, 39 links, a baseline and progress to a status date of Feb 8, 2027), run through the DCMA 14-point checks. It passes twelve and fails two, both planted on purpose.
| Check | Limit | Office move | Result |
|---|---|---|---|
| 1. Logic | At most 5% of open tasks missing a predecessor or a successor | 0 of 26 | Pass |
| 2. Leads | None | 0 of 39 links | Pass |
| 3. Lags | At most 5% of links | 1 of 39 links (2.6%) | Pass |
| 4. Relationship types | At least 90% of links finish to start | 94.9% of 39 links | Pass |
| 5. Hard constraints | At most 5% of open tasks | 4 of 26 (15.4%) | Fail |
| 6. High float | At most 5% of open tasks over 44 working days | 0 of 26 | Pass |
| 7. Negative float | None | 0 of 26 | Pass |
| 8. High duration | At most 5% of open tasks over 44 working days | 0 of 23 | Pass |
| 9. Invalid dates | None | 1 of 36 | Fail |
| 10. Resources | None without | 0 of 23 | Pass |
| 11. Missed tasks | At most 5% | 0 of 10 | Pass |
| 12. Critical path test | A delay on the path moves the finish by the same amount | Moved by the full delay | Pass |
| 13. CPLI | At least 0.95 | 1 | Pass |
| 14. BEI | At least 0.95 | 1 (10 done of 10 due) | Pass |
The two failures are real problems a scheduler would fix. Four tasks carry Start No Later Than or Finish No Later Than dates from the lease and the building, three times the limit, so a delay before them would not reach the finish in full. And "Staff communications and move packs" shows progress although it is not due to start until after the status date, which makes the status date and the progress disagree.
What goes wrong in practice
- Treating health as on time: the checks ask whether the dates can be trusted, not whether they are good news.
- Fixing the count, not the plan: deleting lags or constraints to pass a check while the waiting time or the fixed date is still real.
- Running the checks once at the start and never again. Progress, late changes and rebaselining are when most problems arrive.
- No baseline or no status date in the file, so missed tasks, CPLI and BEI cannot be assessed.
- Reading the 14 checks as a score to maximise. Each failure is a pointer to tasks to look at, and some failures have good reasons.
See this in your own file
Upload an .mpp, .xml or .xer file and get the DCMA 14-point assessment of your own plan, free, beside the Health Check's own analyzers.
Run the Health Check on your own scheduleLonger read: Project Schedule Health Check: 7 Fixes to Make First
Questions
Does a healthy schedule mean the project is on time?
No. Health says whether the schedule's dates can be trusted. A healthy schedule of a late project shows how late it is, and why.
Do I have to pass all 14 DCMA checks?
Not as a rule. The assessment is a set of pointers: a failure tells you which tasks to look at, and some have good reasons, such as a fixed date set by a contract.