2 CFR 200.318(i) Procurement Records: What the File Must Show

A monitor asks one question about the second-ranked offeror

A grants manager at a nonprofit is sitting across from a program monitor three weeks after a site visit was scheduled. The monitor has picked one contract from last year, a consulting engagement paid with federal award funds, and asks a plain question: why did the second-ranked offeror lose? The manager knows the committee did careful work. The scoresheets are in one email thread, the consensus notes are in a Word file on someone's laptop, and the price comparison lives in a spreadsheet that was edited twice after the award.

The manager can find every piece. What the manager cannot easily do is put the pieces in order and show what happened, who decided what, and under which rule. The meeting stretches while people hunt for attachments.

That gap, between having done the work and being able to show it, is what 2 CFR 200.318(i) addresses. After reading this article you will be able to name the four things the file must show, test your own folder against each one, and see where loose files tend to fail.

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

Under 2 CFR 200.318(i), "The recipient or subrecipient must maintain records sufficient to detail the history of each procurement transaction. These records must include the rationale for the procurement method, contract type selection, contractor selection or rejection, and the basis for the contract price." That gives four elements: the method rationale, the contract type, the selection or rejection, and the price basis. This is the core of the 2 CFR 200.318 procurement records requirement. The text is in the eCFR; confirm the current wording there, since eCFR is authoritative but unofficial and the official edition is the annual CFR on govinfo.gov.

Two phrases deserve attention. "History" means the file is read as a sequence, not as a pile. "Each procurement transaction" means the duty applies per procurement, so a single organization-wide binder of policies does not satisfy it.

The rule asks for records that detail the history. It does not prescribe a form, a folder structure or a software product. Nothing in this article, and nothing in any file you assemble, makes a procurement compliant. The records help the issuer show what it did. Whether the procurement met the rule is a judgment for the awarding agency, the pass-through entity and auditors.

Related requirements sit around it. 2 CFR 200.318(a) requires documented procurement procedures consistent with state, local and tribal law and with 2 CFR 200.317 through 200.327. 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 selecting, awarding or administering a contract supported by the federal award. Both of those leave their own traces in the file.

Element one: the rationale for the method of procurement

The first element asks why you used the method you used. 2 CFR 200.320 sets out three types of procurement method: informal (micro-purchases and simplified acquisitions), formal (sealed bids or proposals) and noncompetitive. Our companion piece on 2 CFR 200.320 procurement methods walks through each.

A file that records only the method name, such as "RFP", has not recorded a rationale. A rationale connects the facts of the purchase to the method. It might note the estimated value, the threshold that applied, and why proposals were chosen over sealed bids because factors other than price mattered.

Thresholds are where files most often go stale. As an example of a rule change, the micro-purchase threshold rose from $10,000 to $15,000 and the simplified acquisition threshold rose from $250,000 to $350,000, effective October 1, 2025 (FAR Case 2024-001, 90 FR 41872). If an award was made before that date, ask the awarding agency or pass-through entity which figure applies to it. A local or state threshold may be lower, and where both apply the stricter rule governs.

What should the file record? Four things:

• the estimated value and the threshold you compared it to;
• the citation for that threshold and its effective date;
• the method chosen and the reason;
• who confirmed it, and when.

Recording the rule and its date matters because a file that does not do so cannot show which rule it followed at the time. The Uniform Guidance was substantially revised effective October 1, 2024 (89 FR 30046), and a procurement started before or after that date may sit under different text.

Element two: the contract type selection

The second element is the contract type. In practice this means recording whether the contract is firm fixed price, a time-and-materials arrangement, a cost-reimbursement contract or something else, and why that type fit the work.

This element is the one most often left implicit. Teams know they negotiated a fixed fee, but nothing in the file says that was a choice made against alternatives. A one-paragraph note is usually enough: the type selected, the reason (for example, a well-defined scope that allows a firm price), and the person who approved it.

For sealed bids, 2 CFR 200.320(b)(1) provides that a firm fixed-price contract goes to the responsible bidder whose conforming bid is lowest in price, and sealed bids are preferred for procuring construction services. For proposals, 2 CFR 200.320(b)(2)(iii) says contracts "must be awarded to the responsible offeror whose proposal is most advantageous to the recipient or subrecipient considering price and other factors." The contract type should be consistent with the method you recorded in element one, and a reader should not have to guess whether it is.

Element three: contractor selection or rejection

The third element is where evaluation records live, and where loose files fail most visibly. The rule names both selection and rejection. A file that explains only why the winner won has documented half of it.

For a competitive proposal, 2 CFR 200.320(b)(2)(i) requires public notice and that the solicitation 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. The file should therefore show the factors and weights as published, the written evaluation procedure, the scores, and the rationale for the final ranking.

Consider what a reader reconstructing a selection needs:

1. The solicitation as issued, with its stated factors and weights.
2. The evaluator roster and each person's conflict-of-interest statement, tied to 2 CFR 200.318(c).
3. Each evaluator's individual scores, dated, showing they were entered before group discussion.
4. The consensus record, with a written reason for each final score.
5. The responsiveness determination for each proposal, including any excluded as non-responsive and why.
6. The ranking, the tie rule if one applied, and the human decision to award.

