The RFP Award Memo: How to Write a Selection Memo That Shows Your Reasoning

Why the award memo is the document people read first

Picture a grants manager at a nonprofit whose funder has scheduled a monitoring visit. The monitor opens the procurement folder for a consulting contract and asks a simple question: why did the second-ranked offeror lose? The scoresheets are in one folder, the consensus notes are in a Word document, and the price comparison sits in a spreadsheet tab nobody has opened since the award. The memo that was supposed to tie them together is a two-paragraph email saying the committee "selected the best proposal."

That memo is the first page a monitor, auditor, board member or unsuccessful offeror will read. If it points clearly to the evidence behind it, the rest of the file gets read as support. If it does not, the reader has to reconstruct the reasoning alone.

This article covers what an award memo, also called a selection memo, should contain, how each statement should trace to the evaluation record, and which claims it should leave out.

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

Under a federal award, 2 CFR 200.318(i) requires procurement records detailed enough to show the history of each procurement. That history includes four elements: the rationale for the procurement method, the contract type selection, the selection or rejection of the contractor, and the basis for the contract price. Confirm the current text on eCFR before you rely on this summary.

The award memo is the natural place to gather the last two elements in one readable page. It states why the selected offeror was chosen, why others were not, and how the price was judged. It does not replace the underlying records. It points to them.

The award standard for a proposals-based procurement is in 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." The memo should use that language as its test and then show how the evaluation applied it.

If the procurement used qualifications-based selection for architectural or engineering services, 2 CFR 200.320(b)(2)(iv) allows price to be left out of the selection, with compensation negotiated afterward. In that case the memo should say so and record the negotiation basis. For every other proposal procurement, the memo should address price.

Two caveats apply. State and local rules may impose additional memo or notice requirements, and the stricter rule governs when both apply. Check your own policy and, for federal awards, confirm questions with the awarding agency or pass-through entity.

The sections an award memo should contain

A good memo is short, usually one to three pages, and organized so a reader can verify each statement. A workable outline follows.

Identification and authority

State the solicitation title and number, the issuing organization, the funding source, and the procurement method used. Name the written procedure or policy the evaluation followed. Record which version of that procedure was in force, with its effective date, so a later reader can see which rule applied at the time.

The criteria and their weights

List every evaluation factor and its relative importance as they appeared in the solicitation. Under 2 CFR 200.320(b)(2)(i), the RFP must identify all evaluation factors and their relative importance. The memo should match the solicitation exactly. If the memo describes weights that differ from what offerors saw, that mismatch becomes the story.

Who evaluated, and how

Name the evaluators and their roles. State that each completed a conflict-of-interest attestation before scoring, which connects to the requirement in 2 CFR 200.318(c) that no one with a real or apparent conflict take part in selection or award. Note whether any advisors were non-scoring. Describe the sequence: independent scoring first, then a consensus discussion.

The ranking and the reasoning

Present the final ranked results, with weighted scores for each responsive offeror. Then give the rationale for the selected offeror in terms of the criteria, not general praise. A sentence such as "Offeror B received higher consensus scores on technical approach because its staffing plan identified named personnel for each task, which the anchored rating definition required for the top rating" shows reasoning. A sentence such as "Offeror B was the strongest team" does not.

Explain, briefly, why the next-ranked offerors scored lower on the criteria where they differed. This is the answer the monitor in the opening scenario was asking for.

The price basis

State how price was evaluated and what the selected price was compared against. If the procurement transaction was in excess of the simplified acquisition threshold under a federal award, 2 CFR 200.324(a) requires a cost or price analysis, and independent estimates must be made before receiving bids or proposals. The memo should reference that estimate by date and show it predates receipt of proposals.

A worked example of a lowest-price formula shows what to record. Suppose a procurement assigns 30 points to price, and three offers come in at $80,000, $100,000 and $125,000. The formula is lowest evaluated price divided by this offer's evaluated price, multiplied by the maximum price points. The results are 30, 24 and 19.2 points. The memo should state the formula, the points available and each offer's price points. If alternates or options were excluded from the evaluated price, say so.

Responsiveness and exclusions

