The scoring rubric on the first read of any RFP
Three minutes. Find the scoring paragraph. Note the page, the heading, and the weights. The habit that shapes the entire response — and why most teams skip it.
A short field note on a habit that takes three minutes and changes the entire response.
When an RFP arrives, most proposal teams open it from page one and start reading. The first 10 pages are usually background and qualifications. By the time the reader reaches the scoring methodology — typically section 4 or 5 — they have already formed an opinion of what matters. That opinion is wrong about half the time.
The habit: open the document, hit Ctrl-F, and search for the scoring paragraph before reading anything else. The terms that find it: “evaluation criteria,” “scoring methodology,” “award selection,” “source selection,” “evaluation factors,” “basis of award.” Three minutes, max.
Note three things and write them in the kickoff doc:
- The page number.
- The heading exactly as worded.
- The weights — numerical (40/30/20/10) or qualitative (“technical approach is significantly more important than cost”).
Now read the rest of the RFP knowing what is being scored. The scope section reads differently. The qualifications section reads differently. The compliance matrix you build is structured against the scoring factors, not against the requirement order.
This is the discipline I covered in section four of Reading an RFP like the procurement lead who wrote it — the scoring paragraph is the procurement lead telling you, in plain language, how the rubric works. Most teams do not read it before they start writing. The teams that read it first allocate writing effort against the weights instead of against the requirement count, and the response gets meaningfully better for the same total effort.
It takes three minutes. The teams that don’t do it are not saving three minutes; they are spending forty hours of writing time against the wrong allocation.
A second habit that pairs with the first: once the scoring paragraph is in the kickoff doc, build the response section budget against the weights, not against the page count. If technical approach is 40% of the score, technical approach is 40% of the writing budget — measured in SME hours and editorial attention, not in page count, which is constrained separately by the submission format. A 30-page response with a 40% technical weight gets disproportionate technical effort relative to a 30-page response with a 20% technical weight, even when both have the same page allocation. The weights drive the budget; the format drives the page count; the two are different decisions.
A third habit: at every color-team review (see the color-team review pillar), re-read the scoring paragraph alongside the section being reviewed. The reviewer’s question is “would the rubric this paragraph describes reward this section.” A section that doesn’t make the rubric’s case is a section that needs editing.
The next time an RFP lands in your inbox, before anything else: search, note, then read.