Convert what your program does into the outcomes language funders require: activities → outputs → outcomes → impact, with measures for each.
Convert our work into outcomes language. What we do: {{activities}} (the program, who it serves, what we count today, the change we believe we make). Build the chain: activities (what we do) → outputs (what we count: sessions run, people served — the easy layer) → outcomes (what CHANGES for participants: knowledge, behaviour, circumstances — short and medium term, each with a realistic measure: the pre/post question, the follow-up check, the observable marker) → impact (the long-term change we contribute to — with the honest 'contribute' framing; claiming sole credit for community-level change reads as naive). Then: the measurement reality check (what we can actually collect with our capacity — two good measures beat six abandoned ones), the funder-language mapping (their priority words matched honestly to our chain), and the theory-of-change one-liner: 'because we do X, participants achieve Y, contributing to Z.' Flag the weakest link in my chain — where belief outruns evidence.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekA minute-by-minute run sheet for a community event: the timeline, volunteer roles with names, the co...
Write a fundraising appeal that moves people: one beneficiary story, the concrete ask ladder, and st...
Design a volunteer program that keeps people: role clarity, the onboarding that respects their time,...
Write a grant acquittal that funders remember: outcomes against the promises, the money story clean,...
Prepare a committee meeting pack for a volunteer board: short papers with clear asks, the finance sn...
Run a membership renewal campaign for an association or club: the value reminder, the renewal sequen...