I've read a lot of council Asset Management Plans. Most look similar on the surface. Very few hold up the same way once you look past the executive summary.
Here's what separates the two — without naming names, because the pattern matters more than any single council.
What good looks like
The AMP defines service levels in terms the community would recognise — not just engineering standards. Condition data is current, covers the full asset base, and is dated. Renewal need is calculated from condition and remaining life, not from a flat percentage of replacement cost. The renewal program in the AMP matches the capital figures in the LTFP, line for line. And there's a documented review cycle that's actually been followed.
The warning signs
A renewal forecast that's a straight line for ten years. Real asset portfolios don't deteriorate in a straight line — a flat forecast usually means nobody has modelled it.
Condition data with no date attached, or condition data covering some asset classes and not others. If roads were assessed in 2019 and buildings were never assessed, the backlog figure built from that data isn't a number — it's a guess with decimal points.
Service levels copied from a template, with no link back to what residents actually experience. If the AMP says "maintain roads to an acceptable standard" without defining what that means in practice, it isn't a service level. It's a placeholder.
An AMP and an LTFP that don't reconcile. When the ten-year renewal figure in the AMP doesn't match the capital works line in the financial plan, one of the two documents is wrong — and usually neither has been updated to catch it.
None of these are failures of effort. They're usually the result of a plan built once, under time pressure, and never revisited with fresh data. The fix isn't a full rewrite — it's an honest audit of these four points, one at a time.