Make grant reporting easier by asking better questions after events
Short answerAn attendance count cannot explain what happened at an event. Ask what the team did, what participants experienced, and how it connects to the program's goal — at intake, while someone still remembers.
An attendance total can tell you how many people came to an event. It usually cannot explain what the team did, what changed for participants, or why the work mattered.
In a nonprofit event-reporting project, I redesigned intake questions to capture those parts of the story alongside the numbers. The work connected field reporting with the information a development team needed for grant narratives.
The missing context
A fundraising colleague preparing a report may not have attended the event. If the intake form only asks for a title, date, and headcount, that colleague has to reconstruct the rest later.
The project used three prompts: the effort taken, the direct community impact, and the strategic significance of the work. In everyday language, those are questions about what happened, what people experienced, and how the activity connected to a larger goal.
My role was to help structure the workflow and the information collected. The available archive describes the redesign but does not provide a measured number of hours saved.
What the questions can look like
For a similar form today, I would use prompts such as:
- What did your team do at this event?
- What did participants do, learn, or tell you? Include an observation you can support.
- How does this activity connect to the program's goal?
These are suggested prompts for a new form, not a verbatim copy of the original project form.
A useful answer can be brief. The aim is to preserve enough context for someone else to understand the activity. If a result is not yet known, the form should allow the organizer to say so.
Keep observations separate from conclusions
Someone attending a workshop does not, by itself, demonstrate long-term behavior change. A useful reporting process makes that distinction visible.
Record what the team observed, what participants reported, and what still needs follow-up. That helps a writer explain the work without turning an encouraging anecdote into a claim the evidence cannot support.
Start with the next report you need to write
Look at a recent reporting request and identify the information that required extra follow-up. Add only the questions that would have helped capture that context at the time.
Google Forms and a shared internal reporting process may be enough to start. Decide who reviews responses and how the development team receives them before adding automation.
Explore reporting workflow support, or tell me what your team keeps chasing before a reporting deadline.