You scheduled the volunteers days ago. The names are on the list. And on Saturday evening you still do not know who is actually coming.
That gap between “scheduled” and “confirmed” is where most coordinators lose their time. This article looks at what confirming volunteers by hand really involves, what it costs you and why so many schedules look finished while being full of maybes.
Key takeaways
- Being on the schedule is not the same as having said yes. Most no-shows come from people who were never asked to confirm.
- Confirming by hand means one message per person, a wait, a reminder and often a phone call.
- The silence is the hardest part. You cannot tell “I am coming” from “I have not seen your message”.
- A confirmation that takes one tap gets answered. One that needs a typed reply gets postponed.
Scheduled is not confirmed
A name on a schedule is a plan. Someone who has replied is a commitment. Those are two different states, and most scheduling tools treat them as one.
When you send a schedule and hear nothing back, you have three kinds of people on it:
- Those who saw it and will show up.
- Those who saw it and cannot, but did not say so.
- Those who never saw it.
From your side of the screen they look identical. You find out which is which on Sunday morning, when the position is either filled or empty.
What confirming by hand looks like
Say you have twelve volunteers across the services this week. A manual confirmation round usually goes like this.
- You write a message to each person, or to a group, asking them to confirm.
- You wait. Some answer in minutes, others the next evening.
- You scroll back through the thread to see who has replied and who has not.
- You write a second message to the silent ones.
- You call the people you are most worried about.
- You update your list, one status at a time.
Each step is small. Together they turn a five-minute question into an evening of checking.
The reply that does not count
Even when people answer, the answers are rarely clean.
- “I will try.”
- “Probably yes, I will let you know.”
- A thumbs-up on a message that was about three different Sundays.
- A reply in the group that only makes sense if you remember the previous message.
You then have to decide what each of these means and write it into your list. A lot of confirmation work is not asking. It is interpreting.
Why people do not confirm
It is usually not rudeness. It is friction.
- The request is buried in a long message.
- Answering means typing a sentence, and a sentence feels like it needs thought.
- They mean to answer later and then the day takes over.
- They do not know whether you need an answer at all.
The more effort a reply takes, the more often it is postponed, and a postponed reply is the same as no reply.
What it feels like on the volunteer’s side
It is worth looking at this from the other end. A volunteer gets a long message in a busy chat, between a work thread and a family photo. They read it, think “I will answer when I am home” and move on.
They are not refusing. They simply have not been given a reason to answer now, or a way to do it in two seconds. Meanwhile you see the same silence as a risk.
Most volunteers would answer quickly if answering cost them nothing. The problem is rarely commitment. It is the cost of replying.
What the silence costs you
The direct cost is time: the evenings of chasing, the calls, the scrolling. The less visible cost is what happens when you chase late.
- Late discovery. You learn a position is empty hours before the service, when there is almost nothing left to try.
- Pressure on the same people. The ones who always answer are the ones you ask to step in, again.
- Tension. Chasing the same volunteers every week starts to feel like nagging, for them and for you.
- No clear picture. When the schedule never says who has actually confirmed, you cannot plan the rest of the week around it.
It also changes how you build the next schedule. Coordinators who have been burned start overbooking “just in case”, which creates its own problems.
What a good confirmation looks like
Think about what makes people answer.
- It reaches them where they already look, not in another inbox.
- It says exactly what is being asked: the event, the day, the time and the position.
- It can be answered without typing.
- It takes a second, so there is no reason to postpone it.
If the answer is a tap, the coordinator also gets something better than a message to interpret. They get a status: confirmed, declined or no reply yet.
How Planify handles confirmation
Planify is built around this gap.
When you assign a member to a position for a date, they receive a WhatsApp message with the event, the date, the time and the position. They answer with a button. They do not install an app and they do not log in. WhatsApp is already on their phone.
- One tap to answer. Yes or no, from the message itself.
- A confirmation back. A volunteer who accepts gets an acknowledgement, so they know it was recorded.
- Status per person. You see who has confirmed, who has declined and who has not replied, for each position.
- Reminders for the silent. On plans that include automated reminders, you can set a first reminder and a last call a number of hours before the event, so you do not chase by hand.
- A coordinator alert. If someone declines or stays silent after the last call, the coordinator of that position is told.
- Replacement, position by position. Planify can ask colleagues who cover the same position whether they can step in. A decline on one position does not change the status of another.
Which of these you can use depends on your plan.
Planify supports different ways to staff an event, from structured schedules to open calls. The confirmation step works the same idea for each: ask once, make the answer easy and show the result.
Read next: last-minute volunteer cancellation: a recovery plan.
FAQ
What is volunteer shift confirmation?
It is the step where a volunteer who is on the schedule says that they will actually be there. It is separate from scheduling, and it is what tells you whether a position is covered.
How far before an event should volunteers confirm?
There is no single rule. Many teams ask a few days ahead and follow up the day before. Pick a timing your volunteers can keep and use the same one every week.
Why do volunteers not reply to confirmation requests?
Most often because replying takes effort, the request is buried in a long message, or they plan to answer later and forget. Making the answer a single tap removes most of that friction.
What happens if a volunteer declines after confirming?
You need a replacement quickly. Asking the people who cover the same position, instead of everyone, keeps the request relevant and the chat quiet.