MnDOT Design-Build Program
Federal Project No. [insert #]
11
ROADWAYS
11.1
General
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
Conduct all Work necessary to meet the requirements of roadways. Roadway classifications include mainline
lanes, acceleration lanes, deceleration lanes, auxiliary lanes, escape lanes, ramps, loops, frontage roads,
county roads (including County State Aid Highways [CSAH]), city streets (including Municipal State Aid
[MSA] routes), township roads, and private entrances.
Conduct all Work necessary to meet the requirements of grading, including clearing and grubbing, excavation and embankment, removal of existing buildings and miscellaneous structures, subgrade preparation, and
stabilization.
11.2
Administrative Requirements
11.2.1
Standards
In the event of a conflict between the standards set forth in Book 3 relating to roadways, the order of
precedence shall be as set forth below, unless otherwise specified:
11.2.1.1 Trunk Highway System
 MnDOT Special Provisions
 MnDOT Technical Memoranda
 MnDOT Standard Specifications for Construction
 MnDOT Road Design Manual
 MnDOT LRFD Bridge Design Manual
 MnDOT Standard Plans Manual
 MnDOT Standard Plates Manual
 AASHTO A Policy on Geometric Design of Highways and Streets
 AASHTO Roadside Design Guide
 NCHRP Report 350
 Remaining standards set forth in Book 3
11.2.1.2 State Aid Road System
 MnDOT Special Provisions
 MnDOT Standard Specifications for Construction
 MnDOT State Aid Manual
 MnDOT Road Design Manual
 MnDOT Standard Plans Manual
 MnDOT Standard Plates Manual
 AASHTO A Policy on Geometric Design of Highways and Streets
 AASHTO Roadside Design Guide
 Remaining standards set forth in Book 3
11.2.1.3 Local Road System
Meet local road criteria provided by the local governing agencies unless otherwise specified in Book 2.
RFP
Roadways
11-1
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
11.2.2
Meeting Requirements
11.2.3
Equipment/Software
11.2.4
Permits/Authorizations
11.3
Design Requirements
11.3.1
General
11.3.2
Investigations/Supplemental Work
11.3.3
Design Criteria
Either urban or rural drainage designs may be utilized unless otherwise specified in Section 11 design tables.
Identify and correct clear zone deficiencies on mainline and ramps for trunk highways within the project
limits where new construction is performed, unless otherwise specified.
On local roadways, meet either the local or the MnDOT State Aid clear zone/recovery area standards,
whichever requires a larger clear zone, unless otherwise specified.
MnDOT has preapproved the following clear zone deficiencies.
Table 11-1. Preapproval of Clear Zone Deficiencies
Roadway
Location
Barrier Required
[EXAMPLE I-35E]
Bridge pier at station 100+00 left may be within the clear zone and
at a minimum of 25 ft. from the edge of traveled lane.
Yes
[EXAMPLE
Maryland Ave]
Maryland inslopes are a hazard and within the clear zone from
station 100+00 to 200+00]
No
For State Aid roads, comply with MnDOT State Aid Operations Rules—Chapter 8820.
Apply the aesthetic minimum vertical curve length defined in Section 3-4.03 of the Road Design Manual
only to Trunk Highways. Define the minimum allowable vertical curve for all other roads by stopping sight
distance.
Define the maximum grade for freeways to be 3 percent except as noted in Section 11 design tables. Use the
Collector criteria in Table 3-4.02A of the Road Design Manual for maximum grades on local streets.
In urban section areas, use B424 curb and gutter on all trunk highways and ramps and utilize B624 curb and
gutter on all local roadways unless otherwise specificed on the following design standards tables. Extend the
freeway or ramp curb and gutter around the corner radius to the end of the radius on every cross street, then
transition to the proposed or existing urban or rural section.
Design and construct gutters as input gutters unless otherwise specified.
Unless otherwise specified, design raised medians and splitter islands at least 6 feet wide from curb face to
curb face. Do not use in combination with other types of medians or widening of shoulders along the cross
section.
RFP
Roadways
11-2
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
Follow the mailbox requirements in the special provisions and stated here for mailboxes impacted by
construction activities and examine the roadside mailbox support to determine if it is an unlawful support as
defined in the MnDOT Road Design Manual, Chapter 11. Determine if the property owner wants a lawful
mailbox support salvaged and relocated, and determine if the lawful mailbox support is in a condition that it
can be salvaged without damage. Provide MnDOT with memo explaining how and when you will contact the
property owner before making contact with the property owner. Provide a handout to the property owner that
clearly explains the policy on roadside mailboxes and unlawful mailbox supports as described in the MnDOT
Road Design Manual. If the existing mailbox support is unlawful or cannot be salvaged without damage,
then inform the property owner that they have one of two choices below:

The Contractor will furnish and install the Mailbox Support Swing-Away Type, standard plate 9350,
at no cost to the property owner and follow all other requirements of the special provisions.

The property owner will purchase, furnish, and install a complete mailbox installation that meets
standards. In this case the property owner becomes responsible for any interruptions to mail delivery
service.
For WB-62 turns onto one-lane receiving roadways, encroachment using one full opposing lane width is
allowed.
For interstates, the ramp gore can be considered as part of the ramp.
Follow the Project-specific design standards for specific roadways shown in the following tables. The ramp
design speed referenced in the following tables is for the first curve on an exit ramp and the last curve on an
entrance ramp unless otherwise specified.
Table 11-2. Project-Specific Design Standards for TH [roadway] Mainline
Roadway Type
Design Standards
Trunk Highway
Jurisdictional system
MnDOT Trunk Highway
Functional class
Access control
Highway type
Design vehicle
Terrain
Traffic volumes
AADT—2002
Projected AADT—2030
Projected posted speed
Proposed design speed
Shoulder bus use
Median type
Investment Category
Special Features:
1.
2.
3.
RFP
Roadways
11-3
MnDOT Design-Build Program
Federal Project No. [insert #]
Roadway Type
Design Standards
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
Trunk Highway
4.
5.
RFP
Roadways
11-4
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
Table 11-3. Project-Specific Design Standards for TH [roadway] Mainline
Roadway Type
Design Standards
Trunk Highway
Jurisdictional system
MnDOT Trunk Highway
Functional class
Access control
Highway type
Design vehicle
Terrain
Traffic volumes
AADT—2002
Projected AADT—2030
Projected posted speed
Proposed design speed
Shoulder bus use
Median type
Investment Category
Special Features:
1.
2.
3.
4.
5.
RFP
Roadways
11-5
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
Table 11-4. Project-Specific Design Standards for [roadway]
Roadway Type
Design Standards
Local Road
Jurisdictional system
MnDOT
Functional class
Access control
Highway type
Design vehicle
Terrain
Traffic volumes
AADT—2002
Projected AADT—2030
Projected posted speed
Proposed design speed
Shoulder bus use
Median type
Investment Category
Special Features
1.
2.
3.
4.
5.
RFP
Roadways
11-6
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
Table 11-5. Project-Specific Design Standards for Interchange TH [roadway]/TH [roadway], Individual Ramps
Roadway Type
Design Standards
West-bound Ramps
Jurisdictional system
East-bound Ramps
MnDOT trunk highway
Functional class
Freeway—principal arterial
Access control
Full
Ramp type
Design vehicle
Terrain
Investment Category
Proposed design speed
Traffic volumes
AADT—2002
Projected AADT—2030
Ramp shoulder bus use
Ramp metering
See Section 17
See Section 17
HOV bypass lanes
Yes/No?
Yes/No?
Special Features:
1.
2.
3.
4.
5.
RFP
Roadways
11-7
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
Table 11-6. Project-Specific Design Standards for Interchange Interstate [roadway] over TH [roadway], Full Cloverleaf,
Loop Ramps
Roadway Type
Design Standards
Eastbound
TH [##] Ramp to
Northbound
I-[##]
Jurisdictional system
Southbound
I-[##] Ramp to
Eastbound
TH [##]
Westbound
TH [##] Ramp to
Southbound
I-[##]
Northbound
I-[##] Ramp to
Westbound
TH [##]
MnDOT trunk highway
Functional class
Freeway—principal arterial
Access control
Full
Ramp type
Design vehicle
Terrain
Investment Category
Proposed design speed
Traffic volumes
AADT—2002
Projected AADT—2030
Ramp shoulder bus use
Ramp metering
See Section 17
See Section 17
See Section 17
See Section 17
HOV bypass lanes
Yes/No?
Yes/No?
Yes/No?
Yes/No?
Special Features:
1.
2.
3.
4.
5.
RFP
Roadways
11-8
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
Table 11-7. Project-Specific Design Standards for Interchange Interstate [roadway] over TH [roadway], Full Cloverleaf,
Diagonal Ramps
Roadway Type
Design Standards
Eastbound
TH [##] Ramp to
Southbound
I-[##]
Jurisdictional system
Northbound
I-[##] Ramp to
Eastbound
TH [##]
Westbound
TH [##] Ramp to
Northbound
I-[##]
Southbound
I-[##] Ramp to
Westbound
TH [##]
MnDOT trunk highway
Functional class
Freeway—principal arterial
Access control
Full
Ramp type
Design vehicle
Terrain
Investment Category
Proposed design speed
Traffic volumes
AADT—2002
Projected AADT—2030
Ramp shoulder bus use
Ramp metering
See Section 17
See Section 17
See Section 17
See Section 17
HOV bypass lanes
Yes/No?
Yes/No?
Yes/No?
Yes/No?
Special Features:
1.
2.
3.
4.
5.
RFP
Roadways
11-9
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
11.3.3.1 Slopes
Round slopes on the Project such that they tie naturally into adjacent slopes or the existing groundline.
Slopes steeper than 1:3 (V:H) shall not be allowed on this Project unless otherwise described in this section.
Design slopes to avoid the need for traffic barrier whenever possible. Evaluate if any portion of a fill slope
prior to the toe of slope is not recoverable, even beyond the clear zone, to determine if there is a hazard at the
bottom of the slope, such as a deep pond or other hazards, which would require a traffic barrier .
11.3.3.1.1
Slopes Beyond State Right of Way
Design grading slopes that tie into property beyond the permanent State right of way (R/W) line 1:6 (V:H) or
flatter, except in the following locations.
Table 11-8: Allowable Grading Beyond R/W Steeper than 1:6 (V:H)
Property
Allowable Grading Condition
Parcel 405
1:4 slopes may be used from permanent R/W line to existing ground.
Parcel 104
1:3 slopes may be used from permanent R/W to existing ground from I-35E station
100+00 to 200+00.
11.3.3.1.2
Inslopes on High Speed Roadways
Design inslopes on high speed roadways, including interchange ramps, to be 1:6 (V:H) or flatter within the
clear zone unless otherwise allowed in this Section. Where site conditions are restrictive and do not permit a
1:6 (V:H) or flatter slope, use other criteria shown below. Design the slopes in the order of precedence
shown below with criterion 1 being the requirement, followed by criterion 2 as the next desirable, and other
criteria in decreasing levels of desirability. Submit design plans for MnDOT Approval showing the slope
treatment to be used throughout the Project based on the criterion below. The grading design priority for
inslopes shall be as follows:
1. Use 1:6 (V:H) slopes or flatter.
2. Use slopes of 1:6 to 1:4 (V:H).
3. Use a combination of recoverable slopes (between 1:6 and 1:4 within the clear zone) and non-recoverable
slopes (between 1:4 and 1:3 outside the clear zone) creating a “barn roof” section.
4. Use non-recoverable slopes shielded by traffic barrier.
5. Use retaining walls or reinforced soil slopes where slopes steeper than 1:3 are required.
MnDOT has preapproved steeper high speed roadway inslopes at the following locations:
Table 11-9: Preapproved High Speed Roadway Inslopes Greater than 1:6 (V:H)
Roadway
Allowable Inslope
I-35E
[Example]1:2 inslopes are allowed at each bridge abutment. The inslope shall
transition to 1:3 or flatter no later than the end of the wingwall(s). The inslope shall
then meet the requirements of the remainder of this section 11 no later than 200 feet
from the abutment measured along the roadway alignment.
I-35E
[Example]1:3 inslopes are allowed from stations:
100+00 to 200+00
550+00 to 600+00
1:4 inslopes are allowed from stations:
800+00 to 900+00
RFP
Roadways
11-10
MnDOT Design-Build Program
Federal Project No. [insert #]
11.3.3.1.3
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
Inslopes on Low Speed Roadways
Design inslopes on low speed roadways to be 1:4 (V:H) or flatter unless otherwise described in this Section.
Design slopes to avoid the need for traffic barrier whenever possible. Where site conditions are restrictive
and do not permit a 1:4 (V:H) or flatter slope, use other criteria shown below with Approval by MnDOT.
Design the slopes in the order of precedence shown below with criterion 1 being the requirement, followed
by criterion 2 as the next desirable, and other criteria in decreasing levels of desirability. Submit design
plans for MnDOT Approval showing the slope treatment to be used throughout the Project based on the
criterion below. The grading design priority for inslopes shall be as follows:
1. Use 1:4 (V:H) slopes or flatter.
2. Use a combination of recoverable slopes (1:4 or flatter within the clear zone) and non-recoverable slopes
(between 1:4 and 1:3 outside the clear zone) creating a “barn roof” section.
3. Use non-recoverable slopes between 1:4 and 1:3 shielded by traffic barrier when within clear zone.
4. Use retaining walls or reinforced soil slopes where slopes greater than 1:3 are required.
MnDOT has preapproved steeper low-speed roadway inslopes at the following locations:
Table 11-10: Preapproved Low Speed Roadway Inslopes Greater than 1:4 (V:H)
Roadway
Allowable Inslope
Maryland Ave
[Example]1:2 inslopes are allowed at each bridge abutment. The inslope shall
transition to 1:3 or flatter no later than the end of the wingwall(s). The inslope
shall then meet the requirements of the remainder of this section 11 no later than
200 feet from the abutment measured along the roadway alignment.
Maryland Ave
[Example]1:3 inslopes are allowed from stations:
100+00 to 200+00
550+00 to 600+00
11.3.3.1.4
Backslopes
Design backslopes to be 1:3 (V:H) or flatter with retaining walls, if necessary, outside of the clear zone.
Where site conditions are restrictive, design a cut section retaining wall within the clear zone with proper
roadside protection if desired.
MnDOT has preapproved steeper backslopes at the following locations:
Table 11-11: Preapproved Backslopes Greater than 1:3 (V:H)
Roadway
Allowable Backslope
Maryland Ave
[Example]1:2 slopes are allowed from stations:
50+00 to 75+00
I-35E
[Example]1:2 slopes are allowed from stations:
100+00 to 200+00
550+00 to 600+00
11.3.3.1.5
RFP
Roadways
Other Slope Criteria
11-11
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
11.3.3.2 Traffic Barrier
Use galvanized steel posts for all plate beam guardrail installations unless otherwise Approved by MnDOT.
Do not connect guardrail to bridge structures or retaining walls. Do not use guardrail if a bridge structure
element or retaining wall falls within the deflection zone of the guardrail. See the MnDOT LFRD Bridge
Design Manual for guidance on placement of TL-5 barrier placement.
Use only one of the following terminals for each type of w-beam guardrail installation:
 Tangent terminal: ET-2000 Plus or SKT-350
 Flared terminal: SRT or FLEAT
11.3.3.3 Snow Storage
On trunk highways, excluding bridges, provide a minimum 10-foot-wide boulevard between the shoulder and
retaining walls supporting cut sections, unless otherwise specified elsewhere in this Section, and pave this
area with 6-inch-thick concrete walk and have a maximum slope of 1:10. If the distance between the edge of
shoulder and a retaining wall supporting cut sections is greater than 10 feet, use turf if desired.
On trunk highways, excluding bridges, provide a minimum 10-foot-wide snow storage between the shoulder
and toe of back slope in cut sections. This area may be turf and shall be 1:10 or flatter when sloped toward
the shoulder and may be any contract-compliant cross-slope draining away from the roadway adjacent to the
outside shoulder.
On trunk highways, excluding bridges, provide a minimum 10-foot-wide snow storage area between the
shoulder and objects that can be damaged by thrown snow in fill sections. Objects that can be damaged by
thrown snow include, but are not limited to, vehicles on adjacent roads, control cabinets, and buildings.
Table 11-12. Exceptions to Snow Storage Width Requirement
Minimum Width
Location
10 feet
(Example) Maryland N.E. Ramp—NWALLH1 from Maryland Ave to East Hyacinth
Avenue
3 feet
(Example) Front face of curb along Mississippi Street—NWALLH1 from East Hyacinth
Avenue to just south of Arlington Avenue
6 feet
(Example) Front face of curb along Mississippi Street—NWALLH2 from north of
Arlington Avenue to East Hoyt Avenue
10 feet
(Example) L’Orient Road—NWALLI1 from north of Arlington Avenue to south of
L’Orient Road and Wheelock Ramp A intersection
11.3.3.4 Fencing
Replace R/W fence that is damaged or disturbed by the Contractor with standard MnDOT chain link
fence/steel posts that match the existing fence material type and coating. Install R/W fence one foot inside
permanent R/W except as needed to isolate the trunk highway from the local roadway system and as
approved by MnDOT.
For protective screening systems on bridges, design the minimum height of the fence or railing to be
72 inches above the top of the sidewalk. Use continuous protective screening across the bridge and on the
wingwalls.
11.3.3.5 Cross Slope
The typical cross slope for roadways is 0.02 foot/foot. Do not use a typical cross slope of less than 0.02 foot/
foot. Provide additional overlay thickness for cross-slope correction in mill and overlay sections. The typical
cross slope of shoulders shall be 0.04 foot/foot.
RFP
Roadways
11-12
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
11.3.3.6 Crown Locations
Design divided highways with depressed rural medians with a crowned cross section for each roadway on
each side of the median. Design roadways with raised medians with a crowned cross section for each
roadway on each side of the median. Provide unidirectional cross slopes at the following roadways and an
input gutter at the top of these cross slopes with catch basins to collect drainage:
 Roadway 1
 Roadway 2
 Roadway 3
11.3.4
Reports/Plans
11.3.4.1 Design Exceptions
Design all the elements associated with mainline highway and other roadways in accordance with the criteria
established in the Contract Documents.
There is no assurance that Design Exceptions created by the Contractor will be Approved by MnDOT or
FHWA. If the Contractor’s design creates design exceptions, demonstrate on a case-by-case basis that
substantial benefits to the Project and the public would result from the recommendation. Any exceptions
requested will be subject to MnDOT and FHWA Approval prior to release of RFC plans. Comply with the
Design Exception Process included in Exhibit 11-A.
The following known design exceptions have been approved but the Contractor may consider eliminating
them through design:
 Exception 1)
11.3.4.2 Borrow Site Plan
Do not use any borrow site until MnDOT Approval has been received. In the plan, identify the location of the
borrow site, the material proposed to be used from the site, and the proposed haul route(s).
11.4
Construction Requirements
11.4.1
General
Remove all existing pavement, curb and gutter, sidewalk, steps, drainage facilities, soil, rock, and other
obstructions within the Project limits necessary to construct the Project. Remove all other unused pavements
and sidewalks, including temporary facilities, within the Project limits and grade to match the adjacent
grading. When removing such items, saw cut pavement or sidewalk with neat lines at the removal
terminations.
11.4.2
Construction Criteria
11.4.2.1 Mining
Mining of material within MnDOT R/W will not be allowed without prior MnDOT Approval. To request
MnDOT Approval, develop, implement, and maintain a Mining Plan addressing site restoration,
environmental impacts, material management, and other pertinent information.
11.4.2.2 Removal of Miscellaneous Objects
Remove and properly dispose of all objects encountered within the R/W that are not otherwise designated for
removal, salvage, or reuse, such as, but not limited to, abandoned automobiles, furniture, appliances,
garbage, and other waste materials.
Remove all concrete cable barrier post sockets, anchorages, unnecessary sign footings, and other subsurface
concrete that no longer provides function.
RFP
Roadways
11-13
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
11.4.2.3 Disposal of Materials
Disposal of surplus excavated material on MnDOT R/W may be allowed on a case-by-case basis with
Approval by MnDOT. Develop, implement, and maintain a Disposal Site Plan showing grading and
restoration of any such areas. All material to be disposed of shall become the property of the Contractor and
shall be disposed of off-site.
Do not remove topsoil from the Site. If excess topsoil is available, grade the material over turf establishment
areas within MnDOT’s R/W.
11.4.2.4 Building Removals
11.4.2.5 Protection of Other Facilities
11.4.3
Materials/Testing Requirements
11.4.4
Instrumentation/Monitoring Plans
11.5
Deliverables
 Released For Construction Documents—Produce plans and specifications in accordance with
Book 2, Section 5.
 Mining Plan—Submit a Mining Plan to MnDOT for Approval. Do not mine any material within
MnDOT R/W until MnDOT Approval has been received. MnDOT will respond within 10 Working
Days of receipt of the plan.
 Disposal Site Plan—Submit a Disposal Site Plan to MnDOT for Approval. Do not dispose of any
surplus excavated material on MnDOT R/W until MnDOT Approval has been received. MnDOT
will respond within 10 Working Days of receipt of the plan.
 Borrow Site Plan—Submit a Borrow Site Plan to MnDOT for Approval. MnDOT will respond
within 10 Working Days of receipt of the plan.
 Design Calculations—Provide design calculations to MnDOT as follows:
 Horizontal sight distance: intersections, secondary roads, and mainline
 Vertical sight distance: stopping, 10-second decision, and passing (if applicable) for trunk
highways and stopping secondary roads
 Intersection geometrics (vehicle turning movements)
 Clear zones
 Superelevation
 Traffic barrier, guard rail, end treatments, and impact attenuators
 Design Justification—Upon request from MnDOT, submit design justifications for any element of
the Project where multiple alternatives are viable. Provide computer-generated or hand-written
documentation clearly identifying the following:
 Design issue
 Items requiring consideration
 Basis for evaluation
RFP
Roadways
11-14
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
 Final decision and justification
 Roundabout Design Package—Submit the Roundabout design package to MnDOT as part of the
RFC deliverable
RFP
Roadways
11-15
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
EXHIBITS
All exhibits are provided as electronic files.
Exhibit 11-A
Design Exception Process
Exhibit 11-B
Design Exception Request Form
Exhibit 11-C
Design Exception Documentation Sheet
RFP
Roadways
11-16
MnDOT Design-Build Program
Federal Project No. [insert #]
Book 2—[insert full name of project] Design-Build Project
S.P. [insert #]
EXHIBIT 11-A: Design Exception Process
If the Contractor’s design requires additional Design Exceptions or a Design Variance (defined as a deviation
from the Road Design Manual that is not one of the 13 Critical Criteria), identify them in the design memo.
The memo must be updated and sent to MnDOT for Approval. If Approved, MnDOT will send the updated
memo to FHWA for Approval. Both Approvals are necessary prior to the submission of an RFC package
that includes the concept.
If additional design exceptions are required for the Project, use the following process:
1. Submit design exception requests in the form of a letter addressed to the State Design Engineer and
delivered (five copies) to the MnDOT Project Manager.
2. Provide the following in the design exception request submittals:
a. A letter identifying the exception(s) by number, Project number, location, and status (new submittal,
re-submittal, etc.).
b. A completed design exception request form for each exception proposed. Exhibit 11-A contains the
Design Exception Request form.
c. Supporting documentation indicating the justification for the exception. If desired, use the form in
Exhibit 11-B as part of the documentation. Address the following for justification:
i. Site conditions of the exception
ii. Compelling reason for the exception, including which standard is not being met, if the exception
affects any other standards, and what will be done to mitigate the effects of the exception
iii. Effects of the exception on safety and operation of all affected facilities
iv. Previous crash history near the location of the exception
v. Calculations estimating the cost of attaining the design standard and costs of exception as proposed
vi. Effects on scenic, visual, historical, or other environmental features
d. Plan and profile drawings depicting the exception.
3. Upon Approval by MnDOT, the exception request will be forwarded by MnDOT to FHWA for approval.
RFP
Roadways
11-17