Blatnik Bridge Construction Contract Administration & Verification

Request for Proposals - Qualification Based Selection (QBS)
Minnesota Department of Transportation (MnDOT)
Blatnik Bridge Construction Contract Administration & Verification
MnDOT Contract No. 1061634
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 Minnesota's 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 Minnesota 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.
This document is available in alternative formats for persons with disabilities by calling Cole Maetzold at (218) 341-8283
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.
This RFP does not obligate MnDOT to award a contract or complete the project, and MnDOT reserves the right to cancel
the RFP if it is considered to be in its best interest.
A "Qualification Based Selection" method will be used to review proposals submitted in response to this RFP.
Responses to this RFP will be public information under the Minnesota Data Practices Act, Minnesota Statutes Chapter
13.
As of July 1, 2025, certain terms are unenforceable in state contracts. See Minnesota Statutes 16C.05 subdivision 8.
PROJECT SPECIFIC INFORMATION
Project Overview
MnDOT requests proposals for assistance in performing tasks necessary to verify that the Blatnik Bridge Design-Build
Construction contractor (DB contractor) is meeting all construction requirements of the Design-Build Conformed
Contract for the Project.
The project is primarily located in St. Louis County, Minnesota and Douglas County, Wisconsin between the cities of
Duluth, Minnesota and Superior, Wisconsin. The project limits extend 0.3 miles from the existing bridge structure on the
Minnesota approach to 0.75 miles from the existing bridge structure on the Wisconsin approach, along US 53.
The project includes replacement of the existing John. A. Blatnik I-535 Bridge (Minnesota Bridge number 9030,
Wisconsin Structure B-16-5) on Interstate 535 (I-535) connecting Duluth, Minnesota and Superior Wisconsin across the
St. Louis River and Bay. The project also includes reconstructing an interchange in Superior, WI that routes I-535 directly
to US 53, with local connections to Hammond Avenue and WIS 35. The project includes design and construction of a new
(CSS/CM Last Updated 01/20/2026) 1

mainline bridge (Minnesota Bridge number 69913, Wisconsin Structure B-16-0153) and new exit ramp bridge (WI
Structure B-16-0154) and entrance ramp bridge (WI Structure B-16-0155). The new mainline bridge includes new
Minnesota approach spans, a new main span over the Main Navigation Channel, new spans along Connor's Point, new
spans over the Howard's Pocket Navigation Channel, and new Wisconsin approach spans that connect to US Highway 53
in Wisconsin.
The project includes a new shared use path on the easterly side of the new mainline bridge and Wisconsin entrance
ramp bridge with trail connections in Duluth and Superior, drainage improvements, retaining walls, and improvements
within the City of Superior. The existing bridge will be closed for the majority of construction and traffic will be detoured
to the Richard I. Bong Memorial Bridge.
To find additional project information related to the Project, refer to the project website located here:
https://www.dot.state.mn.us/designbuild/blatnik-bridge/index.html
Project information such as design files, layouts and more can be found on the project SharePoint site, which is found on
the project website. Download and review all files on the project SharePoint site. Contact peter.a.davich@state.mn.us
for Design Build Request for Proposals SharePoint site access.
Project Goal
The goal of this project is to perform all required construction contract administration and verification tasks for the
project.
Scope of Work and Deliverables
A detailed description of the scope of work and deliverables for this project has been posted separately from this RFP as
"Exhibit A - Specifications, Duties, and Scope of Work".
Responders are encouraged to propose additional tasks or activities if they will substantially improve the results of
the project.
Anticipated Term
The term of this contract is anticipated to run from 08/01/2026 to 07/31/2031. MnDOT anticipates that this work may
extend past 5 years, which may result in a subsequent contract being set up to finish the work.
QUESTIONS
Responders who have any questions regarding this RFP must submit questions, by e-mail only, to the Contract
Administrator:
Cole Maetzold, Senior Engineer
cole.a.maetzold@state.mn.us
IMPORTANT: Include the MnDOT Contract Number and Solicitation Title in the subject line of the email.
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 prospective responders will be responsible for checking the web page for any
addendums to this RFP and any questions that have been answered. Note that questions will be posted verbatim, as
submitted.
Questions regarding this RFP must be received by MnDOT no later than 2:00 pm Central Time on 4/20/2026.
MnDOT anticipates posting answers to such questions no later than 2:00 pm Central Time on 4/22/2026.
No other MnDOT personnel are allowed to discuss this RFP before the proposal submission deadline. Contact regarding
this RFP with any personnel not listed above may result in disqualification.
2

PROPOSAL CONTENT
The following will be considered minimum contents of the proposal and must be submitted in the order listed. Item's 1
through 5 must fall within the Proposal page limit identified in the "Page Limits" table below.
1. Contact Information:
Responders must clearly identify the company's full legal name, business address, contact person's name, telephone
number, fax number and e-mail address (as available).
2. Project Understanding:
The purpose of this section is for the responders to detail their understanding of the project. Responders must clearly
state their understanding of the project objectives, goals, and tasks to show or demonstrate their view of the nature of
the project. Responders should demonstrate their understanding by using their own words rather than simply repeating
what is listed in the RFP.
3. Responder Experience & Qualifications (Company & Key Personnel):
The purpose of this section is for responders to provide information detailing the background and experience of the
company, and the project personnel. To do this, responders must:
A. Provide an outline of their background and experience, with examples of similar work done.
B. List the personnel who will be working on this project, specifically detailing their training and work experience.
C. Include resumes for each proposed team member. Each resume must include a list of the team members'
technical qualifications and certifications, relevant to the proposed work and tasks identified in this RFP and
Exhibit A. Exhibit A - Attachment 1 is the Design Build Construction Verification Team (DBCVT) organization
chart and shows how MnDOT will staff the DBCVT for this project. Below is a list of minimum qualifications each
team member must demonstrate.
Responder's personnel are key to this project. As shown below, the bulk of the scoring points will be awarded based on
personnel qualifications. The Scope of Work provides more detail on the expectations MnDOT has for responder's
personnel. Responder's personnel will be scored based on resumes, work samples and/or other documentation of
experience and qualifications.
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. Responders must be sure to specifically address the minimum requirements listed below, if applicable.
Responders must propose one or more person(s) that will fill each of the roles below. The Scope of Work outlines when
it is acceptable for key personnel to be assigned to multiple roles. The following are the minimum requirements for each
personnel position.
Design-Build Construction Verification Consultant (DBCVC) Project Manager (*Key Position)
A. Be a registered engineer in the State of Minnesota AND Wisconsin now or within 6 months from contract award
B. Have ten years of experience performing construction oversight. Provide specific examples of roles and relevant
work performed on previous projects that relate specifically to this role.
C. Have experience performing owner's construction oversight on a minimum of two other Design Build projects.
Provide specific examples of roles and relevant work performed on previous projects that relate specifically to
this role.
Office Management and Document Control
A. High school graduate
3

B. Must have five 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 (*Key Position)
A. High school graduate.
B. Have ten years of 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 Design-Build experience in construction
Chief Roadway Inspection Verifier (*Key Position)
A. High school graduate
B. Have ten years of experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Chief Structures Inspection Verifiers (*Key Position)
A. High school graduate
B. Have ten years of experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Intermediate Inspection Verifiers
A. High school graduate
B. Have five years of experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Concrete Plant Inspector
A. High school graduate
B. Have five years of experience performing similar work. Provide specific examples of roles and relevant work
performed on previous projects that relate specifically to this role.
Qualification and experience of the "firm" should be demonstrated by the experience of the personnel proposed.
MnDOT performance evaluation data (for similar services) may be taken into consideration as part of this rating
factor.
4. Work Plan - Project Approach:
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.
b. Partnering - Explain the responder's approach to enhancing partnership and collaboration with the
Design-Builders during the life of the project. Explain how this team will collaborate with the staff on a
separate Design Verification Contract to ensure constructability reviews have occurred, as well as to
ensure that design is brought into the discussion during construction as issues or questions arise.
Describe how conflict will be resolved between the responder and the Design-Build Contractor
c. Best Practices and Lessons Learned - Provide examples of Best Practices and Lessons Learned that your
team 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.
4

d. 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 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. Do not describe the purpose of verification
overall and do not list project risks.
5. Deliverables:
Responders must provide a clear and detailed description, format, and schedule of the deliverables to be provided in
order to meet the needs of the project.
6. Forms, Documents and Certifications:
Responders must complete and submit all required forms, documents, and certifications, required under any other
section of this solicitation. These forms, documents and certifications will NOT be included in any page limit set for this
solicitation, as applicable.
6.1. Required Forms and Documents:
Responders must complete and submit the forms and documents required under any other section of this
announcement.
Forms/Documents on File with MnDOT Consultant Services:
If applicable, check the forms/documents that are on file with MnDOT Consultant Services:
Workforce and Equal Pay Declaration Page Resident Vendor Form

If these forms/documents are on file with MnDOT Consultant Services, then no need to resubmit the
documents until the form/document end date. All other forms and documents required MUST be attached
to response.
6.2. Solicitation of Disadvantaged Business Enterprises (DBE) Statement: Responders must provide the
following statement and signature:
I hereby recognize that a DBE-Neutral (DBEN) goal has been established for this RFP in accordance with the
"DBE Special Provisions" posted with the RFP. I understand that MnDOT's Office of Civil Rights is required to
clear the successful responder's attainment of the goal, or Good Faith Efforts made to attain the goal, before
a contract can be awarded. I understand that failure to meet the goal or show a Good Faith Efforts to meet
the goal, will deem the successful responder as non-responsive, resulting in rejection of the proposal.
Signature Print Name Date
Responders must not include price information either in the body of their proposal or as a separate submittal.
PAGE LIMITS
The responder's submittal must adhere to the page limitations identified in the following table. If any of the responder's
documents exceed the page limits identified, the excess pages will not be reviewed, regardless of content.
Document Maximum Number of Pages Requirements
Requirement N/A 1. Responders MUST use Calibri font in their response
for all pages 2. No smaller than 11-point font and single line, 0-point spacing
3. 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. As noted above, Item's 1 through 5 of the Response Content
section must fall within these page limits
5

Document Maximum Number of Pages Requirements
Proposal 2 additional pages 1. Single-sided pages, no larger than 11"x17"
2. These 2 pages are designated for schedules and/or maps only.
If used for any content other than schedules and/or maps, the
pages will not be reviewed.
Appendix for 1 page per resume (up to 2 1. Single-sided pages, no larger than 8.5"x11"
Resumes pages per resume for key 2. Not included as part of the page limit, but is restricted to one
positions) page per resume and two pages per resume for key positions
Note: Cover letter and required forms and certifications are NOT included as part of the page limit.
PROPOSAL SUBMITTAL INSTRUCTIONS
IMPORTANT NOTE TO RESPONDERS: You should receive a confirmation email from MnDOT. If you do not, please
reach out to the Contract Administrator to ensure the response was received.
All proposals must be electronically submitted, via e-mail, to the attention of:
Cole Maetzold, Senior Engineer
cole.maetzold@state.mn.us
Copy Consultant Services Forms Inbox: ProfessionalTechnicalContractForms.dot@state.mn.us
IMPORTANT: Include the MnDOT Contract Number and Solicitation Title in the subject line of the email.
All proposals must be received by MnDOT no later 2:00 pm Central Time on 4/29/2026.
PROPOSAL EVALUATION
Representatives of MnDOT will evaluate all proposals received by the deadline. In some instances, an interview may be
part of the evaluation process. A 100-point scale will be used to create the final evaluation recommendation. The
factors and weighting on which proposals will be judged are broken down in the following table:
Rating Factor Weighting Percentage
Project Understanding 10%
Responder Experience and Qualifications (Company & Key Personnel) 50%
Work Plan - Project Approach 30%
Deliverables 10%
Proposals will be evaluated, and a successful responder will be chosen based on qualifications only. The successful
responder will be required to submit a detailed scope of services and budget promptly after notification of selection.
MnDOT and the successful responder will then meet to negotiate the final scope of services and compensation. If
MnDOT and the successful responder are unable to agree upon a scope of services and compensation within a
reasonable time (as determined by MnDOT, in its sole discretion), then MnDOT may declare negotiations to be at an
impasse and may commence negotiations with the next highest-ranked responder.
GENERAL REQUIREMENTS
Responders must adhere to all terms of this RFP.
Late proposals will not be considered. Fax proposals will not be considered. All costs incurred in responding to this RFP
will be borne by the responder.
1. Unenforceable Terms
As of July 1, 2025, certain terms are unenforceable in state contracts. See Minnesota Statutes 16C.05 subdivision 8.
a. A contract entered into by the State will not contain a term that:
a. Requires the State to defend, indemnify, or hold harmless another person or entity, unless specifically
6

