RFT-CDR-08 CorridorWhere narrowing lanes alone doesn't recover enough width for a genuine protected facility, removing a full travel lane does. This is effectively a road diet whose primary purpose, rather than a secondary benefit, is the bike lane it creates. AASHTO recommends this approach specifically where a corridor's traffic volume can absorb the reduced through capacity.
Bike Highway / Greenway (COL-BHG-04), Default (No Parking, No Direct Access) (ART-DEF-01) with Protected Bike Lane / Cycle Track (ELM-PBL-37)
Follows the same volume thresholds as a standard road diet, since removing a lane carries the same through-capacity implications regardless of what the recovered space becomes. Most viable below roughly 19,000 to 25,000 vehicles per day.
FHWA reports crash reductions of up to 29 percent on road diet conversions generally; where the recovered lane specifically becomes a protected bike lane, the same crash-reduction mechanism applies alongside the added bicycling safety benefit of physical separation from traffic.12
Can move through the construction spectrum the same way a standard road diet does, restriping first, with a protected lane's physical separation elements (curbs, planters, or flexible posts) added at the quick-build stage before permanent construction. See Construction Methodology & The Build Spectrum.
Usually a city or county transportation department decision, following the same approval path as a standard road diet. See Legal & Planning Mechanisms.
Protected bike lane retrofit via lane-width reallocation (RFT-CDR-07), Protected bike lane retrofit via parking reduction (RFT-CDR-09) (the other two approaches to the same underlying goal, distinguished by where the recovered width comes from)