Reading a critical path the way an AI does.

Ask three planners to point at the critical path and you'll often get three answers. The bars highlighted red in a printout are rarely the real driver — they're whatever the tool's default settings chose to colour. The actual driver is a chain of logic, and reading it well is the difference between recovering a slip and chasing it.

Start with float, not colour

Total float is how long an activity can slip before it moves the project finish. The critical path is simply the chain of activities with the least float — usually zero. When OPTEAM parses your file, it recomputes float from the live logic rather than trusting stored values, because a single missing relationship can hide the true driver.

• Zero-float chain — the activities that move the date 1:1 if they slip.
• Near-critical paths — chains with a few days of float that become critical after one bad week.
• Float erosion — float quietly shrinking period over period is the earliest warning you'll get.

Logic quality decides everything

A critical path is only as trustworthy as the logic underneath it. Dangling activities, hard constraints standing in for missing links, and excessive leads or lags all distort float. This is exactly what a DCMA 14-point check looks for — and what OPTEAM flags automatically before it ever computes a date.

If the logic is wrong, the critical path is fiction — and so is every recovery plan built on it.

Reading it to recover time

Once the real driver is visible, recovery becomes specific instead of heroic. You protect the near-critical chains, resequence where float allows, and target the few activities that actually move the date — rather than crashing everything and burning the budget.