Final grant report template for funders: narrative and budget

A final grant report is the funder's record of what a grant did. It answers two questions: what happened against what the grantee proposed, and where the money went. The best final report templates are short, ask for things the grantee already tracks, and tell the grantee exactly what "complete" means, so you are not writing follow-up emails for a month.

This guide gives you a template to send grantees, written from the funder's side: the narrative questions, the financial table, how to word the request, and a checklist for reading what comes back. Edit it to match your grant agreements. Every foundation asks for slightly different things, and the agreement is what governs.

Before you write the template

Three decisions make the rest easier.

Ask for what the proposal promised. The final report should mirror the goals, targets and budget in the approved proposal. If the proposal said "serve 1,200 people", the report should say how many were served. Keep a copy of the proposal's goals next to the template.

Keep narrative and money separate. Many foundations ask for a final narrative and a final financial report as two documents with the same due date. Grantees often have different people write them: a program director for the narrative, a finance manager for the numbers.

Accept documents grantees already have. If a grantee's annual report or board report answers your questions, let them send it with a short cover note. You are collecting evidence, not testing writing.

Template: final narrative

Send this as the requirements for the final narrative. Each line is one thing the report must cover.

1. Outcomes against the goals in the proposal. For each goal, what was achieved, with the measure you agreed on.
2. Numbers served or outputs for the full grant period. Compared with the targets in the proposal, with the period they cover (for example July 2025 through June 2026).
3. What did not go as planned, and what you learned. Changes to activities, timeline or staffing, and why.
4. At least one client or participant story, without names. One concrete example of the work, written so nobody can be identified.
5. What happens next. Whether the work continues, and how it will be funded. Optional, but useful for your next round.

Suggested length: two to five pages. Tell grantees that an existing report covering these points is fine.

Template: final financial report

The core of the financial report is a budget-to-actual table: each line of the approved budget, what was spent, and the difference.

Ask for:

1. Budget-to-actual for the grant period, by line item, in the format of the approved budget.
2. An explanation of any line that differs from the budget by more than 10%. Pick your own threshold; 10% is a common starting point, not a rule.
3. Total grant funds spent, and any unspent balance. What the grantee proposes for an unspent balance is a conversation governed by your agreement.
4. The name of the person responsible for the figures, and a signature if your foundation requires one.

If the grant was general operating support, a full organizational budget-to-actual or the most recent audited financial statements may be more appropriate than a line-item table.

How to word the request

Grantees respond faster to requests that are specific and short. Include the grant ID, the report name, the due date, the requirements above and how to send the report. Put everything due in one email rather than a separate message per report.

Hello [first name],

[Foundation] has these reports due for [organization]: Final narrative (Grant [ID]), due [date], and Final financial report (Grant [ID]), due [date].

Each report should cover the points listed on the upload page. An existing report that covers them is fine.

If you need more time, tell us the date you can meet and why.

Send the first request about 30 days before the due date, with reminders closer to it. Final reports due on common fiscal year ends, such as June 30 and December 31, often arrive late because grantees are closing their own books at the same time; asking early helps.

Checklist for reviewing a final report

When the report comes back, read it against the same list you sent.

• Every goal in the proposal is addressed, with a number where one was promised.
• The period covered matches the grant period.
• The grant ID or name appears, so the file is clearly about this grant.
• The story has no names or identifying details.
• The financial table totals add up and match the grant amount.
• Each line over your variance threshold has an explanation.
• Any unspent balance is stated.
• Anything missing is listed in one follow-up email, specific enough that the grantee can answer in one reply.

A good follow-up names the gap, not the grantee's failure: "Please include a short story about one participant's experience, without their name." One clear ask beats three vague ones.

Using the template in Report Back

Report Back ships with editable starters close to the ones above: interim narrative, final narrative, final financial report and a monthly reimbursement packet. You edit them once per report type, and grantees see them on their link page next to the upload. When a report arrives, Report Back compares it with each requirement and lists what looks met, unclear or missing, with the quoted passage where it found one, plus a drafted follow-up for the gaps. It does not decide whether a report is acceptable; you do.

For choosing a tool around the template, see foundation grants management for a small funder. For pass-through reporting from subrecipients, see our subrecipient monitoring checklist.