Skip to main content

Recruiting volunteers without burning them out

Most teams do not have a recruiting problem. They have a retention problem that looks like a recruiting problem, because the people who leave are replaced by asking the same willing few to do more.

Why it goes wrong​

The ask is open-ended. "Would you like to join the worship team?" has no end date, no frequency and no exit. A thoughtful person hears a commitment they cannot size, so they say they will think about it.

The reliable people get asked most. The volunteer who always says yes is the one you call when someone drops out, which means they serve twice as often as anyone else and are the first to quietly stop.

Nobody notices when someone is doing too much. Serving every week feels normal to the person doing it, right up until it does not, and by then the conversation is about leaving rather than about frequency.

Joining has no shape. A new person is added to a rota and left to work out the rest. Some cope. Many decide it is not for them, and nobody ever finds out why.

What works​

Ask for something with edges. A specific role, a specific frequency, and a specific length of time. "Once a month, on the sound desk, until Christmas, and we will talk again then" is a question someone can actually answer. It also makes it easy to say no, which is what makes a yes mean something.

Say what it costs before they agree. If serving once means a rehearsal, a Sunday morning and learning four songs, say all three. People rarely resent the work. They resent discovering it afterwards.

Watch how often each person actually serves, not how often you think they do. This is arithmetic, and it is usually surprising. A team of eight where three people are competent on a given instrument means those three carry a third of the year each, whatever the rota looks like on paper.

Build the rota so nobody serves more than they agreed, then hold that line even when it is inconvenient. The week you break it for a good reason is the week the agreement stops meaning anything.

Give the exit as clearly as the entrance. A season that ends, and a conversation at the end of it, lets someone stop without it being a failure. Teams that never offer an exit lose people abruptly instead.

What it looks like​

Two versions of the same ask.

The one that produces a vague maybe:

We are always looking for more people on the worship team. Let me know if you are interested.

The one that produces an answer:

We need someone on keys once a month. That is one Thursday rehearsal and the Sunday, so about four hours, plus learning the songs during the week. I would ask you to commit until the end of the year, and then we will see how it went. Are you up for it?

The second is longer, more demanding and much easier to say yes to, because it can be checked against a calendar. It is also easy to say no to, which is a feature. The person who declines that ask was never going to last under the first one.

Common mistakes​

  • Asking for open-ended help and being surprised when nobody commits.
  • Calling the same reliable person every time somebody drops out.
  • Never checking how often people actually serve.
  • Treating someone who steps back as a loss rather than a season ending.
  • Recruiting to fill this Sunday rather than to build a team.

Doing it in OnStage​

Positions make what you are asking for concrete, and the schedule shows how often someone has actually been on, which is the number worth checking before you ask them again.

  • Create groups and positions
  • Invite people with a link or team code
  • Check another member's schedule

Frequently asked questions​

How often should someone serve?​

Ask them, then hold to it. Once or twice a month suits most volunteers with jobs and families. Weekly is sustainable for very few people, and the ones who manage it are usually the ones closest to stopping.

Someone said yes and then stopped turning up. What went wrong?​

Usually the ask had no edges, so there was nothing to keep or to leave. Someone who agreed to "help out with worship" has no way to know whether they are doing enough, and stopping is easier than asking.

Should I ask publicly or privately?​

Privately, almost always. A public appeal reaches people who were going to volunteer anyway, and puts quiet, capable people on the spot. A specific private ask is also much harder to ignore, which is the point.

How big should the team be?​

Big enough that nobody serves more often than they agreed. Work backwards from that: if you meet weekly and someone serves monthly, you need four people who can each cover that position. Counting the team you have against that number is usually more useful than counting the team you wish you had.

  • A new team member's first month
  • Building a rota people can commit to
  • Giving feedback to a volunteer