2-RFQ031957 RFP BID Book.pdf
PDF 1 MB Posted
- Solicitation number
- RFQ031957
- Issued by
- Franklin County, Columbus City, Ohio
About this file
This is a Request for Proposals (RFP) issued by the City of Columbus, Ohio, Department of Public Service for professional consulting services for the Roadway Improvements - Multimodal Engagement and Planning 2026 project (CIP No. 530161-100236). The project involves transportation planning, public engagement, and general engineering services to evaluate select corridors and neighborhood streets throughout the City for new multimodal designs addressing mobility demands. Potential services include traffic analysis, bikeway planning, transit considerations, pedestrian infrastructure improvements, parking analysis, placemaking, public art integration, and quick-build or pilot project planning. The selected consultant must attend a scope meeting anticipated for March 4, 2026. Proposals are due electronically through Bonfire by February 12, 2026, at 10:00 A.M. Eastern Time, with a deadline for questions set for January 29, 2026. The contract is structured as a general engineering/task order agreement where task-specific scopes of work and associated fees will be negotiated with the selected consultant prior to proceeding. City Council approval is required before contract execution, with a projected Notice to Proceed in April 2026.
Proposals are limited to twelve pages and must include detailed information on the project team, relevant experience, past performance, project understanding, and approach. The City has established a 0% MBE/WBE goal for this project. Mandatory ODOT prequalifications are required in eight work types including bicycle facilities design, complex and non-complex roadway design, interchange justification studies, safety studies, right-of-way plan development, and basic and system traffic signal design. Evaluation criteria include location of lead offeror (maximum 10 points), project manager qualifications (20 points), project team composition (30 points), past performance (30 points), and understanding of project approach (10 points). All consultants and sub-consultants must obtain valid City of Columbus contract compliance certification numbers within seven business days of award notification. Payment is structured on a progress basis using monthly invoices, with routine expenses incorporated into overhead costs rather than reimbursed separately. The City reserves the right to expand, reduce, or cancel the project scope at its discretion.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 1-RFQ031957 Bidders Guide.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
City of Columbus Solicitation Number: RFQ031957
Request for Proposals for Roadway Improvements – Multimodal Engagement and Planning 2026
Department of Public Service Capital Improvement Project No: 530161-100236
Version Dated: 1/15/26
Response Due Date and Time:
February 12, 2026, 10:00 AM, Eastern Time
Submit Electronic Proposal Package through Bonfire at:
https://columbus.bonfirehub.com/login
CITY MBE/WBE GOAL FOR THIS PROJECT: 0%
NEW PROPOSAL PAGE LIMIT OF 12 PAGES. SEE SECTIONS 6.5 AND 6.6 FOR
DETAILS.
THERE HAVE BEEN MANY CHANGES TO THE RFP DOCUMENTS. PLEASE REVIEW
ALL SECTIONS OF THE DOCUMENTS.
https://columbus.bonfirehub.com/login
PROPOSAL SIGNATURE FORM
This page, signed by an officer of the offering firm or a designated agent empowered to bind that entity in a contract with the Department of Public Service, should accompany each proposal submitted for consideration.
I, the undersigned, having carefully examined the Request for Proposals (RFP), propose to furnish services in accordance therewith as set forth in the attached proposal.
I hereby certify that, to the best of my knowledge, this submission is complete and all statements made therein are true and accurate.
I also affirm I am duly authorized to sign and submit this response on behalf of the Offeror named below.
I further acknowledge that by signing this form I am representing that, in the event this proposal is accepted, the Offeror is willing and able to execute a contract in the form shown in the RFP with no changes to the terms and conditions unless approved by the Department of Public Service, with the understanding that the scope and compensation provisions will be negotiated and included in the final contract.
By my signature below, I attest that I have read, understand and agree to the terms, conditions and requirements set forth in the RFP and associated documents.
Failure to sign and return this form may result in the rejection of the proposal.
OFFEROR CONTACT INFORMATION:
OFFEROR (Company Name): ______________________________________________________________
ADDRESS: ____________________________________________________________________________
CITY, STATE, ZIP: _______________________________________________________________________
CONTACT PERSON: _____________________________________________________________________
CONTACT PERSON PHONE: _________________________
CONTACT PERSON EMAIL: _____________________________________________
AUTHORIZATION TO PROPOSE:
Signature Date
Printed Name Title
LOCATION OF LEAD OFFEROR FORM
This form will be used to determine the scoring for the location of the lead offeror per Evaluation Criteria Section 7.1 of this Request for Proposal (RFP). Failure to submit this form will result in the proposal receiving one point for the location of the lead offeror. This form does not count toward the submission page limit for this RFP.
Location of Lead Offeror status (check only one box below):
Lead Offeror meets the definition of a City of Columbus local business (has a current and fixed local occupancy and is a taxpayer in good standing) by meeting all of the following criteria (10 points):
• Owns or leases office space within the corporate limits of the City of Columbus.
• The office space is occupied and used by at least one executive officer of the business entity.
• The office space has been owned or leased by this business for no less than twenty-four consecutive months immediately prior to the due date of this RFP; or if the business has relocated within the City of Columbus during the preceding twenty-four months, it has owned or leased office space within the City of Columbus for twenty-four consecutive months immediately prior to the due date of this RFP.
• The office space is not just a Post Office box or similar mailing address; is not a moveable work site such as a construction trailer or offices at a construction job site; is not a location zoned for residential use, unless such a location is the sole office space owned and/or leased by the business entity; and is not a location rented or used by the business entity for temporary business functions such as meetings or teleconferences.
• Has filed tax returns for both net profits and payroll taxes with the City of Columbus for no less than two consecutive fiscal years preceding the due date of this RFP.
• Is current and compliant in the payment of any City of Columbus taxes on payroll and net profits; of, if not current and compliant, has entered into an agreement to pay any delinquency and is abiding by the terms of the agreement at the due date of the RFP.
Lead Offeror is located within Franklin County, either not within the City’s corporate limits or within the City’s corporate limits does not meet all of the criteria for a City of Columbus local business as detailed above (7 points).
Lead Offeror is located within one of the counties adjoining Franklin County, Ohio (5 points).
Lead Offeror is located within the State of Ohio (3 points).
Lead Offeror is located outside the State of Ohio (1 point).
I hereby certify that the Location of Lead Offeror status claimed above is true and accurate. I also affirm I am duly authorized to sign and submit this information on behalf of the Offeror.
Signature Date
Printed Name Title
TERMS AND CONDITIONS FOR SUBMITTING PROPOSALS
SPECIAL CONDITIONS
Special conditions included in the specifications, if inconsistent with provisions included in this "Terms and Conditions for Submitting Proposals" section, shall take precedence over any provisions in this "Terms and Conditions for Submitting Proposals” section.
SUBMISSION OF PROPOSAL
Proposals must be submitted according to the information contained in the Request for Proposal form.
All proposals and other material submitted in response to this Request for Proposal (RFP) become the property of the City of Columbus. The City may choose to retain or return these materials to the offeror, at the offeror’s expense.
ACCEPTANCE AND REJECTION
This proposal submitted by the Consultant to the City of Columbus will be accepted or rejected within a period of 180 days from proposal due date. The City reserves the right to waive technicalities and to request new proposals (rebid) for the advertised project. Each Request for Statements of Qualifications and Request for Proposals issued by the City may be cancelled and a proposal may be rejected in whole or in part when it is for good cause and in the best interests of the City.
WITHDRAWAL OF PROPOSALS
Consultants may withdraw their proposals at any time prior to the time specified in the advertisement as the closing time for the receipt of proposals. However, no Consultant shall withdraw or cancel a proposal for a period of 180 calendar days after said advertised closing time for the receipt of proposals.
DEFAULT PROVISION
In case of default by the Consultant, the City of Columbus may terminate any resultant contract and may procure the articles or services from other sources and hold the Consultant responsible for any excess costs occasioned or incurred thereby.
SIGNATURE REQUIRED
By submitting this response electronically, offeror is affixing an electronic signature as defined by the Ohio Uniform Transactions Act. Said signature represents that he/she has the authority to bind the entity to the terms and conditions contained herein
APPLICABLE LAWS
The Revised Code of the State of Ohio, the Charter of the City of Columbus, and all City ordinances insofar as they apply to the laws of competitive bidding, contracts, purchases, and wage theft prevention, are made a part hereof.
REMEDIES
All claims, counterclaims, disputes and other matters in question between the City, its agents and employees, and the Consultant arising out of or relating to this Contract or its breach will be decided in a court of competent jurisdiction within the County of Franklin, State of Ohio. Terms and conditions, submitted with this proposal, which are contrary to City Code or Charter shall be disregarded for the purpose of any subsequent contract.
CONTRACT
The Consultant to whom an award is made will be required to execute a written contract with the City of Columbus, Ohio, within seven days after receiving such contract for execution.
TAXES
The City, being a municipality, is tax exempt.
Federal and/or State Taxes are not to be included in prices quoted. The successful Consultant will be furnished an exemption certificate if needed.
PUBLIC RECORDS REQUESTS
The City of Columbus, as a political subdivision of the State of Ohio, is subject to Ohio Revised Code Chapter 149, known as the Ohio Public Records Act. Accordingly, the Offeror understands that ALL records submitted in response to this RFP are generally considered public records and WILL be released in response to valid request for public records, unless said records are legally exempt or non-record per the Ohio Public Records Act.
Upon receipt of a valid request for public records for this submittal, the City will send notice of said request to the Offeror, via electronic mail, to the most recent electronic email address on record for the Offeror. The City will initially review the submittal and redact records it believes it can legally justify under the Ohio Public Records Act. However, the Offeror has the sole responsibility of identifying records that it believe contains proprietary trade-secrets from release under the Ohio Revised Code. If the Offeror believes the submittal does contain proprietary trade-secrets, the City will NOT assert the legal position of the Offeror that said records are protected. Instead, the Offeror must obtain an order form from a Court of competent jurisdiction in Franklin County, Ohio enjoining the release of said records. The City will delay release of records for seven (7) calendar days after the notice was sent to the Offeror to allow the Offeror to obtain a court order. Failure to take timely action will result in the release of records.
THE CITY STRONGLY ENCOURAGES
BIDDER TO NOT INCLUDE ANY
RECORDS IN SUBMITTAL THAT CONTAIN
PROPRIETARY TRADE-SECRETS.
COSTS INCURRED FOR PROPOSAL SUBMISSIONS
The City is not liable for any cost associated with the preparation of the proposal or any other costs incurred by any offeror prior to the execution of the Contract. The rejection of any proposal in whole or in part, at the City’s sole discretion, will not render the City liable for incurring any cost or damage.
CONTRACT COMPLIANCE
All consultants shall identify all sub-consultant(s) who will perform any type of contracting on City proposal(s). All consultants shall include in their proposal response the anticipated scope of work and percentage of work that will be performed by all sub-consultant(s), along with their contract compliance number(s).
All consultants, including sub-consultants, who are party to a contract as defined in Columbus City Code 3901.01, must hold valid contract compliance certification numbers before a contract can be executed. The consultant and all sub-consultants must have valid contract compliance certification numbers within seven business days of the City issuing a notification of intent to award the contract. If the consultant or any subconsultants do not all have valid contract compliance certification numbers by that time, the City may rescind the contract award and award another offeror.
Go to Vendor Services to verify that vendors have a valid contract compliance number. Vendor Services can be accessed via:
http://vendorservices.columbus.gov/
Vendor Services contact information is:
Email: vendorservices@columbus.gov Phone: 614-645-8315
Vendors must register on the Vendor Services portal before doing business with the City of Columbus and becoming Minority or Women Business Enterprise (MBE/WBE) certified. To get registered, please visit the following link:
https://new.columbus.gov/Business- Development/Bids-Solicitations/Vendor- Resources.
After vendor registration, you will receive an email inviting you to complete the required Contract Compliance (EBO) Questionnaire. Vendors must be contract compliant in order to do business with the City of Columbus. To get compliant, please visit the following link:
https://new.columbus.gov/Business- Development/Bids-Solicitations/Vendor- Resources.
To complete our online certification application, track the status of your application and receive a copy of your certification approval letter, visit:
https://columbus.diversitycompliance.com/.
For more certification information or questions, contact us at: DiversityCertifications@columbus.gov.
For additional inquires, contact the Office of Diversity and Inclusion at: odi@columbus.gov.
REMAINDER OF THIS PAGE INTENTIONALLY LEFT BLANK
http://vendorservices.columbus.gov/ mailto:vendorservices@columbus.gov https://new.columbus.gov/Business-Development/Bids-Solicitations/Vendor-Resources https://new.columbus.gov/Business-Development/Bids-Solicitations/Vendor-Resources https://new.columbus.gov/Business-Development/Bids-Solicitations/Vendor-Resources https://new.columbus.gov/Business-Development/Bids-Solicitations/Vendor-Resources https://new.columbus.gov/Business-Development/Bids-Solicitations/Vendor-Resources https://new.columbus.gov/Business-Development/Bids-Solicitations/Vendor-Resources https://new.columbus.gov/Business-Development/Bids-Solicitations/Vendor-Resources https://new.columbus.gov/Business-Development/Bids-Solicitations/Vendor-Resources https://columbus.diversitycompliance.com/ mailto:DiversityCertifications@columbus.gov mailto:odi@columbus.gov
REQUEST FOR PROPOSAL
1. Project Information
1.1 Project Name: Roadway Improvements – Multimodal Engagement and Planning Capital Improvement Project No: 530161-100236
1.2 Project Overview:
This task order contract is for transportation planning, public engagement, and general engineering to evaluate select corridors or neighborhood streets throughout the City for new designs that are better able to address mobility demands. Tasks may require traffic analysis, bikeway planning, transit considerations, pedestrian infrastructure, parking analysis, placemaking and public art, and other services as needed to complete a study.
For some corridors, assistance may be needed with planning a pilot or quick build implementation to promote a new design before the full design is adopted.
A Consultant may be selected for any individual task or all tasks. Potential project tasks could include:
• Public engagement process, which includes development of a public engagement plan, engagement events, collection and analysis of public input, and public engagement reports
• Alternatives analysis for shared mobility or transit accommodations, including bike/shared mobility lanes, premium transit accommodation, and on-street parking analysis
• Corridor wide improvements such as access management, tree lawns, storm water/drainage improvements, streetscape enhancements, road diets, bicycle improvements, and pedestrian improvements
• Collection of speed and volume data and analysis of proposed improvements on traffic speeds and volumes; collection and analysis of pedestrian and/or bicycle volumes; and analysis of speed and volume before and after project implementation
• Traffic analysis, which may include interchange operations studies, pedestrian safety studies, parking studies, speed studies, traffic pattern analysis, capacity analysis, signal operations analysis, signal warrants, and all-way stop control evaluations
• Quick-build concepts or plans for an accelerated planning and execution process, which could include demonstration projects, pilot projects, or projects intended for interim design
• Public art planning, which could include the integration of art into safety infrastructure, wayfinding elements, and placemaking.
The selected Consultant shall attend a scope meeting anticipated to be held on/ about March 4, 2026. If the Project Manager is not available, the Consultant may designate an alternate(s) to attend in his/her place.
1.3 References:
The references below are intended to help respondents develop a submission that clearly demonstrates departmental goals.
1.3.1 General Design Requirements:
https://www.columbus.gov/files/sharedassets/city/v/2/public-service/design-and-construction/design/general-design-requirements_1.1.pdf
1.3.2 Bike Plus Plan
https://www.columbus.gov/files/sharedassets/city/v/1/public-service/bike-plus/bikeplus-241209.pdf
1.3.3 Vision Zero website with Action Plan
Columbus.gov/visionzero
1.3.4 City of Columbus Complete Streets policy
(see attachment)
1.3.5 NACTO Urban Street Design Guide
https://nacto.org/publication/urban-street-design-guide/
1.3.6 NACTO Transit Street Design Guide
https://nacto.org/publication/transit-street-design-guide/
1.3.7 NACTO Urban Bikeway Design Guide
https://nacto.org/publication/urban-bikeway-design-guide/
1.3.8 LinkUS Community Action Plan
https://linkuscolumbus.com/wp-content/uploads/2022/06/LinkUS-Community- Action-Plan220623_small.pdf
1.3.9 Strategic Parking Plan 2.0
https://www.columbus.gov/files/sharedassets/city/v/1/public-service/parking-service/columbus-spp2.0-final-draft-3.21.25.pdf
2. Scope of Services:
The scope of services that follows generally describes services the selected Consultant is expected to be capable to perform. With each task assigned under this General Engineering/Task Order contract, a task-specific Scope of Services and associated fee for services will be agreed to by the City and the Consultant prior to proceeding.
The following are examples of types of services that may be called for as part of a given evaluation:
2.1 Public Engagement
This task requires the development of a Public Engagement Plan for assigned task orders, conducting public engagement, and attending regular coordination meetings with the City. The intent of public engagement is to inform the goals and purpose of projects by involving the public in the decision-making process and ensuring that projects align with community needs.
https://www.columbus.gov/files/sharedassets/city/v/2/public-service/design-and-construction/design/general-design-requirements_1.1.pdf https://www.columbus.gov/files/sharedassets/city/v/2/public-service/design-and-construction/design/general-design-requirements_1.1.pdf https://www.columbus.gov/files/sharedassets/city/v/1/public-service/bike-plus/bikeplus-241209.pdf https://www.columbus.gov/files/sharedassets/city/v/1/public-service/bike-plus/bikeplus-241209.pdf https://vision-zero-columbus.hub.arcgis.com/ https://nacto.org/publication/urban-street-design-guide/ https://nacto.org/publication/transit-street-design-guide/ https://nacto.org/publication/urban-bikeway-design-guide/ https://linkuscolumbus.com/wp-content/uploads/2022/06/LinkUS-Community-Action-Plan220623_small.pdf https://linkuscolumbus.com/wp-content/uploads/2022/06/LinkUS-Community-Action-Plan220623_small.pdf https://www.columbus.gov/files/sharedassets/city/v/1/public-service/parking-service/columbus-spp2.0-final-draft-3.21.25.pdf https://www.columbus.gov/files/sharedassets/city/v/1/public-service/parking-service/columbus-spp2.0-final-draft-3.21.25.pdf
2.1.1 Public Engagement Plan
The plan may include but is not limited to:
• Development of a communications strategy
• Development of a community and stakeholder engagement process and public engagement plan
2.1.2 Public Engagement
Execution of public engagement plan, which may include but is not limited to:
• Conducting community and stakeholder engagement meetings
• Development of promotional and engagement materials
• Collection and analysis of public input
2.1.3 Project Management Meetings
• The Consultant shall allocate time to attend coordination and progress meetings with the City as projects require.
• Additional meetings may be needed as determined appropriate in the
Public Engagement Plan.
2.2 Baseline Mobility Analysis
This task provides a baseline review of existing conditions, past and ongoing studies and recommendations. The Baseline Mobility Analysis may include but is not limited to the following items:
• Overview of roadway infrastructure conditions, traffic volumes, lane configuration/widths, posted speed and operating speeds
• Analysis of crash history, types, and patterns
• Pedestrian infrastructure conditions, transit routes and stops, and existing bicycle/shared mobility facilities
• Parking utilization, including loading zones and valet zones
• Existing utility infrastructure and planned infrastructure
• Review of existing plans and studies
2.3 Land Use and Transportation Context Analysis
This task includes an analysis of the existing land use and transportation context in the project area. This task may include but is not limited to the following items:
• Evaluation of existing land use plans, development plans, and past planned roadway projects
• Consideration of vehicular, transit, pedestrian, and bike accommodations in conjunction with potential redevelopment plans for the area. This may require coordination with the Department of Development (Economic Development and Planning Division) and Building and Zoning Services. Existing zoning and proposed zoning changes may be viewed here: http://gis.columbus.gov/zoning/
• Assessment of existing and planned high-capacity transit corridors, pedestrian accommodations, existing and planned bike facilities, and on-street parking facilities
• Assessment of opportunities to change or introduce traffic control and improve access management as appropriate for the surrounding land use http://gis.columbus.gov/zoning/
2.4 Right-of-Way and Utilities
This type of analysis explores the feasibility and cost of each alternative based on right-of-way acquisition, natural and cultural resources, impacts to property, structures, or community resources, and utilities. Deliverable may include the following types of analysis:
• Map existing right-of-way limits and potential rights-of-way limits for each alternative. Assess potential right-of-way impacts or constraints.
• Identify existing utilities and location of facilities. Research existing easements and develop alternatives for relocation or consolidation of facilities to improve aesthetics and provide cost estimates, including utility relocation or burial costs.
• Prepare preliminary recommendations for Best Management Practices for storm water management and/or green infrastructure, preferably where drainage issues exist currently and/or where Columbus Water and Power has identified future projects.
2.5 Project Deliverables:
Any or all of the following tasks may be assigned, depending on corridor or area need and level of study:
2.5.1 Technical Report Memorandum
Compile existing conditions and technical analysis report that may include but is not limited to items such as:
• Traffic studies
• Crash history, types and patterns
• Roadway infrastructure conditions
• Pedestrian infrastructure conditions
• Bicycle/shared mobility/activity transportation infrastructure conditions and network connectivity
• Signal operations
• COTA routes and stops
• On-street parking utilization
2.5.2 Alternatives Analysis
Develop multiple corridor alternatives, including planning and design documentation. Each alternative may have different modal emphasis(es), such as transit, active transportation/bicycle, streetscape, etc. Alternatives will be evaluated against the goals and objectives of the Department of Public Service and other planning/engineering best practices. The intent is to identify alignment between goals/objectives at each scale of interest. Where alignment does not exist, trade-off decisions must be considered to arrive at a preferred alternative.
Develop order-of-magnitude cost estimates in conjunction with phasing plan.
2.5.3 Preferred Alternative and Conceptual Design
Based on alternatives analysis, establish a feasible conceptual design for the study area/corridor. Project deliverables may include but are not limited to:
• Modal mix and facility types
• Typical roadway/right-of-way section(s)
• Signalization & pedestrian crossings
• Streetscape character & curbside management
• Access management
• Smart mobility integration
• Illustrative graphics to communicate the design vision (such as perspective and/or plan view renderings)
2.5.4 Construction Cost Estimate
Develop a construction cost estimate for the preferred alternative including direct and indirect project costs. The project estimate should be broken down by task and include a construction contingency.
2.5.4 Record of Public Engagement
This deliverable should include all relevant materials related to public engagement efforts, including but not limited to:
• Process documentation
• Meeting records
• Public engagement materials
• Records of comments received through public engagement and all 311 requests relevant to the study area
• Summary of public engagement efforts
2.5.5 Implementation Plan
Develop a phasing plan of improvements and strategy for implementation. For example, implementation could occur as a single capital project, individual projects with separate funding sources, incremental improvements in conjunction with private development, etc.
2.5.6 Quick Build Plan
Develop a quick build plan for accelerated planning and execution of a mobility project. The plan could include short-term designs intended to pilot designs, demonstrate concepts, or function as an interim design. Quick build plans may vary in detail from conceptual designs to detailed designs. Quick build plans may include items such as:
• Timeline and red flag analysis
• Public and stakeholder engagement plan
• Lane configuration/corridor design
• Determination of appropriate metrics methodology for before/after data collection and analysis
• Maintenance of traffic (MOT) plan
3. Consultant/Personnel Prequalifications
3.1 ODOT prequalification required:
The team must be prequalified in all of the following work types and meet all applicable ODOT inspection certifications and training requirements for the listed work types at the time the proposal is submitted:
3.1.1 Roadway: Bicycle Facilities and Enhancement Design
3.1.2 Roadway: Non-Complex Roadway Design
3.1.3 Roadway: Complex Roadway Design
3.1.4 Interchange Justification/Modification Study
3.1.5 Safety Study
3.1.6 Right of Way Plan Development – Limited
3.1.7 Traffic Signal Design: Basic Traffic Signal Design
3.1.8 Traffic Signal Design: Traffic Signal System Design
To begin the ODOT prequalification process, go to https://www.transportation.ohio.gov/working/engineering/consultant-services, then click on “Consultant Prequalification Requirements & Procedures” under “Prequalification Information and Supporting Materials”.
To confirm ODOT pre-qualifications, go to:
https://www.transportation.ohio.gov/working/engineering/consultant-services, click on “Firm Prequalified List” under “Prequalification Information and Supporting Materials”.
The City is not able to answer questions about ODOT prequalifications other than to state what was listed in the RFP as a required ODOT prequalification and why it is required. For all other questions concerning ODOT prequalification, contact ODOT by going to https://www.transportation.ohio.gov/working/engineering/consultant-services, then clicking “Contact Us” or Help Center” at the bottom of the page.
3.2 Other pre-qualifications required: None
3.3 Other qualifications required: None
4. Project Schedule:
Deadline for question submittal: January 29, 2026 RFP Due:
Consultant Selected:
Scope Meeting City Council Legislation:
Notice to Proceed:
February 12, 2026 February - March 2026 March 2026 March 2026 April 2026
5. RFP Pre-Proposal Meeting: None
REMAINDER OF THIS PAGE INTENTIONALLY LEFT BLANK.
https://www.transportation.ohio.gov/working/engineering/consultant-services https://www.transportation.ohio.gov/working/engineering/consultant-services https://www.transportation.ohio.gov/working/engineering/consultant-services
6. Proposal Submittal Instructions:
6.1 Proposals will be received electronically via Bonfire until 10:00 AM on the due date.
Only proposals received via Bonfire by the due date and time will be reviewed and considered for contract award. Proposals should not be able to be submitted via Bonfire after the due date and time. If any proposals should be received after the due date and time, they will be rejected by the City. Proposals sent or delivered to the City using any other method will not be reviewed.
To submit a proposal via Bonfire go to:
Note: The Bonfire link listed above for submitting proposals is not a help link. See Section 6.2.3 for help with submitting a proposal through Bonfire. See Section 6.3 for information concerning submitting a question concerning this Request for Proposal.
6.2 Electronic Submittals
6.2.1 Proposals shall be submitted as a PDF document. Please do not embed any documents within the uploaded file as such documents will not be accessible or evaluated.
6.2.2 Notes Regarding Submissions
6.2.2.1 Proposals will only be visible and accessible to the Department or evaluators after the due date and time.
6.2.2.2 Uploading large documents may take significant time, depending on the size of the file(s) and the Internet connection speed of the Offeror.
6.2.2.3 Offerors are solely responsible for ensuring their proposals have been successfully uploaded and received by Bonfire before the due date and time specified in the RFP. Technical problems uploading a submission, or longer than expected upload times, causing a response to miss the due date and time will not be considered valid reasons for accepting a late response.
6.2.2.4 The City cannot see any uploads in Bonfire prior to the due date and time specified in the RFP. The City is unable to tell you if your upload was successful until after the due date and time specified in the RFP.
6.2.2.5 Minimum system requirements:
• Use a browser supported by Bonfire: Internet Explorer 11 or Microsoft Edge (Windows); Google Chrome (Windows and Mac): or Mozilla Firefox (Windows and Mac).
• JavaScript and browser cookies must be enabled.
These minimum requirements are in place to ensure a secure and stable submission process. If you have a question about system requirements, contact Bonfire per the contact information in Section
6.2.3 of this document.
6.2.3 Bonfire Technical Help
The City of Columbus is using a Bonfire portal for accepting and evaluating proposals digitally. Offerors must contact Bonfire for technical help related to submissions at:
• https://columbus.bonfirehub.com/portal/support
• or Support@GoBonfire.com
• or 1-800-354-8010 (extension 2)
6.3 Questions Concerning the Request for Proposal Information
The deadline for question submittal for this RFP is stated in Section 4. Project Schedule.
Direct questions via e-mail only to: capitalprojects@columbus.gov
The subject line should reference the name of the project.
In order to receive consideration, questions must be received by the “deadline for question submittal for this RFP” listed in section 4, Project Schedule. Any interpretations of questions so raised, which in the opinion of the City or its representative require interpretations, will be issued by addenda posted on the Bonfire website. A notice stating addenda was posted on Bonfire will also be posted on the City’s Vendor Services website. The City or its representative will not be bound by any oral interpretations which are not reduced to writing and included in the addenda.
No contact regarding an RFP is to be made with the City after the RFP has been posted other than through the generic e-mail listed in this section, or in response to an email from the City sent following up on a question submitted to the generic e-mail address. Making contact with anyone else regarding this RFP after it has been issued, and prior to the due date and time, may result in the disqualification of any proposal submitted by the company of the person that made the contact.
For technical questions regarding submissions/Bonfire, see Section 6.2.3.
6.4 Evaluation
Proposals will be evaluated based on the evaluation criteria listed in Section 7 below and in accordance with Columbus City Code, Title 3, Chapter 329.
6.5 Proposal Page Limit and Page Format
6.5.1 Proposals may not exceed a total of twelve (12) letter-size (8.5” x 11”) pages and shall include the information specified in 6.6.3. A “page” is one side of a sheet of 8.5” x 11” paper with text, graphics, etc. If only one side of a sheet of paper has text, graphics, etc., then that is counted as one page. If both sides of a sheet of paper have text, that is counted as two pages. Proposals exceeding the twelve (12) page limit may be rejected.
6.5.2 The Proposal Signature Form and the Location of Lead Offeror form are required forms. Those documents shall be signed by a person authorized to obligate the Offeror’s firm and be uploaded to Bonfire as separate documents.
https://columbus.bonfirehub.com/portal/support mailto:Support@GoBonfire.com mailto:capitalprojects@columbus.gov
6.5.3 Page numbers are desired and requested to be centered at the bottom of each page.
• The page numbering is to start with the first page of the Proposal Content
(Section 6.6 below).
6.5.4 Font size should be 12 point. A font type of Times New Roman or Arial is preferred but any font type can be used. The purpose of this standard font size is for all proposals to have roughly the same amount of space for their response, giving each Offeror an equal opportunity to present their ideas and information, while staying within a 12 page limit. Offerors not following this criteria may be reformatted by Public Service to meet this standard. Reformatted proposals that exceed the 12 page limit will be rejected per 6.5.1.
6.5.5 Cover letters are not required. If submitted, a cover letter will count against the page limit of the proposal.
6.5.6 Unless listed as an exception in Section 6.5.7, appendices or additional information in any form (even if the information is uploaded into Bonfire as an additional document) will be counted against the page limit.
6.5.7 Pages that will not count against the page limit are:
• Proposal Signature Form
• Location of Lead Offeror Form
• Documentation from ODOT verifying ODOT prequalification status or other prequalifications
• Documents uploaded to verify other qualification requirements
• Section tab dividers (unless they contain text other than that necessary to identify the section)
• Title pages (unless they contain more information than just titles)
• ODI required documentation
6.6 Proposal Content
6.6.1 The purpose of this section is to standardize the information received and the order in which it is presented, aiding the evaluation committee in reviewing and scoring proposals by preventing them from having to hunt for information scattered throughout a proposal. Following this format also helps the Offeror as it minimizes the chance that required information, or information critical to scoring of the proposal, will be overlooked.
6.6.2 Provide the information requested in response to this RFP in the order outlined below. The Department of Public Service may reject any proposal that does not provide the information in the order stated below.
6.6.3 No more than twelve (12) pages of the proposal should be dedicated to the information below, organizing the required information using the headings provided below. These elements correspond to the evaluation criteria noted in Section 7. Note that page breaks are not required between sections.
Section A. Anticipated Project Team Identify the Project Team, including sub-consultants, the percentage of contract dollars anticipated to be paid to each firm, along with the address of each team member’s office. (The percentage of contract dollars is not to be listed as a range.) The overall subcontracted percentage listed in the contract that results from this RFP is expected to be at least the amount the Offeror listed in the proposal. Also include the CAGE Number or System for Award Management (SAM) Unique Entity ID, City of Columbus contract compliance certification number, the City certification business type, and the contract compliance expiration date for each firm.
Replicate the table below in your proposal, providing the requested information for each firm on your team.
Project Team
Firm Name
Full Address of Firm
CAGE
Number or
SAM
Unique
Entity ID
City Contract
Compliance Number
(CC#)
Current City Certification Type (MAJ, MBE, WBE, etc.)
Contract Compliance Expiration
Date
% of Contract Dollars
Immediately beneath the table state the following:
• Number of Columbus based employees for the Lead Consultant.
• Number of employees company-wide for the Lead Consultant. (State this second number even if the number is the same as the number of Columbus based employees.)
Include an organizational chart showing key individuals that are assigned to the project along with resumes of the Project Manager and key Project Team members’ containing professional information relevant to the project.
Project Manager. Present the education, experience, and availability of the Project Manager. Availability shall be indicated as hours per week on average.
Project Team. Present the education, experience, and availability of the key team members. Availability shall be indicated as hours per week on average.
Also include what the various firms will be assisting with on the project.
ODOT Prequalification. Replicate the table below (minus the information in the
3.1.5 example line) in the proposal, providing the information on ODOT Prequalification of work types (Section 3.1 of this RFP) if ODOT prequalification is required for this project. Include a copy of the ODOT documentation verifying prequalification status issued to each firm named in this section showing they are ODOT prequalified for the work types. The ODOT verification documentation is not to be placed with the other information in this section but is to be uploaded in Bonfire as a separate PDF attachment named “Prequalification
Documentation”. The ODOT documentation uploaded in this manner will not count against the proposal page limit.
ODOT Prequalification Table
RFP Section Prequalification Work Type Firm
3.1.5 Safety Study XYZ, Inc.
Address topics discussed in Section 7.2 and 7.3.
Other Prequalifications Required.
If other prequalifications are required per Section 3.2 of this RFP, replicate the table below (minus the information in the example) in your proposal, and provide the requested information. Any documentation listed as needing to be submitted with the proposal as proof of meeting these prequalifications is to be uploaded in Bonfire as a separate PDF attachment named “Prequalification Documentation”. (Do not include this documentation in the response to this section.) This documentation will not count against the proposal page limit if uploaded in this manner.
Other Prequalification Required Table
RFP Section Prequalification Firm
3.2.1 Level Four Storm Sewer
Design Certification Company A
Other Qualifications Required.
If other qualifications are required per Section 3.3 of this RFP, replicate the table below (minus the information in the example) in your proposal, and provide the requested information.
Other Qualifications Required Table
RFP
Section
Qualification Project Name
Engineer of Record
Firm Columbus Water & Power Project Manager
3.3.1 DOP-
distribution experience
Project P Name Company Name
3.3.2 DOW-large
water main experience
Project W Name Company Name
3.3.3 DOWR-large
sewer experience
Project S Name Company Name
Section B. Relevant Experience and Past Performance Present the proposed Project Manager’s and Project Team members’ experience and past performance on specific projects relevant to this project.
For each project identified include: Team member(s), project name, project owner and contact information, design contract amount, and the date the contract was awarded. Projects with greater relevancy to this project will be given greater consideration.
Address topics discussed in Section 7.4.
Section C. Understanding of the Project/Project Approach Present the Consultant’s understanding of the scope, challenges, and limits within the context of the project. Include an explanation of public involvement, innovative approach, and cost containment measures for design and construction.
Address topics discussed in Section 7.5.
7. Evaluation Criteria:
7.1 Location of Lead Offeror (Maximum 10 points)
The City of Columbus places a high value on talent in the Central Ohio region and emphasizes its use on City projects as much as possible. Evaluation points for location are awarded based upon the location of the Lead Offeror as follows:
7.1.1 Location is within the City of Columbus corporate limits and meets all criteria for a City of Columbus local business as defined in City Code 329.01(cc) (10 points)
7.1.2 Location is within Franklin County, either not within the City’s corporate limits or does not meet all of the criteria for a Columbus local business as defined in City Code 329.01(cc) (7 points)
7.1.3 Location is within one of the counties adjoining Franklin County, Ohio (5 points)
7.1.4 Location is within the State of Ohio (3 points)
7.1.5 Location is outside the State of Ohio (1 point)
It is the responsibility of the Offeror to clearly indicate the location of the Lead Offeror.
Failure to do so, or failure to submit the Location of Lead Offeror Form, may result in the Offeror being assigned 1 point for location.
7.2 Project Manager (20 points maximum).
Points will be awarded based on the education, experience, and availability of the proposed Project Manager. An example of the preferred Project Manager is someone with many years of local experience in the type of work that is to be performed on the project with a demonstrated history of managing projects, leading a team of professionals, and communicating with concerned citizens or groups. The proposed Project Manager will be evaluated according to the following criteria:
7.2.1 Education – education consistent with the requirements of the project.
7.2.2 Relevant Experience – experience relevant to the type of project advertised in this RFP. Projects cited should be adequately described to enable an evaluation committee member to determine the project scope, size, and complexity.
7.2.3 Overall Experience – years practicing as a professional engineer, number of years with the lead firm, and number of years of experience with the type of work required by the project.
7.2.4 Communications Experience – experience working with citizens, neighborhood groups, utility companies and City departments. Specific examples should be given.
7.2.5 Availability – the number of hours of availability of the Project Manager for the project per week.
7.3 Project Team (30 points maximum)
Other project team members will be evaluated according to their experience with similar projects and City of Columbus or other local experience. Teams with the most relevant experience with this type of project will receive more points, as explained above. Forming partnerships with other firms to create a stronger, better qualified Project Team also will receive more points. Points will also be awarded based on how the lead consultant expects to share the work with the other team members.
7.4 Past Performance (Maximum 30 points)
The Consultant should describe the proposed Project Manager’s and key staff’s past performance on similar projects. Resultant scores shall be determined based on similar project performance (projects not performed for the Department of Public Service) as well as past performance on Department of Public Service projects.
Scores will be based on quality of work, ability to meet deadlines, previous communication history, organizational skills, and the ability to maintain a project budget. Responses should address these areas on each project referenced. The referenced projects should have some correlation with the projects identified in the previous section for the experience of the Project Team. Firms with similar past projects and experience working together as a Project Team will receive more points.
7.5 Understanding of Project/Project Approach (Maximum 10 points)
The Consultant should demonstrate a thorough understanding of the project and how the Consultant’s entire team will successfully execute the project. The score will be based on the completeness of the responses. The Consultant should make a clear presentation of how the project team is organized, their understanding of the project requirements including the challenges and areas of risk, and a detailed plan for execution.
Specifically, the Consultant’s proposal should contain a narrative description tailored to the project, describing staff assignments and the approach the Consultant intends to take to complete the project. The proposal should identify unique characteristics of the project and the challenges those elements present as well as options to overcome those challenges.
Increased value is placed on innovative concepts that may save time or money or that will lead to a more successful project. These concepts should be well conceived, clearly defined, and demonstrate a thorough understanding of the project and best engineering practices.
9. Selection Process:
The Department of Public Service will appoint an Evaluation Committee (Committee) to evaluate proposals received. The Committee will be composed of at least three voting members. Voting members include staff from the Department of Public Service and may include staff from other City departments and/or representatives from other organizations as appropriate.
The Committee will evaluate all offerors and proposals received and rank the offerors based upon the evaluation criteria specified in the RFP. The Committee may select two or more of the highest qualified offerors with which to hold additional discussions. Offerors not selected for further discussions may be excluded from further consideration for the contract upon notification by the Committee or city agency. The discussions may include, but are not limited to, presentations by the offerors to the Committee to elaborate upon their qualifications, proposals, and/or other pertinent information. The Committee may permit revisions of proposals so long as all offerors who are selected for additional discussions are given equal opportunity to revise their proposals.
Based upon the content of the proposals received including any revisions thereto, and upon any additional discussions with the offerors, the Committee will rank the remaining offerors based upon the evaluation criteria specified in the RFP.
The Committee will submit its ranking of the offerors along with a written explanation to the Director of Public Service. The Director has discretion consistent with appropriate departmental and/or citywide administrative rules in selecting the offeror with which to enter into contract negotiations. The department will enter into contract negotiations with the selected offeror to determine the terms and conditions of the contract, including compensation to be paid by the City. If negotiations fail, negotiations with this offeror will be terminated, and the department may enter into contract negotiations with another offeror as selected by the Director. This process may continue until a contract is successfully negotiated.
Columbus City Council must approve the contract via a legislative request submitted by the Department of Public Service before a contract can be executed.
Per City Code Section 329.11 (Issuance of addenda – Cancellation of invitation for bids, requests for statements of qualifications, and requests for proposals), the Director of Finance and Management (or designee) or the Department of Public Service may issue addenda to cancel any invitation for bids, request for statements of qualifications, and/or requests for proposals, and may reject any or all bids or proposals in whole or in part when it is in the best interests of the City.
PROFESSIONAL SERVICES CONTRACT
BETWEEN
CITY OF COLUMBUS, OHIO
AND
Consultant
FOR
PROJECT NAME
CAPITAL IMPROVEMENT PROJECT xxxxxx-xxxxxx
Appendix B: Draft Professional Services Agreement
This contract is not to be signed and returned with the proposal. It is included as an example of the contract the awarded consultant will sign. The City is unlikely to agree to changes in the terms and conditions contained in this contract. Any requests concerning potential changes to the terms and conditions need to be presented as a question per the instructions for submitting questions in Section 6.3 of this RFP and will be answered per the instructions in that section.
This Contract is made and entered into by and between the City of Columbus, Ohio, acting through the Director of Public Service, pursuant to and under the authority of Ordinance No.
, passed , by the Council of the City of Columbus and approved by the Mayor of said City, hereinafter designated as the CITY, and Consultant, located at address, hereinafter designated as the CONSULTANT. The Purchase Order/Contract number is: .
This Contract sets forth the entire agreement between the parties with respect to the subject matter hereof. Understandings, agreements, representations, or warranties not contained in this Contract, or as written amendment hereto, shall not be binding on either party. Except as provided herein, no alteration of any terms, conditions, delivery, price, quality, or specifications of this Contract shall be binding on either party without the written consent of both parties.
WITNESSETH: That the CITY and the CONSULTANT, for mutual considerations herein contained and specified, have agreed and do hereby agree as follows:
SECTION 1 – GENERAL CONSIDERATIONS
The CONSULTANT shall, for the agreed fees, furnish all technical and professional services necessary to fully and adequately perform and complete the Scope of Services (the “Services”) set forth in Exhibit A to this Contract. In so doing, the CONSULTANT shall comply with and follow all reasonable requests and instructions from the CITY, particularly with respect to the time, timing, and manner of performance of said Services and all applicable federal, state, and local laws, ordinances, rules, regulations, standards, policies, and…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .