The Small-Nonprofit Grant Reporting Checklist

For a small nonprofit, a grant report is where a season of real program work turns into a scramble. The deliverables were met and the money was spent well — but the evidence is scattered across inboxes, spreadsheets, and someone’s memory, and the report is due Friday. The fix isn’t working harder the week it’s due. It’s having a repeatable checklist you run every time, so nothing gets missed and nothing gets invented at the last minute.

This is that checklist. It works for most foundation and state grant reports, and it’s built for organizations where reporting lands on one or two non-technical staff.

Before you start: gather four things

Ninety percent of reporting pain comes from hunting for information that already exists. Pull these together before you write a single sentence:

• The signed grant agreement.Not the application — the executed agreement. It defines what you promised, what you’ll be measured on, and the exact reporting format and dates.
• Budget vs. actuals for the grant. What you were funded for, against what you actually spent, by line item. Ideally straight from your accounting system so the numbers are defensible.
• Your outcome and output data. The counts, percentages, and stories that show what the money accomplished this period.
• Last period’s report.It sets the baseline, keeps your narrative consistent, and reminds you what you told the funder you’d do next.

What every grant report needs

Formats vary, but nearly every funder report is built from the same six parts. Miss one and you’ll get a follow-up email — or a delayed payment.

• Identifying details. Grant number, reporting period, program name, contact person. Boring, and the fastest thing to get wrong.
• Narrative progress. What you did this period, in plain language, tied to the goals in the agreement.
• Outcomes against targets.Each metric you committed to, the target, the actual, and whether you’re on track.
• Financial report. Spending by budget category, usually with budgeted, spent-this-period, and spent-to-date columns.
• Variance explanations. A short, honest note anywhere the plan and reality diverged — in either the numbers or the program.
• Evidence and attachments. Receipts, photos, participant lists, or data exports the funder asked for as backup.

Financial vs. narrative — and why they must agree

The single most common reason a report gets bounced back is that the numbers and the story don’t match. Your narrative says you served 200 families; your financials show you only spent a third of the direct-services budget. Both might be true and explainable — but if you don’t connect them, the funder has to ask.

Read your two halves side by side before you submit. Every major spend should be visible somewhere in the narrative, and every accomplishment you claim should have a plausible cost behind it. When they line up, the report reads as trustworthy. When they don’t, it reads as sloppy — even when the work was excellent.

A good report doesn’t just report numbers. It makes the numbers and the story tell the same truth.

The reusable grant reporting checklist

Run this list before every submission. Copy it into a doc, keep it next to the report, and check off each item:

• Reporting period and grant number match the agreement exactly.
• Every committed metric appears, with target vs. actual.
• Financials reconcile to your accounting system, not a side spreadsheet.
• Budget categories match the ones in the awarded budget.
• Every variance over your funder’s threshold has a one-line explanation.
• The narrative references the same wins and spends as the financials.
• All required attachments are named, dated, and included.
• The submission format matches what the funder asked for (portal, PDF, template).
• A second person has read it end to end.
• You’ve saved a dated copy for next period’s baseline.

Five mistakes that cost small nonprofits

Most reporting problems aren’t about program quality. They’re avoidable process slips:

• Starting the week it’s due. The data you need takes days to assemble, not hours. Begin the moment the period closes.
• Reporting activities instead of outcomes.“We held 12 workshops” is an activity. “83% of attendees passed the certification” is an outcome. Funders fund outcomes.
• Hiding variances. Funders expect plans to shift. An unexplained gap looks worse than the honest reason behind it.
• Numbers that don’t reconcile. If your report and your books disagree, the report loses.
• Reinventing it each time. Without a saved baseline and checklist, every report starts from zero.

Two companion guides go deeper on the parts small teams struggle with most: how to never miss a grant report deadline and what funders actually want in a progress report.