authorized by statute;
b. Binds a party by terms and conditions that may be unilaterally changed by the other party;
c. Requires mandatory arbitration;
d. Attempts to extend arbitration obligations to disputes unrelated to the original contract;
e. Construes the contract in accordance with the laws of a State other than Minnesota;
f. Obligates state funds in subsequent fiscal years in the form of automatic renewals as defined in section 325G.56;
or
g. Is inconsistent with Chapter 13, the Minnesota Government Data Practices Act.
b. If a contract is entered into that contains a term prohibited in paragraph (a), that term will be void and the contract
is enforceable as if it did not contain that term.
2. Affidavit of Noncollusion
Responders must complete the attached "Responder Declarations" form, which includes a Non-Collusion Certification
section, and submit it as part of their proposal.
3. Conflicts of Interest
Responders must provide a list of all entities with which it has relationships that create, or appear to create, a conflict of
interest with the work that is contemplated in this RFP. This list should indicate the name of the entity, the relationship,
and a discussion of the conflict. Responders must complete the attached "Disclosure of Potential Conflict of Interest"
form and submit it as part of their proposal.
4. Proposal Contents Certification
By submitting a proposal, responders warrant that the information provided is true, correct, and reliable for purposes of
evaluation for potential contract award. The submission of inaccurate or misleading information may be grounds for
disqualification from contract award and may subject the responder to suspension or debarment proceedings, as well as
other remedies available to MnDOT, by law.
5. Disposition of Responses
All materials submitted in response to this RFP will become property of MnDOT and will become public record, in
accordance with Minnesota Statutes 13.591, after the evaluation process is completed. Pursuant to the Statute,
completion of the evaluation process occurs when MnDOT has completed negotiating the contract with the successful
responder.
If a 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, the responder must:
a. Clearly mark all trade secret materials in its proposal at the time the proposal is submitted;
b. Include a statement with its proposal justifying the trade secret designation for each item; and
c. Defend any action seeking release of the materials it believes to be trade secret, and indemnify and hold harmless
the state, its agents, and employees, from any judgments or damages awarded against the state in favor of the party
requesting the materials, and any and all costs connected with that defense. This indemnification survives MnDOT's
award of a contract. In submitting a proposal in response to this RFP, the responder agrees that this indemnification
survives as long as the trade secret materials are in possession of MnDOT. MnDOT is required to keep all the basic
documents related to its contracts, including responses to RFPs, for a minimum of seven years.
MnDOT will not consider the prices submitted by the responder to be proprietary or trade secret materials.
6. Contingency Fees Prohibited
Pursuant to Minnesota Statutes 10A.06, no person may act as or employ a lobbyist for compensation that is dependent
upon the result or outcome of any legislation or administrative action.
7. Sample Contract
7

