Infrastructure Projects
Project Time Overruns Analysis
Quantify schedule slippage across infrastructure projects in months against the approved programme.
Why time-overrun analysis matters
Schedule slippage on infrastructure projects delays service delivery, escalates costs through extension-of-time claims, and erodes value for money that the AGSA assesses. Measuring overrun in months across the portfolio turns vague delivery anxiety into a quantified risk register. AuditPro Core baselines each project against its approved programme so slippage is measured objectively and the worst offenders are visible immediately.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Projects Overrunning
31
37% of active
Avg Overrun
4.6 mo
▲ 0.9 mo YoY
Worst Overrun
14 mo
Within Schedule
53
63%
Average Overrun by Sector (months)
Top Overrunning Projects
| Project | Planned (mo) | Actual (mo) | Overrun (mo) |
|---|---|---|---|
| Eastside WTW Upgrade | 18 | 32 | 14 |
| Ring Road Phase 3 | 24 | 35 | 11 |
| Civic Centre Refurb | 14 | 23 | 9 |
| Substation 7 Build | 16 | 23 | 7 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Baseline programme
Overrun can only be measured against an approved baseline schedule with defined milestones. Without a frozen baseline, slippage becomes a matter of opinion rather than fact.
Causes of slippage
Delays commonly originate in late procurement, contractor underperformance, scope changes or community disruption. Categorising the cause is essential to preventing recurrence.
Cost of delay
Time overruns translate into financial overruns through standing-time, preliminaries and escalation costs. A delayed project is rarely a project delivered at the original price.
Variation governance
Legitimate extensions of time require documented approval and a revised baseline. Informal slippage without governance is both a control weakness and an audit finding.
How AuditPro Core Bridges the Gap
- Baseline lock: each project's approved schedule is frozen so overrun is measured objectively in months.
- Cause coding: slippage is tagged to its driver to inform systemic prevention.
- Exception ranking: the most-delayed projects are surfaced for management attention first.
- Traceable approvals: any schedule revision links to its authorising variation for the audit trail.
Key Takeaways
- A frozen baseline schedule is the prerequisite for measuring overrun.
- Coding the cause of delay is what enables prevention.
- Time overruns almost always become cost overruns.
- Every schedule extension needs documented approval and a revised baseline.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.