How to Read a NYC City RFP: A Section-by-Section Guide

Every NYC RFP follows the same predictable skeleton: key dates, scope of services, proposal requirements, and evaluation criteria. Read the deadline and the scoring criteria first — together they tell you whether you can compete at all and exactly where to spend your effort.

A New York City Request for Proposals can run 60, 80, even 120 pages. The first time you open one, it can feel like the city wrote it to keep you out. It didn't. NYC RFPs follow a predictable structure set by the same rules every agency uses, so once you know what each section is for, you can read one in an afternoon and decide — quickly — whether it's worth your time. This guide walks through that structure section by section, tells you which parts to read first, and points you to the official NYC sources for every claim so you can verify it yourself.

An RFP Is Not a Sealed Bid — and the Difference Changes How You Read It

Before you read a single page, know which kind of solicitation you're holding. New York City buys most goods through competitive sealed bids, where the lowest responsible price usually wins. Services and more complex work go through competitive sealed proposals — the RFP — where the agency weighs the quality of your approach alongside cost. That distinction is written into the city's Procurement Policy Board (PPB) Rules, and the section governing RFPs is 9 RCNY § 3-03, Competitive Sealed Proposals.

Why does this matter for reading? Because in an RFP, the narrative you write — your approach, your experience, your staffing plan — carries real weight. You are not just filling in a price. You are making a case. Every section of the document is either telling you what case to make or how that case will be judged. Keep that lens as you read.

Start at the Back: Key Dates and the Submission Deadline

Counterintuitive, but true: the most important page in any RFP is the timeline, not the introduction. Find the key dates table — usually in the front matter or a "Schedule" section — and read it first. You are looking for four things: the release date, the deadline to submit written questions, the date of any pre-proposal conference, and the proposal due date and time.

NYC rules set a floor on how much time you get. Under the PPB Rules, agencies must allow a minimum of 20 days for proposal preparation, and for procurements subject to the city's M/WBE program under § 6-129 of the Administrative Code, a minimum of 27 days. The same rules require the RFP or its notice to be emailed to vendors on the citywide bidders list at least 20 days before the due date (see § 3-03). If the deadline is tighter than you can realistically meet at a quality bar you're proud of, that is a signal — not a dare. It's better to pass on a rushed proposal than to submit a weak one that burns goodwill with an agency you want to work with for years.

Note the due time as carefully as the due date. NYC proposals are typically due at a specific hour, and late submissions are generally not accepted. There is no partial credit for "almost on time."

The Front Matter: Agency, EPIN, and Who You're Really Selling To

The opening pages tell you who is buying and how to track the procurement. The single most useful identifier is the EPIN — the encumbrance/procurement identification number. It's the city's tracking number for this specific solicitation. You'll use it to find the RFP in PASSPort, the city's digital procurement platform, by searching the EPIN or procurement name in the keyword field.

Also note the issuing agency and the program area. A proposal to the Department of Youth & Community Development reads differently than one to the Department of Environmental Protection, even when the work is similar, because each agency has its own priorities and its own past contracts. Reading the front matter is where you start to understand who you're really writing for.

If you aren't sure whether your business is even eligible to compete for a given agency's work, our eligibility checker is a fast way to pressure-test that before you invest hours in a full read.

The Scope of Services: What They Actually Want You to Do

This is the heart of the document and usually its longest section. The scope of services — sometimes called the "scope of work" or "program requirements" — describes the work the city wants performed, the outcomes it expects, and the standards you'll be held to. Read it twice.

On the first pass, read for fit: is this work you genuinely do, at the volume and locations described? On the second pass, read for requirements you must meet to even be considered. These are easy to miss because they're often buried in prose rather than flagged in a checklist. Some NYC RFPs — particularly Health and Human Services solicitations — require an approved prequalification (PQL) status in PASSPort before you can respond at all, as the city's MOCS guidance on responding to opportunities explains. Discovering a hard prerequisite on the day before the deadline is one of the most common and most avoidable reasons good vendors get disqualified.

Highlight every "must," "shall," and "required" you find. Those words mark non-negotiable conditions. Everything else is where you get to differentiate yourself.

The Proposal Requirements: Technical and Price, Kept Separate

Next, the RFP tells you exactly what to submit and in what form. Most NYC proposals break into two parts. The technical proposal is your narrative — your understanding of the problem, your approach, your staffing, your organizational experience, and your past performance. The price (or cost) proposal is your budget. Common supporting documents include proof of insurance, relevant licenses or certifications, and references.

Two habits will save you here. First, build a compliance matrix: list every required document and every page-limit or formatting rule, then check them off as you complete them. Agencies do reject proposals for missing a required form or blowing past a page limit. Second, keep your price proposal physically separate from your technical proposal if the RFP says to — many do, precisely so evaluators can score your approach before they see your number.

The full set of required documents and how to upload them lives in PASSPort once you acknowledge your intent to respond, which automatically creates a draft response for you in the system. If the structure of a bid response still feels daunting, this is exactly the kind of work our bid response service is built to take off your plate.

The Evaluation Criteria: How You'll Actually Be Scored

If the timeline is the most important page, the evaluation criteria are a close second — and most first-time bidders skim them. Don't. This section tells you how the agency will weigh each part of your proposal, often with explicit point values or percentage weights (for example, quality of approach, organizational experience, and cost). That weighting is a map of where to spend your effort.

Read it as instructions, not fine print. If "organizational experience" is worth 30 points and "cost" is worth 15, you now know that a detailed, evidence-backed account of relevant past work matters more than shaving your price to the bone. After the deadline, the agency evaluates every submission against exactly these stated criteria — typically an initial compliance check, then technical scoring, then cost analysis, and sometimes oral presentations or interviews for shortlisted firms. Write toward the rubric you've been handed.

Where NYC RFPs Live: The City Record and PASSPort

You can't read an RFP you never found. NYC publishes procurement notices in two official places. The first is The City Record, the city's official newspaper, published every weekday except legal holidays; its searchable archive, the City Record Online (CROL), carries solicitation notices. The second is PASSPort, where you actually view the full RFP, ask questions through the built-in discussion forum, and submit your response. A PASSPort account is required to respond to any RFx, so set one up well before you need it rather than during a deadline crunch.

A practical workflow: monitor CROL and PASSPort for opportunities in your category, and the moment one fits, jump to the key dates and evaluation criteria to decide whether to pursue it. Seeing opportunities early — before the deadline pressure builds — is half the battle, which is why we built our contract pipeline service around surfacing relevant solicitations as soon as they post.

Putting it together. Reading a NYC RFP well is mostly a matter of order. Start with the dates so you know whether you can compete at all. Read the evaluation criteria so you know what to emphasize. Then work through the scope and proposal requirements, building a compliance checklist as you go. Do that, and a document that looked impenetrable becomes a set of clear instructions for making your strongest case.

If you'd like a second set of eyes before you commit, a free WedgeBid audit can tell you where your business stands against the kinds of contracts you're targeting and what to shore up first.

Not legal advice — see our disclosures for full disclaimers. NYC procurement rules and individual solicitation requirements change; always rely on the official RFP document and current PPB Rules.