Design a volunteer program that keeps people: role clarity, the onboarding that respects their time, recognition rhythms, and the awkward exit path.
Design our volunteer program. Context: {{context}} (the work volunteers would do, current volunteer state, what's failed before: {{failures}}).
Build: role descriptions like real jobs (what they'll do, time commitment honest, the skills grown — volunteers leave from vagueness more than workload), the screening proportionate to role (working-with-children and police checks where required — flag which roles trigger them), onboarding that respects their gift (first-day buddy, the do-something-real-in-week-one rule), the retention rhythms (recognition that's specific and public, the check-in at month 2 — that's when they drift, growth paths for the keen), the coordinator-load honesty (volunteers are not free — whose hours manage this), and the exit paths: the graceful goodbye AND the harder one — moving on a volunteer who's beloved but no longer right, with the script.
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 WeekConvert what your program does into the outcomes language funders require: activities → outputs → ou...
A 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...
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...