It is 8:47 on a Saturday morning and the volunteer coordinator is sitting in the stairwell outside the community hall with her phone in both hands, working through a stack of unread messages from the night before. The session starts at ten. She has twelve volunteers rostered. Based on what she can piece together — a mix of confirmations, late apologies, one message in a language she cannot read, and three people who have not responded at all — she thinks she might have seven. Maybe eight if the person who said "probably yes" meant yes.
Somewhere in her inbox is a spreadsheet. It has the volunteers' names, their mobile numbers, the date they submitted their background check forms. She cannot remember if she ever chased the results for two of the newer people. One of them is scheduled to work directly with the youth group today. She opens email and searches a name. The results give her four threads, none of which are conclusive.
By 9:15, she has confirmed six people. She restructures the room plan in her head, moves the arts session to a smaller space, sends a message to her colleague asking if she can come in early. The session will run. It always runs. But this is the part of the job that nobody sees — the forty-five minutes of improvisation before the doors open, the small cost that accumulates every single week.
Why volunteer coordination gets pushed to the bottom
There is a persistent logic in nonprofits that volunteer management is not the real work. The real work is the programme — the youth sessions, the welfare visits, the food distribution, the counselling. Volunteers exist to support that work, which makes the administration of volunteers feel secondary. It gets handled with whatever tools are already to hand: a shared inbox, a spreadsheet that lives on someone's desktop, a messaging group that started as a temporary measure and never stopped being used.
This is not laziness or bad management. It is resource allocation under scarcity. When a small team has to choose between documenting a volunteer's training history and returning a call from a family in crisis, the family gets the call. Every time, and correctly so. The problem is not the individual decision — it is the structural consequence of making that decision repeatedly, over months and years, without ever catching up.
Funders compound the problem. Very few grants budget for volunteer coordination as a line item. The cost of managing people who are not being paid tends to be invisible in grant applications, which means the organisations doing it well are absorbing that cost somewhere else — usually in staff time, usually uncounted.
What informal systems actually cost
The costs are real, but they arrive slowly enough that they rarely feel like a single attributable failure.
The hours that never get counted
Volunteer hours are a form of in-kind contribution that many funders explicitly want to see reported. A hundred hours of volunteer time in a quarter is evidence of community engagement, of leverage, of reach beyond what paid staff alone could deliver. But if those hours are never logged — if the assumption is that volunteers track their own time and submit it somewhere, and that somewhere is a form that gets emailed to a coordinator who means to add it to a spreadsheet and usually gets to it eventually — the actual figure reported at the end of the year is either a guess or a blank.
A guess is worse than it sounds. Funders know a guess when they see one. Round numbers in volunteer-hours columns signal that nobody actually knows. An organisation that cannot say how its volunteers contributed is, from a funder's perspective, an organisation that is not managing its volunteers.
The records that do not survive turnover
Background checks, training certifications, induction records: these are not administrative niceties. In most jurisdictions, organisations working with children, elderly people, or vulnerable adults have legal or regulatory obligations around who is permitted to be present. The question of whether a given volunteer is cleared to work in a given setting is not a minor operational detail — it is a safeguarding question.
When that information lives in a coordinator's email, it has a lifespan equal to that coordinator's tenure. When the coordinator leaves — and coordinator turnover in the nonprofit sector is high, precisely because the role is demanding and often underpaid — the institutional memory leaves with them. The next person starts from scratch, often without knowing what they do not know. They assume the records exist somewhere. They may not chase them until something goes wrong.
The retention problem nobody names
There is a third cost that is harder to quantify but probably the most expensive over time: volunteers who feel poorly managed drift away.
This is rarely dramatic. It is not usually that someone has a bad experience and leaves angrily. It is more often that someone shows up twice, finds the experience confusing or disorganised, does not feel like they knew what they were supposed to be doing or that anyone would notice if they did not come back, and quietly stops. They do not resign. They just do not reply to the next message.
The experience of being a volunteer is, among other things, an experience of being managed. An organisation that sends a clear welcome, confirms shifts in advance, tells people what they are doing and who to report to, and thanks them by name for specific contributions retains people. An organisation that adds someone to a messaging group and hopes for the best does not. This is not about making volunteers feel special in a performative way. It is about basic respect for someone giving their time for free.
The cascade nobody plans for
A volunteer who does not show up does not simply leave a gap. The gap has downstream effects.
In a programme session, the ratio of staff to participants is usually calculated. When that ratio drops unexpectedly, something gives: either a planned activity gets cut, or participants receive less attention, or one person tries to cover ground that was designed for two. Session quality degrades in ways that are difficult to document but real for participants. If attendance data is collected — and it should be, for funder reporting — the quality of that data depends partly on whether the session had enough people to run it properly.
Across a year, unreliable volunteer attendance produces unreliable programme delivery, which produces data that is harder to report and programmes that are harder to evaluate. Organisations wonder why their outcomes look inconsistent. The answer is sometimes in the staffing structure, not the programme design.
What a proper volunteer record actually needs
A volunteer record that is genuinely useful contains more than a name and a phone number. At minimum, it needs to be possible to answer the following questions for any volunteer at any time: which programmes are they cleared to work on? When did their background check last run, and when does it need to be renewed? How many hours have they logged this year, and across which programmes? What shifts are they committed to in the coming weeks?
These are not complex data points, but they need to be held in one place. A name and number in a spreadsheet, a background check form in an email, an hours log in a separate sheet, and a roster in a calendar are not a volunteer record — they are four separate fragments that require a human to assemble every time a question is asked.
The difference between a database and a system
A volunteer database stores information. A volunteer system does something when information changes.
The difference matters in practice. A database tells you that a background check was submitted on a certain date. A system tells you when that check is approaching expiry and prompts someone to act before it lapses. A database holds shift assignments. A system sends the volunteer a reminder before the shift and records whether they confirmed. A database stores hours submitted. A system aggregates those hours into a report that a coordinator can export at the end of a funding quarter without spending an afternoon with a calculator.
The distinction is not about having sophisticated technology. It is about whether the coordination work — the chasing, the reminding, the checking — is built into the process or delegated entirely to human memory.
What good looks like for a small team
An organisation with ten volunteers does not need the same infrastructure as one with two hundred. But it needs the same structural clarity, just lighter.
That means a single place where volunteer records live — accessible to more than one person, so that it survives turnover. It means a simple way to log hours that volunteers can actually use, not a process so cumbersome that nobody bothers. It means shift assignments that go out in writing, with enough notice for people to plan. It means background check and training status that someone can see at a glance before a session, not something they have to reconstruct from email.
None of this requires a large budget. It requires making the decision that volunteer coordination is infrastructure, not administration — that it is as load-bearing as programme planning and reporting, not an afterthought that gets handled in a stairwell at 8:47 on a Saturday morning.
The organisations that do this well
The organisations that treat volunteers as well as they treat paid staff tend to have some things in common. They retain people longer. The same faces return year after year, accumulating knowledge of the programme and the participants that is genuinely hard to replace. They log more hours, because the infrastructure to log them is easy enough that it actually gets used. And they report more confidently to funders, because the data exists and someone can find it without spending an afternoon searching through inboxes.
That confidence compounds. A funder who sees clean volunteer data in one report is more likely to trust the rest of the report. An organisation that can say "our volunteers contributed 847 hours this year across three programmes, with a 73% retention rate from last year" is telling a story about operational credibility, not just programme delivery.
The volunteers deserve that organisation. So does the coordinator who should not be sitting in a stairwell at 8:47, trying to reconstruct who was cleared to be there.
Socianote includes volunteer management as a native feature — shifts, hours, background checks, and a self-service portal so volunteers can confirm and manage their own commitments. Start free — no credit card required.