TITLE 24. TRANSPORTATION AND MOTOR VEHICLES

COMMONWEALTH TRANSPORTATION BOARD

Final Regulation

Titles of Regulations: 24VAC30-155. Traffic Impact Analysis Regulations (amending 24VAC30-155-60).

24VAC30-315. Standards for Use of Traffic Control Devices to Classify, Designate, Regulate, and Mark State Highways (amending 24VAC30-315-10).

24VAC30-325. Urban Maintenance and Construction Policy (amending 24VAC30-325-10; repealing 24VAC30-325-20).

24VAC30-630. Rules Governing Person with Disability Traffic Signs (amending 24VAC30-630-10, 24VAC30-630-20).

Statutory Authority:

24VAC30-155-60: § 51.2-2222.1 of the Code of Virginia.

24VAC30-315-10: §§ 33.2-210 and 46.2-830 of the Code of Virginia; 23 CFR 655.603.

24VAC30-325-10, 24VAC30-325-20: § 33.2-210 of the Code of Virginia.

24VAC30-630-10, 24VAC30-630-20: § 46.2-830 of the Code of Virginia.

Effective Date: December 17, 2025.

Agency Contact: Steven Jack, Regulatory Manager, Department of Transportation, 1221 East Broad Street, Richmond, VA 23219, telephone (804) 786-3885, or email steven.jack@vdot.virginia.gov.

Background: The Federal Highway Administration (FHWA) issued an updated Manual on Uniform Traffic Control Devices (MUTCD), dated December 2023, which contains the national standards for traffic control devices and is adopted at 23 CFR 655.603. State adoption of the federal MUTCD is required and must be completed by January 2026 through one of the following methods: (i) adopt the federal MUTCD as it stands; (ii) adopt the federal MUTCD with a state-specific supplement; or (iii) develop a state MUTCD incorporating national and state-specific content. All Virginia-specific adaptations to the federal MUTCD must remain in substantial conformance with the federal standards. In response, the Virginia Department of Transportation (VDOT) developed the Virginia MUTCD, version 11.0, effective January 1, 2026, which incorporates the national standards and sets state-specific requirements in substantial conformance with the federal MUTCD. The Commonwealth Transportation Board (CTB) approved this document as the standard for all traffic control devices on highways under the jurisdiction of VDOT.

Summary:

The amendments (i) incorporate the Virginia MUTCD into the Standards for Use of Traffic Control Devices to Classify, Designate, Regulate, and Mark State Highways (24VAC30-315), which completes formal adoption in accordance with the federal requirements; (ii) remove the MUTCD incorporated by reference in Traffic Impact Analysis Regulations (24VAC30-155) and Urban Maintenance and Construction Policy (24VAC30-325); and (iii) update the cross-references in regulatory text to point to 24VAC30-315 instead of the MUTCD document.

24VAC30-155-60. VDOT traffic impact statement.

A. A VDOT traffic impact statement (VTIS) assesses the impact of a proposed development on the transportation system and recommends improvements to lessen or negate those impacts. It shall (i) identify any traffic issues associated with access from the site to the existing transportation network, (ii) outline solutions to potential problems, (iii) address the sufficiency of the future transportation network, and (iv) present improvements to be incorporated into the proposed development.

If a VTIS is required, data collection shall be by the locality, developer, or owner, as determined by the locality and the locality shall prepare or have the developer or owner prepare the VTIS. If the locality prepares the VTIS, it shall provide a copy of the complete VTIS to the applicant when one is provided to VDOT. The completed VTIS shall be submitted to VDOT.

The data and analysis contained in the VTIS shall be organized and presented in a manner acceptable to VDOT and consistent with this regulation.

B. Scope of work meeting.

1. For proposals that generate less than 1,000 vehicle trips per peak hour of the generator, representatives of the locality, the applicant, or the locality and the applicant may request a scope of work meeting with VDOT to discuss the required elements of a VTIS for any project and VDOT shall reply to such request within 30 days of its receipt of such a request and provide a date that is no more than 60 days from such receipt, time, and location for such a scope of work meeting to both the locality and the applicant, if applicable.

2. For proposals that generate 1,000 or more vehicle trips per peak hour of the generator, representatives of the locality and applicant, if applicable, shall hold a scope of work meeting with VDOT to discuss the required elements of a VTIS. Once a locality or applicant has contacted VDOT regarding the scheduling of a scope of work meeting, VDOT shall reply to both the locality and the applicant, if applicable, within 30 days of such contact and provide a date that is no more than 60 days from such contact, time and location for such a meeting.

At a scope of work meeting pursuant to this section, the locality, the applicant, and VDOT shall review the elements, methodology, and assumptions to be used in the preparation of the VTIS, and identify any other related local requirements adopted pursuant to law. The results of the initial scoping meeting may be adjusted in accordance with sound professional judgment and the requirements of this regulation if agreed upon by VDOT, the locality, and applicant, if applicable.

C. Required elements. The required elements and scope of a VTIS are dependent upon the scale and potential impact of the specific development proposal being addressed by the VTIS as determined by VDOT in its sole discretion.

