Record Retention Under 2 CFR 200.334: How Long to Keep the Procurement File

When a pass-through entity asks for a closed grant's procurement file

A finance manager at a grant-funded nonprofit opens an email from the pass-through entity. It asks for the procurement file behind a contract awarded several years ago, as part of a monitoring review. The grant has closed. The staff member who ran the solicitation has left. The evaluation folder was moved to an archive drive during an office migration, and nobody is sure whether the scoresheets came along or only the final award memo.

The manager has two questions that sound simple. First, is the organization still required to hold these records? Second, if it is, what exactly should be in them? The answers depend on which retention clock applies, when that clock started, and whether anything has paused it.

This article walks through the three-year rule in 2 CFR 200.334, what can extend it, how E-Rate and local schedules sit beside it, and how to record one retention date per procurement so you can answer both questions quickly.

2 CFR 200.334 record retention: 3 years from the final financial report

Under 2 CFR 200.334, the recipient and subrecipient "must retain all Federal award records for three years from the date of submission of their final financial report." The records to be retained include financial records, supporting documentation and statistical records. Procurement files are among them, because they support the costs charged to the award.

The starting point matters more than the number. The clock does not begin when the contract was signed or when the evaluation closed. It begins when the final financial report for the award is submitted, which can be years after the procurement itself. (For awards renewed quarterly or annually, the section runs the clock from the quarterly or annual financial report instead.) A file for a contract awarded in the first year of a multi-year grant may therefore need to be kept far longer than three years from its own award date.

Here is a worked example with round dates. Suppose a nonprofit submits the final financial report for an award on June 30, 2027. With no exception in play, the federal three-year period would run to June 30, 2030. A contract awarded in 2024 under that award would still be inside the window in 2029, five years after it was signed.

The Uniform Guidance was substantially revised effective October 1, 2024 (89 FR 30046), and this guide reflects the current text, so check that any older copy of 200.334 in your policy still matches. OMB published a further proposed revision on May 29, 2026 (91 FR 32198); as of October 2026 it is proposed, not final. Confirm its current status before you update a written policy.

What extends the three-year period

The three-year figure is a default. The section lists the exceptions. Two matter most for a procurement file:

• Litigation, claims or audit findings. Under 200.334(a), if any litigation, claim or audit is started before the three years run out, the records must be kept until it has been resolved and final action taken.
• A written extension. Under 200.334(b), the period extends when the federal agency, pass-through entity or a cognizant or oversight agency notifies you in writing.

The others cover property and equipment records (three years after final disposition), records transferred to the federal agency, program income earned after the period of performance, and indirect cost rate computations. Read the section for the detail.

Two practical situations deserve a flag in your file:

• An open audit, monitoring review or claim. If one has started, treat the related records as held until it is resolved, whatever the calendar says. Ask the awarding agency or pass-through entity, and your counsel, how the exception applies to your award.
• A protest or dispute. Under 2 CFR 200.318(k), the recipient settles source evaluation issues, protests, disputes and claims. Your own record is your response, so discarding it while a challenge could still arise weakens the only evidence you control.

A "legal hold" is simply a written instruction to stop routine disposal for a defined set of records. It is an organizational practice, not a number in the regulation. Record who issued it, the date, what it covers and the date it was released. When the hold lifts, the ordinary retention clock still has to be checked, because the hold does not shorten it.

Remedies for noncompliance sit in 2 CFR 200.339 and include temporarily withholding payments, disallowing costs, and suspending or terminating the award in whole or in part. Missing procurement records are one way costs can come into question, so retention is not a housekeeping detail.

How E-Rate and local schedules sit beside the federal rule

Different funding streams run on different clocks, and an organization can be subject to more than one at the same time. When two schedules apply to the same record, follow the longer one.

For schools and libraries in the E-Rate program, 47 CFR 54.516(a)(1) requires applicants to keep all documents related to applying for, receiving and delivering supported services for at least 10 years after the later of the last day of the applicable funding year or the service delivery deadline for the funding request. The E-Rate document retention period of 10 years is more than three times the federal grant default.

