Performing arts volunteer coordination is two jobs, not one

Opening night, twenty minutes to curtain. The foyer is full. The ushers are at their stations, briefed on the production’s two emergency exits and the seven-minute window in the first act when late arrivals can be seated quietly. The bar volunteers know the interval is fifteen minutes tonight, not the usual twenty, because the second act runs long. Backstage, the dresser has sorted the quick-change station. The sound operator has her cue list pinned next to the desk. The stage manager has finished his pre-show round and confirmed everyone in place.

None of this happened tonight. It happened across three weeks of signups, briefings, and rehearsals, plus the eight months before that, when nobody was needed but the volunteer list still had to be alive.

That’s the thing that makes performing arts volunteer coordination its own particular kind of work. It runs at two completely different speeds. The job between productions, when a community stays warm enough to come back. The job during a production, when forty people need to be in the right place at the right time across two weeks of evenings. The same coordinator does both. The skills that work for one don’t always carry to the other.

This post is about both jobs, what software does for each, and what it can’t.

The two modes

Between productions

Three things to do, none of them urgent, all of them necessary.

Keep the list warm. The people who said yes to the last show are the foundation of the next one, even though most of them won’t come back. Some will. The work is staying in light, occasional contact so they remember you exist when the next casting call goes out. A quarterly newsletter, three short paragraphs maximum. A personal text to anyone who did real work in the last show. One social event two months after closing, low-stakes, no agenda. The bar isn’t depth, it’s persistence. If you stop showing up between shows, your list is back to zero next time you need it.

Recruit while you announce. When the next show goes on the season brochure, the volunteer signup goes on the website. The people who buy tickets and the people who volunteer are often the same audience; the marketing campaign and the recruitment campaign can share infrastructure. The signup form belongs on the production page, not in a separate “get involved” tab nobody clicks. Three-quarters of your run-of-show roster should be set before rehearsals begin. The crunch most community theatres feel two weeks before opening isn’t a recruitment problem. It’s a recruitment-timing problem.

Protect the core. The regulars who hold the institutional knowledge need the off-season to be actually off. Not “off-but-can-you-just” off. Quarterly meetings, not monthly. No “quick favour” requests in dark weeks. If you need them between shows, ask once and accept no. The core is what you’re building for the next ten years. Burning them through one off-season to save yourself a Tuesday afternoon buys you nothing and costs you a person.

During productions

Three things to deliver, all of them urgent.

The surge. Forty people across rehearsals, tech week, dress, and the run. Different role mixes for different performances. Different volunteers for matinees and evenings. Self-signup with capacity per slot, role-specific descriptions, group filtering by function. The coordinator stops being the matching bottleneck and becomes the person who answers questions as they come up. That handover is the difference between a coordinator who survives the show and one who’s exhausted by tech week.

The standards. Compliance gates that hold even when you’re short. Role-fit that doesn’t slip when you’re desperate. The discipline of saying no to a willing volunteer who isn’t right for tonight’s slot, even at six pm on opening night. This is the part where coordinators most often crack, because cracking feels like helpfulness. It isn’t. The cost of the wrong person in the wrong role on opening night is paid by the entire production, including the volunteer.

Opening night and the run. Everything has to be in place. The ushers briefed, the bar staffed, the backstage crew at their posts, the marketing volunteer no longer flyering because the run has started. The coordinator’s job by opening night is mostly being available and not being the bottleneck. If the first three weeks were done right, the run is quiet from the coordinator’s side. If they weren’t, it isn’t.

What software does for each mode

Between productions, software does little, and that’s the point. A volunteer list that’s accessible from a phone. A way to push a quiet message to the people who want to hear from you. A record of who did what in the last show, who said yes and showed up, who said yes and disappeared, who’s worth a personal text before the next casting call. The tool should be unobtrusive. If you’re spending more than ten minutes a week in it between productions, something’s wrong.

During a production, software earns its place. Shift signups with capacity per role per performance, so volunteers self-select into what fits their schedule and skills. Role-specific task descriptions that carry the technical requirements (call time, equipment, who to report to) so a volunteer reads what they’re claiming before they claim it. Groups that separate front-of-house from backstage from marketing, so a costume volunteer doesn’t see the rigging signups they’re not qualified for. Compliance fields that mark a volunteer as cleared and gate role-specific signups accordingly. Messaging tied to specific shifts, so when curtain is moved up by ten minutes you reach exactly the people on tonight, not the entire list.

These are real features doing real work. Worth choosing carefully. Also: a smaller part of the actual coordination than the brochures imply.

What software can’t do

Software can’t tell you which seventeen-year-old can be trusted with the spotlight cue and which one isn’t ready yet. That comes from running her through it twice in tech week and noticing how she handles the moment when something goes wrong.

Software can’t run the new-usher walkthrough where someone learns the venue. The fact that the toilet on the upper foyer leaks if you flush twice. The reason the south door is propped on Wednesday matinees. The exact spot where the carpet has lifted enough to trip an audience member if they’re not paying attention. This is institutional memory, and it lives in the coordinator.

