I494 Design Build Project 2 Verification Team

State of Minnesota
REQUEST FOR PROPOSALS (RFP)
PART A: INSTRUCTIONS AND CONTENT
I494 Design Build Project 2 Verification Team
MnDOT Contract Number: 1063501
Date Posted: 06/12/2026
1. Responses must be received by MnDOT no later than 11:00 am Central Time, on 07/14/2026. Late responses
will not be considered.
2. This document is available in alternative formats for persons with disabilities by calling Jodi Thurner at 651-234-
7686 or for persons who are hearing, or speech impaired by calling the Minnesota Relay Service at 1-800-627-
3529. For other information on disability rights and protections, contact MnDOT's Americans with Disabilities
Act (ADA) Coordinator.
3. Responder must also complete and submit PART B of this Request for Proposals, posted separately from this
document.
4. As of July 1, 2025, certain terms are unenforceable in state contracts. See Minnesota Statutes 16C.05
subdivision 8.
Minnesota's Commitment to Diversity and Inclusion
The State of Minnesota is committed to diversity and inclusion in its public procurement process. The goal is to
ensure that those providing goods and services to the State are representative of our Minnesota communities
and include businesses owned by minorities, women, veterans, and those with substantial physical disabilities.
Creating broader opportunities for historically under-represented groups provides for additional options and
greater competition in the marketplace, creates stronger relationships and engagement within the State's
communities, and fosters economic development and equality.
To further this commitment, the Department of Administration operates a program for Minnesota-based small
businesses owned by minorities, women, veterans, and those with substantial physical disabilities. For additional
information on this program, or to determine eligibility, please call 651-296-2600 or go to
www.mmd.admin.state.mn.us/mn02001.html.
SPECIAL NOTICE: This is a request for proposal. It does not obligate MnDOT to award a contract or complete the
proposed program, and MnDOT reserves the right to cancel this RFP if it is considered in its best interest.
(CSS/CM Last Updated: 05/05/2026)

TABLE OF CONTENTS
Request For Proposal Part A Contents
SECTION 1 - INSTRUCTIONS TO RESPONDERS
SECTION 2 - SUMMARY OF PROJECT SCOPE
SECTION 3 - PROPOSAL INSTRUCTIONS AND ADDITIONAL INFORMATION
SECTION 4 - PROPOSAL CONTENT AND SUBMISSION
SECTION 5 - EVALUATION PROCEDURE AND CRITERIA
SECTION 6 - TERMS AND GENERAL REQUIREMENTS
Request For Proposal Required Forms and Declarations (see PART B, posted seperately):
1. Attachment 1: Responder Declarations & Certifications
2. Attachment 2: Exceptions to MnDOT's Terms and Conditions Form
3. Attachment 3: Responder Forms
a. Workforce and Equal Pay Declaration Form
b. Conflict of Interest Checklist and Disclosure Form
c. Resident Vendor Form
d. Targeted Group, Economically Disadvantaged and Veteran-owned Small Businesses Preference Form
THE BALANCE OF THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
(CSS/CM Last Updated: 05/05/2026) 2

SECTION 1 - INSTRUCTIONS TO RESPONDERS
Steps for Follow the steps below to complete your response to this RFP:
Completing Step 1: Read the solicitation documents and ask questions, if any
Your Response Step 2: Write your Proposal and complete the required Forms in Part B of this RFP
Step 3: Submit your Proposal
Incomplete A Proposal must be submitted along with any required additional documents. Incomplete
Submittals Proposals that materially deviate from the required format and content may be rejected.
STEP 1 - READ THE SOLICITATION DOCUMENT & ASK QUESTIONS, IF ANY
How to Ask The Instructions for Questions and Answers section is in this link to Section 3. The contact person
Questions for questions is:
Jodi Thuner, Contract Administrator
jodeen.thurner@state.mn.us
Use the following as the subject line of your email: MnDOT Contract No. 1063501, I494 Design
Build Project 2 Verification Team. Questions must be emailed to the contact person and
received by 11:00 am Central Time, on 06/26/2026. Other personnel are not authorized to
answer questions regarding this RFP.
STEP 2 - WRITE YOUR RESPONSE
How to Write The Proposal Content section is in this link to Section 4. Prepare a written response and supply
your Response all requested content. Proposals must address the requested information and documents
detailed in Section 4 or be disqualified as non-responsive.
All Proposals submitted in response to this RFP will be public information under the Minnesota
Government Data Practices Act, Minnesota Statutes Chapter 13 once the evaluation process is
complete.
Make sure to review and sign your Proposal and include all necessary Part B Attachments.
STEP 3 -SUBMIT YOUR RESPONSE
Where to Send Proposals must be electronically submitted via e-mail to:
Your Response Jodi Thurner, Contract Administrator
and jodeen.thurner@state.mn.us
Confirmation
Use the following as the subject line of your email: MnDOT Contract No. 1063501, I494 Design
Build Project 2 Verification Team.
You must copy: ProfessionalTechnicalContractForms.dot@state.mn.us on the email.
Proposals must be received by MnDOT no later than 11:00 am Central Time, on 07/14/2026.
Late responses will not be considered.
You will receive a confirmation email from MnDOT after submission. If you do not, please email
the Contract Administrator above to ensure your response was received.
By signing and submitting a Proposal, you are making a binding legal offer for the period of time
listed here. This Condition of Offer is discussed in more detail in the Terms & General
Requirements section of this RFP, Section 6.
(CSS/CM Last Updated: 05/05/2026) 3

