RFP Evaluation in Government: The Complete Guide to a Defensible Record

When a monitor asks why the second-ranked offeror lost

A finance manager at a grant-funded nonprofit is three weeks from a monitoring visit. The monitor has pulled one procurement from last year, a program evaluation contract awarded through a competitive RFP. She asks a plain question: why did the second-ranked offeror lose?

The manager remembers the committee meeting and the general mood in the room. What she finds in the folder is a scoresheet workbook with several tabs, a Word document of minutes and an award email. The weights in the workbook add up to 105. One evaluator's sheet carries no date. The minutes say the committee "reached consensus" but do not say on what grounds.

None of this means the award was wrong. It means the file cannot yet show how the ranking was reached, and that is what a reviewer is really asking. This guide walks through the evaluation stage of a competitive-proposal RFP, from criteria to award file. At each step it names what the record should hold, so that by the end you can look at your own file and say which of those things it shows.

What 2 CFR 200.318 asks the file to show

Most small organizations meet this subject through 2 CFR Part 200, the federal rules for spending award money. The Office of Management and Budget published a substantial revision on April 22, 2024 (89 FR 30046), now titled the OMB Guidance for Federal Financial Assistance. It took effect October 1, 2024. Federal agencies could apply it to awards made before that date but were not required to, so the version that governs a given award depends on its terms.

The section numbers in this guide come from the current eCFR, which describes itself as authoritative but unofficial. The official edition is the annual CFR on govinfo.gov. Confirm the current text of each section on eCFR before you write it into your own procedures.

Several provisions shape what an evaluation file should hold. Read together, they describe a record more than a method:

• 2 CFR 200.318(a) requires documented procurement procedures, consistent with state, local and tribal law and with 2 CFR 200.317–200.327.
• 2 CFR 200.318(c) bars any employee, officer, agent or board member with a real or apparent conflict of interest from taking part in the selection, award or administration of a contract supported by the federal award.
• 2 CFR 200.318(i) requires records detailed enough to show the history of each procurement. They must include the rationale for the procurement method, the contract type selection, the contractor selection or rejection, and the basis for the contract price.
• 2 CFR 200.318(k) makes the recipient or subrecipient responsible for settling the contractual and administrative issues that arise from its procurements.
• 2 CFR 200.320(b)(2)(i) requires an RFP to be publicly noticed, to identify all evaluation factors and their relative importance, and to be solicited from multiple qualified entities.
• 2 CFR 200.320(b)(2)(ii) requires written procedures for conducting technical evaluations and making selections.
• 2 CFR 200.324(a) requires a cost or price analysis for every procurement transaction in excess of the simplified acquisition threshold, with independent estimates made before bids or proposals are received.

The award itself is set by 2 CFR 200.320(b)(2)(iii): contracts "must be awarded to the responsible offeror whose proposal is most advantageous to the recipient or subrecipient considering price and other factors."

Notice what the rules do not do. They do not prescribe a scoring formula, a committee size or a spreadsheet layout. They ask that the file be able to show what happened and why. Sections 200.318(i) and (k) together make a useful test for any evaluation file: could someone who was not in the room reconstruct the history from the record alone?

State and local codes may be stricter than the federal rules. When both apply, follow the stricter one, and confirm how each applies to your award with your awarding agency or pass-through entity.

The RFP evaluation process government offices follow, step by step

The RFP evaluation process government agencies and grant recipients run is easier to manage as a sequence of records than as a single event. Each step below ends with what the file should hold. The steps are written for the evaluation stage only. Drafting the solicitation, publishing it and receiving proposals happen elsewhere, and this guide assumes those are done.

Step 1: Record the method and the reason for it

Section 200.320 sets out three types of procurement method: informal (micro-purchases and simplified acquisitions), formal (sealed bids or proposals) and noncompetitive. Sealed bids go to the responsible bidder whose conforming bid is lowest in price, and they are preferred for construction services. Proposals are the method where qualitative factors are weighed alongside price.

One exception matters here. Under 2 CFR 200.320(b)(2)(iv), a method where price is not a selection factor, in which the most qualified offeror is chosen and compensation is then negotiated, can only be used for architectural and engineering professional services. The Brooks Act (40 U.S.C. 1101–1104) sets a similar qualifications-based approach for federal agencies' own A/E contracts; a grant recipient follows 200.320(b)(2)(iv). Many states have their own qualifications-based selection statutes, so check your state's law.

What the file should hold: a short written statement of why proposals were the right method for this purchase, which is the first element 200.318(i) names. Add the rule version you relied on and its effective date. A file that records only the method cannot show which rule it followed at the time.

Step 2: Fix the criteria, weights and anchors before release

Section 200.320(b)(2)(i) requires the solicitation to identify all evaluation factors and their relative importance. In practice, that means weights, and the weights should total 100. A worked example for a program evaluation contract:

Criterion	Weight
Technical approach	40
Staff qualifications	25
Past performance	15
Price	20
Total	100

Weights say how much each criterion counts. They do not say what a good answer looks like. For that you need rating anchors: a written definition of every point on the rating scale. On a five-point scale, a 5 might mean the proposal addresses every requirement and adds a documented, relevant approach, while a 3 means it meets the requirements without added detail. The wording matters less than the timing. Anchors written after the proposals arrive look like anchors written to reach a result.

A weighted score then follows from simple arithmetic. A rating of 4 on a five-point scale for a criterion weighted 40 yields 4 ÷ 5 × 40 = 32 points. This is a worked example with round numbers, not a recommended scale.

Evaluators should score only against the factors the solicitation disclosed. A factor that never appeared in the RFP is very hard to defend later. For more on building criteria that survive scrutiny, see how to write RFP evaluation criteria.

What the file should hold: the criteria, weights and anchors exactly as released, with the date. If an addendum changes them, keep both versions and the date of the change.

Step 3: Seat the evaluators and collect conflict attestations

Section 200.318(c) bars a person with a real or apparent conflict from taking part in the selection. Section 200.318 also requires written standards of conduct covering conflicts of interest. The practical consequence is that each evaluator should attest in writing, before reading any proposal, that no conflict exists. The attestation should say what to do if one emerges mid-evaluation.

Decide each person's role at the outset. A scoring evaluator submits scores that count toward the ranking. An advisory participant, such as a subject-matter expert or a legal reviewer, may answer questions without scoring. Mixing those roles quietly is a common source of confusion later.

What the file should hold: the evaluator list with names, titles and roles, each signed or dated attestation, and a note of anyone who recused and why. The attestation date should precede the first score.

Step 4: Score independently and keep the sheets sealed

Each scoring evaluator reads the proposals alone and scores every criterion against the anchors, with a short written note for each score. Independence matters because a first score spoken aloud or visible in a shared file pulls the others toward it. Even if no anchoring occurs, an accusation of anchoring becomes a protest argument that the file has to answer.

Here the common tools show a structural limit. In a shared spreadsheet or in emailed scoresheets, nothing technically stops one evaluator from seeing another's numbers before everyone has submitted. The file then rests on a statement that people did not look, which is a claim rather than a record.

The way to turn the claim into a record is to control visibility and keep timestamps. RFPManagement, for example, is built to keep each evaluator's scoresheet hidden until the round is locked, and the lock cannot be reversed. All scoring in it is done by people. There is no AI scoring and no score suggestions, which keeps the record a human one. Whatever method you use, the aim is the same: submission times and a lock time that show scores were independent.

What the file should hold: each evaluator's completed scoresheet with notes, the submission time for each, and the time scoring closed.

Step 5: Look at disagreement, then reach consensus with reasons

Once the sheets are open, compare them criterion by criterion. Where evaluators scored the same proposal on the same criterion several points apart, something needs discussion. Perhaps they read different parts of the proposal, or they interpreted an anchor differently. Perhaps one of them missed something. Start the consensus meeting with the largest spreads rather than the easy items. Where software flags spreads, those flags should be informational only. They point the committee at items to discuss and never change a score.

