US 75 Climax Design Build Design Verification and Construction Manager

State of Minnesota
REQUEST FOR PROPOSALS (RFP)
PART A: INSTRUCTIONS AND CONTENT
US 75 Climax Design Build Design Verification and Construction Manager
MnDOT Contract Number: 1062963
Date Posted: 04/09/2026
1. Responses must be received by MnDOT no later than 2:00PM, Central Time, 04/30/2026. Late responses will not
be considered.
2. This document is available in alternative formats for persons with disabilities by calling Michael Friberg at 651-
366-4683 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: 04/01/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: 04/01/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:
Michael Friberg, Contract Administrator
Michael.friberg@state.mn.us
Use the following as the subject line of your email: MnDOT Contract No. 1062963, US 75 Climax
Design Build Design Verification and Construction Manager. Questions must be emailed to the
contact person and received by 2:00PM Central Time on 04/21/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 Michael Friberg, Contract Administrator
and Michael.friberg@state.mn.us
Confirmation
Use the following as the subject line of your email: MnDOT Contract No106 2963, US 75 Climax
Design Build Design Verification and Construction Manager. You must copy:
ProfessionalTechnicalContractForms.dot@state.mn.us on the email.
Proposals must be received by MnDOT no later than 2:00PM, Central Time, on 04/30/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: 04/01/2026) 3

SECTION 2 -SUMMARY OF PROJECT SCOPE
1. Project Overview and Goals
MnDOT requests responses for a Contractor to provide design-build design verification for State Project (SP) 6012-
58 a Bridge and Embankment Stabilization project in Climax, MN. Contractor will provide design verification,
contract administration, and environmental compliance for the Project.
The Climax project involves analysis, design and construction of engineering solutions that stabilize and repair Bridge
60021 over the Snad Hill River, which is currently suffering due to a landslide impacting a pier and south abutment,
as well as stabilize a deforming section of the roadway embankment approximately 750 feet north of the bridge.
The project contains several specific requirements including 3D geo-structural computations modeling and a robust
geotechnical performance monitoring and reporting program. The project also involves roadway construction,
pavement markings, erosion and sediment control, minor grading, paving, grubbing and other related work.
2. Scope of Work and Deliverables
See Exhibit A, posted separately from this RFP, for the full scope of work.
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: 04/01/2026) 4

SECTION 3 - PROPOSAL INSTRUCTIONS AND ADDITIONAL INFORMATION
1. Instructions for Questions and Answers. All questions must be submitted by email only and received no later than
2:00PM 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 2:00PM Central Time on
04/23/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.
2. 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 10 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
3. Page limit does not include cover letter or PART B forms
Proposal 2 additional pages 1. Single-sided pages, no larger than 11"x17"
2. These pages are designated for schedules and/or maps only. If
used for any content other than schedules/maps, the pages
will not be reviewed
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
THE BALANCE OF THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK
(CSS/CM Last Updated: 04/01/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 6 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. Qualifications and Experience
Responder's personnel are key to this project. As shown, the bulk of the scoring points will be awarded based on
personnel qualifications. Exhibit A - Scope of Work and Deliverables, provides more detail on the expectations
MnDOT has for responder's personnel. Exhibit B is the Design Build Verification Team (DBVT) organization chart and
shows how MnDOT will staff the DBVT for this project. Responder's personnel will be scored based on resumes,
work samples and/or other documentation of experience and qualifications. Exhibit C lists the total hours that
should be used to prepare the Cost Proposal.
If sub consultants are to be used on this project, responders must also outline their background and experience,
including examples of similar work done by each sub consultant. Responders must also provide a list of the sub
consultants' personnel who will perform work on the project, detailing their training and work experience.
Note that no change in personnel assigned to the project will be permitted without the written approval of MnDOT's
Project Manager.
Qualification and experience of the "firm" should be demonstrated by the experience of the personnel proposed.
Design Verification Project Manager
1. Should have previous experience performing similar work
2. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 2.1 of the scope of work.
3. Can be the same person as Design Manager
Design Manager
1. Should have previous experience serving in a similar position as this position, or as the Project Manager
within the last 10 years on a previous Design-Build project (verification or on Design-Build Contractor Team)
2. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 3.1 of the scope of work. Examples provided must be
within the last 10 years. Description must include a brief explanation of the size and complexity of the
highway projects and the role preformed.
3. Expertise in Bridge Design is preferred
4. Expertise in Structural Design is preferred
5. Expertise in Geotechnical Design is preferred
6. Must be a registered engineer in the State of Minnesota
7. Can be the same person as Design Verification Project Manager
(CSS/CM Last Updated: 04/01/2026) 6

Office Management and Document Control
1. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 3.2 of the scope of work. Include relevant work
performed on previous projects that relate specifically to this role. Design-Build experience is not required.
Expertise in their discipline is preferred.
Structural Design Verification
2. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 4.1 of the scope of work. Include relevant work
performed on previous projects that relate specifically to this role. Design-Build experience is not required.
Expertise in their discipline is preferred.
3. Must be a registered engineer in the State of Minnesota
Geotechnical and Geo-structural Review
1. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 4.2 of the scope of work. Include relevant work
performed on previous projects that relate specifically to this role. Design-Build experience is not required.
Expertise in their discipline is preferred.
2. Must be a registered engineer in the State of Minnesota
Roadway Design Engineer
1. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 4.3 of the scope of work. Include relevant work
performed on previous projects that relate specifically to this role. Design-Build experience is not required.
Expertise in their discipline is preferred.
2. Must be a registered engineer in the State of Minnesota
Drainage Engineer
1. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 4.4 of the scope of work. Include relevant work
performed on previous projects that relate specifically to this role. Design-Build experience is not required.
Expertise in their discipline is preferred.
2. Must be a registered engineer in the State of Minnesota
CPM Schedule Reviewer
1. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 3.3 of the scope of work. Include relevant work
performed on previous projects that relate specifically to this role. Design-Build experience is not required.
Expertise in their discipline is preferred.
Quality Manager
1. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 5.1 of the scope of work. Include relevant work
performed on previous projects that relate specifically to this role. Design-Build experience is not required.
Expertise in their discipline is preferred.
Geostructural Construction Verification Field Engineer
1. Provide examples of similar experience of roles and relevant work performed on previous projects that
relate specifically to this role as described in Section 5.1.2 of the scope of work. Include relevant work
performed on previous projects that relate specifically to this role. Design-Build experience is not required.
Expertise in their discipline is preferred.
2. Must be a registered engineer in the State of Minnesota
(CSS/CM Last Updated: 04/01/2026) 7

Environmental Compliance Manager
1. Be a geologist, soil scientist, environmental engineer or of similar technical background with work
experience in the State of Minnesota.
2. Have experience performing similar work. Provide specific examples of roles and relevant work performed
on previous projects that relate specifically to this role as described in Section 6 in the scope of work.
3. Should 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:
a. Contaminated and regulated materials management including spill containment
b. Contaminated groundwater dewatering
c. Wetland and floodplain mitigation
d. Storm water pollution prevention
e. Cultural resource surveys
f. Asbestos and regulated material
g. National Pollutant Discharge Elimination System (NPDES) inspections and reports
h. Minnesota permitting related to NPDES, 404, 401, contaminated materials, watershed permitting, etc
4. Work Plan-Project Approach
4.1 Responder must provide a detailed work plan, which must identify the major tasks to be accomplished.
Responders must be sure to not only describe what will be done but also explain how each task will be
accomplished,. These tasks will be used as a scheduling and management tool, as well as the basis for invoicing.
This section of Responder's Proposal must NOT include a Cost Proposal. If cost details are included in this
section, MnDOT may disqualify the Proposal as non-responsive. The detailed work plan must present:
a. The Overall Project Approach;
b. A breakdown of the Project Tasks, detailing the tasks and how they will be completed;
c. Deliverable Due Dates and an Overall Project Schedule; and
d. A List of Personnel Working on the Project, including details of each person's role, by task.
e. 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. For staff
that do not have design-build experience, explain how they will be trained to understand the design-build
process and mentality.
f. Partnering - Explain the responder's approach to enhancing partnership and collaboration with the Design-
Builders during the life of the project. Explain the risks and challenges associated without co-location and how
the responder will address these risks and challenges. Also explain how this team will collaborate with the and
MnDOT staff assigned to the project and with a separate Construction Verification Contract.
g. Schedule- Explain the approach to ensure the Design-Builders submittals will be reviewed within the Design-
Build contract timelines. Explain the scheduling approach to address the fluctuation in submittals that are
submitted and the tasks that will be required. Explain how collaboration between functional units will occur to
ensure all aspects of submittals have received a complete review is done in the required timelines.
h. Construction Perspective during design - Explain the approach this team will use to address and identify
potential issues with designs before construction. Explain the approach to ensure that the designs have
accounted for appropriate existing conditions. Give examples of items that can cause problems during
construction that design reviewers are aware of from past lessons learned. Explain how you will manage those
items. These items may not be key items to project success, but they are items required to be done correctly
and may have been missed or ignored until it was realized too late that they are causing a problem. State is
looking for nuanced detail in this answer to determine the depth of your design-build knowledge and
experience.
i. Best Practices and Lessons Learned - Provide examples of Best Practices and Lessons Learned that your team
(CSS/CM Last Updated: 04/01/2026) 8

will share with MnDOT to enhance MnDOT's construction inspection services for this project. This can include
different processes, software or staffing levels, unique skills and/or abilities.
j. Commonly Missed Verification Items for Construction - Give specific examples of nuanced items that can cause
problems during construction. Explain how you will manage those items, so they are done efficiently to
minimize problems. These items may not be key items to project success, but they are items required to be
done correctly and may have been missed or ignored until it was realized to late that they are causing a
problem. State is looking for nuanced detail in the answer to determine the depth of your design-build
knowledge and experience. Do not describe the purpose of verification overall and do not list project risks.
4.2 Artificial Intelligence. In its breakdown of each Project Task, Responder must also disclose whether it intends to
use any artificial intelligence technologies, either directly or indirectly, to accomplish Project Tasks and if so, a
detailed description of such technologies and how they will be used. See Section 6 for additional information
regarding the use of artificial intelligence.
5. Deliverables. Responders must additionally present a clear and detailed description, format and schedule, of the
deliverables to be provided in order to meet the needs of the Project.
6. Contract Term Exceptions or Modifications
6.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
6.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.
6.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.
7. Cost Proposal
7.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.
7.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.
7.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.
(CSS/CM Last Updated: 04/01/2026) 9

7.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.
7.2 Submission. Responder must have the Cost Proposal signed by an authorized member of Responder's firm, then
submit, by email, both a PDF and Microsoft Excel version, in separate electronic files, 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 RFP Title in the subject line of the email.
7.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.
7.4 Cost Breakdowns and Overhead Rates. Whether proposing a cost plus fixed fee, fixed hourly rate, or unit
budget, Responder must include a breakdown (labor, overhead, fixed fee and expenses) showing how the rate
was derived and must use its current MnDOT-approved overhead rate, not to exceed 175%.
7.4.1 For purposes of its Cost Proposal, Responder must utilize a fixed fee base of 9%, PLUS the overhead fixed
fee additive identified in the following table:
Base Additive Cost Proposal Fee
MnDOT Approved Overhead Less than 140% 9% 4.0 13.0%
MnDOT Approved Overhead 140% through 149.9% 9% 3.0 12.0%
MnDOT Approved Overhead 150% through 159.9% 9% 1.5 10.5%
MnDOT Approved Overhead 160% or Greater 9% 0.0 9.0%
7.4.2 Other additives pertaining to project schedule, duration, size, and risk, along with fixed fee, will be
determined/calculated utilizing MnDOT's Fixed Fee Rate Worksheet upon selection.
8. License Agreements, Maintenance Agreements, or Other Terms and Conditions
8.1 Responder must provide any license agreements, maintenance agreements, or any other terms and conditions
relevant to the work under a resulting contract. Review and approval by MnDOT of any such documents will be
required prior to contract execution. In the event Responder fails to comply with this provision, Responder
agrees that it will not seek to enforce terms and conditions of any such agreement against MnDOT. Further,
failure to provide any of the pertinent documents upon request may result in MnDOT not agreeing to sign any
additional documents, rejecting your response, or cancelling the award.
9. Trade Secret Materials. If Responder submits information in response to this RFP that it believes to be trade secret
materials, as defined by the Minnesota Government Data Practices Act, Minnesota Statutes 13.37, Responder must
clearly mark all trade secret materials in its Proposal at the time the Proposal is submitted. MnDOT will not consider
Cost Proposal information submitted by Responder to be proprietary or trade secret material.
THE REMAINDER OF THIS PAGE IS LEFT INTENTIONALLY BLANK
(CSS/CM Last Updated: 04/01/2026) 10