Illustrative project scenario
Auditing a Primavera P6 Programme Before Contract Submission
A quality-assurance scenario for reviewing schedule logic, calendars, constraints and critical-path integrity before a formal programme submission.
Major infrastructure · Programme Audits · Construction Planning · Project Controls
The situation
An infrastructure delivery team has developed a complex Primavera P6 programme for review. The schedule appears complete, but its suitability for contract administration and ongoing control has not been independently challenged.
The challenge
Hidden open ends, excessive hard constraints, inconsistent calendars and weak progress-measurement rules may obscure the true completion path. The audit must also recognise that contract-specific programme requirements can differ.
A practical approach
Establish audit criteria
Review contract requirements, submission purpose, coding standards and planning basis before running checks.
Run technical schedule checks
Inspect logic links, open ends, constraints, calendars, milestones, lags, out-of-sequence progress and unusual float patterns.
Review delivery realism
Challenge procurement, access, commissioning, handover and resource assumptions alongside the schedule output.
Report remedial priorities
Categorise findings by materiality and propose corrective action without silently changing the submitted programme.
Illustrative deliverables
- Programme audit findings register
- Schedule-quality summary and exceptions
- Prioritised corrective-action plan
- Re-review checklist for resubmission
Key insight: A technically valid P6 file is not necessarily a reliable construction programme; the audit must test both schedule mechanics and delivery logic.
Key lessons
- Separate contractual deficiencies from technical quality issues.
- Investigate the reason for abnormal float before changing logic.
- Retain a controlled copy of each reviewed programme.