What a no-build alternative does in route screening

Every environmental document for a highway or transmission corridor carries one alternative that never gets built: the no-build alternative, sometimes called the do-nothing alternative. If you've scoped a NEPA document or sat through a scoping meeting, you've seen it sitting at the top of the alternatives table, usually described in two sentences and then never discussed again. That brevity is deliberate, and it's worth understanding why before you start scoring your actual candidates.

What the no-build alternative is for

The no-build alternative describes what happens to the corridor, the intersection, or the interchange if the agency does nothing beyond routine maintenance. No new pavement, no new right-of-way, no realignment. It's the baseline against which every build alternative gets measured for impacts to land cover, traffic operations, noise, and everything else in the resource chapters.

NEPA requires it because an EIS or EA needs a fixed reference point. Existing conditions, carried forward with routine maintenance only, give the environmental cost and benefit of building something a baseline to measure against. FHWA guidance treats it the same way: it's rarely a serious contender for selection in capacity or safety projects, but it has to be carried through the full analysis so the document can defend its comparisons.

This is where it gets confusing for people doing field-level work. The no-build alternative is a documentation requirement, not a design exercise. Nobody is drawing slope contours or flagging wetland boundaries for "nothing." It exists in the text and the comparison table, not in your GIS layers. If you're running an alternatives analysis for highway design and you find yourself trying to generate a constraint score for no-build, you've misread what the alternative is doing in the document.

Where the real work happens: scoring the build alternatives

Comparing the build alternatives against each other determines which corridor gets surveyed, which gets a preliminary design, and which gets dropped from the document. That's where land cover, slope, and built-up footprint earn their keep as screening criteria. A corridor that threads through forested slope versus one that clips three parcels of built-up land reads very differently once you lay those masks side by side, and that comparison is what survives into the Section 4(f) discussion, the purpose-and-need justification, and eventually the preferred alternative.

This is also where a lot of time gets burned early in a project. A design team pulls county land cover data, a DEM for slope, and whatever parcel or building footprint layer is on hand, then builds the overlay by hand for each candidate alignment separately. Three candidates means three manual overlays, three sets of judgment calls about where the constraint bands sit, and three chances for the overlays to disagree with each other because they weren't built the same way. None of that touches the no-build alternative. All of it determines which build alternatives are worth taking to survey.

That's the gap Route Selection Map is built for: a constraint-scored view of your candidate alignments, combining land cover, slope, and built-up masks from high-resolution satellite imagery, delivered as a single comparable scoring layer at project start instead of three separate overlays assembled by hand. It doesn't touch the no-build narrative in your document. It's there for the part of the alternatives analysis where you're ranking real corridors against each other before anyone commits survey budget.

A quick way to keep the two straight

The no-build section answers "what happens if we do nothing," and that answer lives in the document text. The build-alternative comparison answers a different question: which of these three alignments crosses less steep ground and fewer built parcels. Constraint scoring handles that second question. Keeping the two separate saves a surprising amount of back-and-forth with reviewers who ask why no-build doesn't have a GIS layer in your appendix. It doesn't need one. It never did.

If you're at the stage of ranking candidate alignments before committing to field survey, take a look at how Route Selection Map scores them.