Grant reporting evidence

Read the reporting request first

Collect the award agreement, current reporting template and any later instructions from the funder. Confirm the period the report covers before asking staff for numbers. A calendar year, fiscal year and award period may not match. Write the actual question above each draft answer so the team can see whether it is being answered. Grantkeeper can organize the template and match supplied records to questions. It should not substitute a generic success story for a requested measure. If two instructions conflict, keep both sources and ask the grant owner to clarify them with the funder. Do not silently choose the easier version.

Make an evidence map

For each question, list the source file, page or table, reporting period and person who can confirm it. Mark the evidence as supplied, needs checking or missing. A link to a folder is less useful than a link to the particular report and the relevant section. Keep source versions visible, especially if staff correct a count after the first draft. Grantkeeper can prepare this map from the records you provide and flag questions with no support. The map is a review aid, not a certification that the records are complete. Ask each owner to confirm their part before the director reviews the full report.

Keep counts and outcomes separate

An activity count says what happened: workshops held, sessions delivered or households recorded. An outcome describes a change and needs evidence suited to that claim. Do not turn attendance into an improvement claim without a checked measure. The same person may appear in several sessions, so distinguish visits from unique participants when the source supports that distinction. If it does not, say which count you actually have. Grantkeeper can compare the wording of a draft with the supplied table and ask about a mismatch. Program staff decide the correct interpretation and provide the source; the assistant does not infer a life change from a sign-in sheet.

Ask finance for the right expense export

Give finance the award ID, reporting period and the funder’s requested categories. Ask for the checked export they want used, with its date and report settings. Keep the exported figures beside the narrative without changing the ledger. A receipt can support a transaction, but a pile of receipts alone does not establish the report total. Grantkeeper can gather and organize receipts, link them to supplied expense rows and flag missing references. It does not decide whether a cost is allowable, reclassify expenses or certify an award balance. Those questions go to the finance lead and, where necessary, the funder through the grant owner.

Turn gaps into specific staff requests

A useful request names the exact question, period and missing item. Please send the September attendance table by Thursday is easier to answer than please send impact data. Include the draft sentence the record is meant to support so the owner can spot a wrong assumption. Grantkeeper can prepare these requests for you to send and group them by staff owner. Do not mark a request answered merely because someone replied; check whether the file or explanation resolves the actual gap. Keep the answer with the source records and update the evidence map. This prevents the director from discovering the same unanswered question at final review.

Write a draft that preserves uncertainty

Use checked facts in short sentences and keep open questions visibly labelled. If a target was missed, state the recorded result and ask the program lead for the reason and planned response. Do not invent an explanation that sounds reasonable. Separate the award’s stated target from the actual period result and any proposed next step. Grantkeeper can shape the material into a readable draft while leaving unsupported claims out. Keep any personal story anonymous unless the organization has approved the intended use through its own process. A report does not need private details to explain a documented program change, delay or lesson.

Review and record the actual submission

Ask program and finance owners to check their sections, then give the director a draft with the evidence map and unresolved questions. Keep a final file that matches what was submitted. Record who submitted it, when and through which route, along with the portal receipt or other confirmation. Grantkeeper preparing the document does not mean the funder received it. If the submission route rejects a file or a required field is unclear, keep the issue open for the grant owner. Save the funder’s follow-up questions and carry them into the next reporting plan so the team can collect the needed evidence earlier next time.

Keep a source trail

Keep the original files beside the working draft. Give each file a clear date and keep later corrections as new versions. A sentence that contains a number should point to a record that another person can open. If a source is missing, keep the question visible rather than filling the space with a plausible answer. Remove private details that the reader does not need. A public update, a staff task list and a finance working paper can use the same checked fact, but they need different access. Test folder permissions with the person who will receive the finished work.

Leave a useful handoff

Finish with the next action, its owner and the date someone will check it. Save the reviewed version where the team already looks for this work. Tell the next person what changed and which questions remain open. Do not mark a task complete because a draft exists. Completion means the person responsible has confirmed the actual result, such as a checked document, a corrected record or a message that was sent. At the next review, start with unresolved items rather than rebuilding the whole process. This keeps a small team’s routine manageable when a volunteer is away or a staff role changes.

Related recipes: Missing evidence list, Grant report draft, Receipts to expense sheet. Integrations: Google Drive, Asana, QuickBooks.