Prioritizing Projects and Nonmonetized Impacts

Prioritizing Projects and Nonmonetized Impacts

Define the decision before ranking

A project with positive net present value can be worthwhile without being the best alternative for a site. Prioritization differs according to whether alternatives are mutually exclusive, whether projects can be combined, and whether a fixed budget constrains implementation. Specify the safety objective, eligible projects, funding restrictions, delivery limits, and mandatory requirements before constructing a ranking.

For mutually exclusive alternatives at one location, compare each alternative with a common baseline. Choosing the highest stand-alone benefit-cost ratio can favor a very small improvement even when a more substantial option produces much larger net benefits. For independent projects across a network, a ratio ranking can help screen possibilities, but indivisible costs and other constraints can make a simple greedy ranking suboptimal. The FHWA Safety Project Selection resources describe selection as part of the larger safety management process.

Incremental analysis for mutually exclusive alternatives

Suppose three mutually exclusive designs have the following illustrative present values. All use the same analysis period, valuation approach, and baseline.

A has the largest stand-alone ratio, but C has the largest net present value. If all are feasible, resources are available, and the goal is to maximize quantified net benefits, C is preferable under these assumptions. The ratio alone does not answer that decision.

Incremental analysis asks whether additional benefits justify additional costs. Moving from A to B adds $900,000 in benefits and $250,000 in costs, an incremental ratio of 3.6. Moving from B to C adds $2,000,000 in benefits and $700,000 in costs, an incremental ratio of approximately 2.86. Both increments exceed one. Compare relevant nondominated alternatives; an option costing more while producing less benefit can be discarded on these quantified measures, subject to any distinct mandatory or nonmonetized requirements.

Do not apply incremental ratios between unrelated independent projects as though only one could be built. Conversely, do not add the benefits of three mutually exclusive designs for the same intersection. Their separate estimates each compare with the same baseline, and only one design can be implemented there.

Why budget packing matters

Consider a budget of 100 illustrative cost units and three independent, indivisible projects. Project A costs 60 and produces 132 units of present-value benefit, giving a ratio of 2.2 and net benefit of 72. Projects B and C each cost 50 and produce 105 benefit, giving ratios of 2.1 and net benefits of 55 each.

A ratio-first choice selects A, but the remaining 40 cannot fund either B or C. Selecting B and C instead uses the full budget and produces 210 benefit and 110 net benefit. It beats A's 132 benefit and 72 net benefit despite the lower individual ratios. This small example demonstrates why a ranking is not a general proof of an optimal investment program. A larger portfolio can require optimization or systematic comparison of feasible combinations.

Real constraints may also reserve funds for a program, require geographic coverage, limit design capacity, or sequence dependent projects. A safety benefit may be shared by overlapping treatments, so package benefits cannot always be summed. Include interaction assumptions and avoid funding two projects that each claim the full reduction of the same crash pattern.

Make intangible impacts visible

Not every important effect can be credibly monetized with the available evidence. A median can reduce dangerous turning movements while changing access to businesses and emergency routes. A crossing project can improve accessibility and independent mobility, while a detour might disadvantage users unable to travel longer distances. Construction impacts, noise, environmental effects, community cohesion, and perceived personal security can affect acceptance and implementation.

A structured decision matrix can record those effects separately from monetized safety benefits. Define each criterion, the direction of improvement, the evidence, and any weight before seeing the preferred answer. For example, distinguish a documented accessible-route improvement from a general statement that a project is “community friendly.” Distinguish a short-term construction burden from a permanent access change. Seek input from people who experience the impacts rather than assuming a professional team represents every road user.

Weights express policy judgments. Publish them and test whether plausible alternative weights change the ranking. Adding an accessibility score does not cancel a legally applicable accessibility obligation; a mandatory requirement is a feasibility constraint. Avoid counting the same injury reduction in both the monetary benefit and a weighted safety score without explicitly explaining the decision method.

Present an actionable recommendation

Recommend a feasible option or portfolio, explain why it addresses diagnosed mechanisms, and show the economic and nonmonetized evidence. State uncertainties, funding conditions, maintenance commitments, responsible agencies, and reasons for deferring other projects. A lower-ranked treatment might still provide a useful interim measure while a larger project is designed, but reassess overlap before assigning both full benefits.

Finally, preserve the decision basis for later evaluation. If implementation costs, traffic patterns, or legal authority change, revisit the comparison. Prioritization is a transparent choice under stated objectives and constraints, not a claim that one metric captures every public value or that the first ranking remains valid forever.