FHWA and MnDOT are conducting a comprehensive review of the Twin Cities Regional Functional Class System. Before starting any change request paperwork, please contact David Burns at 651-602-1887 to discuss how this review may impact your request.
Please review Functional Classification overview pages before requesting changes.
The Council works with MnDOT to aggregate the functional class data for reporting to the Federal Highway Administration (FHWA). Since the FHWA requires that MnDOT report only the functional classification of existing roads, the Council maintains two functional roadway data layers: existing functional class roadways and planned functional class roadways.
These data layers are maintained independently but the process to change the functional classification of the datasets are identical. This is necessary to ensure that reporting is consistent but allows for local planning activities (such as managing access control for planned facilities) to proceed. Local units should direct their requests for changes to the appropriate layer using the following criteria:
- Planned roadways show future functional class of the roadway. They can be unconstructed segments or can overlay an existing functional class road that is planned to change in future.
- Existing roadways MUST function according to the proposed designation in the change request form. It is essential that roadways in the existing functional classification layer exhibit the characteristics of the designation that is being requested.
At this time, local units can submit a roadway for Regional Solicitation fund projects in either the existing OR the planned classification. MnDOT and FHWA reports will include only the existing functional classifications.
Instructions for submitting a Functional Classification Change Request
Only government agencies may submit change requests and only for roadways which are under their jurisdiction.
Requests for changes to roadway functional classification must be submitted using the functional class change request form (Microsoft Word document).
The requests will be reviewed by Met Council and MnDOT staff and sent to the TAC Planning Committee for consideration. A-Minor and Collector changes will be approved by TAC. Changes to the principal arterial system must also be approved by the full Metropolitan Council. Principal arterial requests must include local resolutions of support from impacted jurisdictions.
If submitting a large batch of collector changes, please contact Rachel Wiken (see below) before filling out forms. Collector changes can be combined to reduce paperwork.
Electronic submissions preferred.
Send completed forms in Microsoft Word format to david.burns@metc.state.mn.us
Hard copies can be mailed to:
David Burns
Metropolitan Council
390 N Robert St.
St. Paul MN 55101
Contacts
General questions about the functional class system:
David Burns
651-602-1887
[email protected]
Additional Instructions for Completing the Request Change Form
Please note: for our review process, each request may only have one current functional class. If a roadway for a requested change is not currently a single functional class throughout its full length, please split the roadways into several requests, filling out the top part of page one (From Roadway Name to Purpose of Change) for each section. Purpose of Change and Supporting Criteria need only to be completed once for all sections of a roadway if the related requests are noted.
ID numbers will be assigned by Met Council staff as requests are received. Please leave this field blank.
Roadway Name: Include full roadway names in addition to county and MSA numbers.
Functional Classification Information: Please provide the regional functional class for both the current and requested classification of the road.
- Principal Arterial
- A Minor Augmentor
- A Minor Reliever
- A Minor Expander
- A Minor Connector
- Other Minor Arterial
- Major Collector
- Minor Collector
- Local
See information about the regional functional class and maps of current functional classifications
Contingent Conditions: If requesting a planned alignment, include a short description under explaining requirements for the road to change from planned to existing in the future.
Dependent Requests: Requests which are connected and could not be logically approved individually are dependent requests. Indicate the names of dependent requests.
Boundaries / Letter of Support: For requests which cross a jurisdictional boundary, a letter of support is required from the neighboring city/county. For roads which function as municipal boundaries, a letter of support from the adjacent city/township, or a document showing which has jurisdiction for the segment in question, is required. Principal Arterial requests require formal resolutions of support from impacted communities.
Purpose of Change: Please briefly describe why request is needed.
Typical Characteristics are not required for any change but are helpful in evaluating the request. Contact Information must be submitted for each request.
Technical Corrections: If the request is addressing a technical correction (ex. small segment missing, previously approved request not included on the map, etc.) include a short explanation under Purpose of Change. Additional information is not required.
Note: If our staff does not agree that this is a technical correction, the request may be returned for Supporting Criteria.
A detailed map is required for all requests.
Connectivity
The Functional Classification system should maintain connectivity.
- Intersection — Classifications of roads should only change at intersections with other functional class roads.
- Boundary — Classifications should remain consistent across jurisdictional boundaries. Obtain a letter of support from adjacent communities to continue the request into their jurisdiction or truncate the request to another functional class road. Principal Arterial requests require formal resolutions of support from impacted communities.
- Dead Ends — Functional class roads should not end on local streets or dead end.
- Exceptions — There are exceptions in the system (ex. a dead end collectors which connect to major parks or employment centers), but a supporting explanation is required if the request does not follow regular connectivity guidelines.