What 'reading an RFP' actually means (Part 1 of 4)
Reading an RFP isn't reading. It's six discrete passes — scope, compliance language, evaluation rubric, timeline and addenda, procurement signals, deal quality — each producing its own artifact. Part 1 of a four-part series.
A new proposal manager joins a team. They are handed a 60-page RFP and told to “read it and let us know what you find.” Two days later they come back with a summary memo and the team starts drafting. The bid loses. Nobody knows why.
I have seen this pattern a hundred times. “Reading an RFP” sounds like one activity, and it is six. Each one produces a different artifact. Each one catches a class of failure the others won’t. Skip any of them and a specific mistake will show up in your final response, predictably, every time.
This is part one of a four-part series on reading an RFP before any drafting begins. It names the six passes. Parts two through four go deep on three of them — the compliance language pass, the procurement signals pass, and the deal-quality pass.
Why six passes, and not one careful read
VisibleThread’s analysis of government proposal failure names the root cause I keep seeing: rushing into writing without fully understanding the requirements is the leading reason proposals fail. The fix is not to read more carefully. The fix is to read with structure, because different aspects of an RFP demand different cognitive modes, and trying to do them all at once means you do none of them well.
A scope pass and a compliance pass are not the same activity. One asks “what is the buyer trying to achieve?” The other asks “what contractual obligations am I being graded against?” A reader trying to do both at once loses both threads. So we run the passes in order, and each pass produces an artifact the next pass can use.
Pass 1 — Scope
The question. What is this RFP actually for? Strip away the procurement language and describe the work in one paragraph as if you were briefing a colleague.
The artifact. A scope memo, no more than a page. The buying organization, the operational problem they are trying to solve, the in-scope deliverables, the out-of-scope items called out explicitly, the geography, the engagement timeline (not the response timeline), and the form of contract (fixed fee, T&M, multi-year, milestone-billed).
Why this is first. Until the scope is clear, every other pass is reading without a frame. A clause about data residency reads differently if the engagement is global vs. US-only. A staffing requirement reads differently if the contract is six months vs. five years. Skip scope and you re-read the document a second time once you figure out the shape of the work — the second read is just the first read with friction.
Pass 2 — Compliance language
The question. What is this RFP literally requiring me to do? Every “shall,” “must,” “will provide,” “describe,” “demonstrate,” and “submit” — flagged, listed, numbered.
The artifact. A first-draft compliance matrix. One row per requirement. Each row carries the source paragraph reference, the verb category (shall, must, describe, etc.), the evaluation weight if the RFP exposes one, and a column for the response section that will address it (initially blank).
Why this matters. This is where you separate “the buyer wishes” from “the buyer requires.” A non-compliant response is a disqualified response, and disqualification reasons in public-sector RFPs are unforgiving — wrong cover letter format, missing certification, signature on the wrong page. The compliance matrix is the only artifact in the response process that catches these in time. Part 2 of this series goes deep on the matrix.
Pass 3 — Evaluation rubric
The question. How is this RFP going to be scored? Find the scoring criteria, the weights, the panel composition if disclosed, and the relative emphasis on price vs. technical vs. past performance.
The artifact. A scoring summary on a single page. If the RFP exposes the rubric, copy it. If not, list every signal — language like “lowest responsive bidder,” “best value,” “technical merit,” any statement of weighting, the order in which sections are reviewed, whether oral presentations are scheduled.
Why this matters separately from compliance. Compliance is binary — you either meet a requirement or you don’t. Evaluation is gradient — you can meet a requirement and score badly on it because the buyer cares more about another dimension. Reading for evaluation is reading for what the buyer will reward. A response that is 100% compliant and reads as if every requirement were equally important loses to a response that bears down on the three things the rubric actually weighs.
Pass 4 — Timeline and addenda
The question. What is the response timeline, who can ask questions and by when, when do answers post, when do addenda land, and when does the response have to be submitted in what format?
The artifact. A response calendar with milestones. Q&A submission deadline. Q&A response posting date. Addenda windows. Pre-bid conference (if any). Submission deadline, in the buyer’s stated time zone, with a buffer the team agrees on at kickoff.
Why this is its own pass. Timeline mistakes are unforced errors. A submission missed by 14 minutes loses. A question submitted after the cutoff goes unanswered, and the team responds against a guess. A late addendum changes a requirement and the team responds to the wrong version. The buyer gives you all of this information; the only excuse for missing it is failing to read for it.
The addenda piece is especially load-bearing because it changes during the response period. Most RFPs receive at least one addendum. Some receive five. If your reading-the-RFP work happens once at intake and not again, every later addendum is a surprise.
Pass 5 — Procurement signals
The question. What can I tell about the buyer that they didn’t say out loud? Who are they, what’s their procurement maturity, what’s their incumbent posture, what are the unstated priorities that the document leaks?
The artifact. A signals memo — informal, two pages maximum, written for the capture lead. It names the buyer organization in operational terms, the people likely on the evaluation panel based on the contact list and any organizational research, the apparent presence or absence of an incumbent, the language patterns that suggest who drafted the RFP (procurement-led vs. operations-led vs. consultant-led), and any unusual clauses that hint at past pain (the “we have been burned by X” pattern shows up as overly specific clauses about a particular failure mode).
Why this matters. Procurement signals are the difference between a generic-but-compliant response and one that lands. Shipley’s proposal guide has taught this for decades — the buyer’s evaluation is shaped by unstated priorities, and the RFP leaks them if you read for them. Most teams skip this pass because it doesn’t produce a clear deliverable for a writer. It produces a sensibility a capture lead carries into every later decision. Part 3 of this series goes deep on it.
Pass 6 — Deal quality
The question. Is this a bid we want to win?
The artifact. A bid/no-bid scoring sheet. Strategic fit, probability of win, cost to produce, opportunity cost, deal quality (ACV, margin, payment terms, reference value). Each scored on a defined scale. A floor below which the answer is no-bid.
Why this is last in reading and first in deciding. The first five passes give you the inputs to score deal quality honestly. Until compliance is done, you don’t know what’s hard. Until evaluation is done, you don’t know how the buyer will grade. Until procurement signals are done, you don’t know if you have a real shot. With those in hand, the deal-quality pass becomes a decision instead of a vibes call.
Fairmarkit on buyer-side RFP pain describes operational teams writing RFPs as wish lists. The vendor-side mirror: don’t bid on every RFP. Most aren’t built to be won by anyone except the incumbent. Part 4 of the series is on this pass.
What you have at the end
When the six passes are done, before any drafting begins, you have:
- A scope memo (1 page).
- A compliance matrix (a row per requirement, columns for response sections, evaluation weight).
- A scoring summary (1 page).
- A response calendar (kickoff to submission, with addenda hooks).
- A procurement signals memo (2 pages).
- A bid/no-bid scoring sheet with a written rationale.
That stack is what “reading the RFP” actually produces. A team that hands a writer those six artifacts, in that order, before drafting starts, ships materially different responses than a team that hands the writer a 60-page PDF and a deadline.
Next week: the compliance matrix in detail. The thirty-minute version, the worked example, and the reason almost every proposal team builds it too late.