1. At a minimum, the VTIS shall include the elements shown in the table below. The site generated peak hour trips in the table below shall be based upon the gross vehicle trip generation of the site less internal capture and mode split reductions, if applicable. When the type of development proposed would indicate significant potential for walking, bike, or transit trips either on-site or off-site, the VTIS shall estimate multimodal trips. All distances in the table below shall be measured along roads or streets.

Item
	Less than 500	500 to 999	1,000 or more
Background information
List of all nonexistent transportation improvements assumed in the analysis	Required	Required	Required
Map of site location, description of the parcel, general terrain features, and location within the jurisdiction and region.	Required	Required	Required
Description of geographic scope/ limits of study area.	Within 2,000 feet of site and any roadway on which 50 or more of the new peak hour vehicle trips generated by the proposal are distributed – not to exceed one mile	Within 2,000 feet of site and any roadway on which 10% or more of the new vehicle trips generated by the proposal are distributed – not to exceed two miles	To be determined by VDOT in consultation with the locality
Plan at an engineering scale of the existing and proposed site uses.	Required	Required	Required
Description and map or diagram of nearby uses, including parcel zoning.	Required	Required	Required
Description and map or diagram of existing roadways.	Required	Required	Required
Description and map or diagram of programmed improvements to roadways, intersections, and other transportation facilities within the study area.	Required	Required	Required
Analysis of Existing Conditions
Collected daily and peak hour of the generator traffic volumes, tabulated and presented on diagrams with counts provided in an appendix.	Required	Required	Required
Analyses for intersections and roadways identified by VDOT. Delay and Level of Service (LOS) are tabulated and LOS is presented on diagrams for each lane group.	Required	Required	Required
When the type of development proposed would indicate significant potential for walking, bike or transit trips either on - or off - site, analyses of pedestrian and bicycle facilities, and bus route or routes and segment or segments, tabulated and presented on diagrams, if facilities or routes exist	Within 2,000 feet of site	Within 2,000 feet of site	To be determined by VDOT in consultation with the locality
Speed Study	If requested by VDOT	If requested by VDOT	If requested by VDOT
Crash history near site	If requested by VDOT	If requested by VDOT	If requested by VDOT
Sight distance	If requested by VDOT	If requested by VDOT	If requested by VDOT
Analysis of Future Conditions without Development
Description of and justification for the method and assumptions used to forecast future traffic volumes.	Required	Required	Required
Analyses for intersections and roadways as identified by VDOT. Delay and Level of Service (LOS) are tabulated and LOS is presented on diagrams for each lane group.	Required	Required	Required
When the type of development proposed would indicate significant potential for walking, bike, or transit trips either on - site or off - site, analyses of pedestrian and bicycle facilities, and bus route or routes and segment or segments tabulated and presented on diagrams, if facilities or routes exist or are planned.	Within 2,000 feet of site	Within 2,000 feet of site	To be determined by VDOT in consultation with the locality at the scope of work meeting
Trip Generation
Site trip generation, with tabulated data, broken out by analysis year for multi-phase developments, and including justification for deviations from ITE rates, if appropriate.	Required	Required	Required
Description and justification of internal capture reductions for mixed use developments and pass-by trip reductions, if appropriate, including table of calculations used.	Required	Required	Required
Site Traffic Distribution and Assignment
Description of methodology used to distribute trips, with supporting data.	Required	Required	Required
Description of the direction of approach for site generated traffic and diagrams showing the traffic assignment to the road network serving the site for the appropriate time periods.	Required	Required	Required
Analysis of Future Conditions With Development
Forecast daily and peak hour of the generator traffic volumes on the highway network in the study area, site entrances and internal roadways, tabulated and presented on diagrams.	Future background + site generated traffic, at each expected phase and at build - out or six years after start, whichever is later	Future background + site generated traffic, at each expected phase, at build - out, and six years after build - out, which may be extended or reduced by VDOT in consultation with the locality	At a minimum the future background + site generated traffic, at each expected phase, at build - out, and six years after build - out; may be extended by VDOT in consultation with the locality
Analyses for intersections and roadways identified by VDOT. Delay and Level of Service (LOS) are tabulated and LOS presented on diagrams for each lane group.	Required	Required	Required
When the type of development proposed would indicate significant potential for walking, bike, or transit trips either on - site or off - site, analyses of pedestrian and bicycle facilities, and bus route or routes and segment or segments tabulated and presented on diagrams, if facilities or routes exist or are planned.	Within 2,000 feet of site	Within 2,000 feet of site	To be determined by VDOT in consultation with the locality
Recommended Improvements
Description and diagram of the location, nature, and extent of proposed improvements, with preliminary cost estimates as available from VDOT.	Required	Required	Required
Description of methodology used to calculate the effects of travel demand management (TDM) measures, if proposed, with supporting data.	Required if TDM proposed	Required if TDM proposed	Required if TDM proposed
Analyses for all proposed and modified intersections in the study area under the forecast and site traffic. Delay, and Level of Service (LOS) are tabulated and LOS presented on diagrams for each lane group. For intersections expected to be signalized, MUTCD Signal Warrant analysis or ITE Manual for Traffic Signal Design, as determined by VDOT, presented in tabular form.	Required	Required	Required
When the type of development proposed would indicate significant potential for walking, bike, or transit trips either on - site or off - site, analyses of pedestrian and bicycle facilities, and bus route or routes and segment or segments tabulated and presented on diagrams, if facilities or routes exist or are planned.	Within 2,000 feet of site	Within 2,000 feet of site	To be determined by VDOT in consultation with the locality
Conclusions
Clear, concise description of the study findings.	Required	Required	Required

