How to Document an RFP Evaluation So the File Shows How the Ranking Was Reached

Why a folder of loose files rarely rebuilds the history

Picture a grants manager three weeks before a monitoring visit. The reviewer has asked a plain question: why did the second-ranked offeror lose? The manager opens the procurement folder and finds a scoring spreadsheet, six emailed scoresheets, a Word document of meeting minutes and a draft memo. Two of the scoresheets have no dates. The spreadsheet was edited after the meeting, and nothing shows by whom.

None of these files is wrong. The trouble is that together they cannot say what happened, in what order, and under which rules. The scores exist, but the reasoning that turned them into a ranking lives in people's memories. The memories are fading, and one evaluator has since left the organization.

This article walks through the pieces an evaluation file should hold and the order in which to capture them. By the end you should be able to check your own file against the federal record requirement and see where a gap would appear.

What 2 CFR 200.318(i) asks the file to show

The federal standard is short. Under 2 CFR 200.318(i), a recipient or subrecipient must keep records detailed enough to show the history of each procurement. Those records must include four elements: the rationale for the procurement method, the contract type selection, the contractor selection or rejection, and the basis for the contract price. Confirm the current text on eCFR, which describes itself as authoritative but unofficial.

Two points follow from that wording. First, the standard asks for history, not a final summary. A memo that announces the winner does not show how the evaluation unfolded. Second, "selection or rejection" means the file should explain why each unsuccessful offeror was not chosen, not only why the winner was.

Related provisions shape what belongs in the file. Under 2 CFR 200.320(b)(2)(i), a request for proposals must identify all evaluation factors and their relative importance. 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. Under 2 CFR 200.318(c), no employee, officer, agent or board member with a real or apparent conflict of interest may take part in the selection, award or administration of a contract supported by the federal award.

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." In practice that means your own record is the first thing anyone will read. A longer treatment of the section is in our guide to 2 CFR 200.318 procurement records.

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

Document the method and the rules before the first proposal arrives

The file should begin with decisions made before any offer is opened. These are the items a reviewer cannot reconstruct afterward, because the point is that they were fixed in advance.

Method and rule in force

Record which procurement method you chose and why. For an RFP, that means stating that competitive proposals fit the purchase and noting the funding source. Then record which rule you applied and its effective date. Thresholds move, and the Uniform Guidance was substantially revised effective October 1, 2024 (89 FR 30046). A file that does not record the rule and its date cannot show which rule it followed at the time.

Criteria, weights and rating anchors

Record every evaluation factor, its weight and the relative importance stated in the solicitation. A common mechanic is weights that total 100. Add the rating definitions for each point on the scale, written before anyone scores. If "4" means "meets the requirement with minor gaps," that sentence belongs in the file, dated before the round opened.

Why anchors matter: without them, two evaluators can give the same score for different reasons, and a consensus meeting cannot tell whether a spread is real disagreement or different private scales.

Tie rule and responsiveness approach

Record how ties will be resolved and how non-responsive proposals will be handled. Both should be set before scoring. A tie rule chosen after the totals are known looks like a choice made to reach a result.

Independent estimate, where it applies

Under a federal award, 2 CFR 200.324(a) requires a cost or price analysis for every procurement transaction above the simplified acquisition threshold, and independent estimates must be made before receiving bids or proposals. The regulation does not define "independent," but in practice the estimate need not come from a third party; it should be built without input from anyone with a financial stake in the award. Date it and keep it with the file. A date after the proposals arrived undermines the point.

Capture who evaluated, and what each person attested

Next, record the evaluators. List each person, their role (scoring or advisory) and the date they were invited. Keep the conflict-of-interest attestation for each, signed or confirmed before that person scored anything. An attestation collected after scoring starts does not show that the person was free of conflict when they scored.

Record any evaluator who withdrew or was replaced, and why. A committee that began with five members and ended with four invites a question. A line in the file answers it before it is asked.

Also note the instructions evaluators received: how to score independently, that scores were not to be shared before submission, and what to do with questions. Independence is easy to claim and hard to show. In emailed scoresheets or a shared spreadsheet, nothing technically stops one person from seeing another's numbers. An accusation of anchoring, where one evaluator's scores influenced another's, is a recognized protest argument, so the file should show how independence was handled and not only assert it.

Record scores, spreads and the consensus rationale

This is the stage where most files thin out. Individual scoresheets exist, but the step from individual scores to a final score is not written down.

