7 minute read
Grant closeout checklist: prepare the final report without losing the evidence trail
A practical closeout checklist for organizing final reporting, financial reconciliation, evidence, records, and human review around the controlling award terms.
1. Confirm the closeout terms for this award
Start with the closeout language in the agreement, amendments, agency notices, and funder instructions. Identify every final report, financial reconciliation, deliverable, certification, return-of-funds instruction, record-retention requirement, and deadline. The timeline and submission route can differ across federal, state, local, and foundation awards, so use the terms for the specific award rather than assuming that another funder workflow applies.
Put the external dates and internal review dates on a shared calendar. Name an owner for financial close, program results, document collection, agreement review, and final submission. A closeout task is not complete simply because a draft exists; it is complete when the applicable source requirements, review decisions, and submission records are accounted for.
2. Reconcile the financial position
Use the approved budget, amendments, and final accounting export to review the grant-level financial position. Keep the mapping from accounts to budget categories, document allocation methods, and identify unresolved charges or explanations. Confirm which transactions belong in the grant period and which question needs a source check. If funds are unspent or a variance is material, consult the award terms before making a conclusion about disposition or approval.
Keep the numbers and the narrative separate until both are reviewed. Finance should validate totals and calculations; program and grants staff can provide factual context for activities, timing, and documentation. Do not state that a cost is allowable, approved, or final unless the organization has the relevant support and reviewer decision.
3. Assemble the final evidence package
Collect the agreement, amendments, submitted reports, approved budget versions, accounting exports, calculations, program records, required attachments, correspondence, and submission confirmations in an organized package. Link material report claims to the documents that support them. If a required record is absent, make that gap visible and assign it rather than filling the space with an unsupported statement.
Retention requirements can vary. For awards subject to federal requirements, consult the applicable regulation and agency guidance as well as the award itself. Your operational archive should make it possible for a future reviewer to identify the final version, see what changed, and trace material values to their source records.
4. Run the final human review
Before submission, compare the package to the current award terms line by line: reporting period, required narrative questions, financial fields, metrics, attachments, signatures, certifications, portal instructions, and due date. Record who reviewed the package and what was resolved. This supports continuity and avoids treating a generated draft as an approved submission.
GrantDeskHQ helps teams bring award terms, financial data, program updates, and evidence into a reviewable workflow. It does not submit, certify, or approve a report for your organization. Use the Free First Award flow with one award when you want to test how a source-linked draft can support your closeout preparation.