Notwithstanding the geographic scope noted above, the geographic scope of the study noted above may be reduced or enlarged based upon layout of the local transportation network, the geographical size of the development, and the traffic volume on the existing network, as determined by VDOT in consultation with the locality and the applicant, if applicable. Typically, analysis will be conducted for any roadway on which the additional trips generated by the proposal have a materially detrimental impact on traffic conditions. The analysis presented in the VTIS need not include all roadway and roadway segments located within the geographic scope of the study as determined by VDOT.

2. A VTIS for a development proposal that only meets the low volume road submission criterion (24VAC30-155-40 A 3) shall, at a minimum, consist of the following elements, unless otherwise directed by VDOT.

a. All elements contained in the Background Information portion of the above table in subsection C of this section, except the geographic scope/limits of study area is limited to the highway fronting the proposed development and the closest intersection, in each direction if applicable, of that highway with a highway that has an average daily traffic volume higher than the fronting highway.

b. A roadway safety inventory study of the roadway segment or segments between the site entrance to the nearest intersections with the higher traffic volume highways, to include such elements as, but not limited to, speed limit, existing warning signs, pavement and shoulder type, pavement and shoulder width, intersection sight distances, and safe horizontal curve speeds.

c. Daily and peak hour traffic volumes presented on diagrams, with counts provided in an appendix, for the fronting highway at the site, at the highway's intersections with the higher volume highway, and for the higher volume highways at their intersection with the fronting highway.

d. All relevant elements contained in the Trip Generation portion of the above table in subsection C of this section.

e. Projected daily and peak hour of the generator traffic volumes assuming build-out of the proposal, presented on diagrams for the receiving highway at the site, at the highway's intersection with the higher volume highways, and for the higher volume highways at their intersections with the receiving highway.

f. Delay and level of service analysis for the intersections of the receiving highway with the higher volume highways.

g. A comparison of the existing geometrics of the fronting highway under proposed build-out traffic conditions with the geometric standards, based upon functional classification and volume, contained in the Road Design Manual, 2011 (VDOT).

3. A VTIS for a rezoning proposal may be prepared in accordance with the "Less than 500 Site Generated Peak Hour Trips" category in the table in subsection C of this section, regardless of actual projected trip generation, provided that:

a. The rezoning proposal is in conformance with a locality's adopted comprehensive plan that was reviewed in accordance with 24VAC30-155-30; and

b. The review of the comprehensive plan included the submission to VDOT of a technical evaluation of the traffic impacts for anticipated development based on the future land use policies and map.

D. Methodology and standard assumptions. A VTIS shall be prepared based upon methodology and assumptions noted below or as may be agreed upon by VDOT based upon the results of a scope of work meeting held by VDOT pursuant to this section.

1. Data collection. Preparers shall collect traffic data in accordance with the identified study area. The count data shall include, at a minimum, weekday 24-hour counts, and directional turning movement counts during AM and PM peak times of the day. The 24-hour counts shall include vehicle classification counts. With approval of VDOT, data collected by the transportation professional preparer within the last 24 months may be used, likewise for data from the VDOT count program.

The preparer shall monitor traffic operations during data collection to ensure extraneous events such as vehicle crashes or special event traffic do not affect integrity of count data. Preparers collecting data for utilization in traffic impact studies shall normally avoid data collection during the following instances:

a. Holidays or times of the year when the traffic patterns are deemed to be unrepresentative of typical conditions, unless required by VDOT or the locality, or both.

b. Summer months if school or schools in proximity.

c. Fridays and weekends unless required by VDOT or the locality, or both.

d. Other times of the year contingent upon existing adjacent land use activities.

e. During times of inclement weather.

2. Trip generation. Estimates of trip generation by a proposed development shall be prepared using the Institute of Transportation Engineers Trip Generation, 8th Edition, 2008, unless VDOT agrees to allow the use of alternate trip generation rates based upon alternate published guides or local trip generation studies. VDOT shall at all times after July 1, 2011, have at least one non-ITE trip generation methodology or alternative rate approved for the use in preparation of small area plan traffic impact statements pursuant to 24VAC30-155-30 C that recognizes the benefits of reduced vehicle trip generation and vehicle miles traveled from developments that meet the criteria for a small area plan pursuant to this regulation. Such alternate methodology or rate can be modified based upon local factors if agreed to at a scoping meeting. Rezoning proposals shall assume the highest vehicle trip generating use allowable under the proposed zoning classification. In determining which trip generation process (equation or rate) may be used, the preparer shall follow the guidance presented in the Trip Generation Handbook, Second Edition – an ITE Recommended Practice, 2004, which is summarized here in this subdivision, except rates may be utilized if the criteria for the use of regression equations are not met. Regression equations to calculate trips as a result of development shall be utilized, provided the following is true:

a. Independent variable falls within range of data; and

b. Either the data plot has at least 20 points; or

c. R² is greater than 0.75, equation falls within data cluster in plot and standard deviation greater than 110% of weighted average rate.

If the above criteria are not met, then the preparer can use average trip rates, though if the following do not apply a rate based upon the study of similar local sites should be considered:

d. At least three data points exist;

e. Standard deviation less than 110% of weighted average rate; and

f. Weighted average rate falls within data cluster in plot.

3. Internal capture and pass-by trips.

a. Internal capture rates consider site trips "captured" within a mixed use development, recognizing that trips from one land use can access another land use within a development without having to access the adjacent street system. Mixed use developments include a combination of residential and nonresidential uses or a combination of nonresidential uses only. Internal capture allows reduction of site trips from adjacent intersections and roadways. For traffic impact statements prepared for small area plans pursuant to 24VAC30-155-30 C, the internal capture rate or rates may be based on the non-ITE trip generation methodology approved by VDOT. For ITE-based methodologies, unless otherwise approved by VDOT, the following internal capture rates should be used if appropriate:

(1) Residential with a mix of nonresidential components – use the smaller of 15% of residential or 15% nonresidential trips generated.

(2) Residential with office use – use the smaller of 5.0% of residential or 5.0% of office trips generated.

(3) Residential with retail use – for AM peak hour, use the smaller of 5.0% residential or 5.0% retail trips generated; for PM peak hour, use the smaller of 10% residential or 10% retail trips generated; for 24-hour traffic, use the smaller of 15% residential or 15% retail trips generated.

(4) Hotel/motel with office use – use 15% of hotel/motel trips, unless the overall volume of the office traffic is more than the overall volume of hotel/motel traffic use in which case use the smaller of 10% of the hotel/motel traffic or the office traffic.

(5) Multiuse development with more than five million square feet of office and retail – internal capture rate should be determined in consultation with and approval of VDOT.

(6) Office with retail use – use the smaller of 5.0% office or retail trips generated.

(7) Some combination of the above, if approved by VDOT.

b. Pass-by trip reductions consider site trips drawn from the existing traffic stream on an adjacent street, recognizing that trips drawn to a site would otherwise already traverse the adjacent street regardless of existence of the site. Pass-by trip reductions allow a percentage reduction in the forecast of trips otherwise added to the adjacent street from the proposed development. The reduction applies only to volumes on adjacent streets, not to ingress or egress volumes at entrances serving the proposed site. Unless otherwise approved by VDOT, the pass-by rates utilized shall be those reported in Trip Generation Handbook, Second Edition – an ITE Recommended Practice, 2004. For traffic impact statements prepared for small area plans pursuant to 24VAC30-155-30 C, the pass-by trip reductions may be based on the non-ITE trip generation methodology approved by VDOT.

4. Trip distribution. In the absence of more detailed information, trip distribution shall be in accordance with logical regional travel patterns as suggested by existing highway directional split and intersection movements or population and destination site distribution and shall recognize the effects of increased street connectivity if such streets meet the requirements of the Secondary Street Acceptance Requirements (24VAC30-92). If more detailed information is available from trip origin/destination studies, marketing studies, or regional planning models, this may be used to distribute trips upon approval of VDOT.

5. Planning horizon. In general, the analysis years shall be related to (i) the opening date of the proposed development, (ii) build-out of major phases of a multiyear development, (iii) long-range transportation plans, and (iv) other significant transportation network changes. The preparer should establish the planning horizon in consultation with and subject to the acceptance of VDOT.

6. Background traffic growth. Unless directed by VDOT, geometric growth (or compound growth), based upon historical growth rates, shall generally be used for determining future background traffic levels where extensive traffic-count history is available and capacity constraint is not appropriate. This growth rate replicates "natural growth" and is typical for projecting urban growth. Natural growth of traffic can be adjusted consistent with traffic forecasts associated with previously submitted local land development projects within the study area.

7. Future conditions. For the purpose of the VTIS, future conditions shall include background traffic and additional vehicle trips anticipated to be generated by approved but not yet constructed or improved projects.

8. Level of service calculation. Level of service (LOS) analysis for highways shall utilize the techniques described in the Highway Capacity Manual, 2010 (TRB). Neither the intersection capacity utilization method nor the percentile delay method may be used in the traffic impact calculations of delay and level of service. Preparers shall consult with VDOT on which traffic analysis software package is to be used to conduct the LOS calculations. The results shall be tabulated and displayed graphically, with levels of service provided for each lane group for each peak period. All data used in the calculations must be provided along with the results of the capacity analysis. Any assumptions made that deviate from the programmed defaults must be documented and an explanation provided as to why there was a deviation. Electronic files used for the analysis shall be provided to VDOT as a digital submission (e.g., .hcs, .sy6, .inp, .trf files), along with the printed report. If intersections analyzed are in close proximity to each other so that queuing may be a factor, VDOT may require the inclusion of an analysis with a micro simulation model. Unless actual on-ground conditions dictate otherwise, preparers should use the following defaults when utilizing the Highway Capacity Software (HCS) or other approved programs when evaluating roadway components:

