How to Run a Volunteer Rota Without the Group Chat Doing the Work
A Saturday club running three rooms across a 12-week term, with two adults required in each room, needs 72 adult slots filled. If 19 people have said yes to helping, that is under four sessions each, which sounds easy until you try to book it in a WhatsApp group. The DCMS Community Life Survey has tracked a fall in regular formal volunteering in England since 2019/20, so most groups are filling the same number of slots from a smaller pool than they used to.
TL;DR
Assign named volunteers to named dates for a whole term at once, publish the draft, and let people correct their own line rather than asking a chat who is free. Open availability requests hand the planning work to the people least equipped to do it and leave the coordinator personally on the hook for every gap. Keep the rota, the swap history and the vetting status in something the organisation owns, with the sensitive part behind a role that two people hold. Bitir carries the rota as dated assignments against named volunteers inside a private group, records who actually turned up, and keeps the whole history when a coordinator hands over.
Why do volunteer rotas fall apart in a group chat?
Because a chat has no idea who is responsible for Saturday.
The pattern is the same in a Scout hut, a Saturday supplementary school and a community sports club. The coordinator posts "who can cover this weekend?", three people reply within the hour, four reply on Friday night, two of the replies are conditional, and the message thread is 40 items deep by the time anything is settled. Next week it starts again from zero, because nothing that happened is now readable.
Four specific failures come out of that.
- The willing get worked hardest. Whoever reads notifications fastest ends up covering the most sessions, and nobody notices until they burn out and leave.
- Nothing is planned more than a week ahead. Volunteers with caring responsibilities or shift work cannot commit at 48 hours' notice, so they gradually stop being asked.
- The record lives in the coordinator's head. When they step down, the group loses the rota, the swap conventions and the knowledge of who is checked for what.
- Sensitive detail leaks into the general chat. Reasons for absence, vetting status and safeguarding notes end up in a thread that 25 people can scroll back through.
Coordinators we speak to describe the same weekly cost: "It is not the two hours on Saturday. It is the six evenings of chasing before it."
Should you ask for availability or assign the slot?
Assign the slot, then invite corrections. We would argue this firmly, and against the instinct of most volunteer coordinators, who feel that assigning is presumptuous.
Consider what an open availability request actually asks of a volunteer. They have to load the whole term into their head, cross-reference a work rota and a family calendar, and produce a list of dates in a format the coordinator can use. That is planning work, and they signed up to help run a chess club or teach a Saturday class, not to solve a scheduling problem. Most people answer it badly and late, not because they are unreliable, but because the question is expensive to answer.
A draft rota with names against dates reverses the cost. The volunteer scans for their own name, finds three dates, checks two of them and replies "the 14th does not work, I can do the 21st instead". That takes 90 seconds and it arrives the same evening.
Two rules make the assign-first approach fair rather than high-handed. Collect fixed unavailability once, at the start of term, in a single structured question rather than a chat thread. And publish the slot count per person alongside the rota, so the distribution is visible to everyone in it.
NCVO's Time Well Spent research into the volunteer experience keeps landing on the same theme: people stay where the commitment is flexible and where they feel their time is used well. A rota published six weeks ahead, with an obvious way to swap out, is flexibility. A weekly appeal to a group chat is not, whatever it feels like from the coordinator's side.
What does a workable rota look like in practice?
Priya Raval coordinates 19 volunteers at a Saturday supplementary school in Leicester that teaches 84 children in three rooms, 10am to 12.30pm, across a 12-week term. Six of the volunteers are qualified teachers, the rest are parents and two sixth-formers doing their volunteering hours. Here is the structure she settled on after two terms of chasing.
- One private group for the volunteer team, separate from the parent group. Rota traffic never reaches parents, and parent questions never bury the rota.
- The whole term is published in week zero. Each session is a dated slot with a named volunteer and a room, visible to the entire team.
- Swaps happen between volunteers, not through Priya. The convention is written down: find your own cover from the team list, then update the slot. She is copied automatically rather than asked.
- Two named reserves per week. Not "the group", which means nobody. Reserves rotate so the same two people are not on standby every Saturday.
- Attendance is recorded for adults as well as children. It takes seconds and it answers the ratio question in an inspection without anyone reconstructing a term from memory.
- Vetting status sits behind a coordinator role. Priya and one deputy can see it. Nobody else can, and it is never mentioned in a chat.
In Bitir this is ordinary widget work rather than a bespoke tool. The rota is a set of assignments with dates and named owners inside the volunteer group, the standby list is a poll at the start of term, attendance covers the adult register, and the roles editor decides who can see the sensitive fields. Our guide to roles in a group works through the permission split in more detail.
The change Priya noticed first was not the admin time. It was that two volunteers who had drifted to the edge of the team came back, because a rota published in advance is something a person with a shift pattern can actually say yes to.
How do you keep volunteers past the first term?
By counting, and by making the count public inside the team.
Almost every coordinator who counts finds a distribution they did not intend. A common shape in a 19-person team is four people covering more than half the sessions and eight covering one each. Nobody designed that. It is the arithmetic of who answers the chat fastest, accumulated over a term, and it is the single most reliable predictor of who will quietly stop volunteering by Easter.
A per-member record of sessions covered fixes it without anybody having to complain. The coordinator opens next term's planning with the actual numbers, spreads the load deliberately, and asks the four heaviest volunteers what they want to do less of.
The other half is the part groups skip. Thank people by name for a specific thing they did, in the volunteer group, not in a generic end-of-term message. Our guide to celebrating milestones without it feeling forced applies to adults at least as much as to members.
What happens when the coordinator hands over?
This is the case that decides where the rota should live, and it is the reason a personal spreadsheet is the wrong answer even when it works.
Volunteer coordinators in community groups usually stop when their own child ages out, which means the role turns over on a predictable cycle and the handover is almost always to someone who has never seen the underlying detail. If the rota, the swap history, the unavailability notes and the vetting record all sit in one person's laptop and inbox, the incoming coordinator restarts from a blank sheet and the team spends a term re-explaining itself.
Keep all four in a group the organisation owns. The outgoing coordinator's access ends the day they hand over, the record stays, and the sensitive fields stay behind the same role rather than being forwarded around by email. The same principle governs how youth organisations should handle everything else they write down, which our guide to safeguarding communication in youth groups sets out.
Write down the retention rule while you are at it. A volunteer who left four years ago does not need their absence notes kept indefinitely because deleting them was nobody's job.
Questions volunteer coordinators ask
How do community groups manage a volunteer rota?
By assigning named people to named dates for a whole term at once, then letting those people arrange swaps between themselves. Asking a group chat who is free this Saturday produces a race that the same three reliable volunteers keep winning, and leaves the coordinator personally responsible for every unfilled slot. A rota held in a private group app the organisation owns, with each session visible as a dated slot against a named volunteer, turns cover from a weekly negotiation into a plan people can read three weeks ahead.
Should you ask volunteers for availability or assign them a slot?
Assign the slot, then invite corrections. Open availability requests put the work of planning onto people who volunteered to help with the activity, not to solve a scheduling problem, and the replies arrive over five days in no usable order. A draft rota published in full gets checked in minutes because a volunteer only has to look for their own name. Collect the fixed unavailable dates once at the start of term and build around them.
Who should be able to see the volunteer rota?
Everyone rostered should see the whole rota, and nobody outside the volunteer team should see the notes behind it. Names and dates are ordinary operational information that helps volunteers swap without a broker. Vetting status, safeguarding notes, reasons for absence and contact details are not, and they should sit behind a role that only the coordinator and one deputy hold. A group app with role-based permissions splits those two things cleanly, which a shared spreadsheet cannot.
How do you stop the same volunteers doing every session?
Count the slots per person and publish the count. Most coordinators discover a distribution they did not intend, where four people cover more than half the sessions and eight cover one each. A per-member record of sessions covered makes that visible without anyone having to complain about it, and gives the coordinator a factual basis for spreading the next term more evenly before the heaviest volunteers quietly stop turning up.
Do volunteers need a DBS check to help at a youth group?
It depends on whether the role counts as regulated activity, which turns on frequency and on whether the volunteer is unsupervised with children. Occasional helpers who are always supervised often fall outside it, while a weekly section helper usually does not. The DBS does not charge for volunteer applications, although umbrella bodies charge an administration fee, so cost is rarely the real obstacle. Record the check status somewhere the organisation owns rather than in the coordinator's inbox, and keep it out of the general volunteer chat.
Publish the term, not the weekly appeal
Dated slots against named volunteers, swaps the team can make without a broker, an adult attendance record for ratios, and vetting status behind a role only two people hold. When the coordinator hands over, the rota stays with the group.
Set Up Your Group