Fruitless & Wasteful
Fruitless Spend on Abandoned Projects
Fruitless spend on abandoned projects measures capital sunk into infrastructure that was never completed — investment that delivered no asset.
Why Abandoned-Project Spend Matters
An infrastructure project abandoned before completion converts capital investment into pure fruitless expenditure — money spent, no asset delivered and often a half-built liability left behind. Under the MFMA and PFMA this is fruitless and wasteful expenditure on a large scale, and AGSA consistently highlights stalled projects as a marker of poor planning and project governance. AuditPro Core tracks fruitless spend on abandoned projects so the losses are quantified, attributed and learned from rather than absorbed into the capital programme.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Abandoned projects
612
▲ 11%
Sunk cost
R9.8 bn
Avg completion
41%
Idle over 24 months
284
Sunk cost by sector (R m)
Largest abandoned projects
| Project | Spent (R m) | % complete |
|---|---|---|
| Regional water scheme A | 880 | 38 |
| RDP township B | 640 | 52 |
| District hospital C | 560 | 29 |
| Arterial road D | 410 | 44 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Abandonment as Fruitless
Spend on a project abandoned before it delivers value is fruitless because the outlay produced nothing usable. The larger the sunk cost, the larger the fruitless loss to disclose.
Root Causes
Projects stall from poor planning, contractor failure, funding gaps or scope disputes. Identifying the cause is what prevents the next abandonment, not just the next disclosure.
Sunk vs Salvageable
Not all spend on an abandoned project is lost; some work or materials may be recoverable or redeployable. Distinguishing the truly sunk from the salvageable sizes the real fruitless amount.
Accountability and Liability
Abandonment often involves contractor default or official failure that carries recovery or liability consequences. The fruitless loss should trigger that accountability, not end at disclosure.
How AuditPro Core Bridges the Gap
- Project reconciliation: AuditPro Core ties spend to project milestones so abandoned projects and their sunk cost are isolated.
- Cause classification: abandonments are grouped by root cause to inform planning and contractor controls.
- Exception workflow: abandoned-project losses route to investigation, recovery and disclosure.
- Audit-ready output: the fruitless schedule exports with the project trail for the disclosure note.
Key Takeaways
- An abandoned project turns capital investment into pure fruitless loss.
- Fix the cause — planning, funding, contractor failure — not just the disclosure.
- Separate sunk cost from salvageable to size the real loss.
- Abandonment should trigger accountability, not end at a note.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.