The most common reason volunteer coordinators quit isn't burnout from the thing they signed up for. It's burnout from the thing nobody warned them about: administration.
Call it the coordinator tax. It's the invisible overhead that accumulates every time someone needs to swap a shift, confirm an availability, pull out last minute, or ask "what time am I on again?" — and the answer has to flow through a single human being who volunteered to run the roster, not to manage a logistics operation.
It's a structural problem that community organisations rarely talk about honestly, because the people experiencing it feel guilty. They stepped up. They wanted to help. Complaining about the admin feels ungrateful, even when it's consuming their evenings and weekends.
The numbers nobody tracks
Australia's volunteer effort is enormous. The Snapshot of Volunteering in Australia 2023 — built from surveys of nearly 7,000 volunteers and close to 4,000 volunteer managers — counts over 14 million people contributing more than three billion hours a year. What nobody publishes is a figure for the hours spent organising those hours.
What those numbers don't capture is the secondary burden: the coordinators managing those volunteers. Every organisation has them. The secretary of the surf lifesaving club who spends four hours every Sunday building the next patrol roster. The junior sport convenor who handles sixty-three "can someone swap with me?" messages across three different channels in a month. The NFP events manager who maintains a master spreadsheet that only they understand, held together by conditional formatting and institutional knowledge.
These people are not employed to do logistics. They're volunteers doing logistics on top of the reason they joined.
The group chat as a rostering system
The default infrastructure for most volunteer organisations is a combination of a spreadsheet (often a PDF once published, effectively immutable), a WhatsApp or Facebook Messenger group, and one person who holds the authoritative version of reality in their head.
This works until it doesn't. The failure modes are predictable:
The coverage gap. A volunteer cancels at 11pm. The coordinator is asleep. The group chat fires up. Nobody's sure if a response is needed urgently. By morning, three people have offered and two have been given conflicting information.
The credential problem. Some roles aren't interchangeable. A patrolling lifeguard needs a current Bronze Medallion. A RSA-required bar role can't be filled by just anyone who responds to a group message. The coordinator has to manually check before any swap can be approved. Every time.
The knowledge cliff. The coordinator moves house, takes a new job, has a baby. Suddenly the organisation discovers that the "system" was a person, not a process. The succession plan is: "we'll figure it out."
Why enterprise tools don't help
The logical solution would seem to be software. And software exists — Deputy, When I Work, Tanda, and a dozen others. They're good products, genuinely. But they were designed for a fundamentally different operating context: a business with employees, a payroll system, compliance requirements, and a budget line for workforce management tools.
For a community sports club with a $300 monthly discretionary budget and a team of volunteers who are already suspicious of "yet another app," the enterprise model creates more friction than it solves. Per-seat pricing at $8–15/user/month means a 40-member patrol roster costs $400–600/month before you've filled a single shift. The onboarding assumes someone with time to configure the system. The support model assumes a business contact with authority to escalate.
The volunteer coordinator has none of these things.
The agency inversion
There's a more fundamental design issue at work in most rostering systems: they're built for downward coordination. The assumption is that a manager or coordinator creates the roster, assigns people to slots, and the system notifies assignees who then confirm. Control flows top-down.
This model works for an employment relationship where someone's paid to show up when assigned. It maps poorly to volunteers, who are choosing to give their time and whose goodwill is the engine of the whole operation.
The coordinator-as-bottleneck model is not just inefficient. It's also, subtly, disempowering. It positions the volunteer as a passive recipient of a schedule, rather than an active participant in managing their own time. Every swap request goes up to the coordinator before it can come down as approval. The coordinator becomes a fulcrum that everything must pass through, which is why losing them is so catastrophic.
The more effective model — and the one that mirrors how volunteers actually prefer to work — inverts this. The coordinator sets the rules and the roster structure. Filling, confirming, trading, and adjusting shifts happens laterally, among the volunteers themselves, with the coordinator only entering the loop when a genuine decision or exception requires them.
What this looks like in practice
A surf lifesaving club runs weekly patrol rosters across six roles: two patrolling lifeguards (Bronze Medallion required), one first aid officer, one radio operator, and two general patrol members (open).
In the coordinator-centric model: the coordinator builds the roster from a spreadsheet, sends it to 35 members, fields the replies, updates the spreadsheet, sends a corrected version, and spends the following week managing the inevitable changes.
In an inverted model: the coordinator builds the roster structure once. The two credentialed roles are locked to approved members and require coordinator sign-off on any swaps. The four open roles are claimable by any member and tradeable without admin approval. When a general patrol member can't make it, they post a trade request visible to the other 33 members. Someone claims it. The roster updates. The coordinator gets a notification.
The coordinator has moved from logistics operator to exception handler. Their time is spent on genuine decisions — a credentialing issue, a coverage gap that can't be resolved by the team, a new member who needs orienting. Not on "can you swap your Sunday with me."
The cost of not solving this
The volunteer coordinator burnout pipeline has a downstream effect that organisations rarely model explicitly: it degrades the quality of community infrastructure over time. When the people willing to absorb coordination overhead leave — because the job is invisible, unpaid, and unsustainable — the organisations they served either collapse, shrink, or shift their burden to the next willing person, who lasts a little less long than their predecessor.
Volunteering Australia estimates the economic value of formal volunteering in Australia at over $290 billion per year. A significant portion of that value depends on people who are managing the logistics of making it happen. When those people leave, they don't just take their time — they take the operational knowledge that made the whole thing function.
The coordinator tax is not just an inconvenience. It's a structural risk to the community organisations that depend on volunteer labour.
The path forward
The immediate intervention is simple: tools that eliminate the coordinator from every interaction that doesn't require them. If a volunteer can claim an open shift without the coordinator's involvement, that's a message the coordinator doesn't have to send. If two volunteers can trade shifts within a set of pre-approved rules, the coordinator doesn't need to approve it.
The deeper shift is cultural: recognising coordination overhead as a genuine cost that organisations need to actively manage, not an invisible tax that's simply expected of whoever steps up. Coordinators should be empowered with systems that protect their time, and organisations should make reducing coordinator burden an explicit operational goal — not just thank them at the end-of-year dinner.
The organisations that figure this out first will be the ones with the longest-serving coordinators, the most stable volunteer bases, and the most resilient community infrastructure. That's not a small thing.
RosterMeIn is shift management software for community organisations and small businesses. The Trade Desk lets volunteer teams self-manage swaps without coordinator involvement — with credential-aware strict mode for roles that genuinely need oversight. Try it free →