What Is Construction Schedule Health? A Practical Guide for Commissioning Teams

"Schedule health" gets thrown around in project meetings without much agreement on what it actually means. For most teams it ends up meaning "did anything obviously slip," which catches the loud problems and misses the quiet ones — the logic gap that's been sitting unnoticed for three weeks, the milestone with more float than it should reasonably have, the baseline nobody's updated since the schedule was still mostly theoretical.

Schedule health vs. Schedule Performance Index

Schedule Performance Index (SPI) is the formal earned-value metric — earned value divided by planned value — that most project controls teams already track. An SPI of 1.0 means you're exactly on plan; below 1.0 means behind. It's a useful single number, but it's a lagging indicator: SPI tells you that something's off, not why, and it can hide as much as it reveals when it's averaged across a whole program.

Schedule health is the broader diagnostic underneath SPI — the structural checks that explain why the number is moving the way it is, and that catch problems before they show up in SPI at all. A schedule can have a perfectly fine SPI today and still be unhealthy in ways that guarantee it won't stay that way.

What schedule health actually checks for

Logic gaps. Activities with no predecessor or successor — meaning nothing is actually driving when they happen. In P6 or MS Project, these are easy to create by accident (a copy-pasted activity, a broken link during a schedule revision) and easy to miss unless you're specifically looking for them.

Excessive float. An activity with 90 days of float on a 120-day project isn't "ahead of schedule" — it's usually a sign the logic tying it to the rest of the plan is wrong, or that it was never really tied to a critical path in the first place.

Missing or stale baselines. If the baseline hasn't been updated since early planning, every variance calculation downstream of it — SPI included — is comparing today's reality to a plan that no longer resembles the actual project.

SPI and variance trend. A single SPI snapshot tells you position, not direction. A program at 85% complete against an 87% plan looks fine in isolation; the same program trending downward for three consecutive schedule pulls is a different story.

Why this breaks down in a spreadsheet

None of these checks are hard to run once. The problem is they're not a one-time check — they need to happen every time the schedule updates, across every system in the program, and the answer needs to reach the people managing the work fast enough to matter.

A spreadsheet can hold last week's SPI. It can't tell you a logic gap just appeared in this week's P6 update, because nobody's manually re-auditing schedule logic every time a scheduler pushes a revision. By the time a stale baseline or a broken dependency gets noticed, it's usually because something visibly slipped — which means the schedule was already unhealthy for however long it took someone to notice.

The other failure mode is scale. Checking logic and float by hand across ten systems is tedious but doable. Across two hundred systems on a critical infrastructure project, it's not realistic for a person to do reliably every week, which means it quietly stops happening — right around the point where the risk of an unnoticed problem is highest.

A practical checklist for your next schedule pull

If you're doing this manually for now, here's the minimum worth checking on every update:

1. Pull the list of activities with no predecessor or successor and review each one — don't assume the scheduler caught them all.
2. Flag any activity with float significantly above the program average and ask why.
3. Confirm the baseline date and compare it to the current schedule revision date — if it's more than a few weeks old on an active program, treat SPI and variance numbers with caution.
4. Track SPI trend across at least three schedule pulls, not just the current snapshot.
5. On a commissioning program specifically, cross-reference schedule slippage against open issues and incomplete checklists for the same system — a schedule slip with no corresponding open issue is often a sign the schedule, not the work, is the problem.

How CxLens automates this

CxLens's Schedule Health view runs these checks automatically against every uploaded P6 or MS Project schedule — logic gaps, float outliers, and baseline currency, alongside SPI and variance trends pulled from live schedule data. It's built to catch what a weekly manual review would eventually find, without needing someone to find the time to run it. Pair it with Schedule Connection and the same variances that show up in schedule health automatically surface against the specific commissioning activities and systems they affect.