SECTION 2 -SUMMARY OF PROJECT SCOPE
1. Project Overview and Goals
MnDOT requests responses for a Contractor to provide design-build verification for State Project (SP) 2785-462 on
Interstate (I) 494 Corridors of Commerce Design-Build Project.
Project Limits: The project is primarily located in Hennepin County, Minnesota, in the cities of Edina, Bloomington,
and Richfield. The Project limits are from West (W) Bush Lake Road to 24th Avenue (Ave).
The project scope is to complete the I494 corridor vision. This project will build on the work done in the I494 Project
1 Design-Build Contract. Scope includes addition of EZPass lanes on I494 from I35W to 24th Ave, full pavement
replacement on I494 from I35W to 24th Ave, full pavement replacement on I35W from 82nd Street to 76th Street,
bridge replacements at 82nd Street and Trunk Highway (TH) 77 over I494, drainage, retaining walls, and noise walls.
The Project letting is October 7, 2026.
2. Scope of Work and Deliverables
The scope of work generally includes assisting MnDOT with tasks necessary from a design and construction
perspective to ensure the Design Build (DB)contractor is meeting the DB Contract requirements. This includes but is
not limited to roadway design, structures design, geotechnical design, drainage design, traffic design, Maintenance
of Traffic design, Intelligent Transportation Systems design, utility coordination, schedule review, quality
management, roadway inspectors, structures inspectors, and environmental compliance
See Exhibit C: Specifications, Duties, and Scope of Work, posted separately from this announcement, for the full
scope of work. For purposes of this solicitation, there is not Exhibit A or B.
3. Additional Tasks or Activities.
Responders are encouraged to propose additional tasks or activities if they will substantially improve the results of
this Project. These items must be separated from the required items on the cost proposal required under this RFP.
THE BALANCE OF THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
(CSS/CM Last Updated: 05/05/2026) 4

