--- title: "Industrial Collector" url: "https://commonwaysystem.org/patterns/collectors/industrial-collector/" id: "COL-IND-03" description: "A Collector Typology serving industrial land use, where freight movement outranks vehicle, pedestrian, bicycle, and transit priority." updated: "2026-09-26" --- # Industrial Collector `COL-IND-03` Recommended Collector Industrial Collector A Collector road serving warehouses, freight yards, or manufacturing land use, designed around truck movement and loading rather than the base Collector priority order. Typical at: Suburban Compact Urban Undeveloped, Rural, and Core are edge cases. ## Speed and modal hierarchy Design speed & speed limit \[SPEED LIMIT 30\] Follows the Collector default: 30 mph standard. Freight priority in the modal hierarchy below does not change the vehicle speed cap. See [Design Speed & Speed Limits](https://commonwaysystem.org/guide/design-speed.md). Modal hierarchy Freight > Vehicle > Pedestrian > Bicycle > Transit An override justified because the Typology's stated purpose is freight movement to and from industrial land use. ## Layered guidance across sources The Commonway System column comes first: it is the answer. The four columns after it show the layered sources it was built from. Open gaps are marked in the cells rather than guessed at. Industrial Collector design guidance by source, from the Commonway System answer through federal and state baseline, NACTO, Complete Streets, and Dutch practice ### Travel lane width #### Commonway System **12 ft.** 12 ft. Truck volume is the reason: this is the width freight movement needs, not a rural or comfort-driven choice. #### Federal / State baseline **10 to 12 ft; 12 ft in industrial zones.** 10 to 12 ft depending on volume and speed, with industrial zones specifically built to 12 ft where truck volume is significant. Portland's industrial-zone cross-section uses two 12 ft travel lanes.[1] Minneapolis names the WB-62 design vehicle for highly industrialized streets.[2] #### NACTO enhancement **Not applicable at these volumes.** NACTO's general guidance narrows lanes where feasible, but notes 10 ft lanes still support truck uses only at 35 mph and under. Industrial Collector truck volumes exceed that threshold, so the narrowing guidance does not carry over.[3] #### Complete Streets layer **Not specified.** Not specified in the typical-elements list. #### Dutch / Sustainable Safety **Not researched.** Not researched. ### Number of travel lanes #### Commonway System **Two lanes, plus turn lanes as needed.** Two lanes, one each way, with additional turn lanes as needed at intersections to accommodate slow-turning trucks. #### Federal / State baseline **Two to four lanes, plus turn lanes.** Two to four lanes are typical for industrial roads, with additional turning lanes as needed.[4] #### NACTO enhancement **Not researched.** Not researched. #### Complete Streets layer **Not specified.** Not specified in the typical-elements list. #### Dutch / Sustainable Safety **Not researched.** Not researched. ### Bicycle facility #### Commonway System **Required within a 3 mi bike / 0.5 mi walk catchment; must be physically separated.** A bicycle facility is required, not contingent on a master plan naming this corridor, whenever any population that could plausibly use this street segment for any purpose falls within a 3-mile bicycle catchment or a 0.5-mile pedestrian catchment of it.[22] Measure the catchment against the street segment as a whole, not against any single business or job site along it. This is public right-of-way, and the relevant population is whoever could use it, not only people employed at adjacent industrial land uses.[22][24] Only in the genuine edge case, an isolated segment with no population within either catchment at all, does the facility become context-dependent rather than required. Once required, it must be physically separated, not a painted or buffered-only lane, per the Separation / buffer row below. #### Federal / State baseline **FTA 0.5 mi walk / 3 mi bike distances; FHWA selects by context, not plan status.** FTA's adopted eligibility policy treats pedestrian improvements within one-half mile, and bicycle improvements within three miles, of a public transportation stop or station as having a de facto relationship to public transportation. Those are transit-funding thresholds, and this page borrows the same distances as its catchment.[22] Separately, FHWA's Bikeway Selection Guide selects bikeway facility type from roadway speed and volume, truck mix, and land use context, not from whether a corridor appears in an adopted bicycle plan.[23] #### NACTO enhancement **Coordinate truck and bike routes up front.** Truck route designation should be coordinated with bicycle network mapping up front, rather than resolved after the fact. Bollards are recommended at truck-route corners because of a documented pattern of truck wheels overrunning curbs and striking people nearby.[6] Seattle's freight standards go further: a protected bicycle lane is recommended where a bicycle facility is planned on a truck street, though the standard's first preference is routing the bicycle network away from major truck streets where an alternative exists.[13] #### Complete Streets layer **Not specified.** Not specified in the typical-elements list. #### Dutch / Sustainable Safety **Not researched.** Not researched. ### Pedestrian facility #### Commonway System **Sidewalk both sides, about 6 ft.** Sidewalk on both sides, roughly a 6 ft pedestrian through-zone, with a minimal (roughly 0.5 ft) frontage zone. Driveway and curb-cut count is the real design lever here, not sidewalk width. #### Federal / State baseline **PROWAG width applies.** PROWAG's general minimum access-route width applies regardless of adjacent land use.[7] #### NACTO enhancement **Not researched.** Not researched. #### Complete Streets layer **Not specified.** Not specified in the typical-elements list. #### Dutch / Sustainable Safety **Not researched.** Not researched. ### Speed management #### Commonway System **30 mph, unchanged from base Collector.** 30 mph, unchanged from the base Collector rule. See [Default (Standard Collector)](https://commonwaysystem.org/patterns/collectors/default.md). #### Federal / State baseline **Design speed equals posted speed.** FHWA's design-speed-equals-posted-speed framework, the same source cited across this publication.[8] #### NACTO enhancement **Narrower lanes calm traffic.** The same logic as Default (Standard Collector): narrower lanes calm traffic. Here that logic is limited by the 12 ft truck lane width above, so speed is held by the 30 mph rule and geometry at intersections instead. #### Complete Streets layer **Not specified.** Not specified in the typical-elements list. #### Dutch / Sustainable Safety **Not researched.** Not researched. ### Intersection treatment #### Commonway System **Local: stop control. Collector or Arterial: roundabout.** **Meets a Local street** Stop / Yield on the Local approach. Low volume does not justify a roundabout. The curb radius on the Industrial Collector's own approach still follows freight-street sizing, not a normal Local-street radius, since the truck is still turning even where the cross street is minor.[9] **Meets another Collector** A [Roundabout](https://commonwaysystem.org/patterns/intersections/roundabout.md) is preferred, sized per NCHRP Research Report 1043's current large-vehicle guidance with a truck apron for the occasional oversize check vehicle. The everyday design vehicle should clear the roundabout without off-tracking onto the apron.[10] Confirm actual vehicle-classification counts before defaulting to the largest conceivable design vehicle everywhere. Oversizing has its own safety and cost consequences.[11][12] **Meets an Arterial** A [Roundabout](https://commonwaysystem.org/patterns/intersections/roundabout.md) is preferred, with a [Signal](https://commonwaysystem.org/patterns/intersections/signal.md) only where volume genuinely warrants one, the same logic as Default (Standard Collector). Size it at the higher end, since both legs likely carry freight designation. **Meets a Freeway** Not applicable. A Collector does not connect to a Freeway at grade. That is an interchange condition and belongs to [Grade-Separated Interchange](https://commonwaysystem.org/patterns/intersections/grade-separated-interchange.md). #### Federal / State baseline **NCHRP Research Report 1043.** NCHRP Research Report 1043 is the current national roundabout guide and supersedes NCHRP Report 672.[10] #### NACTO enhancement **Design vehicle vs. check vehicle.** NACTO separates the design vehicle from the check vehicle, and favors rerouting truck routes over reconstructing a corner to fit the largest possible truck.[6] #### Complete Streets layer **Not specified.** Not specified in the typical-elements list. #### Dutch / Sustainable Safety **Not researched.** Not researched. ### Separation / buffer between modes #### Commonway System **Physical separation required: 3 ft minimum buffer plus a durable vertical element, not paint alone.** Physical separation is required on this Typology, not merely preferred: a minimum 3 ft buffer plus a durable vertical element (a curb, planter, or bollard), not a painted line alone, and not flexible delineator posts alone given the truck volumes this street carries. This is not a sliding scale on this page. Industrial Collector's speed is fixed at 30 mph (see Speed management above), and FHWA's bikeway-selection guidance calls for a fully separated facility once a street's speed and volume reach roughly 30 mph and/or approximately 7,000 vehicles per day.[23] A Collector carrying freight-level truck volume meets or exceeds that threshold as a matter of course, so there is no lower tier of separation available on this Typology to fall back to. #### Federal / State baseline **FHWA: full separation above ~30 mph / ~7,000 vpd; 3 ft minimum buffer, curb, planter, or bollard.** FHWA's Bikeway Selection Guide generally recommends a separated bike lane or shared-use path, not a painted or buffered-only lane, once a street's motor vehicle speed and volume exceed roughly 30 to 35 mph and/or approximately 6,000 to 7,000 vehicles per day.[23] FHWA's separate Separated Bike Lane Planning and Design Guide sets a 3 ft minimum buffer width for maneuvering and door-opening clearance, and documents curbs, planters, bollards, and flexible delineator posts as vertical-element options, with a 3 inch mountable curb as the standard detail where street-sweeper access is needed.[5] #### NACTO enhancement **Setback stop bars; bicycle signal phasing.** Seattle's freight standards describe stop bars that can be set back from the intersection and crosswalk to leave room for a turning truck's swept path, and bicycle signals that can separate bicycle and truck movements in time. Both are offered as design tools, not requirements.[13] #### Complete Streets layer **Not specified.** Not specified in the typical-elements list. #### Dutch / Sustainable Safety **Not researched.** Not researched. ### On-street parking #### Commonway System **Discouraged; buffered lane if unavoidable.** Discouraged; off-street is always preferred. Where unavoidable, a buffered lane (10 to 14 ft plus a 2 to 4 ft painted buffer), never bare curbside. No parking or loading within 20 ft of a marked crosswalk. #### Federal / State baseline **20 ft crosswalk setback.** A 20 ft setback before a marked crosswalk keeps sight distance clear and stops drivers pulling forward onto a raised crossing to back into the first space.[14] #### NACTO enhancement **Not researched.** Not researched. #### Complete Streets layer **Not specified.** Not specified in the typical-elements list. #### Dutch / Sustainable Safety **Not researched.** Not researched. ### Property access #### Commonway System **Curb cuts limited by code; forward entry.** Curb cuts limited by code, not "as needed." The driveway and on-site apron are sized so the design vehicle enters forward and never backs across the public sidewalk to reach a loading position. See [Curb Cut / Driveway Apron](https://commonwaysystem.org/patterns/elements/curb-cut-driveway-apron.md). #### Federal / State baseline **Curb-cut counts capped; no backing into the street.** Curb-cut counts are limited by land use code.[15] Backing onto a public street or sidewalk to leave a site is prohibited in multiple adopted jurisdictions: Knightdale, NC bars loading areas from relying on backing movements into the right-of-way,[17] and Bakersfield, CA bars vehicles backing onto any street to leave a site, explicitly once the street is classified arterial or collector.[18] Houston bars back-in loading berths on a major thoroughfare and, where a back-out berth is used, requires it to be deep enough that no part of the vehicle protrudes over the property line.[16] #### NACTO enhancement **Confirm the actual truck mix.** Confirm actual truck mix before assuming the largest design vehicle at every driveway.[19] #### Complete Streets layer **Not specified.** Not specified in the typical-elements list. #### Dutch / Sustainable Safety **Not researched.** Not researched. ## Design notes Industrial land use exists across a wide density range, which is why this Typology's realistic range is broader than most Collector entries, spanning Suburban through Urban with Undeveloped, Rural, and Core all plausible as edge cases rather than clean exclusions.[6] The corner and driveway geometry on this page is driven by more than fit. Federal analysis has found that large trucks are involved in a disproportionate share of fatal pedestrian and cyclist crashes relative to their share of the vehicle fleet, and that turning maneuvers carry far higher odds of a fatal outcome than going straight, largely because a truck's off-tracking during a turn puts a person standing or riding alongside the trailer in a blind zone with no escape path.[20][21] That is why curb-cut minimization and intersection design on this page are treated as life-safety measures, not just access-management or geometry problems. The general pattern for turning-vehicle risk is on the [Signal](https://commonwaysystem.org/patterns/intersections/signal.md) page, and this street is the acute case of it. Two cautions apply when sizing anything on this page to the largest design vehicle. Designing every movement for the largest conceivable truck degrades safety and comfort for other users without a demonstrated need, and oversized intersections carry their own costs: more crash exposure, more confusion, more right-of-way, and longer pedestrian crossing distances.[11][12] Confirm actual vehicle mix before defaulting to the worst case. **Bicycle facility catchment.** The 3-mile bike and 0.5-mile walk threshold above borrows the distances in FTA's own adopted eligibility policy for pedestrian and bicycle improvements, which are themselves reasoned from equivalent travel time at each mode's typical speed: roughly a 15-to-30-minute walk at 2 mph, and the same time budget at a bicycle's roughly 10 mph average commute speed.[22] The trigger is population, not land use classification. An industrial designation for this street does not mean its only legitimate users are people employed at businesses along it, and it should not be read as excusing the facility just because a bicycle plan has not caught up to the corridor. Industrial and logistics employment also skews toward a workforce with lower vehicle ownership and higher walk and bicycle mode share than the general population, including shift-work schedules that raise their own visibility and lighting needs. That is a reason to apply this trigger generously here, not a reason to scope it down to only the workers on-site.[24] Where this pattern's street crosses an active rail spur, an increasingly common condition on industrial land, see [Railroad Grade Crossing](https://commonwaysystem.org/patterns/intersections/railroad-grade-crossing.md) (INT-RGC-15), which covers the geometry and warning devices this page does not. ## Related patterns [Default (Standard Collector)](https://commonwaysystem.org/patterns/collectors/default.md) (COL-DEF-01) (the base order this pattern overrides for Freight priority), [Alley](https://commonwaysystem.org/patterns/local-streets/alley.md) (LOC-ALY-02) (the other cross-Classification pattern overriding to a Vehicle/Freight-first order for a specific access purpose), [Roundabout (Single / Multi-Lane)](https://commonwaysystem.org/patterns/intersections/roundabout.md) (INT-RAB-01) (this pattern's intersection answer depends on that page's freight-street sizing note), [Curb Cut / Driveway Apron](https://commonwaysystem.org/patterns/elements/curb-cut-driveway-apron.md) (ELM-CCA-04) (this pattern's property-access answer depends on that Element's forward-entry requirement), [Railroad Grade Crossing](https://commonwaysystem.org/patterns/intersections/railroad-grade-crossing.md) (INT-RGC-15) (where an active rail spur crosses this street) ## References 1. Legal / regulatory [City of Portland Bureau of Transportation, _PBOT Development Review Manual_, industrial-zone cross-section standard (44 ft curb-to-curb, two 12 ft travel lanes).](https://www.portland.gov/transportation/permitting/documents/pbot-development-review-manual-creating-public-streets-and/download) 2. Legal / regulatory [City of Minneapolis, _Street Design Guidance_ 3.7B, "Design and Control Vehicles" (WB-62 named for highly industrialized streets).](https://sdg.minneapolismn.gov/application/files/4116/1256/7848/3.7B_Design_and_control_vehicles.pdf) 3. Precedent-based [NACTO, _Urban Bikeway Design Guide_, "Protected Bike Lanes" (10 ft lanes support truck uses at 35 mph and under).](https://nacto.org/latest/urban-bikeway-design-guide-protected-bike-lanes/) 4. Precedent-based [City of Portland Bureau of Transportation, StreetsPDX, "Industrial Roads" street type (two to four lanes plus turn lanes as needed).](https://pbotapps.portland.gov/streets-pdx/street-types/industrial-road) 5. Legal / regulatory [Federal Highway Administration, _Separated Bike Lane Planning and Design Guide_, vertical separation type selection.](https://www.fhwa.dot.gov/environment/bicycle_pedestrian/publications/separated_bikelane_pdg/page08.cfm) 6. Precedent-based [NACTO, _Urban Street Design Guide_, "Design Vehicle" (truck route coordination with bike, transit, and pedestrian mapping; bollards at truck-route corners).](https://nacto.org/publication/urban-street-design-guide/design-controls/design-vehicle/) 7. Legal / regulatory [U.S. Access Board, PROWAG Chapter R3, Technical Requirements, pedestrian access route width.](https://www.access-board.gov/prowag/proposed/chapter-r3-technical-requirements/) 8. Legal / regulatory [Federal Highway Administration. "Relationship Between Design Speed, Operating Speed, and Posted Speed."](https://www.fhwa.dot.gov/planning/css/resources/speed) 9. Precedent-based Seattle Streets Illustrated, [3.9 Intersections](https://streetsillustrated.seattle.gov/design-standards/intersections/) and [2.13 Industrial Access](https://streetsillustrated.seattle.gov/street-type-standards/industrial-access/) (curb radius by connection type: 25 to 30 ft for truck-street intersections versus a 20 ft citywide default). 10. Legal / regulatory [Transportation Research Board, _Guide for Roundabouts_, NCHRP Research Report 1043 (2023). Supersedes NCHRP Report 672.](https://www.nationalacademies.org/publications/27069) 11. Legal / regulatory [Delaware Department of Transportation, _Design Guidance Memorandum_ (DGM) 1-26, "Roundabouts" (design vehicle versus check vehicle, and the caution against over-designing for the largest possible truck).](https://deldot.gov/Publications/manuals/dgm/pdfs/1-26_Roundabouts.pdf) 12. Legal / regulatory [Wisconsin Department of Transportation, _Facilities Development Manual_, FDM 11-25 (costs of oversized truck-accommodating intersections).](https://wisconsindot.gov/rdwy/fdm/fd-11-25.pdf) 13. Precedent-based [Seattle Streets Illustrated, 3.11 "Freight" (protected bicycle lane recommended on truck streets; setback stop bars and bicycle signals as tools against large-truck turning movements).](https://streetsillustrated.seattle.gov/design-standards/freight/) 14. Legal / regulatory [Ohio Department of Transportation, _Location and Design Manual_ Volume 1, pedestrian facilities (20 ft parking and loading restriction before a marked crosswalk).](https://www.transportation.ohio.gov/working/engineering/roadway/manuals-standards/multimodal/04) 15. Legal / regulatory [City of Seattle, Land Use Code § 23.54.030, "Parking space and access standards" (curb-cut counts per lot frontage).](http://seattle-wa.elaws.us/code/mc_title23_subtitleiii_ch23.54_sec23.54.030) 16. Legal / regulatory [City of Houston, _Houston Building Code_ (2021), Chapter 31, § 3116.4.6 "Loading Berth" (§ 3112 in the 2015 edition).](https://up.codes/viewer/houston/ibc-2021/chapter/31/special-construction) 17. Legal / regulatory [Town of Knightdale, NC, _Unified Development Ordinance_, Chapter 7, "Development Standards" (loading areas may not rely on backing movements into public rights-of-way).](https://www.knightdalenc.gov/sites/default/files/uploads/developmentservices/udo/07-development-standards-052226.pdf) 18. Legal / regulatory [City of Bakersfield, _Zoning Code_, Chapter 32 (vehicles may not back onto any street or thoroughfare to leave a site, binding once a street is classified arterial or collector).](https://www.zoneomics.com/code/bakersfield-CA/chapter_32) 19. Legal / regulatory [Los Angeles Department of Transportation, _Driveway Design Guide_ (2024) (on-site reservoir and maneuvering space; confirm truck mix by turning-movement path evaluation).](https://ladot.lacity.gov/sites/default/files/2026-04/driveway-design-guide-march-2024.pdf) 20. Evidence-based [U.S. Government Accountability Office, _Pedestrian and Cyclist Safety: DOT Should Take Steps to Address Risks Related to Limited Driver Visibility_, GAO-26-107954 (2026).](https://www.gao.gov/products/gao-26-107954) 21. Evidence-based [Wang, Q. et al., "Exploring the Influencing Factors and Formation of the Blind Zone of a Semitrailer Truck in a Right-Turn Collision," _Sustainability_ 14(16), 9805 (2022).](https://doi.org/10.3390/su14169805) 22. Legal / regulatory [Federal Transit Administration, "Final Policy Statement on the Eligibility of Pedestrian and Bicycle Improvements Under Federal Transit Law," _Federal Register_ 76(161), p. 52046 (August 19, 2011) (one-half mile pedestrian and three-mile bicycle distances from a transit stop or station).](https://www.federalregister.gov/documents/2011/08/19/2011-21273/final-policy-statement-on-the-eligibility-of-pedestrian-and-bicycle-improvements-under-federal) 23. Legal / regulatory [Federal Highway Administration, _Bikeway Selection Guide_, FHWA-SA-18-077 (2019) (facility type by speed, volume, truck mix, and land use context; separated facility thresholds).](https://safety.fhwa.dot.gov/ped_bike/tools_solve/docs/fhwasa18077.pdf) 24. Evidence-based [Chandra, S., Jimenez, J., and Radhakrishnan, R., "Accessibility evaluations for nighttime walking and bicycling for low-income shift workers," _Journal of Transport Geography_ 64 (2017), pp. 97 to 108.](https://doi.org/10.1016/j.jtrangeo.2017.08.010)