When a marked crosswalk alone is not enough

Paint-only crosswalks on higher-speed, multilane roads can be worse than nothing — the multiple-threat crash (one car yields, the next lane doesn’t) is the classic failure. FHWA’s STEP research is the citation: as speed, lane count, and volume rise, the crossing needs escalating treatment, not just fresh thermoplastic. On anything beyond a 2-lane low-speed street, run the selection logic before recommending “install crosswalk.”

STEP selection logic

The Guide for Improving Pedestrian Safety at Uncontrolled Crossing Locations (FHWA STEP program) has the selection matrix. Three inputs, one escalating output menu:

  1. Posted speed — the dominant variable; higher speed pushes you toward PHB/signal territory.
  2. Number of lanes (and whether a raised median exists) — more lanes crossed without refuge = multiple-threat exposure.
  3. Volume (AADT) — higher volume = fewer gaps, more driver-yielding failure.

Menu, roughly cheapest→heaviest: high-visibility crosswalk + advance signs/yield markings + lighting → raised crossing island / median refuge (halves the crossing problem; pairs with everything) → RRFB → PHB → full pedestrian signal (only where MUTCD signal warrants are met) → road diet (4→3) as the geometric fix that makes the cheaper devices viable again.

Warning

Do not quote speed/lane/AADT breakpoints from memory — pull the current STEP matrix tables AND check FDOT TEM guidance before naming a device in a report. #status/verify current STEP tables and TEM section for enhanced/midblock crossings (FDOT adds state-specific criteria and district review steps on the SHS).

Device notes

  • RRFB — rapid-flashing warning beacon supplementing crossing signs; pedestrian-actuated; drivers still yield under normal rules. Now codified in MUTCD 11th Edition, Part 4 (formerly FHWA Interim Approval) #status/verify chapter number in current edition (Rev 1, Dec 2025).
  • PHB (pedestrian hybrid beacon) — dark until actuated, then yellow→red; legally stops traffic. The step up when speed/lanes/volume exceed RRFB territory. Also governed by MUTCD 11th Edition, Part 4 #status/verify chapter + placement criteria.
  • Full signal — requires an MUTCD pedestrian signal warrant analysis; don’t promise one because a resident asked.
  • Refuge island / road diet — geometric companions, both FHWA Proven Safety Countermeasures; often the real answer when devices alone can’t overcome exposure.

Tip

Get the matrix and per-device tech sheets free from the STEP resources page; PEDSAFE walks the same guide interactively from crash type inputs.

Write-up habit

State inputs (posted speed, lanes, median, AADT), state the matrix cell, state the recommendation, cite the guide edition. One paragraph, defensible.

See also: How to Summarize 5-Year Crash Data · How to Pull Crashes from Signal Four Analytics · Countermeasure Selection and CMFs