Item three is where independence is often claimed rather than shown. In a shared spreadsheet or in emailed scoresheets, nothing technically prevents one evaluator from seeing another's numbers. If a losing offeror suggests anchoring, the file has to answer, and a spreadsheet's edit history rarely does.

For qualifications-based selection of architectural and engineering services, price is excluded as a selection factor under 2 CFR 200.320(b)(2)(iv), and compensation is negotiated after the most qualified offeror is chosen. That method may be used only for A/E professional services. Many states have their own QBS statutes, so check your state's law. The file should show the qualifications evaluation first and the fair-and-reasonable negotiation second, in that order. Our piece on the award memo and selection memo covers how to summarize this decision in a single document.

Element four: the basis for the contract price

The fourth element asks how you know the price was acceptable. Above the simplified acquisition threshold, 2 CFR 200.324(a) requires a cost or price analysis for every procurement transaction, including contract modifications, and independent estimates must be made before receiving bids or proposals. The regulation does not define "independent." In practice the estimate need not come from a third party, but 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.

The sequencing matters as much as the number. An estimate dated after proposals arrived looks like a reconstruction. The file should show the estimate with its date, the method behind it, who prepared it, and how the selected price compared.

When price is scored, record the formula. A common lowest-price formula is lowest evaluated price divided by this offer's evaluated price, multiplied by the maximum price points.

Worked example. Three offers come in 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, or 24 points. The third earns 80,000 ÷ 125,000 × 30, or 19.2 points. The file should show these inputs, the formula and the results, and should state whether alternates or options were included in the evaluated price or excluded.

Micro-purchases follow a lighter path. Under 2 CFR 200.320(a)(1)(ii), they may be awarded without soliciting competitive price or rate quotations if the recipient or subrecipient considers the price reasonable based on research, experience, purchase history or other information, and maintains documents to support that conclusion. Paragraph (a)(1)(i) adds that, to the extent practicable, micro-purchases should be distributed equitably among qualified suppliers. Local policy may set a lower threshold.

Why a folder of loose files often cannot show the history

Each of the four elements can be satisfied by documents that exist. The failure is usually one of reconstruction. The scoresheets are in email, the memo has no date, the estimate has no author, and the threshold the team relied on is nowhere cited.

Loose folders tend to share five weaknesses:

• no record of order, so nobody can show the estimate came before the proposals;
• no record of which rule applied and its effective date;
• scores visible to others before everyone submitted;
• consensus decisions with no written reason;
• edits to a spreadsheet after the award, with nothing to show what changed.

These are structural limits of spreadsheets and templates, not defects in any particular one. Free templates are familiar and flexible, and many offices use them well. What they do not do on their own is enforce hidden-until-lock scoring or keep an append-only record.

Why does this matter beyond tidiness? 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." Its own record is its defense.

Evidence from oversight bodies shows how often procurement is where problems surface. In a 2023 article, the Washington State Auditor's Office said federal procurement is the most common single audit finding it reports, about 26 percent of them. That is one state's findings and should not be read as a national rate. Separately, DHS OIG audits questioned $352.3 million in FEMA Public Assistance grant costs over the six years ended September 30, 2014, because subgrantees did not follow federal procurement rules (OIG-16-126-D). Those figures cover FEMA Public Assistance specifically. Remedies for noncompliance under 2 CFR 200.339 include temporarily withholding payments, disallowing costs, and suspending or terminating an award in part or in its entirety. For a view of the audit side, see our note on single audit procurement findings.

Building a file that answers all four elements

A practical approach is to assemble the file as a sequence and test it against a single question: could someone who was not in the room reconstruct what happened, in what order and under which rule?

Start with an index that lists each document, its date and its author. Then check the four elements in turn.

• Method rationale: the value, the threshold with its citation and effective date, the method, and the reason.
• Contract type: the type, the reason, and the approver.
• Selection or rejection: the published factors and weights, conflict statements, dated individual scores, consensus reasons, responsiveness decisions, and the ranking.
• Price basis: the dated independent estimate, the cost or price analysis, the price-scoring formula and inputs, and how alternates were handled.

Then consider retention. Under 2 CFR 200.334, records are generally kept 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. Our piece on 2 CFR 200.334 record retention covers the details, and the procurement file documentation checklist gives a longer line-by-line list.

Keep two cautions in view. First, the award decision stays with your organization. No document, template or tool decides for you. Second, state and local codes may be stricter than the federal rules, and when both apply the stricter one governs.

Where a template can help, and what to do next

The Award Documentation Kit is designed to record the award file in the order the four elements imply: method rationale, contract type, selection or rejection, and price basis, with space for the dates and citations that show which rule applied. It is a store workbook, available now. You can read what it is designed to compute and record on the Award Documentation Kit page.

If you would rather keep the whole evaluation in one record, RFPManagement is a workspace for the evaluation stage, built around weighted criteria, hidden-until-lock scoring, consensus rationale and an append-only audit trail. The app is pre-launch. To hear when it opens, join the waitlist. Plans are described on the pricing page once available.

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