It's common for utility staff to use "Strategic Asset Management Plan" and "Capital Improvement Plan" almost interchangeably, and it's easy to see why: both deal with the same infrastructure, both involve years of planning, and in a lot of small utilities, one person is responsible for both. But they answer different questions, and mixing them up tends to weaken both documents.
What each document is actually for
A Strategic Asset Management Plan answers a broad question: given what we own, its condition, the service we need to provide, and what we can afford, what's our overall approach to managing this system over the next ten to twenty years? It's a framework, not a project list.
A Capital Improvement Plan answers a narrower, more concrete question: which specific projects are we funding, in what sequence, at what cost, over the next five or six years? It's a schedule, built from the priorities the SAMP establishes.
Where the confusion usually starts
The two get blurred most often when a utility builds a CIP first, out of necessity (a grant deadline, a board request, an urgent failure), without a SAMP behind it to justify why those particular projects and not others. The CIP ends up being a defensible list of individual projects, but not a defensible overall plan, and the first time someone asks "why is this project ranked above that one," there's no consistent answer because there was never a shared framework for ranking anything.
The reverse problem happens too: a utility invests in a thorough SAMP, but never translates its risk assessment and lifecycle strategies into an actual funded project schedule. The SAMP sits on a shelf as a well-produced document that never touches a budget.
How they're supposed to connect
In a working relationship between the two, the SAMP's risk assessment and levels of service produce a ranked set of priorities, not specific projects yet, just an understanding of which asset classes and locations carry the most risk relative to the service targets you've set. The CIP then translates the highest-priority items into scoped, costed, scheduled projects, sequenced against realistic funding capacity.
When a board member asks why a particular lift station rehabilitation is in year two of the CIP instead of year five, the answer should trace directly back to the SAMP: this is a high-consequence asset, its condition score reflects real deterioration, and it's tied to a level of service target the utility is currently missing. That traceability, project to priority to risk to level of service, is what makes a capital plan defensible rather than just a list.
You don't need a perfect SAMP to start connecting them
Utilities sometimes delay CIP updates waiting for a "complete" SAMP that never quite gets finished. That's usually unnecessary. Even a partial SAMP, one asset class fully assessed, a first-pass risk ranking, honestly labeled levels of service, gives you enough to start connecting specific capital projects to real evidence instead of institutional memory or whoever asked loudest. The connection between the two documents should get stronger over time, not wait for either one to be finished before it starts.