Playbooks · Small-team tasks
Draft a grant report an agent checked against your own numbers
Written October 27, 2026
For nonprofit staff × drafting a grant report × ChatGPT, ending with a draft that follows the funder's own template, with every number traced to a source export — reviewed and signed off by a named person before it is sent.
Before you start
You need the funder's own reporting instructions and template for this grant, the award letter or grant agreement, the original application or proposal as approved, the approved budget, and the source exports the numbers will come from — the accounting export for spending, and the program records for activities and results. You also need the name of the person who will review and sign off the report, and the funder's stated due date and submission route for this report. If any of those are missing, the first job is to find them, not to start drafting. A report drafted before the funder's template is in hand will be drafted to the wrong shape, and reshaping it afterward is where numbers get moved into the wrong boxes.
The workflow below is built on two real funders' published reporting pages and on the federal performance-reporting rule, cited in the Sources section. Those sources are examples of how funders differ. Your funder's own instructions govern your report, and where they differ from anything on this page, they win.
What "done" looks like
At the end of one sitting you have a draft that follows the funder's own headings in the funder's own order, a number table in which every figure in the draft is traced to a named source export, a list of the gaps where no source existed and the draft says so, and a named reviewer's sign-off that every number was checked. Nothing in the draft claims a result, a spend, or a date that the source material does not support.
Steps
- Collect the funder's own packet before the agent sees anything. Put four items in one folder: the funder's reporting instructions and template for this grant, the award letter or grant agreement, the original application or proposal with its stated objectives, and the approved budget. Note the due date and the submission route exactly as the funder states them. Funders differ in what they ask for and how it must arrive. The Foundation for Food & Agriculture Research, for example, requires three reporting components — a narrative report and an indicator report filled out as online forms, and a financial report as a spreadsheet — and states that uploads of the online forms are not accepted. JHF requires a final report made of two completed templates, narrative and financial, plus supporting proof. A workflow that assumes one funder's shape will misfit the next funder's. Start from this funder's packet, every time.
- Make the agent restate the objectives from the original application, word for word in substance. Give the agent the objectives section of the original application and ask for a plain list: each objective as stated, with nothing added and nothing reworded into a stronger claim. JHF's reporting page requires the final report to show the results of the project and compare them with the objectives as stated in the original application. The federal performance-reporting rule at 2 CFR 200.329 likewise requires a comparison of accomplishments to the objectives of the award established for the reporting period. That comparison is the spine of the report. If the agent restates an objective more ambitiously than the application states it, the report will be measured against a promise the organization never made.
- Build the number table before any prose exists. Give the agent the source exports only — the accounting export and the program records — and ask for a table with four columns: the figure, the source file it came from, the period it covers, and the objective or budget line it belongs to. Tell it explicitly: a figure with no source file is left blank and marked as missing, never estimated, rounded into existence, or carried over from an earlier report. The Foundation for Food & Agriculture Research requires grantees to use the budget template submitted and approved with the grant agreement for the financial report, and JHF requires itemized revenues and itemized expenditures each compared to the project budget in the original application. So build the table on the approved budget's own lines, in the approved budget's own categories, not on categories the agent invents. A number table built first keeps the prose honest; prose written first invents numbers to fill its sentences.
- Draft under the funder's headings, in the funder's order, and nowhere else. Give the agent the funder's template headings and the checked number table, and ask for a draft that uses those headings and that order, with no added sections and no renamed headings. Where the funder asks for a result, the draft states the result from the number table and the source behind it. Where a goal was not met, the draft says so plainly and gives the reason only where the source material gives one. The federal rule requires explanations of why established goals or objectives were not met, and additional information, analysis, and explanation of cost overruns or higher-than-expected unit costs. A shortfall with no explanation reads as an omission; a shortfall explained with a reason the records do not support reads as an excuse. Mark the reason as unknown where the records do not give one, and let the reviewer decide what, if anything, can honestly be added.
- Keep narrative, indicator, and financial material in their own places. Do not let the agent merge the three kinds of material into one document where the funder keeps them separate. The Foundation for Food & Agriculture Research keeps them as three components — narrative, indicator, and financial — plus a signature page, and its indicator report captures a standard set of 14 indicators described in its handbook, which tells grantees what to count. JHF keeps narrative and financial reports as two separate templates, with supporting proof uploaded alongside. If your funder uses an online form, draft the text for each field and enter it in the form; do not upload a drafted document in place of the form. If your funder requires a signature page or a certification, leave it blank for the named person to complete — the agent does not sign, certify, or attest to anything.
- Check every number a second time, from the export, not from the draft. The reviewer — a named person, not the person who drafted — opens each source export and checks each figure in the draft against it: the amount, the period, and the budget line. Then the reviewer checks the comparisons: spending against the approved budget line by line, and results against the objectives as stated in the original application. Any figure that does not match its export is corrected from the export or deleted. Any comparison the draft makes that the exports do not support is deleted. This check is the whole point of the workflow. An agent that drafted the numbers and then checked its own draft would only confirm its own reading; a second person checking from the source is what catches a figure copied into the wrong line.
- Record changes, delays, and problems in the funder's own terms. If the scope, timeline, budget, or personnel changed during the period, state the change and, where the funder requires it, use the funder's own change process rather than burying it in the narrative. The Foundation for Food & Agriculture Research requires grantees to notify its grants team and submit the relevant changes and modifications forms where any aspect of the award changes, including scope, timeline, budget, or personnel. The federal rule requires recipients to notify the awarding agency when a significant development between reporting dates affects the award, including problems, delays, or adverse conditions, together with the plan for corrective action and any assistance needed, and also favorable developments that allow objectives to be met sooner or at less cost. If nothing changed, the draft says nothing changed. Do not let the agent smooth a delay into a revised plan without saying a delay happened.
- Sign off by name, then submit through the funder's route, on the funder's date. The named reviewer signs off that the numbers were checked against the source exports and the draft follows the funder's template. Only then is the report submitted, through the route the funder states, by the date the funder states. The Foundation for Food & Agriculture Research states annual progress reports are due within 30 days after the end of each annual funding period and final progress reports within 90 days after the expiration or termination of an award, and that applicable disbursements will be delayed if all required reports and forms are not received by the due date. JHF requires the final report within three months after completing the project. Those are those funders' dates, not a general rule — use the date in your own award letter. Keep a copy of exactly what was submitted, with the number table and the sign-off, so a later question about a figure can be answered from the same material.
Check the agent's work
- Check that the draft's headings and order match the funder's own template, with no added or renamed sections.
- Check that every number in the draft appears in the number table with a named source file, a period, and a budget line or objective — and that no number appears in the prose that is missing from the table.
- Check that the objectives in the draft match the original application as stated, and that the comparison of results to objectives covers each objective, including the ones not met.
- Check that spending is compared line by line to the approved budget, using the approved budget's own categories, and that any overrun or shortfall is explained only from reasons the records support.
- Check that changes to scope, timeline, budget, or personnel are stated plainly and handled through the funder's own change process where one is required.
- Check that the signature, certification, or attestation is completed by the named person, not by the agent, and that the report was submitted through the funder's route by the funder's date.
What can go wrong
- Drafting to a generic template. A generic grant report reads well and fits no funder. It will be reshaped under deadline, and reshaping is where figures land in the wrong boxes. The funder's template first, always.
- Letting the agent estimate a missing number. A blank in the number table is honest and fixable. An estimated figure in a submitted report is a false statement about spending or results, and it will not survive a check against the export.
- Carrying a figure from an earlier report. A figure from a prior period looks right because it was right once. If it is not in this period's export, it does not belong in this period's report.
- Rewording an objective into a stronger promise. A restated objective that sounds more ambitious than the application makes the real results look like a shortfall, and invites a question the organization cannot answer from its own records.
- The agent checking its own draft. A self-check confirms the draft's own reading of the exports. The check that matters is a named person reading the exports and the draft side by side.
Limits
- The Foundation for Food & Agriculture Research and JHF are examples, not a survey of funders. Their templates, components, and due dates are theirs. A reader's funder may use a single form, a different set of components, or different dates, and the reader's award letter and instructions govern.
- The federal rule cited here, 2 CFR 200.329, governs performance reporting for federal awards as stated in the rule. It does not set the reporting rules for a private foundation's grant, and this page does not present it as doing so. Where an award is a federal award, the award's own terms and conditions state what applies to that award.
- Nothing here promises that a report drafted this way will be accepted, or that it affects future funding. Acceptance depends on the funder's own review of the submitted report.
Related playbooks
- Baseten Grid routes coding-agent traffic
- Claude Code pools budgets and reports costs via API
- Copilot Agent Merge: watch a PR and fix its blockers
- Currents Sessions: one link per agent task
Sources
Sources: Foundation for Food & Agriculture Research on annual and final reports, JHF on reporting requirements, 2 CFR 200.329, Monitoring and reporting program performance.
Back to: Small-team playbooks hub · Skills index