Consensus means the committee settles on a final score for each criterion and writes down why. Some solicitations instead average the individual scores, which is also legitimate if the written evaluation procedures say so, as 200.320(b)(2)(ii) contemplates. What matters is that the method matches what the procedures describe and that the file shows it was followed. For a closer look at running the meeting, see consensus scoring for RFP evaluation.

The rationale for each final score is the part most often missing. Minutes that say "the committee agreed" do not show why Offeror B received a 3 on technical approach when two evaluators gave it a 4. A sentence or two per criterion does.

What the file should hold: the final score for each criterion for each proposal, a written rationale for each, the attendees, and a note of any score that moved from the individual round and why.

Step 6: Check responsiveness and settle ties by rule

Before ranking, confirm that each proposal meets the solicitation's minimum requirements: required forms, certifications and submission instructions. A per-proposal responsiveness checklist, completed and dated, shows which proposals were set aside and for what reason. Rejection of a proposal is one of the places records get challenged, so the reason for each exclusion should be written down.

Settle the tie rule before scoring starts. A tie rule chosen after the totals are known looks like a choice made to produce an outcome. A simple rule, such as higher technical score first, then the next criterion in weight order, written into the evaluation procedures, removes the problem.

What the file should hold: the responsiveness checklist for every proposal, the tie rule and the date it was set, and the final ranking computed by the stated formula.

Price scoring and the independent estimate

Price is a scored factor in most proposal evaluations. The exception is the A/E qualifications-based method described above. The scoring method should be stated in the solicitation and applied the same way to every offer.

A common method is the lowest-price formula: the lowest evaluated price, divided by this offer's evaluated price, multiplied by the maximum price points. Here is a worked example. Three offers come in at $80,000, $100,000 and $125,000, with 30 price points available:

• $80,000 ÷ $80,000 × 30 = 30 points
• $80,000 ÷ $100,000 × 30 = 24 points
• $80,000 ÷ $125,000 × 30 = 19.2 points

Some offices use a points-per-dollar approach instead. Either way, name the method in the solicitation and record the computation.

The harder question is what counts as the evaluated price. Alternates and options may be priced in the proposal, but whether they are included in the number being compared should be decided in advance and applied evenly. Hand-built formulas drift between solicitations, which is one reason to keep the tabulation in a stable, reviewed format. The bid tabulation guide covers layout and exclusions in more detail.

Section 200.324(a) adds a separate duty above the simplified acquisition threshold. The recipient must perform a cost or price analysis for every procurement transaction above that threshold, including contract modifications. Independent estimates must be made before receiving bids or proposals. The timing is the point: an estimate written after the prices are in is not independent of them.

The regulation does not define "independent," but the word points the same way. The estimate need not come from a third party. It should be built without input from anyone with a financial stake in the award, and it should not rest solely on prospective vendors' pricing. For a fuller treatment, see the independent cost estimate under 2 CFR 200.324.

What the file should hold: the independent estimate with its date and basis, the price method as stated in the solicitation, the list of any alternates or options excluded and why, and the computed price points for each offer. The price analysis feeds directly into the fourth element of 200.318(i), the basis for the contract price.

Assembling the award file and preparing for a protest

After ranking, people make the award decision. A tool or spreadsheet can compute the ranking, but the decision belongs to the organization, and the file should say who made it and when. An award memo or selection memo is the usual vehicle. It should state the criteria and weights, the final ranking, the reasons the selected offeror was chosen, the price basis, and any rejected proposals with the reasons.

Retention comes next. Under 2 CFR 200.334, records are generally kept for three years from the date the final financial report is submitted, unless an exception applies, such as a written notice extending the period. Local public-records rules may require longer, so check yours.

Then there is the question of challenges. Section 200.318(k) makes the recipient or subrecipient responsible for settling the contractual and administrative issues arising out of its procurements, and the regulation names them:

"These issues include, but are not limited to, source evaluation, protests, disputes, and claims."

Because the recipient or subrecipient settles those issues, its own record is its defense. The federal text does not prescribe a protest procedure or a debrief, so those come from your own written procedures, state and local law and your award terms. Find out what yours say before you need them.

