What You Will End Up With
You will have a repeatable workflow that takes you from raw program data to a donor report you have checked line by line, without starting from a blank page. The assistant does the drafting, reordering and reformatting. You keep the facts, the figures and the judgment.
That matters because a report is how you show a funder that the money went where the application said it would, and it is the main way you are held accountable to that funder. So the time you save on drafting goes into verification and into an honest account of setbacks as well as successes.
Before You Start
Decide what you will use an assistant for and what you will keep. Use it as a drafting aid: reordering text so findings come first, adapting a core report to a different template, shifting tone for a particular reader, and turning rough notes into a structure. Keep the fact checking, your unit costs and your reading of contract rules to yourself, because the accountability you owe the funder stays with you.
Requirements also differ. Some funders want no written report, some accept a verbal update, and others want an extensive report in their own template. Read your agreement to find out which applies to you.
Gather these before you open any tool:
- The original funding application and the signed agreement.
- Any special or additional provisions attached to the award, which bind you just as the main text does.
- The reporting schedule and check-in points, which are sometimes agreed only after work starts.
- Current year-to-date actuals and a budget-versus-actual summary.
- Program results, with your notes on what went wrong as well as what went well.
Then decide who the primary reader is, and whether they need a short brief or a longer document.
Steps
Treat the assistant as a drafting aid, never as the author. Every step below starts from facts you have already confirmed.
-
Build a core narrative from verified facts. Many funders ask for broadly the same information in different words, so write one thorough report a year and adapt it later. Assemble a plain list of confirmed facts, not messy notes, and organize it under the usual themes: program status, planned versus actual results, outcomes and impact, and lessons learned. Ask: "Using only the facts listed below, draft a narrative section on program outcomes. Do not add anything that is not in the list. If something seems missing, tell me instead of filling it in." Then paste the list.
-
Draft the financial narrative. A typical report pairs a budget-versus-actual summary with a narrative of activities. Where variances are significant, a short exception report helps. Paste only figures that have already been approved for reporting, and ask: "From these figures only, draft a brief narrative on the largest variances. Quote the numbers exactly as given." Afterward, check each sentence against the actuals yourself. The narrative has to agree with the financial report.
-
Put the finding first. A program officer with many grants tends to read in a fixed order. Ask: "Rewrite each section so it opens with the result, then gives the evidence. Use only the text I provided, and keep every figure unchanged." Read the output to confirm the evidence still supports the opening line.
-
Restore the balance. A credible report describes setbacks next to successes. Ask: "Check this section against my notes on challenges. Make sure each setback is described with the same detail as each success. Do not invent causes or fixes." Compare the result with your notes and put back anything that was smoothed away.
-
Adapt the core report to each funder. Paste the funder's own questions and the matching section of your core report. Ask: "Answer this question using only the text below. Keep all figures and facts exactly as written." Reports on general operating support are usually simpler. Project reports need detail from program staff, so get it from them first and add it to your fact list before asking the assistant to draft anything.
-
Run the verification pass. This is the step that protects you.
- Highlight every number, date and percentage in the draft.
- Trace each one to its source: the financial actuals, the program data or the agreement.
- Delete any claim you cannot trace, however plausible it sounds.
- Check any quote against the original record, word for word.
If a single chart can replace a page of text, use it, and put more complex visuals in a labeled annex. When the report is final, share it with the field staff and partners who contributed. Carry any unresolved challenges into the next work plan.
Using AI Safely
Settle what may go into the tool before you paste anything.
Never paste:
- Personal information about program participants or staff, including names, contact details and case notes.
- Financial records that have not yet been approved for reporting.
- Anything your grant agreement or your own policy says you must not share.
- Unredacted contracts.
Do your own arithmetic. A unit cost is the actual cost of a program divided by the actual number of people or targets reached. Work it out from your records, then give the result to the assistant as a fact to be used, never as something to be computed.
Verify everything that comes back. If you cannot tell where a statement came from, treat it as invented until you find its source.
Common Mistakes
Asking the assistant to write the report. A general request such as "write our quarterly report" gives the assistant no facts to stay within. Supply the data first and tell the tool to use only what you provided.
Skipping verification. A report is the main way a grantee is held accountable to a funder, and a drafted paragraph can carry a figure you never confirmed.
Using one prompt for every reader. A compliance-focused reader needs different framing than a general audience. Decide who you are writing for and adjust the request.
Leaving contract rules to the assistant. Some obligations flow automatically to subawards and contracts. Retention rules can come from more than one place, and the guidance this page draws on is to use the longest of the relevant statute of limitations, the agreement's own requirement and any general minimum retention table. Check which of these apply to you, and read the agreement itself.