SECTION 3 - PROPOSAL INSTRUCTIONS AND ADDITIONAL INFORMATION
1. Anticipated Contract Term. The term of this contract is anticipated to be from 10/1/2026 to 09/30/2031.
2. Instructions for Questions and Answers. All questions must be submitted by email only and received no later than
11:00 am Central Time, on the date listed in Section 1, to the Contract Administrator named in Section 1. MnDOT is
not obligated to answer questions submitted after this due date and time.
2.1 Personnel. Only personnel listed above are authorized to discuss this RFP with Responders. Contact regarding
this RFP with any personnel not listed above could result in Responder's disqualification. This provision is not
intended to prevent Responders from seeking guidance from state procurement assistance programs
regarding general procurement questions.
2.2 Question and Answer Posting. All questions and answers will be posted on MnDOT's Consultant Services Web
Page at www.dot.state.mn.us/consult under the "P/T Notices" section. All Responders will be responsible for
checking the web page for any questions and their answers. Note that questions will be posted verbatim, as
submitted. MnDOT anticipates posting answers to questions no later than 11:00 am Central Time, on
06/30/2026.
2.3 RFP Errors and Addenda. If a Responder discovers any significant ambiguity, error, conflict, discrepancy,
omission, or other deficiency in the RFP, please immediately email the Contract Administrator listed above in
Section 1, notifying them of the issue and requesting modification or clarification of the document. If changes
are made to the RFP after initial publication, MnDOT will issue an addendum with notification and post it in
the same manner as the original RFP. Any addenda issued will become part of the RFP. All Responders will be
responsible for checking the Consultant Services web page for any Addenda that may be posted in connection
with this RFP.
3. Page Limits. Responder's Proposal must adhere to the formatting and page limitations identified in the following
table. If any of Responder's documents exceed the page limits identified, the excess pages will not be reviewed,
regardless of content.
Document Max. Page Requirements
Numbers
Requirements for all N/A 1. Responders MUST use Calibri font in their response
documents 2. No smaller than 11-point font
3. No smaller than single line, 0-point spacing
4. The font may not have "condensed," "narrow," or
"compressed" in the font name
Proposal 15 pages 1. Single-sided pages, no larger than 8.5"x11"
2. Unless otherwise noted, all Proposal Content required in
Section 4 below must be within this page limit
Appendix for Resumes 1 page per resume 1. Single-sided pages, no larger than 8.5"x11"
2. Not included as part of the page limit, but restricted to one
page per resume
Organizational Chart 1 page 3. Include an organizational chart showing the consultant team
members and the MnDOT team members and how they will
interact.
4. Not included as part of the page limit.
Note: Cover letter and required forms and certifications are NOT included as part of the page limit.
(CSS/CM Last Updated: 05/05/2026) 5

SECTION 4 - PROPOSAL CONTENT & SUBMISSION
The following is the minimum required contents of the Proposal and must be submitted in the order listed. Items
1 through 9 below MUST fit within the Proposal page limit identified in the Page Limits Table above.
1. Contact Information. Responder must clearly identify the company's full legal name, business address, contact
person's name, telephone number, and email address.
2. Project Understanding. Responder must clearly state its understanding of the Project objectives, goals, and task,
demonstrating its view of the Project's nature and what makes Responder uniquely suited for this work. Responder
should demonstrate its understanding by using its own words rather than simply repeating the RFP's Project
overview and/or goals as stated above.
3. Personnel Pass/Fail Qualifications
Personnel classifications have pass/fail qualifications. These are minimum qualifications which must be met for all
personnel as listed below. All personnel must pass minimum qualifications, or the proposal will be considered non-
responsive and will not be considered. Exhibit C: Specifications, Duties, and Scope of Work, provides more detail on the
expectations MnDOT has for the Responder's personnel. Proposals will be examined by MnDOT to determine if all
pass/fail qualifications have been met satisfactorily before the proposals will be reviewed and scored.
Design-Build Verification Team (DBVC) Project Manager
Pass/fail qualifications:
a) Be a registered engineer in the State of Minnesota
b) Have 10 years experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Deputy Project Manager and Design Manager
Pass/fail qualifications:
a) Be a registered engineer in the State of Minnesota
b) Have 10 years experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Office Manager and Document Control Manager
Pass/fail qualifications:
a) High school graduate
b) Must have three years of experience performing similar work. Provide specific examples of roles and relevant
work performed on previous projects that relate specifically to this role.
Quality Manager
Pass/fail qualifications:
a) Be a registered engineer in the State of Minnesota or have a strong construction management background
b) Have 5 years experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Roadway Inspector 1
Pass/fail qualifications:
a) High school graduate
b) Experience performing similar work. Provide specific examples of roles and relevant work performed on
previous projects that relate specifically to this role.
c) Have the following MnDOT Technical Certifications
(CSS/CM Last Updated: 05/05/2026) 6

