RFP Scoring Matrix: How to Lay Out Criteria, Weights and Scores

When the second-ranked offeror asks how the totals were reached

A grants manager sits across from a monitor who has the award file open. The monitor points to the second-ranked offeror and asks why it lost by 2.8 points. The manager has a spreadsheet with totals, but the formulas sit in cells nobody remembers editing. The weights on the tab also differ slightly from the weights printed in the RFP. Two evaluators' columns look suspiciously alike, and the reasoning behind the technical scores lives in a meeting nobody minuted.

Nothing here suggests the evaluation was careless. The matrix did what a matrix does: it multiplied and added. What it did not do is show how each number was reached, in what order, and under which rule.

This article lays out a clean RFP scoring matrix and the weighted-total arithmetic behind it. It also names the records that have to sit beside the matrix. By the end you will be able to build a layout that reproduces its own totals and say what the rest of the file must show.

The anatomy of an RFP scoring matrix

An RFP scoring matrix is a grid. Criteria run down the rows, and offerors run across the columns or sit on separate sheets. Each cell holds a rating, and a weight column converts ratings into points. Most spreadsheets and templates look like this, and the layout is sound. A weighted scoring model in Excel is a reasonable place to start.

A matrix that can be reconstructed later has six parts:

• Criterion name and description. Use the same wording as the solicitation.
• Weight. Weights must total 100 across all criteria, price included.
• Rating scale. State the minimum and maximum rating, such as 0 to 5.
• Rating definitions. Each point on the scale has a written meaning.
• Rating entered. This is the evaluator's raw score for the criterion.
• Weighted points. This is a formula, never a typed number.

The wording of the criteria and weights is not a matter of taste. Under 2 CFR 200.320(b)(2)(i), a solicitation using the proposals method must identify all evaluation factors and their relative importance. The matrix should therefore mirror the published factors exactly. If the RFP says technical approach carries 40 points, the matrix says 40. For help choosing and wording the factors themselves, see the guide to RFP evaluation criteria.

Place the weights in one clearly labeled column and have every formula refer to that column. When weights are typed into several formulas, they drift. A change made in one place is missed in another, and the totals stop matching the solicitation.

Calculating weighted totals: a worked example

The arithmetic is simple, which is why it is worth showing once in full. For each criterion, divide the rating by the maximum rating, then multiply by the weight. Add the results.

Worked example (illustrative numbers only). An evaluation uses four criteria with weights totaling 100, and a rating scale of 0 to 5. The three offers are priced at $100,000, $80,000 and $125,000.

Price is scored with the lowest-price formula: lowest evaluated price ÷ this offer's evaluated price × maximum price points. With 20 price points, Offeror B at $80,000 receives 20. Offeror A receives 80,000 ÷ 100,000 × 20 = 16. Offeror C receives 80,000 ÷ 125,000 × 20 = 12.8.

Criterion	Weight	A rating	B rating	C rating
Technical approach	40	4	3	5
Relevant experience	25	5	3	4
Staffing and management	15	3	4	4
Price (formula)	20	16 pts	20 pts	12.8 pts

Now the weighted points for Offeror A:

• Technical approach: 4 ÷ 5 × 40 = 32
• Relevant experience: 5 ÷ 5 × 25 = 25
• Staffing and management: 3 ÷ 5 × 15 = 9
• Price: 16
• Total: 82

Applying the same steps gives Offeror B a total of 24 + 15 + 12 + 20 = 71. Offeror C totals 40 + 20 + 12 + 12.8 = 84.8. Offeror C ranks first even though it has the highest price, because its technical rating was the highest and the price criterion carried only 20 points.

Notice what this example shows. Ranking is a deterministic result of weights, ratings and the price formula. If anyone asks why C ranked above A, the answer is a calculation anyone can repeat. The calculation does not explain why the technical ratings were 5 and 4, and that gap is covered below.

Record the price formula by name in the file and keep alternates and options out of the evaluated price unless the solicitation says they count. A longer treatment of price points sits in the guide to the RFP price scoring formula, and the logic of weights themselves is covered in weighted scoring for RFPs.

The RFP scoring rubric behind each cell

