Your grant file is the story of your award, and a good one answers questions before anyone thinks to ask them. This walks through what belongs in the file, how long to keep it, and a few small habits that keep the whole thing current.
If audit or report preparation becomes an exercise in tracking down information to justify expenditures, notating progress towards deliverables, or gathering procurement information, you spend an afternoon hunting instead of answering.
A well-built grant file solves that problem quietly. It is simply the organized record of one award, from the day it was made to the day it closed. When it is complete, you answer questions in minutes, and the person asking walks away with the sense that your organization has its house in order.
Let's walk through what belongs in it.
Think of the file in layers. The first layer is the award itself: the signed Notice of Award (sometimes called the NOA or NGA), the approved budget, the approved scope of work, and any terms and conditions the agency attached. These documents define what you agreed to do and how you agreed to spend the money. Everything else in the file supports them.
The second layer is your application and any pre-award materials, including the version of the budget that was ultimately approved. When a number in your accounting system does not match a number in the award, this is where you go to see how the two connect.
The third layer is the ongoing record of the award. That includes the items you generate month after month:
-
Financial records that tie your expenditures back to the approved budget, including the general ledger detail for the award
-
Progress reports and financial reports you submitted, with the dates you submitted them
-
Approved budget revisions, prior approval requests, and the agency responses to them
-
Procurement documentation for anything you bought, including quotes, purchase orders, and contracts
-
Time and effort records for staff charged to the award
-
Correspondence with your program officer, especially anything that changes what you are allowed to do
The fourth layer is closeout: the final reports, the final drawdown, and any records showing how you handled remaining equipment or unspent funds.
You do not need every email you ever sent. You need the documents that would let a stranger reconstruct what you did with the money and why it was allowable.
The heart of any grant file is the link between what you spent and what you were approved to spend. Auditors call this a clear audit trail. In plain terms, someone should be able to pick any charge on the grant and follow it back to a source document and forward to the approved budget line it belongs to.
Under the Uniform Guidance, your financial management system has to identify the source and application of funds for each award and maintain records that support your charges (2 CFR 200.302). That is the regulatory version of a simple idea: every dollar should have a paper trail.
So for a given expense, your file should let you show three things without much effort. First, that the cost happened, through an invoice or receipt. Second, that grant funds paid for it, through the general ledger. Third, that it fits an approved budget category and serves the funded purpose. When those three pieces sit together, a question about a single charge takes a minute, not an afternoon.
The general rule under the Uniform Guidance is that you keep records for three years from the date you submit your final expenditure report (2 CFR 200.334). For most awards, that is the clock that matters.
There are situations that pause or extend that clock. If litigation, a claim, or an audit starts before the three years are up, you keep the records until that matter is resolved, even if it runs past the deadline. Real property and equipment records are kept for three years after final disposition. And your awarding agency can set a different period in the terms and conditions, so it is worth a quick check of the award document rather than an assumption.
The practical takeaway is to date your retention from the final report, not from the day the project activity ended. Those two dates are often months apart, and using the wrong one is how records get discarded too early.
Electronic records are fully acceptable. The Uniform Guidance lets you keep records in whatever form works for you, as long as they stay accessible and readable (2 CFR 200.335). You are not required to keep a paper original just because a document arrived on paper.
If you go electronic, a few habits keep the file trustworthy. Store the records where more than one person can reach them, not on a single laptop. Use a consistent folder structure so every award looks the same, which makes handoffs easier when staff change. And back up the files, because a lost drive during a monitoring visit is a hard conversation to have.
Whatever format you choose, the goal is the same. The person who opens the file two years from now, who may not be you, should be able to find what they need without a tour guide.
The best grant files are built a little at a time, not assembled in a panic before a monitoring visit. A short monthly rhythm carries most of the load.
Once a month, drop the new items into the file while they are fresh: the reports you submitted, any approvals you received, and the procurement paperwork for anything you bought. Note the submission dates as you go, because reconstructing them later is tedious and easy to get wrong.
Once a quarter, glance at whether your spending still lines up with the approved budget, and flag any category drifting toward a point where you would need prior approval. Catching that early gives you time to ask the question calmly instead of explaining an overage after the fact.
These habits take a few minutes each. They spread the work across the life of the award so that no single week ever feels heavy.
A grant file is really just a promise kept in writing: that you can account for public money and the work it paid for. When you build it steadily, the file becomes less of a chore and more of a quiet form of confidence, ready to answer whatever question arrives. You do not need a perfect file. You need one that tells a complete and honest story, and that is well within reach.