i) Concrete Field Inspector
ii) Bituminous Street Inspector
iii) Grading & Base Inspector
Roadway Inspector 2
Pass/fail qualifications:
a) High school graduate
b) Have experience performing similar work. Provide specific examples of roles and relevant work performed on
previous projects that relate specifically to this role.
c) Have the following MnDOT Technical Certifications
i) Concrete Field Inspector
ii) Bituminous Street Inspector
iii) Grading & Base Inspector
Structures Inspector 1
Pass/fail qualifications:
a) High school graduate
b) Have experience performing similar work. Provide specific examples of roles and relevant work performed on
previous projects that relate specifically to this role.
c) Have the following MnDOT Technical Certifications
i) Concrete Field Inspector
ii) Bituminous Street Inspector
iii) Grading & Base Inspector
iv) Bridge Construction Inspector
Structures Inspector 2
Pass/fail qualifications:
a) High school graduate
b) Have experience performing similar work. Provide specific examples of roles and relevant work performed on
previous projects that relate specifically to this role.
c) Have the following MnDOT Technical Certifications
i) Concrete Field Inspector
ii) Bituminous Street Inspector
iii) Grading & Base Inspector
iv) Bridge Construction Inspector
Roadway Design Engineer
Pass/fail qualifications:
a) Be a registered engineer in the State of Minnesota
b) Have 5 years experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Traffic Engineer
a) Be a registered engineer in the State of Minnesota
b) Have 5 years' experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Maintenance of Traffic Engineer
a) Be a registered engineer in the State of Minnesota
b) Have 5 years experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
(CSS/CM Last Updated: 05/05/2026) 7

ITS Engineer
a) Be a registered engineer in the State of Minnesota
b) Have 5 years experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Structures Design Engineer
Pass/fail qualifications:
a) Be a registered engineer in the State of Minnesota
b) Have 10 years experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Geotech Engineer
Pass/fail qualifications:
a) Be a registered engineer in the State of Minnesota
b) Have 5 years experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Drainage Engineer
Pass/fail qualifications:
a) Be a registered engineer in the State of Minnesota
b) Have 5 years experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Utility Coordinator
Pass/fail qualifications:
a) High school graduate.
b) Have experience performing similar work. Provide specific examples of roles and relevant work performed on
previous projects that relate specifically to this role.
Critical Path Management (CPM) Schedule Reviewer
Pass/fail qualifications:
a) High school graduate.
b) Have experience performing similar work. Provide specific examples of roles and relevant work performed on
previous projects that relate specifically to this role.
Environmental Compliance Manager
Pass/fail qualifications:
a) Be a geologist, soil scientist, environmental engineer or of similar technical background with work experience in
the State of Minnesota.
b) Have experience performing similar work. Provide specific examples of roles and relevant work performed on
previous projects that relate specifically to this role.
c) Must have experience with the following facets of environmental compliance and their associated permitting
requirements or, alternatively, a demonstrated ability to manage specialists completing this work:
i. Contaminated and regulated materials management including spill containment
ii. Contaminated groundwater dewatering
iii. Wetland and floodplain mitigation
iv. Storm water pollution prevention
v. Cultural resource surveys
vi. Asbestos and regulated material
vii. National Pollutant Discharge Elimination System (NPDES) inspections and reports
viii. Minnesota permitting related to NPDES, 404, 401, contaminated materials, watershed permitting, etc.
(CSS/CM Last Updated: 05/05/2026) 8

4. Qualifications and Experience
Beyond the pass/fail criteria, the following factors will be considered when scoring team members:
1) Technical expertise and experience of the team members within their given disciplines. Provide specific
examples of roles and relevant work performed on previous projects that relate specifically to this role.
Recent experience is preferred. Projects of similar scope and complexity are preferred.
2) Availability and time commitment. Explain what other time commitments each member has and how they
will make their verification work on I494 Project 2 a priority. Note that Design-Build verification is
demanding and time intensive work and MnDOT's expectation is that successful team members will
prioritize their work on this project over all other projects as needed for the successful completion of this
mega project. To aid MnDOT in evaluating commitment and availability include the following information for
key personnel:
a. Percent of time committed to the relevant phases of this Project
b. Percent of time committed to other projects, with conditional statements as necessary.
3) Understanding of the Design-Build contract and Design-Build partnering mentality. Explain the team
member's understanding of the design build contract both globally and in their specific discipline area.
Design-Build verification requires a careful balance of protecting MnDOT's interests while also allowing
designs that meet the contract requirements to advance in an expeditious manner; explain the team
members past experience doing such work at a high level. Provide specific examples of how these interests
have been balanced in the past.
Other factors not listed above that MnDOT deems relevant will also be considered.
5. Design-Build Experts
Who is the design-build expert or who are the design-build experts on your team? Explain what makes them a
design-build expert. Which roles will this person, or people, hold on the verification team? How will this person, or
people, be used to train and manage both consultant staff and State staff, so they understand their role on the
project and the specific expectations that are required of a person performing design-build verification? Explain
those expectations and why they are different from design bid build.
6. Deputy Project Manager and Design Manager
Explain this person's experience with being a project manager that meets or exceeds the requirements in the scope
of work. Explain their ability to manage the design in a manner that protects MnDOT's interests while also fostering
Design-Build innovation.
7. Design Team
List your Roadway Design Engineer, Drainage Engineer, Traffic Engineer, Maintenance of Traffic Engineer, ITS
Engineer, Utility Coordinator, Geotech Engineer and Structures Engineer. Explain their experience.
If they do not have design-build experience, explain how they will be trained to understand the design-build process
and mentality.
For any of the roles that have assistants or a Team approach, list the lead engineer, and then list which staff member
will be used to bill most of the work on the bid form.
8. Quality Management Team
List your Quality Manager, Structure Inspectors, and Roadway Inspectors. Note design-build experience is not the
priority. Expertise in their discipline is a priority. If they do not have design-build experience, explain how they will be
trained to understand the design-build process and mentality. Specific examples are recommended.
9. Support Team
List your Environmental Compliance Manager, Critical Path Method (CPM) Scheduler, Office and Document Control
Manager, and any other staff you propose. Explain their experience. Explain who will coordinate with MnDOT Central
(CSS/CM Last Updated: 05/05/2026) 9

