A volunteer organization runs on a scarce resource: time given freely, in small amounts, by people with a life elsewhere. Every minute spent hunting for information or chasing someone comes out of that.
Here's how to structure the way your organization works without imposing a tool nobody will open.
In a volunteer organization, it's the knowledge that gets lost
The tasks always end up getting done.
How to book the venue, which supplier was good last year, the deadline for filing the grant application, the door code for the storage room. That information lives in three people's heads, and it leaves when they do.
When the committee changes hands, the new team rediscovers everything, repeats the same mistakes and spends a year recovering what was already known.
So before listing tasks, write down what transfers badly. One note per recurring procedure is enough: booking the venue, running the general meeting, putting together a grant application.
Organizing your projects around ongoing workstreams
Create one project per ongoing workstream rather than a single catch-all for the year.
| Project | What it gathers |
|---|---|
| Running the organization | General meeting, memberships, administrative obligations |
| Spring event | Everything to do with that one event |
| Communications | Social media, posters, press relations |
| Funding | Grants, partnerships, membership fees |
Each project holds its own tasks, procedure notes and documents. The event project closes once the event is over; the others run all year.
Setting milestones on the dates that won't move
A volunteer organization works against fixed dates: a filing deadline, the date the venue is booked for, the day of the event.
Set those dates as milestones in the relevant project, and attach to them the tasks that have to be finished first. You get a backwards plan without drawing one: what's left to do before each deadline is visible at a glance.
Write the procedure down while you're doing it
Five minutes when you book the venue are worth three hours to whoever takes over from you.
Sharing out the work without chasing anyone
In volunteering you can't demand, only ask. And chasing five people one by one by message eats a whole evening.
Two principles help more than any tool.
A task has a name and a date, or it doesn't exist. "Someone could handle the poster" produces nothing. "Sarah is doing the poster for the 12th" produces something, or at least a clear no.
Tracking is public, not private. When everyone can see how the project is moving, chasing people individually is rarely necessary. What's missing is obvious to everyone at the same time.
A shared calendar for shifts and meetings
Volunteer organizations run on slots: drop-in shifts, rehearsals, committee meetings, the day of the event.
A shared calendar saves the endless back-and-forth over who's around on Wednesday. The practical setup is covered in sharing a calendar across a team, and if your organization already publishes a calendar, subscribing to an .ics feed lets you pull it in without retyping it.
Preparing the handover now
A handover is prepared all year, by writing things down as you go, not in June when the committee changes. It's the advice everyone takes too late.
An organization whose procedures are written down can change its team without losing its know-how; one that runs on memory starts from scratch at every changeover.
If the most involved person in your organization stopped tomorrow, how much would stop with them?
For the underlying mechanics, see getting started with projects and recurring tasks and routines, useful for everything that comes back every year.
What your organization knows, written down somewhere.
