Anatomy of a mid-sized municipal RFP: Chicago-shaped
A walk through the structure of a typical mid-sized municipal RFP — front matter, technical scope, evaluation, contractual riders — using a representative Chicago-shaped solicitation as a composite worked example.
Composite teardown. The document described below is not a specific Chicago solicitation. It is a composite drawn from the patterns we see across mid-sized City of Chicago RFPs — the kind of package vendors respond to for municipal IT services, facilities-adjacent procurements, or professional-services contracts. Where we describe structural features, they are features we see recur; where we describe page ranges, they are directional. Real Chicago solicitations are indexed by the City of Chicago Department of Procurement Services and bid tabulations are publicly available for anyone who wants to look at recent issued solicitations directly.
Municipal RFPs are not federal RFPs in miniature. They are their own genre. A mid-sized Chicago-shaped solicitation has a shape that is recognizable across large U.S. cities but distinct from the federal Section L / Section M architecture, with its own conventions about where the evaluation criteria live, how the contractual riders are stacked, and what the vendor is expected to do with the long tail of compliance attachments.
This post walks through the anatomy of a typical mid-sized Chicago-shaped RFP. We are describing the common structure rather than reproducing any specific solicitation document, because municipal solicitation packages are large, frequently amended, and not stable URLs across years.
The structural pattern
A mid-sized Chicago-shaped RFP — and the pattern generalizes across many large U.S. cities — typically breaks into five distinct sections. They appear in this order more often than not.
Pages 1–6: front matter and instructions. The cover letter from the Chief Procurement Officer (or designate). Solicitation number, issue date, due date, pre-bid conference details. A short summary of the work being procured. A list of attachments. The bidder’s submission instructions: what to submit, where, in what file format, in how many copies (yes, sometimes a paper copy is still required).
Pages 7–22: scope of work / technical specifications. The substantive description of what the city wants to buy. For a services engagement, this reads as a narrative description of the work — the systems involved, the user base, the operational expectations, the deliverables. Often broken into named sections (Tasks 1, 2, 3 or Phases A, B, C). For a goods or construction procurement, it would be a different specification structure.
Pages 23–34: evaluation criteria and minimum qualifications. What the city will use to score proposals. Minimum qualifications — must-meet thresholds — typically come first. Then the scoring categories with point allocations: technical approach (often the largest share), past performance, key personnel, MBE/WBE/DBE participation (Chicago has specific minority-and-women-business-enterprise participation requirements that figure heavily in scoring), and price (which is often a smaller share than vendors expect). Pricing is sometimes evaluated separately on a pass-fail rather than scored.
Pages 35–52: contractual exhibits and riders. The Master Consulting Agreement (or applicable contract type) is usually attached as an exhibit. Insurance requirements, indemnity provisions, audit-rights clauses, confidentiality, intellectual property, termination-for-convenience. This section is where deal-quality attributes live and where a careful procurement-aware vendor flags clauses that affect the bid/no-bid math.
Pages 53–64: forms and attachments. Required certifications. Affidavit of compliance with anti-collusion and anti-kickback rules. Disclosure forms for political contributions, ownership, and disclosed-relationships. MBE/WBE/DBE participation plan templates. Vendor information forms. References template. Often a dozen separate forms, each with its own filing instructions.
A total page count in the 60s is not unusual for a mid-sized Chicago RFP; the exact distribution shifts solicitation to solicitation, but the section sequence is consistent.
Where the actual work hides
A vendor reading a Chicago RFP for the first time tends to focus on the scope of work — the substantive middle of the document — and underweight everything else. That is the wrong allocation of attention. The disqualification risk is concentrated outside the scope.
The MBE/WBE/DBE participation section. Chicago’s compliance regime requires specific percentage participation by certified minority- and women-owned business enterprises. The form requires named subcontractors with certifications attached. A response without a complete participation plan, with the named subcontractors and the executed letters of intent, can be deemed non-responsive — disqualified before scoring. This is a category that catches vendors who think of subcontracting as a post-award activity. It is a pre-submission compliance gate.
The disclosure forms. Chicago has unusually detailed disclosure requirements covering political contributions, beneficial ownership, and “doing business” relationships with the city. Forms must be completed accurately for the bidding entity and for major subcontractors. Errors on these forms can trigger non-responsiveness or, after award, contract challenges. They are the lowest-glamour part of the response and arguably the highest-risk.
Insurance requirements. The contractual exhibit specifies coverage limits and additional-insured language. Vendors whose existing policies don’t meet the limits need riders, which take time to procure. A team that doesn’t read the insurance schedule until the last week of response is the team that submits without a certificate of insurance, which is a frequent cause of disqualification.
Pricing format. Chicago RFPs typically include a specific pricing form — a fixed schedule, a labor-rate schedule, a unit-priced schedule — and require pricing to be submitted on that exact form. Submitting pricing in your own format, even if it contains identical numbers, is a non-responsive submission in some procurements.
A response strategy that gives the substance-of-work the most calendar time and treats the rest as final-week paperwork misallocates risk. The disqualification gates are concentrated in the paperwork.
What good intake captures
For a mid-sized municipal solicitation, intake should produce a structured record that a human can read in five minutes and a search system can index in seconds. The structured record we recommend has six fields:
- Solicitation identifier and version. With a fingerprint of the document so subsequent amendments can be diffed.
- Section index. Where each major section starts (front matter, scope, evaluation, contractual, forms).
- Compliance matrix seeds. Every “shall,” “must,” “will provide,” and “describe” extracted with section references.
- Evaluation criteria with point allocations. A separate list, because evaluation criteria are not in the same section as the scope they evaluate.
- Required forms list. Each named, with the page reference and an explicit field for “completed?” status.
- Critical-path dates. Pre-bid conference, Q&A close, addenda windows, submission deadline. Set as calendar entries, not buried in prose.
A response built from this structured intake starts with full visibility into the disqualification gates. A response built without it discovers the disqualification gates one at a time, usually in the last week, sometimes after submission.
How the evaluation actually works
Chicago RFPs typically state a scoring rubric explicitly. Technical approach often carries 30–40 points out of 100. Past performance 15–25. Key personnel 10–20. MBE/WBE participation 10–20. Price 10–25.
Two patterns matter for response strategy.
Price often weights less than vendors expect. A vendor who optimizes hard on price can still lose if the technical-approach section is weak. The reverse is also true: a strong technical approach with mid-range pricing routinely wins over a low-price submission with a thin technical narrative.
MBE/WBE/DBE points are sometimes a structural advantage for a well-prepared vendor. A vendor with established and certified minority-business-enterprise subcontracting partners can earn full points; a vendor putting together a participation plan in the last week of the response is going to under-perform. This is a category where past relationship investment pays off in measurable proposal points.
What the post-mortem should ask
For a Chicago response that won, the post-mortem should validate that the technical-approach narrative, MBE/WBE plan, and key-personnel section were the things that earned the points the team thought they would. That validation is achievable through a debrief with the contracting officer, which Chicago and many large cities will grant on request.
For a Chicago response that lost, the post-mortem should ask the same question, plus: which forms or compliance items, if any, contributed to the loss? Sometimes the answer is “the technical approach scored 8 points behind the winner.” Sometimes it is “the MBE participation plan was incomplete and the proposal was scored without those points.” Knowing which is the difference between a useful next-time recalibration and a misdirected one.
What this generalizes to
The structural pattern — front matter, scope, evaluation, contractual, forms — recurs in most large U.S. municipal solicitations. The specific compliance regime (Chicago’s MBE/WBE program, Los Angeles’s Living Wage Ordinance, NYC’s Iran Divestment certifications, etc.) varies. The intake discipline does not. A team that has a structured intake on a Chicago-shaped RFP can adapt to a Houston RFP or an LAUSD RFP without re-inventing the workflow. The disqualification gates move; the existence of disqualification gates does not.
Municipal procurement is a category where the cost of a sloppy intake is concentrated in the paperwork, not the prose. A team that internalizes that — and structures their first 48 hours after RFP receipt accordingly — wins on contracts where the substance-of-work scoring is otherwise close. Which it usually is.