Responders should be aware of MnDOT's standard contract terms and conditions when preparing their proposal.
Responders may view the current version of the Professional/Technical contract template 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
Much of the language reflected in the contract template is required by statute. However, if a responder does take
exception to any of the terms, conditions, or language in the contract template, they must indicate those exceptions in
their response. Responders should note that certain exceptions may result in your response being disqualified from
further review and evaluation. Only those exceptions indicated in the response will be available for discussion or
negotiation.
8. Travel Reimbursements
Reimbursements for travel and subsistence expenses actually and necessarily incurred by the successful responder,
because of the contract, will not exceed the amounts provided in the current MnDOT Travel Regulations.
Reimbursements will not be allowed for travel and subsistence expenses incurred outside of Minnesota, unless the
successful responder has received MnDOT's written approval for out-of-state travel. Minnesota will be considered the
home base for determining whether travel is out-of-state.
9. Organizational Conflicts of Interest
The responder warrants that, to the best of its knowledge and belief, and except as otherwise disclosed, there are no
relevant facts or circumstances, which could give rise to organizational conflicts of interest. An organizational conflict of
interest exists when, because of existing or planned activities or because of relationships with other persons, a vendor is
unable or potentially unable to render impartial assistance or advice to MnDOT, or the vendor's objectivity in
performing the contract work is or might be otherwise impaired, or the vendor has an unfair competitive advantage. The
responder agrees that, if after award, an organizational conflict of interest is discovered, an immediate and full
disclosure in writing must be made to the Assistant Director of the Department of Administration's Office of State
Procurement which must include a description of the action which the selected responder has taken or proposes to take
to avoid or mitigate such conflicts. If an organization conflict of interest is determined to exist, MnDOT may, at its
discretion, cancel the contract. In the event the responder was aware of an organizational conflict of interest prior to the
award of the contract and did not disclose the conflict to the contracting officer, MnDOT may terminate the contract for
default. The provisions of this clause must be included in all subcontracts for work to be performed similar to the service
provided by the prime contractor, and the terms "contract," "contractor," and "contracting officer" modified
appropriately to preserve the State's rights.
10. Pre-Award Audit Requirement
The successful responder will be required to submit pre-award audit information and comply with audit standards.
Failure to do so may result in disqualification.
11. Soliciting Responses from Disadvantaged Business Enterprises (DBE)
The MnDOT Office of Civil Rights has assigned a Disadvantaged Business Enterprise-Neutral (DBEN) goal to this Project.
Responders are directed to read the DBE Special Provisions, posted along with this RFP. The DBE Special Provisions
explain how to comply with the DBE requirements and what documents Responder must submit with its Proposal. The
form required to be submitted with the Proposal is included in Attachment C to this RFP. To view a listing of certified
DBE's, please contact the MnDOT Office of Civil Rights at 651-366-3073, TTY 651-282-5799, or visit:
https://www.dot.state.mn.us/civilrights/find-small-business.html.
12. Work Force and Equal Pay Declaration Page
Responders are required to complete the attached "Workforce and Equal Pay Declaration Page" and submit it as part of
their proposal.
Workforce Certification [For contracts estimated to be greater than $100,000]
8

As required by Minnesota Rule 5000.3600, "It is hereby agreed between the parties that Minnesota Statute
363A.36 and Minnesota Rule 5000.3400 - 5000.3600 are incorporated into any contract between these parties
based upon this specification or any modification of it. A copy of Minnesota Statute 363A.36 and Minnesota Rule
5000.3400 - 5000.3600 are available upon request from MnDOT."
Equal Pay Certification [For contracts estimated to be greater than $500,000]
As required by Minnesota Statutes 363A.44, Laws of Minnesota 2014 Chapter 239, the Responder must obtain an
Equal Pay Certificate from the Minnesota Department of Human Rights (MDHR) or claim an exemption prior to
contract execution. A responder is exempt if it has not employed more than 40 full-time employees on any single
working day in one state during the previous 12 months. Please contact MDHR with questions at: 651-539-1095
(metro), 1-800-657-3704 (toll free), 711 or 1-800-627-3529 (MN Relay) or at compliance.MDHR@state.mn.us.
13. Equal Pay Certification
If the proposal submitted in response to this RFP could be in excess of $500,000, responders are required to complete
the attached "Equal Pay Certification" form and submit it as part of their proposal. As required by Minnesota Statutes
363A.44, Laws of Minnesota 2014 Chapter 239, the Responder must obtain an Equal Pay Certificate from the
Minnesota Department of Human Rights (MDHR) or claim an exemption prior to contract execution. A responder is
exempt if it has not employed more than 40 full-time employees on any single working day in one state during the
previous 12 months. Please contact MDHR with questions at: 651-539-1095 (metro), 1-800-657-3704 (toll free), 711 or
1-800-627-3529 (MN Relay) or at compliance.MDHR@state.mn.us.
14. Certification Regarding Lobbying
Federal money will be used (or may potentially be used) to pay for all or part of the work under the contract; therefore,
responders must complete the attached "Responder Declarations" form, which includes a "Certification Regarding
Lobbying" section, and submit it as part of their proposal.
15. Certification Regarding Debarment and Suspension
Federal money will be used (or may potentially be used) to pay for all or part of the work under the contract; therefore,
this contract is a covered transaction for purposes of 49 CFR Part 29. As such, the successful responder is required to
verify that none of the contractor, its principals, as defined at 49 CFR 29.995, or affiliates, as defined at 49 CFR 29.905,
are excluded, or disqualified as defined at 49 CFR 29.940 and 29.945.
The successful responder will be required to comply with 49 CFR 29, Subpart C and must include the requirement to
comply with 49 CFR 29, Subpart C in any lower tier covered transaction it enters. By signing and submitting its proposal,
responders certify as follows:
The certification in this clause is a material representation of fact relied upon by the MnDOT. If it is later determined
that the responder knowingly rendered an erroneous certification, in addition to remedies available to the MnDOT,
the Federal Government may pursue available remedies, including but not limited to suspension and/or debarment.
The responder agrees to comply with the requirements of 49 CFR 29, Subpart C while this offer is valid and
throughout the period of any contract that may arise from this offer. The responder further agrees to include a
provision requiring such compliance in its lower tier covered transactions.
19.1. Insurance Certificates and Continuity of Coverage Required. The successful responder must provide a certificate
of insurance showing that they have each type of insurance coverage and limits required herein. The certificate
must be filed with MnDOT's Authorized Representative within 30 days of execution of the contract, and prior to
commencing work under the contract. The successful responder must maintain such insurance in full force and
effect throughout the term of the contract.
19.2. Required Insurance. The successful responder will be required to maintain the furnish satisfactory evidence of the
following insurance policies:
19.2.1. Workers' Compensation Insurance: Except as provided below, the successful responder will be required to
provide Workers' Compensation insurance for all its employees and, in case any work is subcontracted, will
require its subcontractor(s) to provide Workers' Compensation insurance in accordance with the statutory
9

