Project AssureA contractor hands over a Primavera P6 programme showing completion three weeks inside the contract date. Total float looks healthy, the critical path runs clean through the structure, and the monthly report is green. Six months later the job is late, the delay claim is on the table, and the same programme is being pulled apart line by line in a dispute room.
Nothing was fixed in that six months. The programme was already broken on day one: it simply took an independent audit, or a tribunal, to say so. That is the gap a Primavera P6 schedule audit exists to close: it reads what a status report cannot, before the defects harden into cost.
What is an independent Primavera P6 schedule review?
An independent schedule review is a forensic examination of the programme's logic, structure and integrity by someone with no stake in the answer. Not the planner who built it. Not the PMO that signs the monthly report. An external reviewer running a defined method against the native P6 file: activities, relationships, constraints, calendars, resources and the baseline behind them.
Owners, lenders and contractors commission one for the same reason: the number on the front page is only as good as the network underneath it. A schedule health check tests whether that network can bear weight.
What defects does a P6 schedule audit surface?
Metrics catch some of this. Judgement catches the rest. A thorough audit consistently finds:
- Broken logic, open ends, dangling activities and missing predecessors that let key work float free of the network. A programme with 3% open-ended activities is not a programme; it is a wish list with dates.
- Constraint-driven dates, "must finish on" and "start no later than" constraints propping up a completion date the logic cannot actually produce. Strip the constraint and the date moves.
- Unrealistic float, hundreds of days of total float sitting on activities that are anything but flexible, usually a symptom of severed logic rather than genuine slack.
- Resource and cost gaps, a resource-loaded programme where the histogram is physically undeliverable, or an unloaded one that cannot support earned value at all.
- Critical-path manipulation: logic quietly re-routed so the critical path runs through the party's own risk, or away from it, ahead of a claim.
The seven red flags in a P6 schedule covers the most common of these in detail. The pattern behind them is almost always the same: the programme was built to report well, not to be run.
A schedule that cannot survive an independent audit will not survive a tribunal. The only question is which one you meet first.
Why does independence change what a schedule review finds?
An in-house review checks whether the programme matches the plan the team already believes in. That is useful, and it is not assurance. The planner who embedded a "finish on" constraint to hit the contract date is not the person who will flag it.
Independence supplies two things an internal review cannot. First, no incentive to protect the number, the reviewer is paid to find the defect, not defend it. Second, method: a repeatable framework, the DCMA 14-point assessment, GAO's scheduling best practices, SCL Protocol principles, applied the same way every time, so the finding stands up when someone hostile reads it later.
What should a good P6 schedule audit produce?
A credible P6 schedule assurance mandate delivers more than a pass/fail sticker:
- A scored DCMA/GAO result, with each failing check traced to the specific activities that caused it.
- A defect register ranked by severity, what threatens the completion date versus what is cosmetic.
- A plain-English narrative a lender or board can read without opening P6.
- Clear remediation, so the next revision is fixed rather than re-papered.
When should you run a P6 schedule audit?
Three moments earn their keep:
- Baseline acceptance. Never accept a baseline you have not audited. Every defect you sign off becomes your problem at the next revision, and every claim after it.
- Monthly. A light health check each cycle catches drift, creeping constraints, quietly rebuilt logic, while it is still cheap to fix.
- Pre-claim. Before you rely on a programme in a delay claim, or before you rebut one, know exactly what a forensic reviewer on the other side will find in it.
The mechanical checks are fast. Schedule Intelligence runs the full DCMA and GAO suite against a native P6 file in about 60 seconds and flags every failing activity, enough to see whether a programme is fit to accept. A full mandate pairs that speed with expert forensic review through our project planning and controls team, so the judgement calls the metrics cannot make are made by someone who has stood behind them in a dispute. Start with the tool; escalate the moment the numbers stop adding up.