a. Terrain – choose the appropriate terrain type. Most of the state will be level or rolling, but some areas may qualify for consideration as mountainous.

b. Twelve-foot wide lanes.

c. No parking or bus activity unless field conditions include such parking or bus activity or unless the locality has provided VDOT with a written statement of intent for the services to be provided.

d. Peak hour factor by approach – calculate from collected traffic counts (requires at least a peak hour count in 15-minute increments). However, the use of peak hour factors lower than 0.85 shall only be allowed if based upon the average of more than three peak hour counts. For future conditions analysis, unless specific site conditions can be expected to create extreme peak hour factors, default peak hour factors between 0.92 and 1.00 should be used.

e. Heavy vehicle factor – calculate from collected traffic (classification) counts or obtain from VDOT count publications. For future conditions analysis with development traffic, the existing heavy vehicle factor should be adjusted based upon the nature of the traffic being generated by the development.

f. Area type – noncenter of business district.

The VTIS shall identify any existing or proposed bicycle and pedestrian accommodation that would be affected by the proposal. For the purposes of this subsection, a bicycle accommodation is defined as on-street bike lanes, paved shoulders of roadways that are not part of the designated traveled way for vehicles, or exclusive and shared off-street bicycle paths.

For the purposes of this subsection, a pedestrian accommodation is defined as sidewalks, intersection treatments, and exclusive or shared off-street trails or paths. If significant potential for bicycle or pedestrian trips exists, the VTIS shall include current and future service level analyses at build-out for existing or proposed bicycle and pedestrian accommodations. When the proposal requires or includes improvements or modifications to the roadway, bicycle, or pedestrian accommodations, the VTIS shall analyze the impacts of such improvements and modifications on bicycle and pedestrian accommodations and service levels, and provide recommendations for mitigation of adverse impacts.

The VTIS shall provide analysis for all bus service with routes that have, or will have a station or stop within 2,000 feet of the proposal. The VTIS shall evaluate and discuss potential for increased demand for bus use due to the proposal, addressing whether such increases will result in longer dwell time at stops or increase the need for buses on a route. The quality of service analysis for bus service shall be determined in accordance with the Transit Capacity and Quality of Service Manual, 2nd Edition, 2003 (TRB). The VTIS shall provide both route and segment quality of service. The VTIS may consider the benefits of dedicated bus lanes for more frequent and rapid service. The VTIS shall provide recommendations for mitigation of adverse impacts where adverse impacts are expected to the quality of service to bus service. If an analysis of pedestrian quality or level of service is required for calculation of the bus quality of service, the preparer shall use a methodology approved by VDOT.

9. Trip reduction, and pedestrian and bicycle accommodations. When a proposal meets the criteria listed below, the preparer of the VTIS may reduce the number of vehicle trips generated by the proposal in the VTIS analysis in accordance with this subsection. Notwithstanding the percentages below, the total number of reductions used by a preparer in accordance with this subsection shall not exceed 500 vehicle trips per peak hour of the generator unless otherwise approved by VDOT. The trip reductions for traffic impact statements prepared for small area plans pursuant to 24VAC30-155-30 C may be based on the non-ITE trip generation methodology approved by VDOT and are not subject to limitations or requirements of this subdivision.

a. Pedestrian accommodations. For the purposes of this subsection, a pedestrian accommodation is defined as a sidewalk, pedestrian path, or multiuse trail. Where a pedestrian service level of A exists, vehicle trips per peak hour of the generator may be reduced by 4.0% for those portions of the development within a 2,000-foot radius of the connections between the proposed development and the adjoining network. Where a pedestrian service level of B exists, vehicle trips per peak hour of the generator may be reduced by 3.0%; where a pedestrian service level of C exists, vehicle trips per peak hour of the generator may be reduced by 1.5% for the portion of the development noted above. These reductions may only be taken if:

(1) Pedestrian facility coverage in a 2,000-foot radius of the connections to the proposed development is on or along at least 80% of the road network;

(2) The pedestrian facilities inside and outside the development provide reasonably direct access to traffic generators; and

(3) There are at least two of the 10 major land use classifications, as defined in ITE Trip Generation, 8th Edition, 2008, within the 2,000-foot radius.

b. Bicycle accommodations. For the purposes of this subsection, a bicycle accommodation is defined as a street with a design speed of 25 MPH mph or less that carries 400 vehicles per day or less, on-street bike lanes, a pedestrian accommodation, paved shoulders of roadways that are not part of the designated traveled way for vehicles and are at least two feet wide, or exclusive and shared off-street bicycle paths. Where a bicycle service level of A exists, vehicle trips per day may be reduced by 3.0%. Where a bicycle service level of B exists, vehicle trips per day may be reduced by 2.0%. Where a bicycle service level of C exists, vehicle trips per day may be reduced by 1.0%. These reductions may only be taken if:

(1) Bicycle accommodations within a 2,000-foot radius of the connections to the proposed development exist on or along at least 80% of the road network;

