A radiologist does not read an X-ray pixel by pixel. They scan for the shapes that matter — the fracture line, the shadow that should not be there — and everything else fades into background. After two decades of tender adjudications and monthly progress reviews, I read a Primavera P6 programme the same way. The skill is not speed. It is knowing which shapes carry the diagnosis.

I was reminded of this during a competitive tender for an 8.4 km motorway widening package. Three contractors submitted programmes; two looked polished and one looked plain. The evaluation panel was leaning toward the prettiest bar chart. Ten minutes inside the actual P6 files reversed the ranking completely — the plain-looking programme was the only one with sound logic, and one of the "polished" ones was held together by fourteen hard constraints. That is what a disciplined ten-minute diagnostic buys you: the confidence to disagree with a good-looking printout.

The 5-Layer Schedule Health Check

The mindset: pattern recognition, not line reading

New planners try to read a schedule by scrolling through activities. Experienced planners read it by layer, from the structural skeleton outward to the resource load. Each layer answers a single diagnostic question, and — crucially — a failure in a lower layer makes every layer above it meaningless. There is no point analysing float on a programme whose logic is full of holes, just as there is no point reading soft tissue on an X-ray until you have confirmed the bones. That ordering is the whole method.

Layer 1 — The skeleton: WBS, milestones, data date

Begin with structure. In roughly ninety seconds you can read the work breakdown structure, locate the contractual milestones, and — most importantly — find the data date. The data date is the programme's timestamp; it tells you where actual progress ends and forecast begins. If a contractor hands you a "current" programme whose data date is six weeks stale, you are not reviewing progress — you are reviewing history dressed up as a forecast.

The WBS itself is diagnostic. A clean, discipline-based breakdown (earthworks, drainage, structures, pavement, surfacing) signals a planner who thought in terms of how the job is built. A WBS organised purely by month or by cost code often signals a programme built to satisfy a reporting template rather than to model the works.

Layer 2 — Circulation: logic and open ends

Logic is the circulation system of a programme — if it does not connect, nothing flows. Run three quick tests: count the open ends (activities missing a predecessor or successor), count the constraints, and scan for oversized lags. On the motorway tender, the losing programme had 22 open ends and 14 hard constraints. Those constraints were not scheduling — they were the planner manually forcing dates the logic could not produce on its own.

⚠ Common mistake — confusing a hard constraint with a plan. A "Finish On" constraint on completion makes the programme report the date the contractor wants, not the date the logic produces. On a marine wharf project I reviewed, removing a single completion constraint pushed the forecast finish out by nine weeks — the logic had been saying so all along, quietly, underneath the constraint.

Layer 3 — Pressure points: the critical and near-critical paths

With logic confirmed, trace the driving path. I use the Longest Path view rather than total-float filtering, because constraints distort float but not the longest chain of driving logic. Then read the path as a build narrative: "earthworks in Cut A drive drainage, which drives pavement subbase, which drives surfacing, which drives opening to traffic." On a linear project like a road, the driving path should broadly follow the chainage — if it jumps around the alignment illogically, the sequencing is suspect. See our Critical Path Method entry for the underlying theory, and near-critical path for what watches to keep alongside it.

Do not stop at the critical path. The near-critical activities — the amber bridge works above, carrying only 30 days of float — are where projects actually slip. A single wet-weather month on the bridge deck consumes that float and promotes the bridge onto the critical path. Experienced planners spend as much attention on what is about to become critical as on what already is.

Layer 4 — Vital signs: float and constraints under load

Float is the programme's blood pressure. Rather than reading single figures, read the spread. A healthy programme shows a driving path near zero, a band of near-critical work, and a broad tail of flexible activities. Two readings should trigger a closer look: negative float, meaning work is already behind its required dates, and implausibly high float, which almost always means the activity is dangling on an open end rather than genuinely flexible. On the motorway tender, one programme showed 200-plus days of float across a third of its activities — not comfort, but disconnection.

⚡ Expert tip. Add a "Total Float" column and sort ascending. The top of the list shows you what is behind (negative float); the bottom shows you what is disconnected (absurd float). Both ends of that single sorted column are where the schedule's real problems live — the healthy middle rarely needs your attention in the first ten minutes.

Layer 5 — The load: resources and cost realism

If the programme is resource- or cost-loaded, the final layer is a physical reality check. Open the resource histogram and the cost S-curve and ask one question: could this actually happen on this site? A histogram that stacks 90 pavement crew into a single week on a corridor that can safely hold 30 is not a plan — it is arithmetic. A cost curve that jumps vertically implies a month of spend compressed into days, which usually means the underlying durations are fictional. You are not auditing the loading; you are looking for the physically impossible. A schedule health checker can flag many of these signals automatically, but the physical plausibility check remains a judgement call.

Healthy vs unhealthy schedule — the signs at a glance

The five layers on a ten-minute clock

In practice the layers map neatly onto the clock. The timings below are the rhythm I settle into on a review — fast on structure, generous on logic and pressure points, because that is where the diagnosis usually hides.

The point of fixing the rhythm is not stopwatch precision — it is discipline. Without a rhythm, planners drift into the layer they enjoy most (usually the driving path) and neglect the ones that decide trust (usually logic and load). The clock keeps you honest across all five, which is exactly what makes the read reliable rather than merely fast.

Field lessons that shaped this method

• Diagnose bottom-up. I once spent an hour analysing float on a rail programme before realising the logic beneath it was riddled with open ends. The float was meaningless. Now I never skip a lower layer to reach an interesting upper one.
• A pretty bar chart is not a healthy schedule. The motorway tender taught the whole panel that polish and soundness are unrelated. Presentation lives in the printout; health lives in the file.
• Watch the near-critical, not just the critical. More projects are derailed by a near-critical bridge or tie-in eating its float than by anything already on the critical path.
• Constraints are a confession. Every hard date constraint is the planner telling you the logic could not get there on its own. Read them as admissions, not decisions.

Continue reading on PMMilestone

• Encyclopedia foundations: Critical Path Method, Near-Critical Path, Float Management, Baseline Schedule, Schedule Constraints, Work Breakdown Structure.
• Career context: Becoming a Senior Planning Engineer, How to Become a Delay Analyst, Construction Scheduler Career Roadmap.
• Practical tools: Schedule Health Checker, SPI Calculator, EVM Calculator.
• Learning support: Project Controls Academy, Learning Tracks, PM glossary.

Reading a programme in layers is less a technique than a discipline. Do it on the next few schedules that land on your desk and you will find yourself diagnosing their condition before the meeting has even settled — which is the quiet advantage an experienced planner's ten minutes really represents.