From spreadsheet to defensible: fixing the IP&R Report on Infrastructure Assets

~6 min read · For councils preparing the Integrated Planning & Reporting infrastructure report

The Report on Infrastructure Assets (the report many still call by its old "Special Schedule 7" name) looks like an accounting exercise. It isn't. It's where your asset condition story and your financial story have to agree — and when they don't, the gap is visible to every auditor and ratepayer who reads it.

The three numbers that cause the most trouble

1. The backlog ("cost to bring to satisfactory")

This should be grounded in the replacement cost of assets below a satisfactory condition — not an escalated future cost, and not a figure that can exceed gross replacement cost. A common error is mixing the basis: estimating backlog on one cost convention and replacement value on another, so the ratio comes out nonsensical. Pick one defensible basis and apply it consistently across every asset class.

2. The asset renewals ratio

Renewals spend ÷ depreciation. It's the headline ratio TCorp and the OLG watch, because it signals whether you're renewing assets as fast as they wear out. The trap: a renewals number pulled from the capital ledger that quietly includes upgrade or expansion work. Renewals means renewals — like-for-like restoration of service potential. Get the classification wrong and the ratio flatters or damns you for the wrong reason.

3. Required vs. actual maintenance

If you state a "required maintenance" figure, it has to come from somewhere defensible — not a fabricated percentage of asset value. If you don't have a robust basis, it is more honest (and more defensible) to mark it "data required" than to invent it. Auditors trust a stated gap more than a suspiciously round number.

The fastest way to lose credibility in this report is a number that can't be reproduced from a source. The fastest way to keep it is a clear, consistent basis applied the same way to every class.

Why the spreadsheet makes this hard

• No single basis. Different tabs, built by different people over years, quietly use different cost conventions.
• No condition scale. "Poor" means one thing for roads and another for buildings, so "below satisfactory" isn't comparable.
• No reconciliation. The condition-driven backlog and the finance-driven depreciation were never built to tie together.
• No reproducibility. Change one input and you can't re-derive the whole report — so nobody dares touch it before lodging.

What "defensible" requires

1. One condition scale across all classes (IIMM 1–5) so "satisfactory" is defined and comparable.
2. One backlog basis (replacement cost of below-satisfactory assets) applied consistently.
3. Explicit ratios — backlog ratio and renewals ratio — computed from the same dataset, not different spreadsheets.
4. Honest gaps — where council inputs (required maintenance, accounting depreciation) are needed, label them, don't fabricate.
5. Reproducibility — the whole report re-derivable from the source data on demand.

How AIPP helps

AIPP generates the Report on Infrastructure Assets from your scored data with a single, consistent basis: IIMM condition grading across every class, a backlog computed from replacement cost of below-satisfactory assets, the asset renewals ratio surfaced explicitly, and council-input fields clearly flagged rather than fabricated. Every figure is traceable, and the whole report re-derives from the data — so you can change an input and lodge with confidence.

General guidance only, not financial or audit advice. The OLG's IP&R guidelines and your auditors are the authority. AIPP content is "aligned" and validated to your council's circumstances at onboarding.