Director’s judgement
Project Controls Red Flags
The signals that tell an experienced Director to stop and look harder — before accepting a baseline, a progress figure, a recovery or a claim. Each is a real pattern from major programmes, not a textbook definition: what you see, why it matters, what I would check, and the decision it could change.
The baseline is approved, but nobody can explain the critical path.
A critical path no one owns is one no one has validated — and everything measured against it inherits the doubt.
Whether the longest path runs through real logic or through constraints and open ends.
Whether the baseline can be relied on as the control reference.
Progress is 92%, but the forecast completion date keeps moving.
Progress and completion have decoupled — either the remaining 8% is all on the critical path, or the progress is overstated.
What the last 8% actually contains, and whether it is driving completion.
Whether the forecast date can be trusted.
A recovery programme finishes earlier with no change in resources, logic or sequencing.
Recovery without a mechanism is arithmetic, not a plan — the time has been typed in, not created.
What actually changed to produce the time: method, crews, shifts, logic.
Whether to accept the recovery or reject and escalate.
The EOT narrative is detailed, but the programme impact is not demonstrated.
A story is not an entitlement; impact lives in the programme, not the prose.
Whether each event sits on the critical path to the affected milestone, in its window.
What extension is actually demonstrable.
The dashboard has thirty KPIs but does not name the decision required.
Measurement without a decision is decoration with a licence fee.
Which of the measures maps to a management action.
What to act on this cycle.
Every contractor reports progress a different way.
You cannot roll up or compare what is not measured the same way — the consolidated picture is an illusion.
Coding, calendar and progress-method consistency across contracts.
What to standardise before the next reporting cycle.
The critical path changes dramatically at every update.
A volatile critical path usually means weak logic or constraint-driven dates — not real change on the ground.
Logic integrity, constraint count, and how the path migrates.
Whether the forecast built on it is reliable.
Float is large and positive everywhere, yet the job feels late.
Implausible float almost always means missing or wrong logic, not genuine slack.
Open ends, dangling activities and lag misuse across the network.
Whether the network can be trusted at all.
The programme is updated every month but never changes a decision.
Updating is not controlling — a report that drives nothing is overhead, however neat.
Whether the update surfaces the decision it should.
What the monthly cycle is actually for.
Negative float appears, and the response is to delete the constraint.
Removing the symptom does not fix the delay — it hides it, and the slip surfaces later, larger.
What the negative float is telling you about the driving path.
Whether to act on the real slippage now.
The contractor claims time to fix an error in its own baseline logic.
A self-inflicted logic omission is not an Employer-risk event, however it is narrated.
Whether the event passes a contractual validity screen before anything else.
Whether it earns any entitlement at all.
Automation produces a clean report from a flawed control.
Automating a bad check scales the error — and wraps it in the authority of a system, so it gets questioned less.
Whether the underlying rule would be right if a good practitioner did it by hand.
What to automate, and what to keep under judgement.