You have willing people but nothing real for them to do, or you recruit volunteers into vague roles they drift out of, and no one is clearly coordinating any of it.
This guide fixes the foundation: meaningful, bounded roles worth a volunteer's unpaid time, and the basic structure that holds the program together. It is the part that must exist before recruiting makes sense. It is not recruitment, training, or retention; those come after and stand on this. It is not a corporate volunteer department; it is the few things a lean organization needs. And it is not a way to get free labor for whatever is undone; it is about designing roles a volunteer would genuinely want.
What it will take: honest thought about what work truly suits a volunteer, and a decision about who coordinates them. What must be true first: you know what your organization does. If roles are unclear because the programs are, that comes first.
Not all work suits a volunteer, and using volunteers for work that needs paid staff sets everyone up to fail. List the work you would like help with, and for each ask honestly: does this genuinely suit a volunteer, someone giving bounded time from goodwill, or does it really need the reliability and hours of paid staff.
Stop. That is a staffing and money reality, not a volunteer-design problem. Volunteers can extend your capacity, but they cannot be the paid team you actually need. A route, not a stop. The staffing and HR work, and the money side of it, which is financial health and management.
A volunteer gives time for meaning, so a role has to offer meaning, a clear ask, and a real contribution, not leftover tasks. For each volunteer-suitable area, write a role: what they will do, why it matters to the mission, the time it asks, the skills it needs, and who supports them. Make it bounded and real, so a volunteer knows the ask and feels the point.
Continue in the Volunteer Role Designer, the design part →A volunteer program with no one coordinating it and no place in the organization runs on the executive's spare minutes and falls apart. Decide who coordinates volunteers, even if part of someone's role, how volunteers work alongside staff, and who a volunteer goes to when they need something.
Open the Volunteer Program Structure, the coordination part →You cannot recognize, schedule, or keep in touch with volunteers you are not tracking, and a program that loses track of its people loses its people. Decide how you will keep basic records: who your volunteers are, their roles, their hours, and how to reach them, in whatever simple form you will actually maintain.
Continue in the Volunteer Program Structure, the tracking part →The clearest edge in this guide is the one in Step 1: volunteers cannot be the paid team you actually need. If your program design keeps running into work that genuinely requires reliable, paid hours, that is a real limit, and the honest move is to name it and take it to the staffing and HR work, not to keep asking volunteers to carry what should be a job. And if roles could not be designed because the programs are unclear, that is the mission and direction work or the program design work.
Every volunteer role is meaningful, bounded, and worth someone's time. Someone clearly owns the volunteer program. And you can say who your volunteers are and how to reach them.
Most leaders move from here to Recruit Volunteers, because good roles are worth filling well. Recruit Volunteers →
And if you came to Elementum in a crisis and have steadied, the whole-organization check-up is the honest next look, when you are ready. The whole-organization check-up →