Infrastructure Projects
Stalled Project Recovery Tracker
Recovery status and elapsed downtime for projects that previously stalled on site.
Why stalled projects need active recovery
A stalled infrastructure project ties up committed funds, exposes incomplete works to deterioration and theft, and denies citizens the intended service. Stalled and blocked projects are a recurring AGSA and Treasury concern because the lost time often converts directly into cost overruns and fruitless expenditure. AuditPro Core tracks recovery status and elapsed downtime for previously stalled projects so management drives them back to delivery with accountability.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Stalled Projects
13
Remobilised
5
▲ this year
Still Idle
8
> 6 months
Value at Risk
R 624 m
Recovery status by cause
Idle projects
| Project | Downtime | Recovery action |
|---|---|---|
| Regional Library | 14 months | Re-tender underway |
| WWTW Phase 3 | 9 months | Funding re-prioritised |
| Taxi Rank | 11 months | Community MoU signed |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Stall causes
Projects stall for distinct reasons such as contractor default, funding gaps, community unrest or design failures. Recovery action must address the specific cause, so accurate classification is the first step.
Elapsed downtime
The longer a project remains stalled, the greater the cost of remobilisation and the risk of deterioration. Tracking downtime quantifies the urgency and the accumulating exposure.
Recovery plan
Each stalled project needs a documented recovery plan with actions, owner and a restart date. A project without an active plan is drifting toward write-off.
Fruitless expenditure risk
Money already spent on a project that never completes becomes fruitless and wasteful expenditure. Recovery tracking is therefore a direct control against that classification.
How AuditPro Core Bridges the Gap
- Stall register: AuditPro Core records each stalled project with its cause and date of stoppage.
- Downtime tracking: elapsed downtime is measured to quantify urgency and exposure.
- Recovery workflow: each project carries a recovery plan with owner, actions and restart date tracked to resumption.
- Escalation export: projects without progress are escalated to the accounting officer with a full audit trail.
Key Takeaways
- Classify the specific cause of each stall to target recovery.
- Quantify elapsed downtime as a measure of urgency and cost risk.
- Require a documented recovery plan with an owner and restart date.
- Treat recovery as a control against fruitless and wasteful expenditure.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.