(2) The bicycle accommodations inside and outside the development provide reasonably direct access to traffic generators; and

(3) There are at least two of the 10 major land use classifications as defined in ITE Trip Generation, 8th Edition, 2008, within the 2,000-foot radius.

10. Modal split and trip reduction. All vehicle trip reductions used in the VTIS pursuant to this subsection are subject to the approval of VDOT.

a. If a proposal is located within 1/2 mile along roadways, pedestrian or bicycle accommodations of a transit station, excluding bus stops and stations, reasonable vehicle trip reductions of vehicle trips generated by the proposal may be made with approval of VDOT. The preparer shall submit documentation to justify any such vehicle trip reductions used with the VTIS. When a proposal is located more than 1/2 mile but less than two miles from a transit stop, excluding bus stops and stations, with bicycle parking accommodations additional bicycle modal split reductions may be utilized. The analysis of capacity of the parking accommodations shall be included in the VTIS when such trip reductions are used.

b. If a proposal is located within 1/4 mile along roadways, pedestrian or bicycle accommodations of a bus stop or station where the segment and route service levels are C or higher, reasonable vehicle trip reductions of vehicle trips generated by the proposal may be made with the approval of VDOT. The preparer shall submit documentation to justify any such vehicle trip reductions used with the VTIS.

c. Transit and bus modal split data from similar developments within the geographic scope of the VTIS or one mile of the proposal, whichever is greater, shall be collected if the VTIS vehicle trip reductions are used pursuant to this subsection and similar developments exist within the geographic scope of the VTIS or one mile of the proposal, whichever is greater.

11. Signal warrant analysis. Traffic signal warrant analysis shall be performed in accordance with the procedures set out in the Manual on Uniform Traffic Control Devices, 2003, revised 2007 Standards for Use of Traffic Control Devices to Classify, Designate, Regulate, and Mark State Highways (24VAC30-315), or ITE Manual of Traffic Signal Design, 1998, as determined by VDOT.

12. Recommended improvements. Recommendations made in the VTIS for improvements to transportation facilities shall be in accordance with the geometric standards contained within the Road Design Manual, 2011 (VDOT).

DOCUMENTS INCORPORATED BY REFERENCE (24VAC30-155)

Requests for information pertaining to the availability and cost of any of these publications should be directed to the address indicated for the specific document. Requests for documents available from VDOT may be obtained from VDOT's division and representative indicated; however, VDOT documents may be available over the Internet at www.vdot.virginia.gov.

Highway Capacity Manual, 2010, Transportation Research Board, 500 Fifth Street NW, Washington, DC 20001.

ITE Manual of Traffic Signal Design (1998), Institute of Transportation Engineers, 1627 Eye Street, NW, Suite 600, Washington, DC 20006.

Manual on Uniform Traffic Control Devices for Streets and Highways, effective 2003, revised 2007, Federal Highway Administration, Superintendent of Documents, U.S. Government Printing Office, P.O. Box 371954, Pittsburgh, Pennsylvania 15250.

Road Design Manual, 2011, VDOT, 1401 E. East Broad Street, Richmond, Virginia 23219.

Transit Capacity and Quality of Service Manual, 2nd Edition, 2003; Transportation Research Board of the National Academies, Keck Center of the National Academies, Transportation Research Board, 500 Fifth Street, NW, Washington, DC 20001.

Trip Generation, 8th Ed. Edition, 2008, Institute of Transportation Engineers, 1627 Eye Street, NW, Suite 600, Washington, DC 20006.

Trip Generation Handbook, Second Edition – an ITE Recommended Practice, 2004, Institute of Transportation Engineers, 1627 Eye Street, NW, Suite 600, Washington, DC 20006.

24VAC30-315-10. General provisions.

A. The Manual on Uniform Traffic Control Devices for Streets and Highways, 2009 Edition (2009 MUTCD), is incorporated by reference in the Code of Federal Regulations (23 CFR Part 655 Subpart F), and is accessible from http://mutcd.fhwa.dot.gov/. 23 CFR 655.603 (December 19, 2023) adopts the National Manual on Uniform Traffic Control Devices for Streets and Highways (National MUTCD) as the national standard for any street, highway, or bicycle trail open to public travel in accordance with the United States Code (23 USC §§ 109 (d) and 402 (a)), and the National MUTCD shall apply to all such locations in Virginia except those specified in subsection B of this section.

B. The 2009 MUTCD dated December 2009 shall be the standard for all highways under the jurisdiction of the Virginia Department of Transportation, with the following exceptions: (i) the Virginia Supplement to the 2009 MUTCD (2011 Edition) contains standards and guidance that exceed minimum federal requirements concerning traffic control devices and presents additional pertinent traffic control parameters not addressed by the 2009 MUTCD and (ii) the Virginia Department of Transportation uses the Virginia Work Area Protection Manual (WAPM) (2011 Edition), which is a part of the Virginia Supplement to the 2009 MUTCD (2011 Edition), instead of the 2009 MUTCD Part 6, Temporary Traffic Control The Virginia Manual on Uniform Traffic Control Devices for Streets and Highways, which includes the Virginia Work Area Protection Manual (Virginia MUTCD), version 11.0 (2025), shall be the standard for all traffic control devices on streets, highways, and bicycle facilities under the jurisdiction of the Virginia Department of Transportation. All signs, signals, pavement markings, and other traffic control devices under the jurisdiction of the Virginia Department of Transportation or on streets, highways, and bicycle facilities under the jurisdiction of the Virginia Department of Transportation shall conform accordingly.

