Nominal and Substantive Safety: Standards and Performance

Nominal and Substantive Safety: Standards and Performance

Separate two questions

Nominal safety asks whether a facility or design element meets the applicable design criteria and standards. Substantive safety asks about its actual or expected crash performance, including frequency, type, and severity. FHWA Road Safety Fundamentals attributes this distinction to Ezra Hauer and explains why both questions matter.

Compliance is assessed against a specified set of requirements. Standards can vary by facility, context, jurisdiction, project type, and adopted edition. A 12-foot lane is not a universal minimum for every road. A claim that an 11-foot lane is automatically nominally unsafe omits the applicable criterion and could be wrong. Identify the governing requirements before making a nominal classification.

Substantive performance is a continuum. It cannot be reduced to “safe” merely because a site has no recent crashes, nor to “unsafe” after one event without context. Use appropriate periods, exposure, crash definitions, peer comparisons, and models. A site can comply with criteria yet have a severe turning-conflict pattern requiring action.

Understand the four possible combinations

The following teaching matrix illustrates the relationship. It is not a universal ranking of facility types or a statement that one geometric feature determines performance.

“Relatively favorable” means favorable under a defined comparison, not absence of risk. For example, a lower-than-peer injury rate may coexist with a large number of injuries because exposure is high. Conversely, a very low count on a lightly traveled road may coexist with an elevated rate. The substantive conclusion depends on the safety question.

A standards revision can change a nominal classification even if the physical facility and its crash performance remain unchanged. A change in traffic or land use can change substantive performance without changing the original geometry. These examples show why the concepts should be tracked separately.

Diagnose the mechanism rather than the label

Suppose an intersection meets its applicable sight-distance and lane criteria but experiences repeated serious injuries during permissive turns. Nominal compliance does not explain away the pattern. Investigate approach speeds, gaps, turning volumes, pedestrian crossings, visibility, phasing, and crash records. Potential responses should fit the mechanism and applicable operational requirements.

Now suppose an existing urban street has a constrained lane width and relatively low severe-crash frequency. That history does not waive a legal requirement or establish that every similar narrow lane is appropriate. Assess the applicable criteria, users, speeds, freight and transit needs, accessibility, and uncertainty. If an exception process applies, use it transparently rather than assuming either automatic reconstruction or automatic exemption.

Perceived safety adds another dimension. People may avoid a route or crossing, leaving low recorded crashes partly because exposure is suppressed. Community input and observation can reveal needs not visible in totals. Combine those findings with substantive evidence and nominal requirements rather than treating any one measure as complete.

Design exceptions require a reasoned process

A formal design exception may be required when a project cannot meet an applicable controlling criterion. Requirements depend on the facility, criterion, and responsible approval authority. Not every departure from a recommendation has the same formal process. Verify current federal and state rules for the project rather than declaring that all noncompliance requires one identical approval.

Document the constraint, alternatives considered, operational and safety implications, applicable standards, mitigation, and approval. Quantitative analysis can help estimate consequences where suitable models and CMFs exist. Explain limitations when the model does not represent the proposed feature or users well. A nominal deficiency should not be justified by a poorly matched SPF merely because it produces a reassuring number.

An approved exception is a documented decision under the governing process, not a blanket legal-liability waiver or guarantee against injury. Agencies should preserve the analysis and monitor performance. Design standards and professional judgment remain relevant while substantive evidence helps assess the actual consequences of alternatives.

Use performance-based decisions responsibly

Performance-based practical design considers objectives, constraints, and expected outcomes when choosing feasible improvements. It can help avoid consuming a large budget to correct a nominal feature with little demonstrated benefit while more effective safety opportunities remain elsewhere. It does not mean that standards are optional or that financial efficiency overrides mandatory requirements.

Compare alternatives on expected crash changes, severity, operations, accessibility, cost, maintenance, and community impacts. A treatment may improve one outcome while worsening another; show those changes rather than using a single “safe” label. Use appropriate economic appraisal and budget prioritization methods when projects compete for resources.

For RSP1 scenarios, the key skill is recognizing what evidence supports each claim. A statement about lane width relative to an adopted criterion supports a nominal assessment. A statement about expected injury crashes supports a substantive assessment. A complete decision uses both and investigates why performance differs from expectations before selecting a treatment.