How Many People You Need to Cover a Temple Festival Season

If you are trying to work out how many people you need to cover a temple festival season, the honest answer is that the number depends less on how many events there are and more on how much verification each one needs. Listing is fast. Confirming that a date, a time and a venue are correct is slow, and it is the part that breaks small teams.

Here is what the work actually looks like when hundreds of local events land inside a compressed window.

The four jobs hiding inside one job

People plan for one task called covering an event. It is four.

• Finding. Discovering that the festival exists at all. Notices, local groups, temple committees, word of mouth, last year's records.
• Verifying. Confirming dates and timings with someone who knows. This is where the hours go, because the person who knows is often not reachable at office hours.
• Writing. Turning it into a listing somebody unfamiliar with the place can use. Location that makes sense to a visitor, timings that mean something, what actually happens.
• Photographing. Getting an image that represents the event rather than a stock temple picture. This one has a hard constraint: you have to be there.

Only the first three can be done from a desk. That distinction drives your staffing more than anything else.

Why the season is not evenly loaded

The instinct is to divide the number of events by the number of weeks. That fails, because the work does not sit where the events sit.

Before the season, finding and verifying dominates. This is a research load and it can be spread. It is also the work most often started too late, which is why so many listings go out with dates that turn out to be wrong.

During the season, the load moves to photography and same day corrections. Events cluster on auspicious days, so several will run on the same date, sometimes in different districts. It is the same clustering that makes office delivery dates unreliable around Onam and Pooram. No amount of desk work fixes this. Either someone is physically at each one or you do not have original photographs of it.

After each event, there is a small tail of corrections and cleanup that everyone forgets to staff.

Where a small team runs out

Three failure points show up again and again.

The verification bottleneck. One person can only make so many calls, and temple committees are volunteers with day jobs. If verification sits with a single person, your ceiling is their phone time rather than your listing capacity.

The clash day. When five festivals fall on the same date across three districts, a team of two covers two of them. This is a scheduling problem you can see months in advance, and it is the one most worth planning for.

The correction backlog. Every wrong timing generates work later, usually during the busiest week. Sloppy verification early is a debt that comes due at the worst moment.

A way to size the team honestly

Do this with last season's list rather than a guess.

• Count the events, then mark which ones need original photography rather than a supplied image. That subset drives your on the ground headcount.
• Group the photography subset by date and district. Count the worst clash day. That number is your minimum field capacity if you want full coverage, and it tells you immediately whether full coverage is realistic. If you need extra hands for it, the start date matters more than the headcount.
• Estimate verification separately. How many calls, how many callbacks, how many events had unreliable information last time. Verification is a steady load you can start early and it does not have to be the same people.
• Decide what you will not cover. Every team makes this decision. Making it deliberately is much better than discovering it on a Saturday.

The part nobody staffs

Organisers. A large share of local festivals are run by committees who rely on word of mouth and a printed notice, and who are scheduling volunteer crews without a rota tool at the same time. Getting them to submit their own details is slower than researching them yourself the first time and much faster every time after.

Time spent building that relationship in the quiet months reduces the verification load permanently. It rarely gets staffed because it produces nothing this week.

This is the two sided problem EventifyPlus works on in Kerala: people trying to find what is on, and organisers who otherwise depend on word of mouth to be found. Both sides are real work, and the second one is the one that compounds.

There are already established players in this market, which tells you the demand is genuine and the coverage problem is hard rather than novel. Anyone sizing a team for a festival season should assume verification is the constraint, plan around the clash days, and be honest early about what will not be covered.