C. Where (i) state standards exceed the minimum federal requirements; (ii) the 2009 MUTCD does not cover some design, installation, and operation details; or (iii) additional guidance on traffic control devices is needed, the Commissioner of Highways or a designee is authorized to establish and distribute appropriate documentation including, but not limited to, standards, specifications, and instructional memoranda. The Virginia Supplement to the 2009 MUTCD (2011 Edition) and the WAPM (2011 Edition) shall be applicable for all highways under the jurisdiction of the Virginia Department of Transportation. If there is a conflict between the 2009 MUTCD and the Virginia Supplement to the 2009 MUTCD (2011 Edition), the Virginia Supplement shall govern.

D. The Commissioner of Highways or a designee is authorized to make revisions to the Virginia Supplement to the MUTCD (2011 Edition) or the WAPM (2011 Edition), or both, to reflect changes to the Code of Virginia or to the 2009 MUTCD as incorporated into the Code of Federal Regulations and to be consistent with the Code of Virginia where discretion is allowed.

E. In addition to the authority referenced in subsection C of this section, the C. The Commissioner of Highways is authorized to act for and on behalf of the Commonwealth Transportation Board in matters relating to classifying, designating, regulating, and marking state highways and the installation of signals, signs, and markings to regulate, control, and manage traffic movement.

DOCUMENTS INCORPORATED BY REFERENCE (24VAC30-315)

Manual on Uniform Traffic Control Devices for Streets and Highways, 2009 edition, December 2009, U.S. Department of Transportation, Federal Highway Administration, 1200 New Jersey Avenue, S.E., Washington, DC 20590, telephone (202) 366-1993. The text is also available from the Federal Highway Administration's website at http://mutcd.fhwa.dot.gov and by individual parts and chapters below:

Cover, Table of Contents, and Introduction

Part 1 - General

Part 2 - Signs

Chapter 2A - General

Chapter 2B - Regulatory Signs, Barricades, and Gates

Chapter 2C - Warning Signs and Object Markers

Chapter 2D - Guide Signs - Conventional Roads

Chapter 2E - Guide Signs - Freeways and Expressways

Chapter 2F - Toll Road Signs

Chapters 2G-2H - Preferential and Managed Lane Signs and General Information Signs

Chapters 2I-2N - General Service Signs, Specific Service Signs, Tourist-Oriented Directional Signs, Changeable Message Signs, Recreational and Cultural Interest Area Signs, and Emergency Management Signing

Part 3 - Markings

Part 4 - Highway Traffic Signals

Part 5 - Traffic Control Devices for Low-Volume Roads

Part 7 - Traffic Controls for School Areas

Part 8 - Traffic Control for Railroad and Light Rail Transit Grade Crossings

Part 9 - Traffic Control for Bicycle Facilities

Appendices A1 and A2 - Congressional Legislation and Metric Conversions

Virginia Supplement to the 2009 MUTCD, 2011 Edition, Virginia Department of Transportation, 1401 E. Broad Street, Richmond, Virginia 23219:

Cover and Introduction

1. General

2. Signs

3. Markings

4. Signals

7. Schools

8. Railroads

9. Bicycles

Appendix A