Office Contaminated Materials and Regulated Waste Units and explain why this coordination is important. Note design-
build experience is not the priority.
10. Contract Term Exceptions or Modifications
10.1 Responder must be aware of MnDOT's standard contract terms and conditions when preparing its
Proposal. Responder may view MnDOT's current Professional/Technical Contract templates on the Consultant
Services website, at www.dot.state.mn.us/consult (Click on Contract Documents tab to view templates):
a. Contract Template
b. Contract Terms and Conditions
c. Insurance Requirements
d. Consideration and Payment
10.2 Much of the language reflected in these contract templates is required by statute. If Responder takes
exception to any of the terms, conditions, or language in the contract template, however, it must complete and
sign Attachment 2: Exceptions to MnDOT's Terms and Conditions and submit it with its Proposal.
10.3 Please Note: certain exceptions, or requests for exceptions, that would cause any contract term to
become unenforceable according to the statutory requirements described in Section 3 below, may result in its
Proposal being disqualified from further review and evaluation. Only those exceptions indicated in the Proposal
will be available for discussion or negotiation in the evaluation process. Any exceptions or modification to
MnDOT's insurance requirements that Responder desires must be clearly noted in Attachment 2, or Responder
will be deemed to have accepted MnDOT's requirements and waived any request for exception.
11. Cost Proposal
11.1 Content. Responders must provide, in a separate electronic file, a cost proposal. The rate(s) identified in
the Cost Proposal must include all costs, including but not limited to: travel expenses, mass mailings, fees,
commissions, compensation, indirect costs, equipment, supplies, and other charges.
11.1.1 Responder must include a total Project cost along with the following:
a. A breakout of the hours by task for each employee;
b. Identification of anticipated direct expenses;
c. Identification of any assumptions made while developing its Cost Proposal; and
d. Identification of any cost information related to additional services or tasks, clearly identified as
additional costs and not made part of the total project cost.
11.1.2 Additionally, if Responder anticipates MnDOT's provision any equipment, services, supplies, etc. for the
Project, Responder must identify such items in its Cost Proposal and detail cost allowances for this
participation.
11.1.3 Please Note: MnDOT does not make regular payments based solely upon the passage of time; it only pays
for services performed or work delivered after it is accomplished.
11.2 Submission. Responder must have the Cost Proposal signed by an authorized member of Responder's
firm, then submit, by email, a PDF version of its Cost Proposal to the attention of the Contract Administrator
identified in Section 1. The email must also include: ProfessionalTechnicalContractForms.dot@state.mn.us as a
recipient. The email must include the MnDOT Contract Number and Project Title in the subject line of the email.
11.3 Acceptance. The Cost Proposal must be open for acceptance until a contract is executed, the RFP is
cancelled, or 180 days after the due date and time of the RFP, whichever comes first. Cost estimates included in
the Cost Proposal must remain valid for the length of the Project.
(CSS/CM Last Updated: 05/05/2026) 10