Record any proposals that were found non-responsive, the reason, and who determined it. Exclusions made quietly are harder to defend than exclusions made in writing.

The decision and signature

State who made the award decision, their title and the date. The decision belongs to a person at your organization. The memo should not suggest the evaluation process itself selected the vendor.

Linking the memo to the consensus record and price analysis

The most useful habit is to write the memo from the file, not from memory. Each paragraph should cite where the evidence lives: the consensus rationale for each final score, the tabulated price comparison, the cost or price analysis worksheet, the responsiveness checklist.

This matters because of 2 CFR 200.318(k), which makes the recipient or subrecipient 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." The recipient's own record is its explanation. A memo that cites its sources lets a reader test it. A memo that merely asserts conclusions invites the reader to assume the support is missing.

For readers who want the broader file structure, the guide to RFP evaluation documentation walks through what belongs alongside the memo, and the explainer on 2 CFR 200.318 procurement records covers the record elements in more depth. A procurement file documentation checklist can help you confirm nothing the memo cites is missing from the folder.

If scoring ended in a tie, the memo should name the tie rule and show that it was set before scoring began. The article on an RFP tie-breaking procedure covers how to define one.

Claims an award memo should avoid

Several statements look reassuring and cause problems later.

• Compliance conclusions. Do not write that the procurement "complies with 2 CFR 200" or is "fully compliant." The memo describes what was done. Whether it met the rule is a determination for the awarding agency, pass-through entity, auditor or counsel.
• Predictions about protests. Do not claim the award cannot be challenged. Nothing about an evaluation makes it immune, and the statement reads as defensive.
• Facts not in the file. If the memo says all evaluators scored independently, the file should be able to show it. Claim only what the record supports.
• Reasoning added after the fact. Do not introduce a rationale in the memo that never appeared in the consensus record. Reviewers notice when the memo's explanation is newer than the scores.
• Opinions on offerors' character. Stick to the criteria. Comments about an offeror's reputation or personality that are not tied to a stated factor are hard to defend.
• Unsupported price statements. "Fair and reasonable" should link to the analysis that supports it.

Context for why the evaluation record gets attention: in its FY2025 bid protest annual report (GAO-26-900695, December 12, 2025), GAO identified unreasonable technical evaluation, unreasonable cost or price evaluation and unreasonable rejection of a proposal as the top grounds on which protests were sustained. Those figures describe federal agency procurements, not grant-recipient or local ones. They are useful only as an illustration of where evaluation records get challenged.

Notice of intent to award and the debrief

Many organizations send a notice of intent to award before the contract is signed, and some local policies require one. Whether yours does, how long the notice period runs and what it must say are set by local policy, state law or the solicitation itself. Check those sources and confirm with your counsel or awarding agency. We do not publish a notice period here because it varies.

The memo and the notice serve different readers. The memo is an internal record of reasoning. The notice tells offerors the outcome. Keep the notice consistent with the memo, and do not release the memo itself without checking your public-records and confidentiality rules. When offerors ask for explanations, the memo and consensus record are the source for a debrief. The guide to debriefing unsuccessful offerors covers how to prepare.

Putting the memo into your file

Finish by confirming three things. First, every statement in the memo traces to a document in the file. Second, the file will be kept for the required period. Under 2 CFR 200.334, the general rule is three years from the date the final financial report is submitted, unless an exception applies, and local public-records rules may require longer. Third, the decision-maker has signed and dated the memo.

RFPManagement is designed to produce an award memo in DOCX and PDF from the evaluation record. In that design, a person enters the award decision, the memo draws on the consensus rationale and the price analysis already in the file, and an append-only, hash-chained audit trail and ZIP export hold the full evaluation file. Scoring is designed to be human-only, and the product is not designed to recommend awards. The reference rules inside the app are designed to show the rule in force with its citation and effective date.

The Award Documentation Kit is a store workbook with Word forms, designed to track conflict-of-interest attestations, assemble the selection memo inputs and check debrief and protest-file completeness. It is available now on the Award Documentation Kit page. To hear when the evaluation workspace opens, join the waitlist. For plan details, see pricing.

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