A rating of 4 means little unless everyone agrees what a 4 is. An RFP scoring rubric supplies that meaning. For each rating point on each criterion, it states in a sentence what a proposal must show to earn that rating. A short, generic scale is a start. Criterion-specific descriptions are better, because "meets requirements with minor gaps" reads differently for technical approach than for staffing.

Two habits make the rubric useful:

• Write the definitions before any proposal is opened. If the anchors are written after reading the proposals, they can drift toward a preferred offeror, or look as if they did.
• Use the same scale for every criterion where possible. A 0 to 5 scale on some rows and a 1 to 10 scale on others invites conversion errors in the totals.

Under 2 CFR 200.320(b)(2)(ii), an entity using the proposals method must have written procedures for conducting technical evaluations and making selections. The rubric is part of that written procedure in practice. If it is fixed in advance, it shows evaluators were working from the same definitions. For the mechanics of building and wording the scale, see the guide to rating scale definitions.

What a matrix cannot record

A well-built RFP evaluation scoring sheet answers one question: what is the total? The file has to answer several others. 2 CFR 200.318(i) requires records detailed enough to show the history of each procurement, including the rationale for the procurement method, contract type selection, contractor selection or rejection, and the basis for the contract price. A grid of numbers addresses only part of that. Here is what usually sits outside it.

Who scored, and when. Each evaluator should complete a separate sheet. In a shared workbook or emailed files, nothing technically prevents one evaluator from seeing another's scores first. That does not mean anyone did, but the file cannot show that no one did.

Conflict-of-interest attestations. 2 CFR 200.318(c) bars anyone with a real or apparent conflict of interest from taking part in selection or award of a contract supported by a federal award. The attestation belongs in the file, dated before the first score.

Disagreement between evaluators. A matrix totals scores, and the average can hide a wide spread on a single criterion. If one evaluator gave a 1 and another gave a 5, the consensus meeting should discuss that item. Otherwise it may be skipped, and the reason for the final score never gets written down.

The rationale for each final score. The number is the outcome. The sentence explaining it is what answers a debrief question or a monitor's visit.

Which version of the matrix applied. If weights or definitions change mid-evaluation, the file should show what changed, when, and why. A saved copy with a new date does not do that.

Under 2 CFR 200.318(k), the recipient or subrecipient is responsible for settling the contractual and administrative issues arising out of its procurements. "These issues include, but are not limited to, source evaluation, protests, disputes, and claims." That puts the issuer's own record at the center of any response. A matrix supports that record, but it is one part of it.

These limits are structural. They describe what a grid of cells can hold, and they say nothing against any particular template. A free state-office or consultancy template can be sound. The challenge is that independence, version history and rationale have to be handled by the people running the evaluation, and handled again for each solicitation.

Steps to take before the scoring round opens

Whatever tool you use, a short sequence helps the matrix hold up when someone reads it later.

1. Copy the factors and weights from the solicitation. Confirm they total 100 and match the published wording.
2. Write rating definitions for every point on every criterion. Date them and store them before proposals are opened.
3. Choose the price formula and the tie rule in advance. Record both in the file.
4. Collect conflict-of-interest attestations first. No evaluator scores until theirs is on file.
5. Have each evaluator score separately. Keep the sheets apart until all are submitted.
6. Set a flag for large spreads. Decide in advance what spread triggers discussion, such as two or more rating points on one criterion. This is an illustrative threshold, so set your own.
7. Record the rationale for each consensus score. Write it at the time, in a sentence or two.
8. Keep the full file for the required retention period. Under 2 CFR 200.334 the general rule is three years from the date the final financial report is submitted, subject to exceptions, and local public-records rules may require longer. Confirm yours with the awarding agency or pass-through entity.

RFPManagement is built around that sequence. Its evaluation workspace is designed to require weights that total 100 and anchored rating points before a round opens, keep independent scoresheets hidden until the round is locked, and require a rationale for each consensus score. Scoring is human-only, with no AI scoring or score suggestions, so the record stays a human record. If you want to hear when the workspace opens, join the waitlist.

If you would rather start with a workbook, the Criteria Builder is available in the store. It is designed to hold weighted criteria, check that weights total 100, and record the rating anchors for each criterion. Check the store page for current availability. If you are comparing spreadsheet options in the meantime, the guide to an RFP scoring template in Excel covers what to look for.

RFPManagement records and computes. It does not give legal or procurement advice. The award decision stays with your organization.