How RFP responses are scored: evaluation criteria from the respondent's side
Short answer: Most RFPs are scored with a weighted scoring matrix. The buyer lists evaluation criteria (for example functionality, approach, experience, price), gives each a weight, has evaluators rate each response against each criterion on a fixed scale, then multiplies ratings by weights and adds them up. Price is often converted to points with a formula that gives the lowest price full marks. As a respondent, your job is to make every criterion easy to score: answer in the order of the criteria, use their words, and put proof where the weight is.
In Iris: the RFP Analyzer extracts the scoring criteria and weights from the RFP, with citations, so you see where the points are before you write.
Who this is for: proposal managers, sales engineers and bid leads who want to write for the evaluator.
What are RFP evaluation criteria?
Evaluation criteria are the factors the buyer will use to compare responses, usually with their relative importance. Common ones:
| Criterion | What evaluators look for | Typical evidence |
|---|---|---|
| Functional / technical fit | Each requirement met, clearly | Requirement-by-requirement answers, demos |
| Approach and methodology | A credible plan for this buyer | Implementation plan, timeline, roles |
| Experience / past performance | Done this before, for similar buyers | Case examples, references |
| Team / key personnel | Qualified people assigned | Named roles, CVs |
| Risk / security | Low delivery and security risk | Security questionnaire, certifications held, policies |
| Price / cost | Value and affordability | Price form, assumptions |
| Commercial terms | Acceptable contract terms | Few or no exceptions |
In US federal procurement, the rules are explicit: price or cost "shall be evaluated in every source selection" (FAR 15.304(c)(1)(i)); the solicitation must state all factors and significant subfactors and their relative importance (FAR 15.304(d)); and it must say whether non-price factors combined are significantly more important than, approximately equal to, or significantly less important than price (FAR 15.304(e)). Federal evaluation factors appear in Section M.
How does weighted scoring work?
- Each criterion gets a weight (often percentages adding to 100).
- Evaluators give each response a rating per criterion on a fixed scale.
- Weighted score = rating ÷ maximum rating × weight, summed across criteria.
Common rating scales:
| Scale | Example levels |
|---|---|
| Numeric 0–5 | 0 not addressed · 1 poor · 2 marginal · 3 acceptable · 4 good · 5 excellent |
| Adjectival (common in federal) | Outstanding · Good · Acceptable · Marginal · Unacceptable |
| Pass/fail | Mandatory requirements; a fail can eliminate the bid |
How is price scored?
A widely used public-sector formula gives the lowest price full points and others a proportion:
Price points = (lowest price ÷ your price) × price weight
Some buyers use other methods (bands, or scoring against budget), and some evaluate price separately from technical scores. The RFP should say which.
Worked example: a scoring matrix for three bidders
A fictional city scores three bidders. Ratings are on a 0–5 scale; price uses the formula above.
| Criterion | Weight | Bidder A | Bidder B | Bidder C |
|---|---|---|---|---|
| Functionality | 35 | 4 → 28.0 | 5 → 35.0 | 3 → 21.0 |
| Implementation approach | 25 | 3 → 15.0 | 4 → 20.0 | 4 → 20.0 |
| Experience | 15 | 5 → 15.0 | 3 → 9.0 | 4 → 12.0 |
| Price | 25 | $100k → 25.0 | $125k → 20.0 | $110k → 22.7 |
| Total | 100 | 83.0 | 84.0 | 75.7 |
What this shows:
- Bidder B wins despite being 25% more expensive, because it scored highest on the heaviest non-price criterion.
- Bidder A lost by one point. One more rating point on implementation (worth 5 points) would have won it. That's usually a writing problem: a vague plan, not a weak one.
- Bidder C's lower price couldn't make up for weaker functionality.
Where should you spend effort?
| If the RFP says… | Then… |
|---|---|
| Non-price factors significantly more important than price | Invest in proof, approach and experience; don't over-discount |
| Price and non-price approximately equal | Balance; sharpen price and make the strongest criterion unmistakable |
| Lowest price technically acceptable (LPTA) | Meet every requirement clearly; no credit for exceeding them; compete on price |
| Pass/fail mandatory requirements | Confirm each one explicitly; one miss can disqualify |
| Oral presentation scored | Rehearse; the written proposal is only part of the score |
How do you write a response that's easy to score?
- Mirror the criteria. Organize sections in the order of the evaluation criteria and use their headings.
- Answer the requirement in the first sentence, then prove it. Evaluators skim for "Yes, and here's how."
- Make compliance visible. A compliance matrix shows where each requirement is answered.
- Use their vocabulary. If the RFP says "service desk", don't write "help desk."
- Quantify carefully. Real, attributable numbers beat adjectives; never invent them.
- Remove friction. Page limits, fonts, file names and forms matter; non-compliance can cost points or the bid.
- Ask for a debrief after award, win or lose, to learn how you were scored.
Pre-submission scoring self-check
- [ ] Every evaluation criterion has a clearly labelled section
- [ ] Highest-weighted criteria get the strongest proof
- [ ] Every mandatory requirement is answered "Yes/Comply" or explained
- [ ] Price follows the required form and states assumptions
- [ ] An independent reviewer scored a draft against the criteria
- [ ] No unexplained exceptions to terms
How Iris helps you write to the score
- See the scoring before you start. The RFP Analyzer returns the summary, key dates, contacts, scoring criteria and requirements, each cited to the RFP.
- Check fit requirement by requirement: met, partial or likely not met, with the sources from your Knowledge Map.
- Qualify against your own criteria. Your go/no-go red and green flags and weights roll up to a qualification percentage and a Go, Review or No-Go recommendation.
- Draft from approved content with citations and confidence labels, so reviewers spend time on the high-weight sections.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.
FAQ
What is RFP scoring?
The method a buyer uses to rate and compare responses, usually a weighted matrix of criteria, ratings and price points.
What are the most common RFP evaluation criteria?
Functional fit, approach, experience, team, risk and security, price and commercial terms.
How much does price usually count?
It varies by RFP. The weight or relative importance should be stated; in US federal procurement it must be (FAR 15.304(d)–(e)).
Can we see the buyer's scoring matrix?
Often the criteria and weights are in the RFP; the detailed rubric may not be. Ask during the questions period.
What's the difference between RFP scoring and a go/no-go scorecard?
RFP scoring is the buyer rating you; a go/no-go scorecard is you deciding whether to bid.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
