Skip to content
Kairos OneBook a demo
Menu
Intermediate · 2 min read

Schedule quality

Whether a schedule can be trusted as a forecast — judged from its mechanics, not its promises.

Working definition

Schedule quality is the degree to which a schedule’s mechanics — its logic, durations, constraints, and statusing — support the dates it prints. It is deliberately a different question from "is the project on time." A schedule can show an on-time finish and be mechanically rotten, which means the on-time finish is fiction. Quality is what a reviewer checks first, because every other analysis inherits it.

Key takeaways

  • The core checks are consistent across the industry: open ends (activities missing predecessors or successors), the share of non-finish-to-start relationships, long or unlabeled lags, hard constraints overriding logic, unusually long durations that resist statusing, invalid or out-of-sequence progress, and float values at implausible extremes.
  • Constraints pin dates in place while the logic underneath falls apart; missing logic lets delayed work float free instead of pushing the finish; progress override hides the consequences of out-of-sequence work.
  • Delay analysis, earned value, risk simulation — all of it computes on top of the network.
01

The mechanical checks

The core checks are consistent across the industry: open ends (activities missing predecessors or successors), the share of non-finish-to-start relationships, long or unlabeled lags, hard constraints overriding logic, unusually long durations that resist statusing, invalid or out-of-sequence progress, and float values at implausible extremes. Each is mechanical — countable from the file, no judgment required.

02

Why a bad schedule can still show "on time"

Constraints pin dates in place while the logic underneath falls apart; missing logic lets delayed work float free instead of pushing the finish; progress override hides the consequences of out-of-sequence work. In each case the software reports the date it was steered to, not the date the network supports. This is why "the finish didn’t move" is never, by itself, good news.

03

Quality before analysis — always

Delay analysis, earned value, risk simulation — all of it computes on top of the network. Run them on a low-quality schedule and you get precise numbers about a fiction. The reviewing discipline is strict ordering: establish that the update is mechanically credible, then let it into the analytics. An owner-side review that grades every submission on the same checks, every period, makes that ordering automatic.

Sources and scope

Follow the reference trail.

This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.

Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01Checking schedulesOracle · checked 2026-08-01UFGS 01 32 01.00 10: Project ScheduleWhole Building Design Guide / U.S. Department of Defense · checked 2026-08-01Recommended PracticesAACE International · checked 2026-08-01