Reading the RFP the procurement lead actually wrote
RFPs are procurement documents written by named humans with known constraints, not sales documents. Read them that way and you respond 40 to 60 percent better. A preview of next week's pillar piece.
There are two ways to read an RFP. One is the way your sales team scans it: requirements list, scoring rubric if you can find it, due date, hand off to proposal. The other is the way the procurement lead who wrote it reads it: as the manufactured output of a constrained role, drafted from a template they have used for fifteen or twenty bids, designed to compare four to seven vendors against a rubric they wrote first.
Most proposal teams default to the first reading. Most win rates reflect that.
Next week I am publishing the long version of this argument — a 3,500-word pillar piece on reading the RFP the way the procurement lead wrote it. This post is the preview. The reframe is simple, and once you have it, the rest of the work changes shape.
The reframe
An RFP is not a sales document. It is a procurement document.
That distinction sounds pedantic. It is the most useful thing I know about reading RFPs.
A sales document is written to you. The author wants you to do something — buy, schedule, sign. The structure is persuasive. Every section is designed to move you toward an action. When your sales team reads an RFP as a sales document, they look for “what do they want from us.” That is the wrong question.
A procurement document is written for an evaluation panel, by a procurement officer who is themselves accountable to a chain of policy and precedent. The structure is comparative. Every section is designed to elicit comparable answers across vendors so a rubric can be applied. The right question is “what is the rubric, what are the constraints, and what evaluators are reading the responses.”
When you ask the right question, the document tells you most of what you need to know — usually in a section labeled something like “Evaluation Methodology” that nobody on your team has read yet.
The procurement lead’s constraints
The person who wrote your RFP is a named human with a job title, a budget code, and a chain of accountability. Their constraints are knowable.
They are constrained by agency or organizational policy. In federal procurement, the FAR. In state and local, the procurement code. In commercial procurement, internal procurement policy plus a legal review. These constraints determine what they can ask, how they can score it, and which clauses are non-negotiable.
They are constrained by precedent. The RFP you are reading is, with very high probability, version 4 or 7 or 12 of a template they reused from the last buy. The structural choices, the section ordering, the boilerplate language are not original — they are inherited. If you have responded to this buyer before, the inherited structure is your map.
They are constrained by the need for comparability. If they ask the question in a way that lets four vendors answer four different ways, the rubric does not work and the procurement is challengeable. So the questions get tighter. The format gets prescriptive. The page limits get enforced.
They are constrained by the rubric they wrote first. In most disciplined procurement shops, the scoring rubric is drafted before the requirements section. The requirements then get written to the rubric. This is why some RFPs feel like the questions are oddly weighted toward dimensions that seem secondary — the dimension is on the rubric, so the question has to be there.
Read the RFP knowing those four constraints exist and the document stops being a wall of asks. It becomes a set of choices a human made, in a job they have done before, against pressures you can name.
The scoring paragraph
The most important paragraph in any RFP is the one that describes the scoring methodology. It is hidden in section 4 or section 5, sometimes appended as Attachment B, sometimes referenced in a one-line callout that says “see Evaluation Methodology document, separately posted.”
If your team is not reading this paragraph first, your team is responding to a different document than the one being evaluated.
The paragraph tells you, typically, three things. The factors being scored (technical, past performance, management approach, cost). The relative weights (40 / 20 / 10 / 30, give or take). The evaluation method — is this a best-value tradeoff, where they buy higher quality at higher cost, or LPTA (lowest price, technically acceptable), where the cheapest compliant vendor wins.
That distinction alone determines the entire shape of your response. In an LPTA bid, the technical narrative is a checkbox exercise — meet the threshold, do not over-write, win on price. In a best-value bid, the technical narrative is the whole game and price is one input among several.
Teams that conflate the two write best-value-style narratives into LPTA bids and lose to a cheaper compliant vendor. Or they write LPTA-grade minimal narratives into best-value bids and lose to a more thorough competitor. The mismatch is invisible if you have not read the scoring paragraph.
What you do with this
Three things, before next week’s long version drops.
Read the scoring methodology before the requirements. Whichever section it lives in, find it first. Highlight the weights. Note the evaluation method. Now read the requirements knowing what they will be graded against. The compliance matrix you build (see Stage 4 of the eight-stage pipeline) gets a column for which scoring dimension each requirement maps to. Cross-reference that column when you allocate writing effort.
Identify the procurement officer by name. Most RFPs name them. The Q&A process is conducted in their voice. Public agencies often have a history of past awards searchable on a procurement portal — read three of their past awards. You will learn the template they reuse, the dimensions they consistently weight, and the kind of vendor that has won before.
Read the inherited template, not just the document. When a section feels redundant or oddly placed, ask whether it is there because this buy needs it, or because the template has had it since 2014. The answer tells you whether to over-invest or write to the box and move on.
These three habits cost you maybe an hour per RFP. The lift is structural, not stylistic — you are reading the right document.
Next week
Next Thursday — July 23 — I publish the long version. Eight sections, ~3,500 words. It covers the procurement lead’s full template structure (the standard sections you will see in nearly every public RFP), the five red-flag clauses that signal incumbent lock-in or wired bids, how the pre-bid Q&A process actually works on the procurement side, and how to request and run a debrief that produces real intelligence rather than a polite ten-minute call.
It is the canonical version of an argument I have been making to every proposal lead I work with for a decade. If the reframe in this preview lands, the long version is the operationalization of it.
Until then: stop reading RFPs as sales documents. Start reading them as procurement documents written by a named human with known constraints. The win rate moves on its own.