Guide

How to plan staff shifts and hours for a long event

How to build the shift grid for a long or multi-day event: operational blocks, overlapping handovers, call times in writing and nobody booked twice at once.

8 min readBy SOMOS DER

A four-hour event can be handled with a list. A twelve-hour one, or a three-day one, can't: it needs a grid. And the grid is built in an order that almost nobody follows.

First: stop thinking about "the event"

A long event isn't a long day. It is four different operations that overlap:

  • Setup. Loading and unloading, building, technical. Almost always the day before or in the early hours.
  • Opening and registration. The shortest peak, the most visible and the hardest to recover if it goes wrong.
  • Operation. Bars, catering, guest service, cleaning, technical crew in the booth.
  • Close and teardown. In the early hours, with fewer people available and systematically understaffed.

Each block has its own headcount, its own call time and, in general, its own people. If you build one giant shift to cover them all, you are paying people to stand around in the dead hours and you'll be short at the peak.

Second: build the grid by position, not by person

This is the right order, and it is counterintuitive:

  1. Write down the positions that need to be covered and in which time slot. "Bar 1, 9 pm to 3 am". "Door 2, 7 pm to 9 pm".
  2. Cut each slot into shifts according to what the role can sustain.
  3. Only then put a name in each slot.

Almost everyone does it the other way round: they start with the people available and fit the hours around them. That is how you end up with a grid that adds up on the spreadsheet and has gaps exactly where it hurts.

Third: the call time is not the opening time

The time you send people is not the time the event opens. It is the time they have to be at their post, changed and briefed.

That difference is real and it costs money: it is time the person is at your disposal, and it is also the buffer that saves you when someone is late. A no-show spotted at call time can be covered; the same no-show spotted with the doors open can't.

Always write both times: when people are called and when they are expected to finish.

Fourth: overlap the handovers

If the relief starts at 11 pm and the outgoing person leaves at 11 pm, the post is uncovered during the handover. Ten minutes of overlap at each handover costs little and avoids the classic "the queue built up during the shift change".

And something that always gets forgotten: relief staff are headcount. If you don't count them as positions, they come out of the same team, and you are back to the empty post you wanted to avoid.

Fifth: the hours travel with the offer

A grid that lives on your spreadsheet is useless if each person has a different version in their head. The hours have to be inside the confirmation, not in a separate message.

At LABURO each offer carries the role, the date, the place, the amount and a conditions field where everything that needs spelling out goes: call time, estimated finishing time, tasks, clothing. The person sees it before deciding, accepts it with one tap and is confirmed for that event. There is no different version going round on chat.

Sixth: the reminder the day before

At a long event most people accepted their shift weeks ago. Nobody remembers an old email.

That is why the system sends an automatic reminder to the confirmed team before the shift, with the place and time, and asks them to say straight away if they can't make it. The same mechanism works on the other side: if an offer is about to expire with no reply, a reminder goes out before it lapses. An early warning can be covered; a silent absence can't.

Seventh: no one double-booked

In high season the most expensive mistake isn't being short-staffed: it is confirming the same person for two overlapping events and finding out on the day.

That isn't solved by memory. It is solved by having everything in one place:

  • The master calendar, with each event and how many confirmed staff it has.
  • A filter in the search to hide people already assigned to an overlapping event.
  • The dashboard for each event, showing how many positions in the headcount are covered, how many are pending and how many are open.

Eighth: close the loop with check-in

At the end of the event you need to be able to say, without argument, who was there and during what hours. At LABURO staff clock in and out from their phone on the day of the event, and the hours are recorded. If you entered the venue's address, the system also records how far from the venue the check-in happened: it doesn't block anything, it flags it so you can decide.

That is the difference between paying people based on data and paying them from memory.

The grid checklist

  • Did I separate setup, opening, operation and teardown?
  • Did I build the grid by position before adding names?
  • Did I write the call time and estimated finish, not just "Saturday"?
  • Are handovers overlapped and counted as headcount?
  • Are the hours inside the offer the person accepts?
  • Did I check that nobody is confirmed for two overlapping events?
  • Do I have a way to record the actual hours?

This shift structure is the one SOMOS DER builds for multi-day events. If the event has registration, the staffing peak is concentrated at door opening, and that is where it pays to measure it with real entry data: that is what PASE shows.

If the long event has a bar or food service, the hospitality team is planned separately: see hiring bartenders for a corporate event.

Planning an event in Argentina?

LABURO is the event staffing platform built by SOMOS DER in Buenos Aires. Tell us the date, the venue and the roles you need and we'll tell you how we can help: write to us on WhatsApp.

FAQ

What people ask us most.

How are staff shifts organised at a multi-day event?

By splitting the event into operational blocks instead of thinking of it as one day: setup, opening and registration, operation, and close and teardown. Each block has its own headcount, its own call time and often its own people. Then you build the grid by position (not by person) and only at the end put a name in each slot. Building the grid the other way round, starting from the names available, is what leaves gaps at the peak.

How long should an event staff shift be?

You set the number according to the role and the physical demand, but the rule that is general is that the length of the shift has to be written down before the person accepts, and it has to include the call time beforehand. A bar shift at the peak and a cloakroom shift in the small hours don't wear people out equally over the same number of hours: critical roles get cut shorter than quiet ones.

How do I do handovers without leaving a post empty?

By overlapping. The relief arrives a few minutes before the person on duty leaves, so there is a handover and the post is never left unattended. If the relief starts at the same time the previous person leaves, in practice the post is uncovered during the handover, just when the queue builds up. And relief staff count as headcount: if they aren't in the numbers, you take them out of the same team.

How do I avoid confirming the same person for two overlapping events?

By keeping the calendar and the confirmations in one place, not in separate chats. At LABURO the search has a filter to hide people already assigned to an overlapping event, the master calendar shows each event with the number of confirmed staff, and the dashboard shows for each event how many positions are covered and how many are missing.

LABURO

Real staff,
for your event.

LABURO is the event staffing platform built by SOMOS DER, an event production company in Buenos Aires, Argentina. If you are planning an event in Argentina or want to know how it works, write to us.