How to read a schedule health score
A schedule health score tells you more than just a number. Here is how to interpret the result, which checks matter most, and what to fix first.
The Schedule Health Score is a 0-to-100 composite number computed from 17 structural checks run on your schedule file. It is not a project forecast. It is a diagnostic: a structured way to measure how well your schedule is built, not how well your project is going.
What the score ranges mean
Good
The schedule is structurally sound. Most or all of the critical checks pass. The schedule can be managed and updated as the project progresses. Focus on the specific failures, if any, and prioritize by weight.
Watch
The schedule has meaningful structural problems. It may still be manageable, but the float calculations are suspect and the finish date prediction is unreliable. Fix the high-weight failures before using this schedule for decision-making.
Needs work
The schedule has critical structural problems. It should not be submitted for review or used as the basis for project decisions until the major failures are fixed. Start with any check showing negative float or hard constraints above 5%.
How the score is calculated
Each of the 17 checks has a raw point value. Logic and Critical Path Test are weighted most heavily at 12 points each. Hard Constraints and Negative Float are 10 points each. Other checks range from 4 to 8 points. If a check returns Not Applicable (for example, Resources returns N/A when the schedule is not resource-loaded), that check is excluded from the denominator so it does not unfairly penalize the score.
The score is computed as: points earned divided by points possible (excluding N/A checks), multiplied by 100. See the full weight table.
What to fix first
The report ranks failures by weight. Start with the highest-weight failures. In order of priority:
- Negative float — zero-tolerance, 10-point weight. This means the schedule already predicts a late finish. Fix the constraining dates before anything else.
- Missing logic (Logic check) — 5% threshold, 12-point weight. Open-ended tasks make float unreliable everywhere. Fixing these often improves the critical path test and CPLI as a side effect.
- Hard constraints — 5% threshold, 10-point weight. These are usually the cause of negative float. Review each flagged task and replace the constraint with logic where possible.
- Critical Path Test — 12-point weight. If this fails, the network is broken. Trace the break in the Network Diagram view.
- CPLI and BEI — 7 points each. These are performance indicators. A low CPLI is a reliable predictor of late finish. A low BEI means you are already behind baseline.
Limits of the score
The score measures structural health, not project reality. If your schedule has accurate logic, realistic durations, and current data dates but is still heading for a late finish, the score may be high even as the project struggles. The score reflects what is in the file. If the file does not reflect reality, the score does not either. This is why schedule hygiene and regular progress updates matter as much as the structural checks.
Frequently asked questions
My schedule scored 72 but I know it has problems. How is that possible?
A score of 72 means most structural checks pass. If you know there are problems, check whether they are in the structural layer (logic, constraints, float) or the content layer (scope is wrong, durations are guesses, resources are not realistic). Structural checks can only assess what is structurally measurable in the file.
What is a target score before submitting a schedule for review?
There is no universal standard, but as a practical threshold: 70 or above before any external review, and 85 or above for a DCMA or agency review where the methodology will be scrutinized. Below 70 means you have structural problems that a reviewer will find.
Can I re-score after making fixes?
Yes. Every upload is a fresh analysis. There is no limit on free re-scoring. Make your fixes in Microsoft Project, export the updated file, and run it again to see the improvement.