Planning a volunteer rota looks like the same job you do in a business, with less money. It is not: it is structurally different work, and the reason sits in one difference that changes the whole method.

In a business you start from demand and look for someone to cover it, because a contract makes that request legitimate. In a voluntary organisation the demand exists just the same, but nothing obliges anyone to meet it. Keep the same method and the rota becomes a list of requests somebody will have to decline, and every decline costs a piece of the relationship.

The data everything rests on

Declared availability is, in a voluntary organisation, what contracted hours are in a business: the starting constraint, not a side note.

Collecting it properly means three things:

  • days and time bands, not "I am fairly available". Tuesday evening and Saturday morning are data, goodwill is not;
  • updatable without asking permission. Volunteers' lives change, and availability that can only be corrected by messaging the coordinator goes stale in two months;
  • with a validity date, because "available on Saturdays" said in September does not mean available in June.

Once that data exists, the rota stops being a request and becomes a proposal: it assigns shifts only inside windows people have already declared. The number of noes collapses, and the friction with it.

The problem that remains: the slots nobody wants

Collecting availability does not make volunteers appear in the uncovered hours. Nights, Christmas lunches and August Sundays stay hard, and those need a different method.

The three things that work, in order:

Ask early, not last minute. A night asked for six weeks ahead can be organised around; the same night asked for on the Thursday before is a favour.

Count them and show the count. A visible counter of how many awkward shifts each person has done changes the conversation more than any appeal. Those who have done many feel seen, and those who have done few know it without anyone telling them.

Do not always ask the same people. It is the fastest way to lose the people everything rests on. That is true in a business and doubly true here, where nobody has a salary as a reason to stay.

Minimum cover has to be declared

A recurring mistake: building the rota around the people you have, then discovering on the day that they are not enough.

The minimum cover for a service, meaning how many people with which competencies, is data that must be written down in advance, independently of who is around. It serves one purpose, but an essential one: knowing ahead of time which shifts will be uncovered, while there is still time to call somebody.

A shift discovered uncovered on the morning is not a planning problem, it is an emergency. And emergencies, in a volunteer organisation, are paid for in people who stop coming.

The relationship is the scarce resource

The last point, which is also the criterion for deciding everything else. In a business the scarce resource is hours. In a voluntary organisation it is availability and trust, and they get consumed together: every request outside declared availability, every shift assigned without asking, every change communicated late takes a piece.

A rota that respects what people said they could give is not just kinder: it is the only one that holds over time. The reasons volunteers stop are lined up in why volunteers drop out.

In Sked Solve each person declares in the app the days and bands they can be there, and generation only assigns shifts inside those windows. See how it works at Sked Solve.