Individual scores

Keep each evaluator's scoresheet as submitted, with the submission time. Keep comments tied to each criterion. A score of 2 with a comment explaining the gap is far more useful than a bare number.

Spreads worth discussing

When evaluators differ widely on a criterion, that is where the consensus meeting should spend its time. Decide in advance what counts as a large spread, and record which criteria crossed the line. Flags like these are informational. They point the committee toward discussion and do not change any score. Our piece on consensus scoring for RFPs goes through how to run that meeting.

The rationale for each final score

For every criterion and every proposal, record the final score and a sentence or two on why. "Final score 3: committee agreed the staffing plan covered the stated scope but did not name a transition lead." That sentence is what answers the monitor's question about the second-ranked offeror. Without it, the final numbers float free of any reasoning.

If the committee changes a score from an individual evaluator's, say so and say why. Changes are normal. Unexplained changes are what cause trouble.

Show the price basis and the ranking arithmetic

The fourth element of 200.318(i) is the basis for the contract price. Your file should show how price entered the evaluation.

Record the bids as received, with the formula used to convert price into points. A common lowest-price formula is: lowest evaluated price ÷ this offer's evaluated price × maximum price points.

Worked example (round numbers for illustration only): three offers at $80,000, $100,000 and $125,000, with 30 price points available. The first earns 30 points. The second earns 80,000 ÷ 100,000 × 30 = 24 points. The third earns 80,000 ÷ 125,000 × 30 = 19.2 points. Record the formula, the inputs and the results, so a reader can recompute them.

Note which components went into the evaluated price. If alternates or options were excluded, say so, and say that this was stated in the solicitation. Mixing optional items into the evaluated price for some offerors and not others is a common source of error.

Then record the combined ranking: technical points plus price points, with the tie rule shown if it was used. Treat the arithmetic as something a second person could repeat from the file and get the same ranking.

Two cautions. Under 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." And price is excluded as a selection factor only for architectural and engineering services under 2 CFR 200.320(b)(2)(iv); for other RFPs, the file should show how price was weighed.

Why an append-only record matters, and how the memo fits in

Everything above can be captured in a spreadsheet and a folder. The difficulty is sequence and change. A spreadsheet can be edited after the fact with no trace, and a folder shows file dates that may reflect copying rather than creation.

An append-only record addresses this. Each entry is added to the end, earlier entries cannot be silently altered, and the order of events is preserved. A hash-chained audit trail goes one step further, linking each entry to the one before so that tampering becomes detectable. Whatever tool you use, the principle is the same: the file should be able to show not only what was decided but when, and that it was not rewritten afterward.

The award memo then summarizes the record; it does not replace it. The memo states the selection, points to the ranking and records the basis for the decision. Our guide to the award memo and selection memo covers its contents. For a broader inventory, see the procurement file documentation checklist.

Retention is part of documentation too. 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. If a protest or dispute arises, the procedure comes from your own policy and state or local law, not from the federal text; our overview of bid protest procedure for local government explains why that is a question for your own policy.

For context on the stakes, federal agency procurements show where evaluations get challenged. In its bid protest annual report for fiscal year 2025 (GAO-26-900695), GAO identified the most common sustain grounds as unreasonable technical evaluation, unreasonable cost or price evaluation, and unreasonable rejection of a proposal. Those figures describe federal agency procurements, not grant-recipient or local ones, but the same three areas are the ones a good file documents.

A short sequence to follow on your next RFP

1. Before release: record the method, the rule and its effective date, the criteria, weights, anchors, tie rule and independent estimate.
2. Before scoring: collect conflict attestations and record the evaluator roster and instructions.
3. During scoring: keep each scoresheet as submitted, time-stamped.
4. At consensus: record the final score and rationale for each criterion and proposal.
5. At tabulation: record bids, formula, inputs and ranking arithmetic.
6. At award: write the memo, then archive the whole file for the retention period.

The Award Documentation Kit is designed to hold award-stage items such as conflict-of-interest attestations, the selection memo inputs and debrief and protest-file checklists, with Word forms for the attestation, selection memo and debrief letter. It is available in the store now. RFPManagement is being built as a workspace for the evaluation stage. It is designed to keep scoring human-only, set criteria and anchors before a round opens, hide scores until the round is locked, and keep an append-only audit trail with a ZIP export of the file. To hear when it opens, join the waitlist. Plan details will be on the pricing page.

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