In addition to research that describes findings related to operating speed and factors that potentially influence it, a number of jurisdictions include target speed and related concepts in their guidance. This chapter summarizes findings from a review of current practices.
ITE’s RP, Designing Walkable Urban Thoroughfares: A Context Sensitive Approach (ITE 2010) states that factors potentially affecting target speed in urban areas include transition from higher- to lower-speed roadways, terrain, intersection spacing, frequency of access to adjacent land, type of roadway median, presence of curb parking, and level of pedestrian activity. Their guidance on target speed for walkable urban thoroughfares advises that it is not set arbitrarily but rather is achieved through a combination of measures that include the following:
Other elements of walkable, mixed-use urban areas that ITE describes as factors widely believed to influence speed include a canopy of street trees, the enclosure of a thoroughfare formed by the proximity of a wall of buildings, the striping of edge lines or bicycle lanes, or parking lanes.
The FHWA Speed Limit Setting Handbook (Schroeder et al. 2025) provides practitioners with information on how to conduct an engineering study to set a speed limit for a speed zone based on the provisions in the MUTCD. In that handbook, the guidance notes that understanding the expected speed ranges in various contexts and functional classifications can create a starting point for assessing the engineering study outcomes and account for the surrounding community, user needs, and road function. In addition, identifying a target speed for a road can help agencies identify appropriate design and operational features to support a motorist speed choice consistent with the target speed, defined in the handbook as “the highest desired operating speed given
land-use contexts, multimodal activity, and vehicular mobility”. The handbook notes that target speed policies usually consider some or all of the MUTCD’s six speed limit-setting factors as part of the development of target speeds for typical roadway conditions in a given context. In the handbook’s guidance, when a jurisdiction has a target speed policy, it has already set a target speed for a roadway or for its combination of functional and context classification characteristics. The handbook uses NCHRP Report 966 (Fitzpatrick et al. 2021c) as a basis for examples of target speed ranges that can be used in a target speed policy that supports setting speed limits.
The handbook notes that, when evaluating target speeds, it is important to remember that roadway context can change over time. Most commonly, the target speed may need to lower over time as contexts shift from rural or suburban to a more urban context as development occurs and land use changes. In other cases, it may be that the roadway’s target speed is too low given a changing context due to roadway design changes, access management, and separation of users walking and bicycling.
The 2020 Florida DOT Design Manual (Florida DOT 2020b), in its discussion on speed management and target speed, provides a table of potential speed management strategies for the designer to consider for given combinations of context classification (Florida DOT 2020a) and design speed. Strategies include roundabouts, on-street parking, chicanes, lane narrowing, horizontal deflection, street trees, short blocks, vertical deflection, speed feedback signs, speed limit pavement markings, median islands, curb extensions (i.e., bulbouts), RRFBs and PHBs, and terminated vistas. Table B-1 summarizes the speed management strategies presented in the FDOT manual for lower design speed categories.
| Context Classification | Design Speed (mph) | Strategies |
|---|---|---|
| Rural Town | 40-45 | Roundabout, Lane Narrowing, Horizontal Deflection, Speed Feedback Signs, RRFBs and PHBs |
| 35 | Techniques for 40-45 mph, plus On-street Parking, Street Trees, Short Blocks, Median Islands at Crossings, Road Diet, Bulbouts, Terminated Vista | |
| 30 | Techniques for 35-45 mph, plus Chicanes, Median Islands in curved sections, Textured Surface | |
| ≤ 25 | Techniques for 30-45 mph, plus Vertical Deflection | |
| Suburban Residential or Commercial | 40-45 | Roundabout, Lane Narrowing, Horizontal Deflection, Speed Feedback Signs, RRFB and PHB |
| 35 | Roundabout, Lane Narrowing, Horizontal Deflection, Speed Feedback Signs, Median Islands in crossings, Road Diet, RRFB and PHB, Terminated Vista | |
| Urban General | 40-45 | Roundabout, Lane Narrowing, Horizontal Deflection, Speed Feedback Signs, RRFB and PHB |
| 35 | Techniques for 40-45mph plus On-Street Parking, Street Trees, Short Blocks, Median Islands at Crossings, Bulbouts, Terminated Vista, Road Diet | |
| 30 | Techniques for 35-45 mph plus Chicanes, Median Islands in Curve Sections, Textured Surface | |
| Urban Center | 35 | Roundabout, On-street Parking, Street Trees, Short Blocks, Speed Feedback Signs, Median Islands in Crossings, Road Diet, Bulbouts, RRFB and PHB, Terminated Vista |
| 30 | Techniques for 35 mph plus Chicanes, Median Island in Curve Sections, Textured Surface | |
| 25 | Techniques for 30-35 mph plus Vertical Deflection | |
| Urban Core | 30 | Roundabout, On-Street Parking, Horizontal Deflection, Street Trees, Median Islands in Curve Sections, Road Diet, Bulbouts, Terminated Vista, Textured Surface |
| 25 | Techniques for 30 mph plus vertical deflection |
The manual says that the designer, in potentially selecting one or more of those speed management strategies, should consider:
The FDOT guidance also states that, typically, the strategies provided are most effective when several are used together. It encourages designers to use existing conditions to the greatest extent possible to support speed management. In particular, it states that existing street grids with short blocks and frequent intersections represent excellent speed management opportunities already in place, and such opportunities should be accentuated and used where they exist.
The 2020 FDOT Context Classification Guide (Florida DOT 2020a), in its guidance on designing for a target speed, advises that when the current design speed does not match the target speed, roadway design and operation changes are needed to affect the design speed and posted speed toward the target speed; a concurrent effect is described as helping the road “read” more consistently for road users. When the current posted speed is higher than the target speed, FDOT says that the design team may use this feedback-loop process:
Table B-2 summarizes the FDOT table of transportation characteristics that can be used to select a target speed for the lowest design speed ranges.
| Target Speed | 25 mph | 30 mph | 35 mph | 40-45 mph |
|---|---|---|---|---|
| Context Classifications | Rural Town, Urban Center, Urban Core | Rural Town, Urban General, Urban Center, Urban Core | Rural Town, Suburban, Urban General, Urban Center | Rural Town (rarely), Suburban, Urban General (rarely) |
| Fronting Uses | Most parcels fronting street | Most parcels fronting street | Some parcels fronting street | Not applicable |
| Population Density | High | High | Medium to High | Medium |
| Vulnerable Users | High | High | Medium to High | Medium |
| Cross-Section Elements | On-street parking; sharrows | On-street parking; sharrows | Separated bicycle lanes; buffered bike lanes | Shared-use path |
| Access Class* | 6 and 7 | 6 and 7 | 5, 6, and 7 | 3, 4, 5, and 6 |
| Transit Service | Highest frequency and local service | Highest frequency and local service | Highest frequency and local service | Moderate frequency and local+regional service |
| Transit Ridership | High | High | Medium to High | Medium to High |
| Pedestrian and Bicycle Generators | High | High | Medium | Sporadic |
| Vehicular Trip Type | >75% Local | >75% Local | >50% Local | >50% Regional |
| Average Trip Length | <3 miles | 3 to 5 miles | 3 to 5 miles | 5 to 10 miles |
| *Defined in the FDOT Access Management Guidebook (Florida DOT 2019) | ||||
Florida DOT updated their Context Classification Guide (Florida DOT 2024) and Design Manual (Florida DOT 2025) in 2024 and 2025, respectively. The 2024 FDOT Context Classification Guide expands on the 2020 discussion of context-based speeds and provides an example process for determining target speed:
The 2025 FDOT Design Manual (Florida DOT 2025) specifies that design speed should be selected early in the design process and should be influenced by target speed, which is determined by the process described in the 2024 Context Classification Guide (Florida DOT 2024). A context-appropriate design speed is selected to attain a desired degree of safety, mobility, and efficiency. Where the recommended target speed is not feasible to attain in a single project, the design speed should be as close to the target speed as can be achieved within the constraints of the project. Target speed is defined in the 2025 FDOT Design Manual (Florida DOT 2025) as “the highest speed at which vehicles should operate on a thoroughfare in a specific context, consistent with the level of multi-modal activity generated by adjacent land uses, to provide both mobility for motor vehicles and a supportive environment for pedestrians, bicyclists, and public transit users.” An appropriate target speed is determined for all non-limited access projects where a design speed is also required.
The 2021 Washington State DOT (WSDOT) Design Manual (Washington State DOT 2021) states that design speed is determined through the use of a target speed. It says that the objective of the target speed approach is to establish the design speed at the desired operating speed. The target speed selection is derived from other design controls, as well as transportation and land use context characteristics. The manual provides suggestions for high, intermediate, and low ranges of target speed for various land use contexts and roadway types, as summarized in Table B-3.
| Roadway Type | Rural | Suburban | Urban | Urban Core |
|---|---|---|---|---|
| Freeways | High | High | High | High |
| Principal Arterial | High | Intermediate/High | Low/Intermediate | Low |
| Minor Arterial | High | Low/Intermediate | Low/Intermediate | Low |
| Collector | Low/Intermediate | Low/Intermediate | Low | Low |
| Local | Low/Intermediate | Low | Low | Low |
The WSDOT Design Manual (Washington State DOT 2021) describes the speed ranges shown in Table B-3 as follows:
In selecting the target speed, the 2021 WSDOT Design Manual advises to engage the public, local agency staff and officials, and transit agencies before making that decision. The selected target speed becomes the design speed for the project, with the goal that it is also ultimately the operating speed on the completed roadway. With that in mind, the designer is advised to consider the following factors:
The 2021 WSDOT Design Manual also provides guidance on coordinating the target speed with the posted speed limit. In particular, if a target speed is selected that exceeds the existing posted speed, the designer is encouraged to either consider speed management treatments to achieve lower vehicle speeds (and thus enable a lower target speed) or consider treatments that reduce conflicts in activities and modal uses (to make the roadway more consistent with the higher target speed). The designer is also cautioned about basing a target speed on contextual characteristics that are proposed to take place after the project opens, because other factors are used with target speed in setting posted speed, and a lack of coordination with the appropriate region traffic engineer may result in a posted speed that is not equal to the design speed at opening.
The 2024 WSDOT Design Manual (Washington State DOT 2024) provides similar information, with minor adjustments to the speed ranges shown in Table B-3. It states that WSDOT uses a target speed approach for determining design speed, and it defines target speed as “the highest speed at which vehicles should operate on a thoroughfare in a specific context, consistent with the level of multimodal activity generated by adjacent land uses, to provide both mobility for motor vehicles and a desirable environment for pedestrians, bicyclists, and public transit users.”
The 2024 WSDOT Design Manual also provides guidance on lowering and raising target speeds for a given roadway. When selecting a target speed lower than the existing posted speed, or where operating speeds were identified from contributing factors analysis of the baseline performance need, designers are to consider the use of roadway treatments, particularly speed
management treatments, that will help achieve the selected target speed during formulation of alternatives.
When selecting a target speed in excess of the existing posted speed, WSDOT advises that measures such as greater restriction of access control and segregation of modes may be necessary to reduce conflicts in activities and modal uses. Wider cross-sectional elements like lanes and shoulders are often used with higher speed facilities. Careful consideration of other modal needs, any Level of Traffic Stress requirements, and safety impacts for all modal uses should be evaluated before raising target speeds.
The Oregon DOT Blueprint for Urban Design (BUD) (Oregon DOT 2020a, Oregon DOT 2020b) provides recommendations for target speeds in each urban context (see Table B-4) and advises that “…the recommended target speed should be used as the starting point. If the target speed is not practical for a specific project, justification should be provided. The urban context, community values, and safety for vulnerable users should be considered when reviewing tradeoffs associated with a different target speed, such as construction cost or vehicle mobility objectives. The multidisciplinary project team introduced in the Blueprint for Urban Design should make the final decision in the target speed determination.”
In practice, the BUD advises, the target speed and design speed should be the same, and a roadway should encourage an actual operating speed at the target speed. When the target speed is below the current design or operating speed, speed management treatments (such as those shown in Table B-4) should be used to help achieve the selected target speed. The target speed is also intended to be used as the posted speed limit; however, per the MUTCD, posted speeds should be established based on statutory limits unless an engineering study has been performed in accordance with established traffic engineering practices. ODOT typically uses the 85th percentile operating speed to set the posted speed within the limits of existing state statutes. The BUD states that when the target speed is lower than the current operating speed, ODOT should consider the following steps under existing statutes to obtain acceptance of a lower posted speed based on the speed reduction potential of the design treatments being implemented.
| Urban Context | Target Speed (mph) | Design Treatments |
|---|---|---|
| Traditional Downtown/CBD | 20-25 | Roundabouts, lane narrowing, speed feedback signs, on-street parking1, street trees2, median islands, curb extensions, chicanes, textured surface, coordinated signal timing, speed tables, road diets |
| Urban Mix | 25-30 | Roundabouts, lane narrowing, speed feedback signs, on-street parking1, street trees2, median islands, curb extensions, chicanes, textured surface, coordinated signal timing, road diets |
| Commercial Corridor | 30-35 | Roundabouts, lane narrowing, speed feedback signs, median islands, coordinated signal timing, road diets |
| Residential Arterial | 30-35 | Roundabouts, lane narrowing, speed feedback signs, median islands, coordinated signal timing, road diets |
| Suburban Fringe* | 35-40 | Roundabouts, transverse pavement markings, lane narrowing, speed feedback signs, road diets |
| Rural Community | 25-35 | Roundabouts, lane narrowing, speed feedback signs, on-street parking1, street trees2, median islands, curb extensions, chicanes, speed tables, road diets |
|
* The “fringe” context is typically adjacent to rural areas at the edge of urban development, but often is in the process of developing. For projects in the “fringe” context zone, practitioners should consider likely future development and consider applying designs for “residential arterial,” “commercial corridor,” or “urban mix” contexts if this type of development is likely to occur. 1 If on-street parking is not well utilized, the additional pavement width may increase operating speeds. 2 When used along roadways, street trees may not reduce speeds in a specific urban context to a point where it is appropriate to have a vertical element adjacent to the roadway. |
||
The 2025 edition of the ODOT Highway Design Manual (Oregon DOT 2025) in Section 207.10.3 includes much of the information from the BUD. It also defines target speed as “the appropriate speed at which drivers should be operating a vehicle on a section of roadway based on context, classification and overall operations.” It reproduces Table B-4 as a summary of recommended target speed and design treatments, with the addition of entry treatments as options for Suburban Fringe and Rural Community contexts and revision of the Residential Arterial context to be labeled Residential Corridor. The table in the Highway Design Manual also notes that speed tables and chicanes may not be appropriate on most state roadways but may be considered in special cases.
As early as 2006, Massachusetts DOT (MassDOT) included target speed in their Project Development & Design Guide (PDDG) (Massachusetts Highway Department 2006). In the PDDG, target speed has not only a definition (“the desired operating speed along a roadway”) but also related guidance on how it should be used in the project development process, stating that it is determined early in that process and that an appropriate target speed should consider:
The 2023 PDDG (Massachusetts DOT 2023) provides additional guidance in Section 3.6 on speed concepts in the design process. The PDDG has an updated definition of target speed as “a selected speed used to identify the highest operating speed at which vehicles should operate in a particular context to provide safer environments for all roadway users. Used to identify speed management measures and select design speed.” The guidance in the PDDG states that the objective of selecting a target speed is to inform the selection of a design speed and design treatments that aim to achieve operating speeds that are appropriate for the context and mix of roadway users. It adds that although target speed informs and influences various design elements, it does not directly control the design geometry. Instead, target speed informs:
Conversely, the PDDG says, design speed controls the following elements, which include, but are not limited to:
The target speed and design speed should be identified in the early stages of the project development process through collaboration with a multi-disciplinary team that is responsible for developing the project scope. The PDDG provides a table (reproduced here as Table B-5) that summarizes the process for identifying target and design speeds throughout the project development process.
| Project Development Step | Target Speed Process | Documentation | Review |
|---|---|---|---|
| Scoping | Identify target speed and design speed range |
|
|
| Pre-25% | Verify existing operating speed. Assess a target speed appropriate for the project context. Determine if speed management is needed to achieve target speed. If so, select speed management measures. Finalize target speed and select design speed. Assess the need for separation between motor vehicles and people walking and biking. |
|
Approval:
|
| 25% | Design project based on design speed. |
|
DJW:
FDR:
|
| Through 100% / PS&E | Confirm design elements meet target speed, design speed(s), and user separation needs. |
|
|
The PDDG also provides a range of target and design speeds based on the area type and roadway type. The range of target and design speeds recognizes the diversity of roadway types, area types, and topographies and provides flexibility to the designer. The target and design speed ranges are based on two factors, Area Type (the surrounding existing or future built and natural environment) and Roadway Type (the role the roadway plays in terms of providing regional connectivity and local access), both of which have a defined set of categories within the PDDG. The range of target and design speeds is summarized in Table B-6.
| Area Type1 | Arterial Roadway Target and Design Speed Range (mph)2 | Collector Roadway Target and Design Speed Range (mph) | Local Roadway Target and Design Speed Range (mph) |
|---|---|---|---|
| Rural Natural | 25-55 | 25-45 | 15-35 |
| Rural Developed | 25-45 | 20-40 | 15-35 |
| Rural Village | 20-35 | 20-35 | 15-30 |
| Suburban Low Density Development | 20-45 | 20-40 | 15-35 |
| Suburban High Density Development | 20-35 | 20-35 | 15-30 |
| Suburban Town Center | 20-30 | 20-30 | 15-30 |
| Urban (Park, Residential, Central Business District) | 20-30 | 15-30 | 15-30 |
| Notes: 1 This table does not apply to limited access roadways and freeways. The design speed range for a limited access facility such as a freeway is 50 to 75 mph regardless of area type. 2 A design speed higher than these values, up to 55 mph, may be appropriate for multi-lane, divided arterials. |
|||
The PDDG says the designer should use engineering judgment to select an appropriate target speed by assessing eight factors described below.
The first seven factors are assessed based on general context and need, to identify whether target speed should be at the low or high end of the target and design speed range based on the general context and needs. This assessment is summarized in the Draft DJW. The eighth factor is based on project achievability or appropriateness, to select the target speed for the project.
The PDDG says target speed may vary along the overall length of the project based on changing context, and a single project corridor may have segments with different target speeds. Examples include:
Relating the target speed to the design speed, the PDDG advises that, in general, target speed and design speed should be the same. If the design speed is higher than the target speed, the roadway geometry will allow for and may encourage speeding. The roadway design should encourage an operating speed that matches the target speed, consistent with FHWA’s self-enforcing roadways concept (Donnell et al. 2018). Alignment among target, design, and operating speed is expected for new construction and reconstruction projects that can change the roadway’s alignment.
The 2024 Texas DOT Roadway Design Manual (RDM) (Texas DOT 2024) includes guidance on posted speed relative to design speed and other speed concepts for project development. It states in Section 4.2.4 that the working definition for target speed is “the operating speed that the designer intends for drivers to use”. In mixed-use urban areas, the RDM says that target speed is the highest speed at which vehicles should operate on a low-speed thoroughfare in a specific context, consistent with the level of multimodal activity generated by adjacent land uses, to provide both mobility for motor vehicles and a desirable environment for pedestrians, bicyclists, and public transit users. In general, the RDM advises that the target speed for rural roadways should be at the higher end of the design speed range. Subsequent tables in the RDM provide target design values for design elements for various roadway and context classifications; each table provides values for design speeds with a note that the selected design speed should meet the anticipated target speed of the facility during non-peak hours.
The Draft Street Design Guide for the city of Austin, Texas (Austin Transportation Department 2017) provides guidance for multimodal considerations in street design that includes target speed based on context, street level (a descriptor related to functional classification, ranging from Level 1 residential local streets to Level 5 controlled-access expressways and freeways), and traffic volumes. The information in the document says that traffic volumes should help guide the decision regarding number of lanes and target speed. Some overlap in volume ranges is provided to allow for flexibility in choice of lanes and design speed. Table B-7 provides a summary of 25-45 mph categories in the Multimodal Design Table from the Austin guide, which is intended to be an overview of the various characteristics of possible cross-sections described elsewhere in the guide. The description of the table says that the table should be referenced for decision-making when there is not enough space to accommodate the recommended bicycle, transit, or parking facilities and clarifies what elements to use for those facilities. The four- and six-lane cross-sections are specified in the table as divided with a median. Images of example cross-sections are provided in the guide for designers’ reference.
| Context | Level | ADT (1000 vpd) | # Lanes | Target Speed (mph) | Bus Frequency | Bike Facility Type | Sidewalk | Pedestrian Crossing Density | Transit Facility Type | Parking Facility Type |
|---|---|---|---|---|---|---|---|---|---|---|
| Urban | 2 | 2 - 5 | 2 | 25 | Low | Conventional, buffered, or raised | Sidewalk and buffer | 1/8 mi | Boarding islands/bulbs | Parallel |
| 5 - 10 | 2 | 25 | Med | Buffered or raised | Peak-only dedicated lanes | |||||
| 3 | 10 - 20 | 3 | 35 | High | Raised | Dedicated or peak-only lanes | ||||
| 15 - 40 | 4 | 35 | Very High | Raised | Dedicated transit lanes | |||||
| 4 | 35 - 45 | 4 | 40 | High | Raised | 1/4 mi | Dedicated or peak-only lanes | Access lanes | ||
| 40+ | 6 | 40 | Very High | Raised | Dedicated transit lanes | |||||
| Suburban | 2 | 2 - 5 | 2 | 25 | Very Low | Conventional, buffered, or raised | 1/4 mi | None | Parallel | |
| 5 - 10 | 2 | 30 | Low | Buffered or raised | Boarding islands/bulbs | Parallel | ||||
| 3 | 10 - 20 | 3 | 35 | Med | Raised | Peak-only dedicated lanes | Curb extension |
| Context | Level | ADT (1000 vpd) | # Lanes | Target Speed (mph) | Bus Frequency | Bike Facility Type | Sidewalk | Pedestrian Crossing Density | Transit Facility Type | Parking Facility Type |
|---|---|---|---|---|---|---|---|---|---|---|
| 15 - 40 | 4 | 40 | High | Raised | Dedicated or peak-only lanes | None | ||||
| 4 | 35 - 45 | 4 | 40 | Med | Raised lane or shared-use path | Sidewalk or shared-use paths and buffer zone | 1/2 mi | Peak-only dedicated lanes | None | |
| 40+ | 6 | 45 | High | Raised lane or shared-use path | Dedicated or peak-only lanes | None | ||||
| Industrial | 2 | < 20 | 3 | 25 | N/A | Buffered | Sidewalk and Buffer Zone | 1/2 mi | None | Parallel |
| 3 | 10 - 30 | 5 | 30 | N/A | Raised | None | None |
The Urban Street Design Guide for the city of Charlotte, North Carolina (Charlotte DOT 2007) focuses on street types (akin to functional classification) that are selected based on a six-step design process. The design process, which is intended to primarily be applied to planning and designing “non-local” street types, was developed to better incorporate planning, design, and stakeholder input and participation in the decision-making process, to increase the likelihood that the resulting streets are appropriately based on the existing and proposed land use and transportation contexts. The six steps in the design process are as follows:
The six steps can be applied either to a single street or to a collection of streets in an area (such as when an area plan is being developed). In either case, the first four steps should take an area-wide approach to gathering and assessing the information required for each step, since even individual street segments do not exist or function in isolation from the surrounding street network and land uses. Steps 1 and 2 lead to Step 3, which leads to Step 4, which leads to Step 5. The design process may end with Step 6 or with an iterative development of Steps 5 and 6 together. The result of the design process is selection of a street type. The street type is defined primarily based on context, cross-section, and block spacing, though speed thresholds are included in those definitions. A summary of street types in Charlotte’s guide is provided in Table B-8. The guide also provides sketches that illustrate example cross-sections for each street type.
| Type | Design Speed (mph) | Posted Speed (mph) | Through Lanes | Lane Width (ft) | Median | Block Length (ft) |
|---|---|---|---|---|---|---|
| Main Streets | Not stated | 25 | 2 | 13, plus parking | Generally no | 400 max |
| Avenues | 30-40 | 25-30 | 2-5 | 10-11 | Can be used | 600 max |
| Boulevards | ≤ 45 | 35-40 | 4 | 10-11 | Should be used (6 ft min, 17 ft preferred) | 1000-1200 max |
| Parkways | ≤ 55 | 45-50 | 4-6 | 11-12 | Should be used (17 ft min) | 2640 min |
| Local Residential | 25 | 25 | 2 | 10-12, plus parking | Generally no (min 8 ft if provided for aesthetics) | 400-1000 |
| Local Office/Commercial | 25 | 25 | 2 | 12, plus parking | Generally no (min 8 ft if provided for aesthetics) | 400-1000 |
| Local Industrial | 25 | 25 | 2 | 12, plus parking | No | 400-1000 |
The city of Chicago, Illinois also provides a street typology as part of its Complete Streets Design Guidelines (Chicago DOT 2013). Similar to that found in Charlotte, the Chicago guidelines describe a six-stage project delivery process, intended to allow opportunities for public input, stakeholder and interagency outreach, and iterative design. A series of worksheets and resources is provided for project managers to complete the project delivery process of Selection, Scoping, Design, Construction, Measurement, and Maintenance.
Within the Design stage, the Chicago guidelines describe six types of roadway form and function related to the physical layout of the roadway; those six types, listed below, are generally equated to functional classification as follows:
The Chicago guidelines state that they will use target speed rather than design speed. To that end, the target speed of each street is equal to or less than the speed limit, based on roadway type. Table B-9 provides a summary of those target speeds, as well as associated design vehicles and lane widths. Target speeds higher than 30 mph, lanes wider than 11 ft, and design vehicles greater than WB-50 require approval of the Compliance Committee.
Table B-9. Design elements for street types in Chicago, Illinois. (adapted from Chicago DOT 2013)
| Street Type | Target Speed (mph) | Lane Width (ft) | Design Vehicle |
|---|---|---|---|
| Thoroughfare | 25-30 | 10-11 | WB-50 |
| Connector | 20-30 | 9-11 | BUS-40 |
| Main Street | 15-25 | 9-10 | SU-30 |
| Neighborhood Street | 10-20 | Not applicable | DL-23 |
| Service Way | 5-10 | Not applicable | DL-23 |
| Note: The DL-23 design vehicle has dimensions corresponding to a United Parcel Service P-80 delivery truck. Other design vehicles correspond to their respective AASHTO Green Book definitions. | |||
The guidelines add that Chicago’s prima facie speed limit is 30 mph, and the document advises that the use of target speeds may require lowering the speed limit or posting speed advisory signs. The guidelines advise that target speed should account for specific geometric elements such as curves and traffic calming devices. In addition, the Chicago Pedestrian Plan proposes a 20-mph target speed for residential streets (generally applicable to Main Streets and Neighborhood Streets).
In its discussion on speed, the Chicago guidelines document adds that speed control elements are often necessary to achieve target speeds, rather than relying solely on the posted speed limit. Examples of geometric and operational elements to control speed are provided as: