How to Write RFP Evaluation Criteria That Actually Work
The single biggest predictor of getting comparable proposals is clearly written evaluation criteria. Most buyers copy last year's template. Here's how to write criteria that work.
Evaluation criteria serve two audiences simultaneously: vendors deciding how to write their proposals, and evaluators deciding how to score them. Most criteria fail both audiences because they're written for neither — they're written to satisfy an internal compliance requirement, copied from a previous RFP, and published without anyone asking whether they actually describe how selection will happen.
Good evaluation criteria are operational. They tell vendors exactly what to demonstrate and tell evaluators exactly what to look for. When criteria are specific, proposals are better, scoring is faster, and award decisions are easier to defend.
The Structure of Effective Evaluation Criteria
Every evaluation factor needs three components:
1. The factor name and weight
E.g., “Technical Approach — 35%”. The weight tells vendors where to invest proposal effort. Publishing weights is not optional — hidden weights produce misaligned proposals.
2. What the factor evaluates
Specific enough that vendors know what to write and evaluators know what to look for. Not “technical capability” — “demonstrated ability to implement cloud-based data integrations for organizations processing 500GB+ per day, with specific methodology described for the current scope.”
3. Rating definitions
What does an Outstanding / Acceptable / Marginal / Unacceptable response to this factor look like? Rating definitions are frequently omitted and consistently produce inconsistent scoring across evaluators.
Weighting Frameworks That Work
Weights should reflect your actual decision logic, not a template. Three common frameworks:
Best Value: Technical Emphasis
Use when quality and approach differentiate vendors more than price. Typical for complex implementations, professional services, or situations where execution risk is high.
| Technical Approach | 40% |
| Past Performance | 30% |
| Team Qualifications | 20% |
| Price | 10% |
Best Value: Balanced
Use when price and quality are both genuinely important and you want proposals that compete on both dimensions.
| Technical Approach | 35% |
| Past Performance | 25% |
| Price | 30% |
| Team Qualifications | 10% |
Lowest Price Technically Acceptable (LPTA)
Use when the requirements are fully defined and execution risk is low. Technical factors are pass/fail; award goes to the lowest price among technically acceptable proposals.
| Technical Acceptability | Pass/Fail |
| Past Performance Acceptability | Pass/Fail |
| Price | Evaluated (lowest wins) |
Writing Rating Definitions
Rating definitions are the element most frequently missing from RFP evaluation sections, and the one that most affects scoring consistency. Without them, two evaluators reading the same proposal will score it differently because they're applying different implicit standards.
A standard five-point scale with definitions:
| Rating | Definition |
|---|---|
| Outstanding | Proposal exceeds requirements with specific, credible, and low-risk methods. Contains significant strengths that benefit the buyer. No deficiencies or significant weaknesses. |
| Good | Proposal meets requirements with some strengths. No significant weaknesses or deficiencies. |
| Acceptable | Proposal meets requirements. Strengths and weaknesses balance. No deficiencies. |
| Marginal | Proposal fails to meet some requirements. Has weaknesses that may be correctable. No fatal deficiencies. |
| Unacceptable | Proposal has one or more deficiencies. Fails to meet requirements in material ways. Non-recoverable. |
Qualitative vs. Quantitative Criteria
A common mistake is trying to make all criteria quantitative (scoring on a numeric scale) in the belief that it makes evaluation more objective. Quantitative scoring of qualitative criteria creates false precision — a score of 87 vs. 84 on “technical approach quality” isn't meaningfully more objective than “Outstanding vs. Good.”
- Price: Always evaluate quantitatively. Lowest cost = highest score, scaled.
- Past performance: Evaluate qualitatively (Outstanding / Acceptable / etc.) against the reference criteria, not a number.
- Technical approach: Qualitative rating with narrative justification from evaluators. More defensible than numeric scores.
- Team qualifications: Can be semi-quantitative — years of experience and certifications are objective; approach to staffing is qualitative.
Legal Defensibility
For government procurement, evaluation criteria are the primary basis of protest defenses. For commercial procurement, they're important for procurement integrity and internal accountability. In both cases, the same principles apply:
- Publish criteria before proposals are received — never add or change factors after submission
- Evaluate all proposals against the same criteria in the same way
- Document evaluator scores and rationale for each factor
- If you add non-price factors, weight them in a way you can defend as proportionate to their actual importance to the award decision
- Never apply criteria inconsistently across offerors
Extract evaluation criteria from any RFP instantly
RFParse reads solicitations and returns structured evaluation criteria — factors, weights, and rating definitions — so proposal teams can align their response to exactly what evaluators will score.
See RFParse →