How to prioritize resurfacing projects on a fixed annual budget
Every pavement engineer hits the same wall each budget cycle. The resurfacing list is twice as long as the tonnage you can place this season, and the number got locked in months before anyone finished rating the roads. Whatever didn't get surveyed by the time the spreadsheet froze just doesn't get considered. That's just whoever the windshield crew happened to drive past this season, dressed up as a priority list.
If you're trying to figure out how to prioritize resurfacing projects on a fixed annual budget, the honest answer is that you can't do it well without a complete picture of the network first. Partial data produces a partial list, and a partial list means segments with real distress sit untouched for another year while something a councilmember complained about jumps the queue.
Rank by distress, not by who called
A defensible resurfacing programme ranks segments the same way, using the same criteria, across the whole network, every year. That sounds obvious until you look at how most programmes actually get built: a mix of recent complaint logs, whatever the last windshield survey caught, a few segments nobody's rated since the last term-limited director retired, and one or two projects that got added because a council member drove over them.
The fix is consistent inputs: cracking, ravelling and patching extent, scored the same way on every mile of the network. That means every segment gets a condition score, including the ones a windshield crew never had time to reach this year. Once you have condition classes assigned by segment across the whole system, worst-first sorting is a formula, not a committee meeting. A network map with condition classes by segment and a ranked candidate list is exactly what you need before the first budget conversation, and it's the deliverable Road Surface Condition builds from an annual aerial or satellite pass.
Where the money goes once you have a ranked list
With a complete, consistently-scored network in hand, pavement management budget allocation stops being a negotiation and starts being arithmetic. You know your resurfacing budget covers, say, 40 lane-miles this year. You have a ranked list of several hundred candidate segments. You start at the top and work down until the tonnage runs out.
A few things usually shake loose once engineers do this for the first time. Segments that "felt fine" from a drive-by turn up mid-list because ravelling had spread further than anyone clocked from a truck window at 45 mph. Segments that generated complaint calls turn out to be cosmetic rather than structural, and drop several spots once they're scored against the rest of the network instead of judged in isolation.
The ranked list also survives a change in council or a new director. When someone asks why segment 14B got resurfaced before segment 22A, the condition class on file is the answer.
What this doesn't fix
A ranked list doesn't change how much money you get. It doesn't account for a watermain project scheduled for next spring that's going to tear up a segment regardless of its crack rating, and it won't catch a drainage failure that happened last week. Coordination with utilities and capital projects is still a separate conversation, and it should happen after the condition-based ranking, as an adjustment to it.
What it does fix is the starting point. Build the resurfacing programme from a complete picture of the network, scored the same way everywhere, updated on the same schedule every year, instead of from whichever segments happened to get surveyed or whoever complained loudest.
That's the whole case for moving resurfacing programme prioritisation off the windshield survey and onto an annual, network-wide read of condition. If your list is currently built from a mix of memory, complaints and whatever got driven this year, Road Surface Condition is built for exactly that gap, and it's worth a look before next year's budget cycle starts.