By the time most utilities sit down to build a capital improvement plan, there's already a list of candidate projects in someone's head, the main that keeps breaking, the lift station that alarms every storm, the tank a consulting engineer flagged in a report five years ago. The temptation is to start ranking those projects immediately. It's worth resisting that temptation long enough to answer five questions first.

1. What are we actually trying to achieve?

Before any project gets evaluated, it's worth being explicit about what the CIP is supposed to accomplish. Reducing main breaks in a specific corridor? Meeting a new regulatory requirement? Supporting planned growth? A CIP built without a stated purpose tends to default to "whatever gets requested loudest," which is a fine way to fund squeaky wheels and a poor way to manage a system.

2. What do we actually know about asset condition, and what are we guessing at?

Every CIP is built on some mix of hard data and reasonable assumption. The question worth answering honestly is which is which. If a project is justified by "this main is old and in a neighborhood with a lot of breaks," that's a reasonable planning assumption, but it's a different kind of evidence than an actual condition assessment, and it's worth knowing the difference before defending the ranking to a board.

3. How are we comparing projects that don't look like each other?

Ranking a lift station rehabilitation against a water main replacement against a new SCADA upgrade is difficult because the projects don't share an obvious common unit. A consistent scoring approach, one that weighs consequence of failure, likelihood of failure, and service impact the same way across asset types, is what makes it possible to compare genuinely different projects on the same list without the ranking just reflecting whoever built the strongest slide deck.

4. What can we actually afford, and over what period?

A CIP that lists more projects than a utility can plausibly fund over the planning period isn't a plan, it's a wish list with dates attached. Before ranking projects, it's worth having a realistic picture of funding capacity: rate revenue, debt capacity, likely grant or loan sources, so the CIP reflects a sequence that could actually happen rather than an order of preference with no bearing on what gets built.

5. What happens if we don't do this project, and by when?

This is the question that separates urgent projects from important-sounding ones. A project that genuinely can't wait usually has a clear answer: continued deterioration leads to a specific, describable consequence within a specific timeframe. A project that's been on the list for years without a clear answer to this question is worth re-examining, it may belong further down the list than its position suggests, or it may belong in the SAMP's longer-term strategy rather than the near-term CIP at all.

Why this matters more than the ranking method itself

Utilities sometimes spend more energy debating scoring methodologies (weighted criteria, risk matrices, point systems) than answering these five questions honestly first. The scoring method matters less than most people assume. A simple, consistently applied method built on honest answers to these questions will produce a more defensible CIP than a sophisticated method built on assumptions no one examined closely.