Who this checklist is for
This checklist is for the people who inherit a grant after the celebration: grants and development managers who own the calendar, finance leads who own the restricted budget, program staff who produce the deliverables, and executive directors who have to answer "are we on top of our grants?" It assumes you are a nonprofit recipient, not a grantmaker, and that you manage several awards at once — the point where inboxes and one shared spreadsheet stop being enough.
Federal awards are governed by the Uniform Guidance in 2 CFR part 200; every federal item below cites the section it comes from and was checked against the eCFR on the date shown at the top of the page. Foundation and corporate grants have no single rulebook. For those, the award letter or grant agreement controls, and the checklist tells you which clauses to look for.
The checklist
Work through the eight stages in order for each new award, then use the monthly rhythm at the end to keep the whole portfolio current.
1. Accept and set up the award
- File the fully executed award document, the approved budget and the approved proposal or scope in one place per grant.
- Record the period of performance start and end dates, the total award, cost-share commitments and any pre-award cost approvals.
- List every restriction: purpose, budget categories, indirect cost rate, unallowable items, publicity or acknowledgment requirements, and any special conditions.
- Identify the funder contacts — for federal awards, the grants management officer and program officer named in the award; for foundations, the program officer and grants administrator.
- Set up the award in your accounting system so expenditures can be identified by grant. 2 CFR 200.302 requires that federal award records "sufficiently identify the amount, source, and expenditure of Federal funds" and support "comparison of expenditures with budget amounts for each Federal award."
Why: everything later depends on knowing exactly what was promised and what is restricted. Grants.gov's own advice is to clarify terms with your grants and program officers early rather than "submit a report and wait for problems to be identified."
2. Build the obligation calendar and assign owners
- Enter every reporting deadline (financial and performance), deliverable date, site visit, renewal or reapplication window and the period-of-performance end date.
- Give each obligation exactly one internal owner. Shared ownership is no ownership.
- Add lead time: an internal due date two weeks before the funder due date for reports, and a 30-day pre-closeout review.
- Note the reporting cadence the award requires. For federal awards, agencies may not collect financial or performance reports more often than quarterly (unless a specific condition applies) and must collect them at least annually; annual reports are due no later than 90 calendar days after the reporting period and quarterly or semiannual reports within 30 calendar days (2 CFR 200.328 and 200.329).
Why: missed deadlines are almost never caused by ignorance of the date; they are caused by the date living in one person's inbox with no owner and no lead time.
3. Set up the restricted budget
- Enter the approved budget by category as the plan for the grant.
- Decide how you will measure spending against the grant period, not the calendar or fiscal year. A grant that is 40% through its period with 65% of funds spent is running hot regardless of what month it is.
- Set a tolerance for variance (for example ±15 percentage points between percent spent and percent of period elapsed) and decide who is told when a grant crosses it.
- Confirm which budget changes need funder approval before you make them (see stage 6).
Why: restricted funds that run out early stall the program; funds that sit unspent may have to be returned at closeout. Both problems are visible months in advance if you compare burn to elapsed period. Our guide to restricted funds management goes deeper on the calculation.
4. Design the evidence system
- For each deliverable and each report, list the evidence that will prove it: attendance records, invoices, timesheets, photos, survey results, deliverable files, sign-offs.
- Decide where evidence is stored and how it is named so that anyone on the team can find it without the person who created it.
- Attach evidence to the deliverable it supports as it is produced, not the week the report is due.
- Two weeks before any report, check the required evidence is present and readable.
Why: 2 CFR 200.329 asks performance reports for "a comparison of accomplishments to the objectives of the Federal award" and explanations where goals were not met. That comparison is only credible when the evidence already exists.
5. Run the reporting cadence
- Draft financial reports from the accounting system, reconciled to the approved budget, with cost share and program income shown where required.
- Draft performance reports that compare accomplishments to objectives, explain any shortfall, and address cost overruns or higher-than-expected unit costs (2 CFR 200.329).
- Route each report through an internal reviewer before submission — typically finance reviews program numbers and program reviews financial narrative.
- Submit through the funder's required channel and file proof of submission (confirmation email, portal receipt) with the report.
- Notify the funder between reports if a significant development threatens the objectives; 2 CFR 200.329 requires recipients to report problems, delays or adverse conditions along with a corrective plan.
Why: the report is the funder's window into the grant. A late or thin report is the most common trigger for closer monitoring.
6. Watch for changes that need prior approval
For federal awards, 2 CFR 200.308 lists changes that need the funder's prior written approval. Check your award terms, because agencies can waive some and add others. Common triggers:
- A change in the scope or objective of the project, even without a budget change.
- A change in key personnel named in the award, or the project director disengaging for more than three months or reducing effort by 25% or more.
- Transfers of funds budgeted for participant support costs to other categories.
- Subaward activities not proposed and approved in the award.
- Changes to the approved cost-sharing amount, or a need for additional federal funds.
- Extending the period of performance beyond a one-time no-cost extension. Under 200.308, a recipient may take a one-time extension of up to 12 months without prior approval, provided the award's conditions allow it and the agency is notified in writing at least 10 calendar days before the period ends.
For foundation grants, look for clauses on budget reallocation thresholds, use of unspent funds, changes in staffing and extension requests. When in doubt, ask in writing and file the answer.
7. Close out on time
- Thirty days before the end date, list open deliverables, unspent balances, outstanding invoices and any evidence still missing.
- Submit all final reports and liquidate all obligations within the deadline. For federal recipients that is 120 calendar days after the period of performance ends; subrecipients report to their pass-through entity within 90 calendar days (2 CFR 200.344).
- Return or account for unobligated balances as the award requires, and reconcile cost share and program income.
- Complete equipment and property dispositions if the award funded them.
- Record the closeout date and confirmation from the funder.
The grant closeout checklist covers the federal and private branches in detail.
8. Retain records and prepare for audit
- Keep the complete grant file — award, budget, approvals, expenditure support, evidence, reports, correspondence and closeout — for at least three years from the date you submit the final financial report (2 CFR 200.334), longer if litigation, claims or audit findings are open, and three years after final disposition for property records.
- Track total federal expenditures each fiscal year. An organization that expends $1,000,000 or more in federal awards in its fiscal year must have a single or program-specific audit for that year (2 CFR 200.501); Grants.gov notes the reporting package is due within nine months after the audit period ends.
- Keep foundation grant files for at least as long as the agreement requires, and apply the same three-year floor if it is silent.
Federal vs. foundation grants: what changes
| Item | Federal award (2 CFR 200) | Foundation or corporate grant |
|---|---|---|
| Reporting cadence | At least annually, no more than quarterly without a specific condition | Set by the agreement; often mid-term and final |
| Interim report deadline | 90 days after an annual period; 30 days after a quarterly or semiannual period | Set by the agreement |
| Final reports and liquidation | 120 calendar days after the period ends (90 for subrecipients) | Set by the agreement; commonly 30–90 days |
| Budget changes | Prior approval triggers listed in 200.308 | Reallocation thresholds vary; ask if unstated |
| Record retention | Three years from the final financial report, with exceptions | Set by the agreement; use three years as a floor |
| Audit exposure | Single audit at $1,000,000 in federal expenditures per fiscal year | Funder review or site visit at the funder's discretion |
How to run the checklist month to month
Stages 1 through 4 happen once per award. Stages 5 through 8 repeat, and they are where portfolios drift. A workable rhythm for a team managing 5–25 grants:
- Weekly, 15 minutes: everything due in the next 30 days, its owner, and whether the evidence is ready.
- Monthly, one hour with finance: percent spent versus percent of period elapsed for every active grant, any grant outside tolerance, prior-approval questions, and grants entering their last 90 days.
- Quarterly, with leadership: reports submitted on time, closeouts completed, renewals decided, and anything an auditor would flag.
Write the outcome of each review down. The habit of recording "who decided what, when" is most of what an audit trail is.
Where software helps — and where it does not
A spreadsheet can hold every item above, and for a handful of grants it should. It stops working when deadlines, evidence and budgets live in three different places and nobody is warned when they diverge.
Post-award grant management software such as GrantConsole is built for exactly this checklist: it stores deadlines, deliverables and renewals with a named owner per grant, tracks restricted budget burn against the elapsed grant period, attaches evidence to the deliverable that requires it, and evaluates active grants against explainable risk rules — for example a deliverable past due, an evidence gap inside the final 14 days before a report, spending more than 15 points ahead of or behind the elapsed period, a closeout window inside 30 days with work still open, or a grant with no internal owner. Each warning names the rule and the record behind it, so a person can check it. You can see the workflow with example data in the live demo without a sales call.
What no software does: interpret your award for you, decide whether a cost is allowable, or make you compliant. Those judgments stay with your team and, when the stakes justify it, your auditor or grants counsel.
Common mistakes this checklist prevents
- Treating the calendar as the system. Dates without owners, lead time and evidence checks still get missed.
- Measuring spending against the fiscal year instead of the grant period, so overspending is discovered at closeout.
- Collecting evidence at report time, when the people who have it have moved on.
- Making budget or personnel changes first and asking the funder afterward.
- Letting a grant with no owner sit in "active" status for months.
- Discarding files three years after the grant ended rather than three years after the final financial report was submitted.
Print the checklist, adapt the foundation column to your funders' actual agreements, and review it on the rhythm above. The next resources in this series cover the reporting calendar template and the closeout checklist in depth.