How to set pass/fail thresholds for a route-screening score

Every corridor study eventually hits the same meeting: three or five candidate alignments on the table, a shrinking survey budget, and someone asking which ones get cut before the field crews get scheduled. A screening score only earns its keep if it comes with a cutoff. A number with no threshold attached is just a ranking nobody will act on.

What's in the score before you cut anything

Most route-screening scores are a blend of three layers: land cover (what you'd have to clear or avoid), slope (what grades a given design speed can tolerate), and built-up extent (how many structures or parcels sit in the corridor). Each layer gets weighted, combined per segment or per full alignment, and rolled into a single composite number. Building that composite is the easy part for most teams. The hard part is deciding where on that scale "proceed to survey" turns into "drop it."

Set the fail conditions first, then rank what's left

The cutoff that holds up under scrutiny usually doesn't start as a single score threshold. It starts as a list of hard disqualifiers: slope exceeding what your design speed and vehicle class can handle on sustained grade, built-up density past the point where relocation costs eat the project's contingency, land cover that triggers a permitting process your schedule can't absorb. Run every candidate against those conditions first. Anything that fails one of them is out, regardless of how its composite score looks.

What's left is where a numeric cutoff actually does useful work. Among surviving alignments, rank by composite score and set a pass line based on how many candidates the survey budget can carry forward. A cutoff like 70 out of 100 means nothing on its own; it only means something once you've pinned it to that budget constraint. If the budget supports two field surveys, your cutoff sits wherever the second-best surviving score lands.

Calibrate against something you've already built

If your agency has a corridor that was built and performs fine, run it through the same scoring method before you trust a cutoff on a new study. That existing alignment should score well above whatever pass line you're proposing. If it doesn't, the weighting on one of your three layers is off, usually slope, since grade tolerance varies more by design speed and vehicle mix than most default weightings assume. This calibration step takes an afternoon and saves you from presenting a threshold in a design review that an experienced reviewer immediately flags as wrong for the terrain.

It's also worth running the reverse check: take a corridor your agency rejected for cause, and confirm it would have failed your disqualifiers. If it slides through, your hard-fail conditions are too loose.

There's no universal number

A slope cutoff that makes sense for a rural two-lane realignment will reject every option in mountainous terrain, and a built-up threshold calibrated for a bypass study will pass almost anything in an urban infill corridor. Use published thresholds from other agencies as a starting weighting, then adjust for your own design speed, terrain classification, and right-of-way costs, which set the real numbers from project to project.

None of this is easier when the land cover, slope, and built-up data live in three separate GIS layers that someone has to overlay and reconcile by hand for each candidate before the scoring conversation can even start. That's the step a constraint-scored map of candidate corridor alignments is built to skip, delivered at project start so the threshold-setting discussion happens over one combined view instead of three.

If you're staring down a set of candidate alignments and a survey budget that won't stretch to all of them, Route Selection Map is worth a look before you draw the cutoff line.