Before you send a grant report, check the dates, the source behind every number, the current approved budget, the measure definitions, and the submission instructions. Then have someone who did not assemble the report read it once. Those five checks catch many avoidable questions.
The hard part is rarely writing a polished paragraph. It is making sure the report says what the records can actually support. Here are seven gaps I would look for before clicking submit.

This article focuses on covered U.S. federal awards. A private foundation grant or a state and local award may use different rules. Read the signed agreement, its amendments, and the funder’s current portal instructions before applying any general guidance.
For the companion AI checks, see seven prompts for reviewing a grant file. The series also includes a step-by-step award workflow, answers to common questions, and five reusable grant templates.
Quick review: seven gaps to look for
| Gap | What to compare | Who should verify |
|---|---|---|
| Wrong period or version | Report dates, award amendment, portal form | Grant owner |
| Missing source for a number | Draft answer and source record | Program or finance owner |
| Mixed measures | Target, actual, estimate, and cumulative totals | Program manager |
| Expense mismatch | Ledger, approved budget, source documentation | Finance lead |
| Unexplained change | Prior report, current result, reason for variance | Grant manager |
| Missing attachment or certification | Current instructions and upload list | Submitter |
| No final review or receipt | Approval notes and funder confirmation | Second reviewer |
1. The report uses the wrong dates or an old form
This one happens when the team reuses last quarter’s file and changes only the heading. The award may have been amended. The reporting period may start or end on a different date than the program team expects. The portal can also ask for a new form or attachment.
Check three things side by side:
- The current signed award and any amendments.
- The reporting schedule and form in the funder’s current system.
- The reporting period printed on the actual draft.
For covered federal awards, financial reporting requirements are in the award. The current 2 CFR 200.328 gives general timing limits for annual, quarterly, semiannual, and final financial reports. Don’t turn those limits into your calendar without checking the specific award.
2. A number has no source behind it
“We served 84 households” sounds clear until someone asks where 84 came from. Was it a unique household count? Did it include repeat visits? Was one event counted twice? A number without a definition and source is hard to explain later.
For each reported number, keep a small evidence note:
- What the measure means.
- Which date range it covers.
- Where the source record lives.
- Who checked the calculation.
Current federal financial management rules require source documentation for covered award expenses. Performance reporting also needs to connect accomplishments and financial data to award goals and objectives when required. See 2 CFR 200.302 and 2 CFR 200.329.
3. Targets, estimates, and actual results are blended together
A proposal target is not a result. A year-to-date total is not the current quarter’s total. A projection is not a count of work already done.
Put the labels in the report or supporting worksheet:
- Target: what the approved project plans to reach.
- Actual: what the records show happened in this reporting period.
- Cumulative: the total since the agreed project start.
- Estimate or forecast: a forward-looking number, if requested.
If the funder’s form does not explain how to calculate a measure, ask before you submit. Keep your calculation notes so the next report uses the same definition.
4. Expenses do not match the approved budget or ledger
A report may show a reasonable total and still have the wrong category, period, or source. Watch for a budget amendment that is missing from the folder, a transaction dated outside the reporting window, a duplicate line, or a cost shared across awards without a clear allocation record.
Ask finance to reconcile the report total to the grant ledger and compare it with the latest approved budget. For a covered federal award, 2 CFR 200.302 calls for tracking federal expenditures, supporting them with source documentation, and comparing expenditures with budget amounts. It does not mean an AI tool or a narrative reviewer can decide whether a particular cost is allowable.
If a cost looks wrong, hold the figure and ask the authorized finance lead. Keep the transaction reference and source document with the question.
5. A change or missed target is hidden in a vague sentence
Program work changes. A partner may leave. A venue may close. Hiring may take longer than planned. You do not help the funder by smoothing that into “implementation is progressing well” if the numbers show a delay.
Use a plain sequence instead:
- What was planned for this period?
- What happened, based on the records?
- What explains the difference?
- What has the team changed or asked permission to change?
- What source or approval supports that explanation?
Keep the description factual. If the team has not confirmed the reason yet, say that an internal review is underway and assign an owner and date. Don’t present a guess as the cause.
6. A required file, approval, or answer is missing
Reports sometimes fail for a simple clerical reason: an attachment was mentioned but not uploaded, a certification box was skipped, or one question was left blank because no one knew who owned it.
Make a final crosswalk from the funder’s instructions to the report packet. For every required field, note:
- Who provides the answer.
- Which record supports it.
- Whether an attachment is required.
- Who approves the final wording.
- Whether the field is complete in the portal.
Never fill an empty field with an invented explanation. Ask the funder contact or follow the system’s instructions for “not applicable,” unavailable data, and extension requests.
7. Nobody checks the whole packet or saves the receipt
The person who built the packet knows what each file is supposed to show. That can make a second review feel unnecessary. It is exactly why the review helps.
Ask a colleague to confirm the reporting period, required form, totals, attachments, and open questions. Then save a copy of what was submitted, the approval record, and the portal confirmation or email receipt. Put the next reporting date on a shared calendar.
For federal awards, recipients and subrecipients have oversight responsibilities under 2 CFR 200.329. Internal controls under 2 CFR 200.303 also call for monitoring compliance and taking prompt action when a problem is identified. Keep the review simple enough that your team will actually do it.
How AI can help, and where it should stop
If your organization allows an approved AI tool, use it for mechanical checks. For example:
“Compare this de-identified report draft with the supplied award instructions, budget, and source table. Flag inconsistent dates, totals that do not match the source rows, missing attachments, unclear measure labels, and claims without a source reference. Return a checklist with the location of each issue. Do not invent results, decide cost allowability, or rewrite unsupported claims.”
Then check each flag against the original records. Do not upload participant names, protected information, payroll details, or banking information unless the tool is approved for that data. A person still owns the report.
A fictional example: one count, two definitions
A small food access nonprofit reports that it served 310 people in a quarter. A reviewer asks whether that means unique people or total visits. The program lead checks the sign-in log and finds 248 unique participant IDs and 310 visits. The report draft had used the visit total while its question asked for people reached.
The team checks the form instructions, changes the answer to 248 unique people, and records 310 visits in the narrative where the form allows it. The numbers were both real. They answered different questions.
Before submission, use this short checklist
- Current award, amendment, form, and reporting period confirmed.
- Every total can be traced to a source.
- Target, actual, cumulative, and estimated figures are labeled.
- Expenses reconcile to the ledger and approved budget.
- Variances and missed targets are explained from known facts.
- Required questions, certifications, and attachments are complete.
- A second person reviewed the packet.
- The final copy and submission receipt are saved.
Need a practical grant prompt reference?
The Nonprofit Grant Compliance Prompts book gives small teams prompts for organizing award conditions, checking budgets, connecting evidence to report answers, reviewing file gaps, and preparing follow-up questions. It is a starting point for staff who have limited time and need a clear next step. It does not replace the award agreement, current funder instructions, or finance review. Use it alongside the companion articles on AI checks for a grant file, the award-to-closeout workflow, common questions, and reusable record sheets.
Frequently asked questions
What should a nonprofit check before sending a grant report?
Confirm the reporting period, current award instructions, sources for every number, budget alignment, measure definitions, required attachments, reviewer, and submission receipt.
Can I use the same report schedule for every federal grant?
No. The award sets the specific schedule within applicable requirements. Check the current agreement and portal rather than copying another grant’s calendar.
Should projected results be included with actual results?
Only when the funder requests them. Label projections clearly and keep them separate from measured results and targets.
Can AI check a grant report?
An approved tool can flag missing fields or mismatches. A person must verify the flags and approve the report.
Do federal reporting rules apply to private foundation grants?
Not automatically. Read the private foundation agreement and its instructions. Do not assume federal award rules apply.
Last reviewed: November 16, 2026. This article is general information, not legal or accounting advice. Award instructions and requirements can change.