Free Resource for Small Nonprofits

Grant Reporting Checklist for Small Nonprofits

A step-by-step checklist for preparing grant reports at a small nonprofit: know every due date, gather the numbers and documents before the deadline, make the financial and program reports agree, and keep a record of what was sent.

Jump to Checklist
Use browser Print to save as PDF

Best for

Small nonprofits reporting on one or more active grants

Use it to

Prepare each report calmly and send it on time

Format

Web page now, print-friendly PDF anytime

Why this matters

Late or inconsistent reporting is the most common way a small nonprofit damages a funder relationship, and it almost never happens because the program failed. It happens because the due date lived in one inbox, the numbers lived in three places, and the report was started the week it was due. This checklist front-loads the work so each report is assembled, not improvised.

1

Know every report that is due

Most late reports are not forgotten work. They are reports nobody wrote down.

  • Every report for every active grant is listed in one place, with its due date
  • Each report says whether it is financial, program, or both
  • The reporting period each report covers is written next to it
  • Recurring reports (quarterly, semiannual, annual) are listed for the whole grant period, not just the next one
  • Final and closeout reports are on the list from day one
  • Due dates that depend on something else (30 days after the period ends, 90 days after closeout) are converted to real dates
  • The funder's portal, email address, or form for each report is noted

Quick check: Can you name the next three reports due across all your grants, without opening a file?

2

Give every report an owner and a start date

A due date is not a plan. A start date is.

  • One person is responsible for each report, by name
  • One backup person knows the report exists and where the pieces live
  • Each report has an internal start date at least two weeks before it is due
  • Someone other than the writer reviews it before it goes out
  • The person who signs or submits is known and available on the due date
  • Deadlines are visible to finance and program staff at the same time

Red flag: The report owner is whoever notices the deadline first.

3

Gather the numbers before you write

The report is the easy part once the data exists. The scramble is finding it.

  • Spending for the reporting period is pulled by grant and by approved budget category
  • Spending matches the general ledger, and any difference is explained
  • Match or cost-share amounts for the period are documented, if the grant requires them
  • Program numbers (people served, units delivered, outcomes) are collected the same way every period
  • The data sources for each metric are written down, so the next report uses the same ones
  • Variances from the budget or the work plan are known before the report is drafted
  • Drawdowns or reimbursement requests for the period reconcile to what was reported

Quick test: Could you produce this quarter's spending by budget category today, in under an hour?

4

Make the financial and program reports agree

Funders read both. When the two tell different stories, questions start.

  • The reporting period on the financial report matches the program report
  • Activities described in the program report are reflected in the spending
  • Personnel costs charged match the staff time described
  • Big changes in spending pace are explained in the narrative
  • Numbers that appear in both reports are identical, down to rounding
  • Prior-period corrections are called out rather than quietly absorbed

Red flag: Finance and program staff prepare their reports without seeing each other's.

5

Have the backup ready

Funders rarely ask for support documents until they do. Assemble them as you report, not after.

  • Invoices, receipts, and proof of payment for the period's major expenses are filed with the grant
  • Timesheets or personnel activity records support payroll charged to the grant
  • Procurement or bid documents exist where the grant requires them
  • Subrecipient or partner reports are in hand before you report on their work
  • Deliverables mentioned in the report (curricula, photos, surveys, products) are saved
  • Any required certifications or signatures are current

Quick test: Pick two expenses from the last report. Can you prove each one in five minutes?

6

Submit it right, then keep the record

A report that was sent but cannot be found is a report that was never sent.

  • The report is submitted the way the funder requires: portal, email, or signed PDF
  • A copy of exactly what was submitted is saved with the grant file, with the date
  • The confirmation, receipt, or portal screenshot is saved with it
  • Questions from the funder, and your answers, are filed with the report
  • Anything the funder asked you to fix is written down and fixed before the next report
  • The next report's due date is confirmed and still on the list

Red flag: You know the report went out, but not what was in it or when.

Risk scan

If several of these feel true right now, your next report is already at risk.

  • Report due dates are tracked in more than one place, or in nobody's
  • Reports are started the week they are due
  • Spending by budget category takes days to pull together
  • Finance and program numbers have disagreed in a past report
  • Support documents are gathered only when a funder asks
  • Nobody can say what was in the last report without opening it
  • One person holds every reporting deadline in their head

Self-score

Give yourself 1 point for every statement you can honestly say is true.

  • Every report and due date is listed in one place
  • Each report has a named owner and a start date
  • We can pull spending by grant and category quickly
  • Our financial and program reports agree
  • Backup documents are filed as we go
  • We keep a copy and confirmation of every submission
  • Someone reviews each report before it goes out
  • Funder questions and fixes are written down

7 to 8: Strong foundation

4 to 6: Some gaps, manageable if addressed now

0 to 3: High risk of preventable problems

Next step

Want the due dates, the backup, and the numbers in one place?

GrantGuard reads your grant agreement, puts every reporting deadline on one calendar with alerts, keeps supporting documents with the requirement they prove, and tracks spending against the approved budget, so each report starts from a file that already exists.

Start Free 30-Day Trial Book a Demo
Print this page to save as PDF

Related guides