Software can’t have the conversation with the regular who’s been front-of-house lead for six years and is starting to find it exhausting, but doesn’t want to step down because the role is part of how she sees herself. That conversation is yours to have.

Software can’t manage upward. The board that wants more productions next season but won’t fund a coordination role. The producer who needs front-of-house staffed for every show but doesn’t see volunteer fatigue as her problem. The artistic director whose programme decisions land on your roster without anyone asking how. These are conversations the coordinator has, often without backup, often without much shared language for what’s being protected.

Software can’t moderate the dynamics of a backstage that holds a fifteen-year-old assistant stage manager, her mother on costumes, the retired electrician who’s been in the rigging since the 1990s, and the university student home for the summer trying to work out if theatre is what she wants to do. Each of those people has a different reason for being there, a different idea of what a production should be, and different needs from the coordinator. Holding a room like that is human work all the way down.

Software can’t make a brilliant teenager grow into a stage manager across four productions. That’s recruitment, mentoring, a director who’ll back her, and a coordinator paying attention to who’s ready for what next.

Software can’t reduce the coordinator’s own load. The unpaid hours. The decisions about who to rest and who to lean on. The weight of being the person who says no when no needs to be said. Burnout in this role doesn’t come from doing too much. It comes from doing too much without anyone seeing it. Other coordinators see it. That’s why the people who do this work for years either find a peer or don’t last.

This is most of the work. The coordinator who lasts in this role is the one who designs both modes deliberately, knows their volunteers as people, holds the line on standards when the surge tempts compromise, carries the institutional memory nobody else holds, builds the relationships that make people come back, and looks after themselves in a job that doesn’t always reward it. None of which is a setting you can configure. All of which is what determines whether a community theatre runs for two seasons or twenty.

Common mistakes, and the behaviour that fixes them

Mixing the two modes. It’s tempting to keep the production-pace newsletter going through the off-season, schedule “planning meetings” that feel like still-in-show meetings, ask the core for “small favours” in dark weeks. Each one feels harmless in isolation. The cost is that the coordinator and the core never get the actual recovery the cycle was designed to give them. The remedy is hard discipline about what off-season looks like. If a between-shows email could just as easily be sent during a run, it shouldn’t be going out.

Recruiting production volunteers too late to integrate them. Most community theatres launch recruitment in the weeks before opening, leaving no time for a venue walkthrough, a compliance check, or a chance for the new volunteer to meet the regulars before the pressure hits. The new volunteer arrives confused, either underperforms or feels invisible, and doesn’t come back. The remedy is opening recruitment when the show is announced, not when rehearsals start. Treat the signup as part of the marketing. The production has a roster three weeks before tech week instead of three days, and you’ve absorbed the new volunteers into a working team before opening night.

Filling shifts on availability instead of fit. When you’re short three days before opening, the temptation is to put any willing person in any open slot. In performing arts that creates damaged equipment, slow crews, awkward front-of-house moments, the occasional safety risk. The remedy is keeping written notes per volunteer: what they’re good at, what they want to learn, what they’ve handled before. The notes don’t have to be elegant. They have to exist. Match for fit, not just availability. The volunteer who feels matched to the role they got is the one who comes back for the next production.

How to think about choosing tools

The same principles apply here as anywhere. Pick something that does its slice well and doesn’t pretend to be the programme.

Mobile-first matters more than usual. Volunteers are signing up from their phones, often during a fifteen-minute break at their day job, often after seeing a Facebook post about the next show. If the signup experience is clunky on mobile, half of them won’t finish.

Calendar-aware is non-negotiable. Productions are dates, not perpetual programmes. The tool needs to flex around opening nights, dark weeks, and runs, not assume a steady weekly rhythm.

Free or close to it is fine. Most community theatres aren’t paying for software. They shouldn’t have to. A tool that holds a small volunteer list, runs production-time signups, and stays out of the way the rest of the year is what’s needed. Nothing more.

Boring is good. The boring tool used the same way for every production is the tool the volunteers actually use. Each new flourish is something that breaks during tech week.

Where Zelos fits

A short note, because the post’s whole argument is that the tool isn’t the programme.

Zelos handles the pieces software handles. Profile fields hold compliance information (working-at-height, first aid, child protection clearance) so checking who’s cleared for a role doesn’t require a separate spreadsheet. Groups separate front-of-house, backstage, and marketing volunteers within a production, and separate productions from each other. Tasks carry the role-specific descriptions and capacity limits, and surface only to the right group. Built-in messaging on each shift means a curtain change reaches exactly the people on tonight, not the whole list. Self-signup means volunteers see what’s available and claim what fits. All messaging is admin-supervised, by design, which is the right shape when youth productions put adult volunteers and minors in the same workspace. The free plan covers unlimited volunteers and 25 active tasks at a time, which is enough for a full production cycle without paying anything.

It is not the programme. The programme is what you build with it across seasons, productions, and the quiet months in between. You can explore the product or start a free account and try it on the next show. The work, either way, is yours.