requirements of the state of Minnesota, including Coverage B, Employer's Liability. Insurance minimum
limits are as follows:
a. $100,000 - Bodily Injury by Disease per employee
b. $500,000 - Bodily Injury by Disease aggregate
c. $100,000 - Bodily Injury by Accident
If Minnesota Statutes 176.041 exempts the successful responder from Workers' Compensation insurance
requirements, or if such responder has no employees in the state of Minnesota, the successful responder
will be required to provide a written statement, signed by an authorized representative, indicating the
qualifying exemption that excludes the successful responder from the Minnesota Workers' Compensation
requirements. If, during the contract, the successful responder becomes subject to the Workers'
Compensation Insurance requirements, the successful responder then must comply with such
requirements and must provide MnDOT with a Certificate of Insurance evidencing such coverage.
19.2.2. Commercial General Liability Insurance: The successful responder will be required to maintain insurance
protecting the successful responder from claims for damages for bodily injury, including sickness or disease,
death and for care and loss of services as well as from claims for property damage, including loss of use
which may arise from operations under the contract whether the operations are by the successful
responder or by a subcontractor or by anyone directly or indirectly employed by the successful responder
pursuant to the contract. Insurance minimum limits are as follows:
a. $2,000,000 - per occurrence
b. $2,000,000 - annual aggregate
c. $2,000,000 - annual aggregate - Products/Completed Operations
The following coverages must be included:
a. Premises and Operations Bodily Injury and Property Damage
b. Personal and Advertising Injury
c. Blanket Contractual Liability
d. Products and Completed Operations Liability
e. State of Minnesota named as an Additional Insured, to the extent permitted by law
19.2.3. Commercial Automobile Liability Insurance: The successful responder will be required to maintain
insurance protecting the successful responder from claims for damages for bodily injury as well as from
claims for property damage resulting from the ownership, operation, maintenance or use of all owned,
hired, and non-owned autos which may arise from operations under the contract, and in case any work is
subcontracted the successful responder must require the subcontractor to provide Commercial Automobile
Liability insurance. Insurance minimum limits are as follows:
a. $2,000,000 - per occurrence Combined Single limit for Bodily Injury and Property Damage
In addition, the following coverages must be included:
a. Owned, Hired, and Non-owned Automobile
19.2.4. Professional/Technical, Errors and Omissions, and/or Miscellaneous Liability Insurance. The successful
responder will be required provide coverage for all claims the successful responder may become legally
obligated to pay resulting from any actual or alleged negligent act, error or omission related to the
successful responder's professional services performed under the contract. Unless otherwise specified
within this RFP, the successful responder will be required to carry the following minimum limits:
a. $2,000,000 - per claim or event
b. $2,000,000 - annual aggregate
Any deductible will be the sole responsibility of the successful responder and may not exceed $50,000 with
the written approval of MnDOT. If the successful responder desires authority from MnDOT have a
deductible in a higher amount, the successful responder will be required to make such request in writing,
10