Working Volunteer / Starting

A volunteer who is unhappy simply stops appearing

Paid staff give notice, have exit interviews and appear in turnover data. Volunteers leave silently, which is why most organisations do not know why they lose them.

An employee who becomes dissatisfied works through a fairly visible sequence. They raise something, or they do not and their engagement drops in ways a manager can observe, and eventually they resign, giving notice and a reason. The organisation records it. Somebody may ask what happened. There is a data trail, however imperfect.

A volunteer does none of this. They miss a shift, which is unremarkable. They miss another. They reply more slowly, then not at all. At no point do they announce a decision, frequently because they have not consciously made one, and at no point does anybody in the organisation record that a person who used to help no longer does. The loss is invisible, the reason is never captured, and the same cause continues operating on everybody else.

This single structural difference explains most of what is distinctive about managing volunteers. Feedback does not arrive, so it has to be sought. Dissatisfaction is not expressed, so it has to be noticed. And the accumulated cost of a poorly run programme does not appear anywhere in the accounts, which is why organisations routinely operate volunteer arrangements that a paid workforce would not tolerate for a month.

The second distinctive feature is that the relationship has no formal obligation on either side, which cuts both ways. The volunteer can stop at any time with no consequence, and the organisation frequently feels it cannot ask much. That produces a characteristic pattern: expectations left unstated because stating them feels presumptuous, followed by frustration on both sides when they are not met. Volunteers report this constantly. They wanted to be told what was needed, and everybody was so grateful that nobody would tell them.

The third is that volunteers are usually there for a reason that is not the task. They want to contribute to something, to use a skill, to have somewhere to be, to meet people, to build experience, or to give back to a service that helped them. Two people doing the identical role can want entirely different things from it, and an organisation that does not know which is which will lose one of them by giving them the other's experience.

There is also a persistent framing problem in how this work is discussed. Volunteering is described in the language of generosity, which is accurate and incomplete. It is also work: it requires reliability, it has quality consequences, it involves risk, and in many settings it is doing things that would otherwise require paid staff. Treating it as a favour makes it awkward to set expectations, to address poor performance, or to ask somebody to stop, and all three of those are occasionally necessary.

The organisations that run this well tend to hold both framings at once. They are genuinely grateful, and they are also clear about what the role requires, what training is needed, what the boundaries are, and what happens if it is not working. Volunteers consistently report preferring that to vagueness, because vagueness makes it impossible to know whether you are doing it right.

One further point about how this work is resourced, since it explains most of what goes wrong. Volunteer coordination is genuinely a job, requiring recruitment, induction, rostering, supervision and pastoral care, and in most organisations it is added to somebody's existing role on the reasoning that volunteers are free. They are not free; they are unpaid, which is different. The costs are real and fall on whoever is holding the arrangement together, and where nobody is holding it, the cost is paid instead by the volunteers who drift away and by the people the service exists to help.