Here is a second worked example, with round dates. If a funding year ends June 30, 2027 and the service delivery deadline falls earlier, the 10-year period would run to June 30, 2037. If the service delivery deadline falls later, the later date controls. The same district may also hold federal grant awards with their own three-year clocks, and a state records schedule on top of both.

Local schedules are a separate layer. A procurement file record retention local government schedule is set by state law or local policy, and the periods vary widely. Public-records rules may require records to be kept longer than the federal minimum. We do not summarize any state's schedule here. Ask your records officer, state archives office or counsel which schedule governs the procurement file, and record the answer in the file.

Special districts and other small local bodies often have the least formal setup here. Our guide on writing a special district purchasing policy shows where a retention statement belongs in the written procedures that 2 CFR 200.318(a) calls for.

What the retained procurement file should contain

Retaining a file only helps if the file can explain itself. Under 2 CFR 200.318(i), records must be detailed enough to show the history of the procurement. That includes four elements:

1. the rationale for the method of procurement;
2. the selection of contract type;
3. the selection or rejection of the contractor;
4. the basis for the contract price.

Our guide to 2 CFR 200.318 procurement records takes each element in turn, and the procurement file documentation checklist lists the items that usually support them. For a competitive-proposal procurement, that normally means:

• the solicitation, with every evaluation factor and its relative importance (2 CFR 200.320(b)(2)(i));
• the written technical evaluation and selection procedures (2 CFR 200.320(b)(2)(ii));
• evaluator conflict-of-interest attestations (2 CFR 200.318(c));
• individual scoresheets, the consensus rationale and the final ranking;
• the price analysis and, above the simplified acquisition threshold, the independent estimate made before proposals arrived (2 CFR 200.324(a));
• the award decision and the notice to unsuccessful offerors.

A file that exists but cannot show the order of events is hard to defend. Keep date-stamped versions where you can, and keep the rule that applied at the time. Thresholds change, and a file that does not record which rule it followed cannot show which rule it followed at the time.

For E-Rate applicants, the competitive bidding process adds its own documentation, and beginning with funding year 2028 the FCC has adopted a requirement that applicants upload bid evaluation and vendor selection documents, including contracts, to a USAC-managed portal (91 FR 29051, May 19, 2026). Check USAC for the current implementation schedule. RFPManagement does not submit to or integrate with that portal.

Audits are one place missing records surface. Under 2 CFR 200.501(a), an entity that expends $1,000,000 or more in federal awards during its fiscal year must have a single or program-specific audit for that year. In one state, the Washington State Auditor's Office says federal procurement is the most common single audit finding it reports, about 26 percent of them (blog post updated 2023). That figure describes one state's findings and should not be read as a national rate. See our overview of single audit procurement findings for how reviewers tend to approach the file.

Setting one retention date per procurement

The simplest control is a retention date written down when the procurement closes, not discovered years later. For each file, record these items:

• the funding source or sources, and which retention rule each one brings;
• the date the final financial report was submitted, once it is known;
• the federal date calculated from that report, the E-Rate date if it applies, and the local schedule date as confirmed with your records office;
• the controlling date, which is the latest of them;
• any hold, with the date issued, the reason and the date released;
• who may authorize disposal.

Update the controlling date when the final financial report goes in, because that is the event that starts the federal clock. Review it again before any disposal, and ask the awarding agency or pass-through entity if you are unsure whether an extension applies.

An evaluation workspace can help with part of this. RFPManagement is built to keep an append-only, hash-chained audit trail and a ZIP export of the full evaluation file, and closed evaluations stay readable and exportable after a plan lapses. Those features help you show what was done and when. They do not set your retention period for you, and your local rules still govern where the exported file lives and for how long. To hear when the evaluation workspace opens, join the waitlist.

If you want a place to track dates across all procurements, the Annual Procurement Log and Threshold Tracker is designed to record each procurement, the threshold and method applied, and the dates tied to it. It is available in the store now.

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