For bid managers and presales teams deciding where effort goes before they write. Buyers drafting criteria: start with our guide to writing an RFP.
RFP evaluation criteria are the factors a buyer uses to score responses and choose a winner, each with a weight or an order of importance. In US federal and EU public procurement, the buyer must publish those factors and their relative importance in the solicitation. So the scoring grid is in the documents: find it, spend your effort in proportion to it, and answer in its order. In private RFPs the weights are often hidden, and you have to infer them.
Key takeaways
- FAR 15.304(d) requires US federal solicitations to state every evaluation factor and its relative importance.
- EU Directive 2014/24 requires public buyers to publish the weighting of award criteria, or their order of importance.
- The European Commission proposed on 9 September 2026 to make quality at least 30% of the score in EU public tenders.
- A US federal contracting officer asked vendors in August 2026 to read the stated evaluation criteria before responding.
What are RFP evaluation criteria?
RFP evaluation criteria are the factors, weights and rating rules a buyer uses to score proposals and select a supplier. A factor is an area the buyer scores, such as technical approach, past performance or price. A subfactor splits a factor into smaller scored parts. The weight, or relative importance, says how much each factor counts in the final decision.
Criteria come in two kinds. Pass or fail requirements decide whether your response is considered at all. Scored criteria decide where it ranks. The award method then decides how price and quality combine.
The award method changes how you write before it changes what you write. Under an acceptability-based method, the aim is a clean, compliant response at a sharp price. Under a tradeoff or a price-quality ratio, the aim is to give evaluators specific, evidenced strengths they can record against each factor.
Do buyers have to publish their evaluation criteria?
In US federal and EU public procurement, yes. In private RFPs, no general rule applies.
The guides that rank for this topic do not agree on the point. Responsive advises buyers to share their weights with vendors. A buyer-side guide from Fohlio treats the scoring as internal. Our own guide to responding to an RFP said buyers often score against a grid the bidder never sees. Each statement is true somewhere, and none is true everywhere.
The primary sources settle it. FAR 15.304(d) says the factors and their relative importance "shall be stated clearly in the solicitation". Article 67(5) of the EU directive says the contracting authority "shall specify, in the procurement documents, the relative weighting" of its criteria. So in a public tender, a bidder who says the grid was hidden has usually not read Section M or the award criteria.
US federal solicitations also say how price compares with everything else. Under FAR 15.304(e), the contracting officer states whether all evaluation factors other than cost or price, combined, are "significantly more important than cost or price", "approximately equal to cost or price", or less important. That one sentence in Section M tells you whether you are in a price contest or a quality contest. Read it before anything else.
The federal rule has a second half that matters just as much. Under FAR 15.305, an agency evaluates proposals "solely on the factors and subfactors specified in the solicitation". The grid is both the map and the boundary.
How evaluators actually score a response
An evaluator scores what the criteria ask for, and nothing else. That is the practical reading of FAR 15.305. A strong section that answers no stated factor earns no points, however good it is.
Two consequences follow for the writer. Anything you want credit for has to sit under a factor, in words an evaluator can match to the criterion: a differentiator buried in the company overview may never be scored. And silence on a subfactor gives the evaluator nothing to score, so a short, specific answer beats an eloquent gap.
The award method then changes what extra effort is worth. Under lowest price technically acceptable, FAR 15.101-2 says tradeoffs are not permitted, and proposals are rated for acceptability but not ranked on non-price factors. Effort beyond "acceptable" earns nothing there, and price decides. Under a best value tradeoff, the buyer can pay more for a better proposal, so strengths above the minimum can win. Under a best price-quality ratio, every quality point has a known exchange rate against price, set by the weights.
The same regulation limits where lowest price technically acceptable applies. FAR 15.101-2(d) tells civilian agencies to avoid it, where practicable, for information technology, cybersecurity and other knowledge-based professional services. That matters for IT consulting firms answering public tenders: in those markets, quality usually carries real weight.
Few guides make this link between the rule and the writing. The three top-ranking pages on RFP evaluation criteria that we reviewed on 10 September 2026 (Responsive, Hudson Bid Writers and Fohlio) did not cite FAR 15.304 or Section M once.
What the contracting officer wants you to do first
Buyers say the same thing in public that the regulation says in writing: read the criteria. In an r/1102 thread for US federal contracting professionals, a new service-disabled veteran-owned small business asked what would make a contracting officer's job easier. One answer asked vendors to "actually read the attached documentation, stated evaluation criteria" before responding (thread, 30 August 2026).
Practitioners on the bid side describe the failure from the inside. Brad Brewington, writing on LinkedIn on 1 September 2026, described the day an RFP drops: "Color teams. War rooms. Pizza at 9pm. Everyone is finally 'doing BD.' They're not." (post). His point is that activity after the release is not the same as work on the buyer's problem.
Darrell Woodward added a different angle on 8 September 2026: proposal professionals are good at interpreting requirements to find the buyer's underlying needs (post). The two views fit together. The criteria tell you what gets scored. The underlying need tells you how to score well within them. Our reading is that teams lose when they skip the first and jump to the second.
In practice, reading the criteria first changes four habits:
- Use the buyer's numbering and headings, so each answer lands where the evaluator looks for it.
- Answer each subfactor explicitly, even when the answer is short.
- Replace general claims with evidence an evaluator can quote in their notes: a figure, a named project, a date.
- Cut material that answers no factor. It costs pages and scores nothing.
How to build your response around the scoring grid, step by step
Treat the published criteria as the outline of your response. The steps below turn a grid into a plan the whole team can follow.
- Copy the factors, subfactors and weights into one table, with the exact wording from the solicitation.
- Split your pages and your writing hours by weight. A factor worth 40% gets about 40% of both.
- Mirror the buyer's order and headings. The evaluator should find each factor where the solicitation lists it.
- Write to the rating definitions, if the solicitation gives them. If "exceeds" means a measurable benefit, state the measurable benefit.
- Attach evidence to each subfactor: a reference, a figure, a named project.
- Keep pass or fail items separate. Check them in a compliance matrix, not in the scored narrative.
Here is how step 2 looks for an illustrative solicitation with four weighted factors, a 25-page narrative limit and 80 hours of writing time. The weights are invented for this example.
The logic is simple, and it is often skipped under deadline. A thread on r/GovernmentContracting explaining federal best value makes the same point: "The relative weights tell you where to spend your proposal hours." (thread).
The table also exposes the usual mistake. Many responses spend their first pages on company history and generic capability, which maps to no factor in this example. Within a 25-page limit, three pages of history are three pages taken from technical approach, the factor worth 40%. The weights make that cost visible before anyone writes.
The hours in that table go further when the repeated material is not rewritten each time. Open, an IT services firm that answers public RFPs, reports a 50% reduction in its RFP response time after moving to Cobl (how Open answers public RFPs). Cobl starts each response with a bid evaluation and a go/no-go, then drafts the rest from the team's past bids, for people to review and adapt: see an RFP response built from your past bids, starting with the bid evaluation.
When the grid is hidden: private RFPs
Private buyers are not bound by FAR 15.305 or the EU directive. They may score on factors they never wrote down, such as a demo, a reference call or an existing relationship. You can still infer much of the grid from the document itself.
- Question order. Buyers tend to put what matters most first.
- Page and word limits. A section with a two-page limit and a section with a ten-page limit do not weigh the same.
- Mandatory and desirable labels. Mandatory items are the gate. Desirable items are where the ranking happens.
- The pricing template. A detailed price breakdown usually signals a price-sensitive evaluation.
Then ask in writing, during the clarification window. Useful questions are short and specific. How will responses be evaluated? What is the relative weight of price against the other criteria? Will shortlisted suppliers present, and does the presentation carry a score? Is there a minimum threshold on any criterion? Each answer either confirms your plan or tells you to change it. A buyer who will not answer has told you something too. If you cannot see where you would score, treat it as an input to your bid decision, not as a writing problem. Our go/no-go framework covers that call, and tools for bid managers shows how the evaluation feeds the rest of the response.
Scoring is changing: the EU quality floor and the UK small-supplier problem
Two public announcements in the week of 7 September 2026 point in the same direction: less weight on price alone, more attention to what the criteria exclude.
On 9 September 2026, the European Commission proposed a new public procurement regulation. It would make the best price-quality ratio the standard award method, with quality criteria worth at least 30% of the score, and at least 50% for labour-intensive contracts. Buyers could deviate if they explain how quality is otherwise ensured (Commission press release). This is a proposal, not law yet: the European Parliament and the Council still have to adopt it.
On 8 September 2026, the UK Competition and Markets Authority published two reports on public procurement, presented by its chief executive Sarah Cardell. Participants in its civil engineering research reported that bidding processes often demand extensive evidence of previous public infrastructure projects, which is hard for smaller suppliers to show and seen to favour incumbents (CMA report).
If the EU proposal is adopted, bidders used to price-led public tenders will need quality content that can be scored: method, risk management, social and environmental commitments, each backed by evidence. That content takes longer to write than a price schedule, and it is where a library of approved past answers saves the most time.
For bidders, the practical reading is the same in both markets. Read the pass or fail criteria before the scored ones, because they decide whether you compete at all. Then expect more of the score to sit in quality sections that someone on your team has to write and defend. Reading the grid, and deciding whether to bid on it, stays a human call.
