Volunteer Crews for Local Festivals: Scheduling Without a Rota Tool

Most temple committees and neighbourhood festival crews in Kerala run their volunteer scheduling on phone calls, a WhatsApp group and the memory of two or three people who have done it for years. That works, right up until it does not. The point where it breaks is usually not the number of volunteers. It is the number of separate jobs happening at the same hour.

If you take one thing from this: you do not need a rota tool. You need one written list of jobs by hour, and one named person per job. Almost every scheduling failure at a local festival is a job nobody was told was theirs.

What actually breaks

Committees rarely fail at getting people to turn up. Kerala festivals do not have a volunteering shortage. What goes wrong is more specific.

• Two people think someone else is handling the same job, so nobody does it
• One person is asked to do two things that both start at 6pm
• The person who knows the plan is inside the ground and unreachable for two hours
• Volunteers turn up at the announced time and stand around because the job before theirs is late
• Nobody knows who has the keys, the cash box or the generator contact

Notice that four of those five are information problems, not people problems. That matters because information problems are cheap to fix.

The smallest change that helps

Write the schedule as hours down the left and jobs across the top. Not people first. Jobs first.

This sounds trivial. It is not, because the usual method is people first: someone thinks of a volunteer, then thinks of what to give them. That method always leaves gaps at the awkward hours, because you run out of enthusiasm before you run out of hours.

Jobs first means you list what has to happen at 4am, at noon, during the procession, and in the hour after everyone leaves. Then you fill names in. Gaps become visible before the day rather than during it. The same counting exercise scales up to how many people a whole festival season needs.

Name one person per job, not a group

"The sound team will handle it" is not an assignment. One name per job per time slot. That person can bring five friends, and usually will. But when something goes wrong, one phone rings, not a group of eight where everyone assumes someone else picked up.

For anything involving money, keys, or a licence, write the name down twice: once on the schedule and once with the committee secretary.

Print it

This is the part that people resist and it matters most. Print the schedule. Put copies where volunteers stand: the entrance, the kitchen, the sound desk, the gate. Phone batteries die during a fourteen hour Theyyam or an all night boat race preparation. Network is uneven near the water and inside crowded grounds. A paper sheet taped to a pillar has never failed to load.

Keep the phone version too. Just do not make it the only version.

Build in the handover

Long festivals have shift changes and shift changes are where things fall over. Two minutes of overlap costs nothing and saves an hour of confusion. If the shifts do not fill at all, that is a staffing question, and a seasonal hire's start date matters more than the headcount.

Ask the outgoing person for three things, out loud, to the incoming person:

• What is done
• What is stuck, and who is chasing it
• What you would do next if you were staying

That is a handover. It does not need an app.

Where the crowd side is different

Volunteer scheduling is an internal problem. Getting people to know your festival is happening is a different one, and committees often mix the two up.

Most local festivals in Kerala are still discovered through word of mouth, a poster at a junction, and whoever remembers last year. That is fine for a fixed local crowd and poor for anyone new: a family visiting Thrissur for the first time, someone who has just moved to Kochi, a traveller who would have come to a Kathakali night if they had known it existed.

That is the gap EventifyPlus works on. It lists hyperlocal events across Kerala, temple festivals, Onam programmes, Thrissur Pooram, Theyyam and Kathakali nights, backwater boat races and Kochi carnivals, so organisers who otherwise depend entirely on word of mouth have somewhere to put the details, and people looking for what is on can find them. It is not a rota tool and it will not schedule your volunteers. It handles the other half of the problem.

A short checklist for the week before

• Jobs listed by hour, including the hours nobody wants
• One name per job, per slot
• Two names for money, keys and licences
• Schedule printed and taped up in four places
• One person nominated as the answer to "who do I ask", and their number on every printed sheet
• Two minute handover at every shift change

Six lines. No new software. Most of the difference between a festival that runs and a festival that mostly runs comes from exactly this much preparation, done a week earlier than feels necessary. Office teams meet the same weeks from the other side, planning delivery around Onam and Pooram.