Create a Grant Document Retention Schedule

Grant records outlive the grant. Staff may move on. Systems may change. Auditors, funders, or federal agencies may still ask for proof years later.

A retention schedule prevents two bad outcomes: deleting records too early and keeping disorganized records forever.

For federal awards, 2 CFR 200.334 is the main starting point. In many cases, records must be kept for three years from the date the final expenditure report was submitted. But exceptions can extend that time.

Step 1: list the grants

Start with active and closed grants. Include federal, state, local, foundation, and restricted gifts if they have reporting or audit risk.

For each grant, capture the funder, award number, period of performance, final report date, closeout date, and archive location.

If the grant is not closed, leave the retention date blank and mark it pending. Do not guess.

Step 2: set the retention trigger

The trigger is the event that starts the retention clock. For many federal grants, this is the final expenditure report submission date.

Do not use the award end date unless the rule says to. A grant that ends June 30 may have a final report due months later. The retention period usually starts later.

For non-federal grants, read the agreement. Some funders require longer retention. State grants may also add state rules.

Step 3: list record types

A useful schedule names the record types, not just the grant.

Include:

• award agreement and amendments
• approved budget
• ledger support
• invoices and payroll support
• procurement files
• reports and submissions
• funder correspondence
• equipment records
• subrecipient records
• monitoring notes
• closeout notices

This helps staff know what belongs in the archive.

Step 4: identify holds and exceptions

Retention can extend when there is an audit, litigation, claim, negotiation, agency notice, or unresolved finding. Some property records may also have a different retention rule.

Create a hold log. For each hold, note the grant, reason, start date, owner, and release condition.

Do not destroy records while a hold is open. It does not matter if the normal retention date has passed.

Step 5: choose the archive location

Records can be electronic if they are readable, protected, and accessible. 2 CFR 200.335 covers electronic records.

Pick one archive location per grant file. If records must live in more than one system, the schedule should say where each type lives.

Avoid vague locations like “shared drive.” Use the folder path or system name.

Step 6: assign an owner

Every schedule needs an owner. The owner does not have to keep every file personally. The owner makes sure the file exists, holds are checked, and destruction review happens.

Finance may own ledger and payment records. Grants staff may own award and report records. Leadership should approve the policy and any final destruction.

Step 7: review before destruction

Do not auto-delete grant records just because a date passed. Use a review checklist.

Before destruction, confirm the retention period ended, no hold applies, no open audit or claim exists, and leadership approved the action. Save the approval log.

This ties directly to the federal award closeout workflow. A clean closeout file makes retention review much safer.

Handle mixed funding

Some files contain more than one rule. A project may include federal funds, state funds, foundation funds, and private restricted gifts. Use the longest required retention period when records cannot be separated cleanly.

Write that choice down. Future staff should not have to guess why the file is kept longer than the federal minimum.

If the file includes payroll, procurement, equipment, or subrecipient records, make sure those records follow any special retention rule too.

Make the schedule usable

A retention schedule should be easy to scan. Use columns for grant name, funder, final report date, retention rule, hold status, archive path, owner, destruction review date, and approval status.

Review the schedule at least once a year. Add newly closed grants. Release holds that no longer apply. Update archive paths when systems change.

The schedule is not only about deleting old files. It also helps staff find records when a funder asks a question, an auditor selects a sample, or leadership needs proof of a closed award.

Keep a copy of the retention policy beside the schedule. The schedule shows dates and owners. The policy explains the rule, approval process, and hold process behind those dates.

How GrantPipe helps

GrantPipe can keep closeout dates, report submissions, archive notes, and retention dates attached to each award. That helps staff find records later without rebuilding the file from email.