Library volunteer coordination is two programmes, not one

Thursday, 9.58am. Margaret arrives at the library, hangs her coat in the volunteer cupboard, says hello to the Tuesday-Thursday morning crew, and starts shelving in non-fiction. She has done this for four years, on the same day, at the same time. She didn’t get a reminder text on Wednesday night. She didn’t sign up again for this week. She just came, the way she always does.

That’s the steady half of library volunteer coordination. The Tuesday-Thursday morning crew, the Wednesday-afternoon children’s-hour team, the donation sorters. They run on routine and the coordinator’s job is to hold the rhythm without disturbance. Recurring slots that hold without weekly confirmation. Onboarding done once and not reset by a database migration. Programmes kept separate so each volunteer sees only what’s relevant. Communication silent except when something has actually changed. The well-coordinated steady programme is one where the coordinator hardly has to do anything, because nothing has changed. Library volunteers don’t stay because their coordinator engages them. They stay because their coordinator leaves them alone in exactly the right way.

That’s one programme. The modern library runs another one alongside it.

The other programme

A library in 2026 isn’t only books and shelves. It hosts the local history society’s annual lecture, the summer reading launch, the maker fair, the children’s Halloween event, the local author signings, the twice-yearly book sale. It runs the National Library Week celebrations, the digital literacy taster days, the writing workshop weekends, the conference room bookings for community groups that need extra hands. None of these are core operations. All of them need volunteers. None of them suit the steady programme’s coordinator-stays-out-of-the-way logic, because they require the opposite: active mobilisation for a defined event, a defined task, a defined window, and people who’ll show up for it.

This is the second programme. It runs on a different kind of volunteer.

The volunteer for the events programme isn’t necessarily Margaret. It might be Priya, a parent who can give a Saturday morning twice a year. A retired teacher who’d happily read at children’s events but doesn’t want a weekly shelving slot. A teenager doing a school project on local history. A regular patron who’d help at the book sale if asked. The events programme draws from a wider pool than the core: people who want to contribute occasionally, around their own life, without committing to a recurring slot. The pool is bigger than the core programme’s, and it has to be, because most of the people in it will only volunteer once or twice a year.

The contrast with Margaret is direct. Margaret is recognised by name when she walks in on Thursday morning; the coordinator knows that she prefers non-fiction, that she had hip surgery in the spring, that she takes her break with the assistant librarian. Priya isn’t recognised by name, and doesn’t need to be. She’s there for three hours, doing a defined job, and that’s the right shape for what she’s giving. Margaret’s onboarding took two months four years ago. Priya’s signup takes two minutes the day she sees the task on the library’s website. Margaret’s place is held for her in perpetuity. Priya has no place to hold; her contribution is the day, not the slot. Both arrangements are right for the volunteer who’s in them. Pretending one logic fits both is how libraries lose people at both ends.

What the events programme requires

Three things. Each one is what the recurring core doesn’t need, and what the steady programme’s tools usually do badly.

Easy entry, easy exit. A volunteer for the spring book sale shouldn’t have to fill out a long onboarding form, complete background-check paperwork, or commit to ongoing engagement. They should be able to find the task, sign up, show up, and disappear back into their life when it’s done. The steady programme’s careful onboarding is the right shape for someone who’s going to be around for years; it’s the wrong shape for someone who can give three hours on a Saturday in May. Software that treats every volunteer as a long-term commitment makes this layer harder than it needs to be, and the harder it is to enter, the smaller the pool.

Tasks with clear scope and time. “Help at the book sale” is not a task. “Sort and document books donated for sale at the main counter, Saturday 9am to 12pm” is. Events run on defined-window contributions: you arrive for a specific job at a specific time and the work has clear boundaries. The coordinator’s job is making the task clear before signup, not after, so volunteers know what they’re committing to and what they’re not. This also lets a parent who’s only available 9am to 11am decline without guilt, instead of arriving at 9 and having to leave halfway through something open-ended.

Communication that activates and stops. Event volunteers need signal at the right moment: the day before (a reminder), the morning of (final details, weather, parking, who to find on arrival), during (any quick coordination needed), and then silence. They don’t want to be in an ongoing chat about the next event when they only signed up for this one. The communication has a sharp window, and the system has to handle that without forcing the coordinator to manage who’s in which thread.

What software does for the events layer

Self-signup that doesn’t require a long-term account. Tasks listed by date and time, with location, scope, and any specifics described in the task itself. Group chat that activates when the event is near and goes quiet when it’s done. Notifications that fire on the right cadence. The coordinator doesn’t manage who sees what; the structure does.

For the steady programme, software has a smaller role. It can hold standing arrangements and flag compliance status, but the deeper work of background checks, programme-specific training, and long-term relationship-building usually lives in dedicated volunteer-management systems, in the library’s HR processes, or in the coordinator’s institutional memory. Many libraries run their recurring programme on a spreadsheet, an email list, and the coordinator’s knowledge of who does what. If that’s working, software doesn’t need to replace it.

How to think about choosing tools

Don’t try to use one tool for both programmes. The recurring core and the events layer have different volunteers, different mechanics, different communication patterns. Software that handles both well is rare. Software that handles one well, used alongside whatever’s working for the other, is more common and usually more practical.

For the steady programme, you may already have what you need. If a spreadsheet, a few email threads, and the coordinator’s institutional memory are holding the regulars, the risk of switching is the same one this post is mostly about: introducing change where the routine was holding.

For the events programme, you’ll want something simple, mobile-friendly (event volunteers do check their phones), free or close to it, and easy enough that someone who’s never used the tool before can sign up without help. Boring is good: the tool should run the same way for each event, so the coordinator isn’t reinventing the workflow every time.

Where Zelos fits

Zelos is built for the events programme, not the recurring core. The recurring shifts that hold long-time volunteers, the background-check tracking, the programme-specific training records: these aren’t what Zelos does, and there are dedicated volunteer-management platforms that do that work better.

What Zelos is good at is hosting an events programme with minimal setup. A coordinator can publish a list of tasks for the spring book sale (sorting donations, running the till, restocking tables during the sale, setting up Friday evening, packing up Saturday afternoon), open them for self-signup, and let community members claim what they can take. Group chat handles the coordination in the lead-up and during the event itself. Notifications fire at the right moments. The interface is simple enough that a parent who’s never used it can sign up for the children’s Halloween event in a couple of minutes from their phone. Workspaces are invite-only, which fits the patron-privacy culture libraries build their programmes around.

The free plan covers unlimited volunteers and 25 active tasks at a time. For an events programme, that fits comfortably: a single event with five roles uses five tasks, and most libraries don’t run more than four or five overlapping events. When an event is done, the tasks close and the conversation goes quiet. The next event opens new tasks. Some volunteers come back, some don’t, new ones arrive. That’s how the events programme works, and it’s the shape Zelos was built for.

It is not the routine. Margaret’s Thursday-morning shelving holds because of years of trust, careful onboarding, and a coordinator who knows what they’re doing. The events programme runs alongside it: a wider pool, a different rhythm, the moments when the library becomes more than its core operations. You can explore the product or start a free account and try it for your next event. The work, either way, is yours.