You build next month's schedule, send it out and within the hour the first reply arrives. "I am travelling that week, sorry."
You knew that. Or you were told, three weeks ago, in a message that is now somewhere in a chat. Either way, the name is on the schedule, the person is away and you are back to fixing it.
Volunteer availability is the quiet reason schedules break. This article looks at why it is so hard to keep track of by hand, what it costs and what it takes to stop scheduling people who are not there.
Key takeaways
- Availability is not one piece of information. It is dozens of small ones that arrive in different places at different times.
- Most of it lives in memory, in chats and in side notes, which means it is incomplete when you build the schedule.
- Scheduling someone who is away costs more than the correction. It costs trust.
- Availability only helps if every step of scheduling respects it, not just the first one.
Why availability is harder than it looks
On paper it is simple. Ask people when they cannot serve, write it down and avoid those dates.
In practice it looks more like this.
- Someone mentions a holiday after a service.
- Another sends a message about an exam week in a thread about something else.
- A family member is in the hospital, and the person tells you at the door.
- A long-term volunteer travels every summer, and you are supposed to remember.
- Someone says "I am free most Sundays" and you have to guess what "most" means.
None of this arrives in a form. It arrives in conversation, and you are the one who turns it into a list.
Where it ends up
By the time you sit down to build a schedule, availability is spread across:
- Your memory.
- A group chat and several private ones.
- A note on your phone.
- A column in a spreadsheet that was up to date in March.
- Verbal comments you promised yourself you would write down.
You then build the schedule from whatever you can find. What you cannot find, you do not account for.
How it goes wrong
The person who told you, and you forgot
This is the most common case, and it is nobody's fault. You were told, it was not recorded and it did not come back to you at the right moment.
The schedule that ignores a long absence
A volunteer is away for three weeks. You remember the first week and schedule them in the third.
The conflict you discover late
You assign someone, send the message and then see the note you made two weeks ago. Now you have to undo an assignment that the volunteer has already read.
The replacement who is also away
A volunteer cancels, and you ask a colleague to step in. That colleague is on holiday too. You have wasted a request and some of their patience.
The quiet disappearance
Someone who is away stops replying. Without a recorded absence, you cannot tell "away until the 20th" from "stopped caring". Both look like silence.
A small example
Take a team of fifteen volunteers and a month with four services. Three people are away for part of it. One is gone for a week, one for two, and one for the whole month.
That is not a lot. But it means that for each of the four services you have to remember who is out, avoid them in the main schedule, avoid them when a replacement is needed and avoid them again if a service gets added.
Multiply that by the number of positions and the number of months, and you can see why even careful coordinators slip. The information is simple. Carrying it in your head, every time, is the hard part.
What it costs
- Trust. Scheduling someone who told you they were away makes them feel unheard. Do it twice and they stop telling you.
- Time. Undoing and redoing assignments, and finding replacements for slots that should never have been assigned.
- Reliability. Every wrongly scheduled person is a no-show waiting to happen, or a cancellation just before the event.
- Pressure on the available. The people who are always free get asked most, because they are the ones you know will answer.
Each correction is small. They add up to a schedule that nobody fully believes.
What good availability handling looks like
You do not need a complicated system. You need three things.
- One place. Absences are recorded where the scheduling happens, not in a chat.
- Dates, not feelings. "Away from the 3rd to the 17th" is an answer that a schedule can use.
- Respect at every step. When you assign, when you generate the month, when you invite, when you look for a replacement, absences count.
The last point is where most manual systems fall down. You might check availability when you build the schedule and forget it when you need a replacement a week later.
How Planify handles it
In Planify, absences are part of the member's profile.
- Unavailable periods. You add a from date, an until date and an optional note to a member.
- A warning about existing assignments. When you add a period, you see any assignments of that member that fall inside it, so you can fix them.
- No overlapping periods. Planify does not accept two periods for the same member that overlap.
- Manual assignment. If you try to assign someone for a date when they are unavailable, Planify tells you.
- The monthly planner. It does not place people on dates they are away.
- Open calls. Members who are away on that date are not invited.
- Replacement requests. When Planify asks colleagues to cover a position, it skips the ones who are away.
- A visible label. In the planner, people who are away on a date are marked, so you can see it before you decide.
Planify records the periods you enter. Volunteers do not enter them themselves in the app today, so the habit of noting an absence still sits with you or the coordinator. What changes is that you enter it once and every step respects it.
Which features you get depends on your plan.
Read next: the monthly volunteer schedule and why it eats your weekend.
FAQ
How do you track volunteer availability?
At minimum, record absences as date ranges in one place that you use when scheduling. Chats and memory are the common alternatives, and they are where information gets lost.
How far ahead should volunteers share their availability?
It depends on how far ahead you schedule. Collect absences before you build the schedule and let people update them when plans change.
What should I do when a volunteer is away for a long time?
Record the full period so that none of the dates in it get assigned. A single note covering the whole absence is safer than remembering each Sunday separately.
Why do volunteers not tell me when they are away?
Often because they do not know it matters, or they assume you already know. Showing that absences are used, and making them easy to share, helps.