Virginia Work Area Protection Manual (WAPM), 2011 Edition, Virginia Department of Transportation, 1401 E. Broad Street, Richmond, Virginia 23219 ( https://www.vdot.virginia.gov/doing-business/technical-guidance-and-support/technical-guidance-documents/work-area-protection-manual-and-pocket-guide/).

Virginia Standard Highway Signs, 2011 Edition, Virginia Department of Transportation, 1401 E. Broad Street, Richmond, Virginia 23219 ( https://www.vdot.virginia.gov/doing-business/technical-guidance-and-support/technical-guidance-documents/virginia-standard-highway-signs/).

Virginia Manual on Uniform Traffic Control Devices for Streets and Highways, January 2026, Version 11.0 (eff. 1/2026)

Virginia Work Area Protection Manual, January 2026, Version 11.0 (eff. 1/2026)

24VAC30-325-10. Eligibility criteria and conditions governing receipt and use of urban maintenance funds.

A. In addition to the eligibility requirements identified in § 33.2-319 of the Code of Virginia, the road and street eligibility criteria for urban maintenance payments shall also include the following:

1. The basic right-of-way width for cul-de-sacs eligible for payment will be 40 feet, with consideration of requests for pavement widths less than 30 feet. For the purpose of making this assessment, a cul-de-sac will be defined as a dead-end street, open only at one end.

2. If a municipality has jurisdiction over and operates a toll facility, such facility is eligible for street payments.

3. Local one-way streets, loop roads, and school bus entrances will be eligible for payment provided that they are constructed to a width of 16 feet with a right-of-way width of not less than 40 feet. This includes service and frontage roads where contiguous to an interstate, primary, or urban system route.

4. VDOT can consider a waiver of standards on a site-specific basis with appropriate supporting information. Each case will be considered on its own merits.

B. In determining lane mileage eligibility, the following conditions will apply:

1. Turning lanes and ramps will not be considered for street payments. This includes center turn lanes unless they serve as moving through lanes during peak hours.

2. Parking must be restricted and enforced by towing during peak traffic periods.

3. Each road or street with more than two moving lanes must have pavement markings in accordance with the Manual on Uniform Traffic Control Devices for Streets and Highways, 2003 Edition, including Revision 1 dated November 2004, published by the U.S. Department of Transportation, Federal Highway Administration Standards for Use of Traffic Control Devices to Classify, Designate, Regulate, and Mark State Highways (24VAC30-315).

4. Pavement widths of less than 14 feet qualify for only one moving lane even if it carries traffic in two directions.

5. Nonhard surfaced streets do not qualify for street payments.

C. Mileage adjustments, including the results of annexations, mergers, or incorporations, will be made on an annual basis as part of the board's approval of the annual maintenance payments. All adjustments submitted to the department by February 1 will be eligible for payment effective July 1 of the following fiscal year.

D. For the purpose of calculating maintenance payments, streets will be functionally classified based on the Federal Functional Classification system, except where the federal system is not parallel with the state system.

E. Bridge safety and regular inspection is of utmost importance. The Federal Highway Administration and the department require strict compliance with the National Bridge Inspection Standards (23 CFR Part 650) regarding the frequency of inspection and load posting requirements. The Commissioner of Highways may elect to withhold street payments from a municipality for delinquent or inadequate bridge inspection reports.

F. The Commissioner of Highways is directed to establish administrative procedures to assure ensure the provisions of this chapter and legislative directives are adhered to and complied with.

24VAC30-325-20. Document incorporated by reference. (Repealed.)

Information pertaining to the availability and cost of the Manual on Uniform Traffic Control Devices (MUTCD), 2003 Edition with Revision No. 1 Incorporated, dated November 2004, should be directed to Federal Highway Administration, Superintendent of Documents, U.S. Government Printing Office, P.O. Box 371954, Pittsburgh, PA 15250-7954. The MUTCD is also available from the following website: http://mutcd.fhwa.dot.gov/index.htm.

DOCUMENTS INCORPORATED BY REFERENCE (24VAC30-325)(Repealed)

Manual on Uniform Traffic Control Devices (MUTCD), 2003 Edition with Revision 1 Incorporated November 2004, Federal Highway Administration.

24VAC30-630-10. Requests for signs.

A. Any person who is deaf, blind, or deaf-blind; any person with autism or an intellectual or developmental disability as defined in § 37.2-100 of the Code of Virginia; or the agent of any such person may submit a request to the Virginia Department of Transportation (VDOT) by filling out a Request for Person with Disability Sign Form and submitting the completed form to the local VDOT office in the area where the sign is requested. The submitted form must include (i) medical certification that such person meets the disability requirement and (ii) the location of the requested sign.

B. Signs shall conform to the edition of the Manual on Uniform Traffic Control Devices for Streets and Highways (MUTCD) and the Virginia Supplement to the MUTCD in 24VAC30-315-10 Standards for Use of Traffic Control Devices to Classify, Designate, Regulate, and Mark State Highways (24VAC30-315) .

C. The requestor shall notify the VDOT office to which the original request was made of any change in circumstances such that the sign is no longer necessary (e.g., when the person with a disability relocates).

24VAC30-630-20. Signs; type, size, color, location, and installation.

A. Signs warning drivers to be aware of persons with disabilities must be posted on a non-limited access highway maintained by the Virginia Department of Transportation (VDOT) and shall be installed in advance of the location where a person with a disability may be on or near the roadway, such that motorists may effectively perceive and respond to the signs.

B. The type, size, color, installation, and specific location of signs shall be determined at VDOT's discretion using engineering judgment in accordance with related VDOT procedures and regulations (, including the MUTCD and the Virginia Supplement to the MUTCD as referenced in 24VAC30-630-10 Standards for Use of Traffic Control Devices to Classify, Designate, Regulate, and Mark State Highways (24VAC30-315).

C. Signs warning drivers to be aware of persons with disabilities may not be posted:

1. Where any pedestrian activity is highly discouraged due to safety concerns.

2. Where they may conflict with, are redundant to, or in combination (e.g., on the same pole) with any other regulatory or warning signs.

3. Closer than 200 feet to any existing regulatory or warning signs.

4. At signalized locations such as crosswalks at intersections or pedestrian hybrid beacons. Requests concerning a person with a visual disability and the absence of accessible pedestrian signals at a particular traffic signal will be addressed separately.

5. At a crossing with an existing rectangular rapid flashing beacon. Requests concerning a person with a visual disability and the absence of audible information devices will be addressed separately.

6. At any location in which the presence of the sign would otherwise create a safety concern, in the discretion of VDOT.