For a sense of where evaluation records come under challenge, the GAO's Bid Protest Annual Report for fiscal year 2025 (GAO-26-900695, December 12, 2025) lists the most common grounds on which protests were sustained. They were unreasonable technical evaluation, unreasonable cost or price evaluation, and unreasonable rejection of a proposal. These findings cover federal agency procurements only, not grant-recipient or local procurements. They are useful here because each ground maps to a record described above:

• A technical evaluation is supported by anchors fixed in advance and a written rationale for each final score.
• A cost or price evaluation is supported by the stated formula, the independent estimate and the documented treatment of alternates.
• A rejection is supported by a responsiveness checklist with reasons.

A record like that supports a response. It does not make any evaluation protest-proof, and it cannot substitute for sound judgment during scoring.

What the award file should hold, in order:

1. The method rationale and rule version.
2. The released solicitation with criteria, weights and anchors.
3. Evaluator list, roles and conflict attestations.
4. Individual scoresheets with submission times.
5. Consensus record with rationale for each final score.
6. Responsiveness checklists and the tie rule.
7. The independent estimate, price tabulation and price analysis.
8. The award memo and the human-entered decision.

For the full list of what 200.318(i) expects, see procurement records under 2 CFR 200.318.

Rules change, so record which rule applied

Thresholds and rules move. A file built under one version can be reviewed under another, which is why each file should record the rule it followed and the date that rule took effect.

Three changes affect many small organizations right now.

First, the 2024 revision described above took effect October 1, 2024, and your award terms tell you whether it governs an older award. It also changed some terms. For example, "simplified acquisition" now describes the informal method above the micro-purchase threshold and below the simplified acquisition threshold, replacing "small purchase."

Second, the FAR Council raised two thresholds. In FAR Case 2024-001 (90 FR 41872, August 27, 2025), the micro-purchase threshold rose from $10,000 to $15,000, and the simplified acquisition threshold rose from $250,000 to $350,000, both effective October 1, 2025. If you hold an award made before that date, ask your awarding agency or pass-through entity which figure applies to it. A written procurement policy that still cites the old figures may look out of date. Under 2 CFR 200.320(a)(2)(ii), an entity's own simplified acquisition threshold may be lower than the FAR figure but must not exceed it. A local or state threshold may be lower still, and your procedures must be consistent with state and local law as well as the federal rules.

Third, a further rewrite has been proposed. On May 29, 2026, OMB published a proposed rule, "Regulation for Federal Financial Assistance" (91 FR 32198), that would revise 2 CFR Part 200 again. As of October 2026 it is proposed, not final; check federalregister.gov for its current status before you change any procedure.

School districts and libraries using E-Rate funds have a different weighting rule. Under 47 CFR 54.503, price must be the primary factor, and the applicant selects the most cost-effective offering. Documents must be kept for at least 10 years under 47 CFR 54.516(a)(1). The FCC has also adopted a requirement, starting in funding year 2028, for bids to go through a USAC-managed bidding portal and for applicants to upload their bid evaluation and vendor selection documents. As of the May 19, 2026 Federal Register notice, confirm the current USAC schedule. A district also still follows its state and local procurement rules.

What to do before your next solicitation

You do not need new software to improve a file. These steps cost only time and can be done before the next RFP is released:

1. Write down the procurement method and the reason for it, with the rule version and effective date.
2. Fix weights that total 100, and define every rating point before the solicitation goes out.
3. Collect conflict attestations before any evaluator opens a proposal.
4. Decide how scoresheets will stay private until all evaluators have submitted.
5. Write the independent estimate before proposals arrive, and date it.
6. State the price formula and the treatment of alternates and options in the solicitation.
7. Set the tie rule in writing before scoring.
8. Require a written rationale for every final consensus score.

If you want the pieces in one place, the RFP Evaluation Complete Kit is a store listing for a set of workbooks designed to record criteria and anchors, scoring and consensus, bid tabulation and award documentation. It is available in the store now. If you would like to hear when the evaluation workspace opens, you can join the waitlist. Plans and pricing will be on the pricing page when they are published.

Before you adopt any of this, check your own written procedures, your state and local requirements and the terms of your award. Your awarding agency, pass-through entity or counsel can tell you how a rule applies to you.

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