What to check before hiring staff for an event
The six things to verify before confirming temporary event staff, and what goes wrong in practice when it is handled via WhatsApp chains and spreadsheets.
Hiring temporary event staff almost always goes wrong for the same reason: you confirm people who aren't really confirmed. These are the six things to check beforehand, and what happens in practice when you don't.
1. That the profile is verifiable
A name and a phone number on a spreadsheet are not a profile. Before confirming someone you should be able to see what they've done before: which roles they've worked, at what kind of events, and their CV. Not to ask a runner for a corporate-style résumé, but to know whether the person has already worked a bar on a Saturday night or whether it's their first time.
What goes wrong if you don't check: you confirm by role and find out on the day that "bartender" meant two shifts at a small bar. It isn't the person's fault, it's a badly set expectation. With the profile in front of you, you put them where they perform best.
2. That the confirmation is in writing, with the terms included
An "ok" in a WhatsApp group is not a confirmation. A confirmation has, at the very least: which role, which days, what hours, where, how much is paid and when it's paid. And an explicit acceptance from the person.
What goes wrong if you don't check: on the day, the arguments nobody wants to have at the door start. "I understood I started at eight." "I was told a different amount." There's no bad faith: there are twenty different conversations and none of them written in the same format.
On LABURO each person receives an offer with the pay, dates and hours, accepts it with one click and is confirmed for that event. And the producer sees the real status of each offer: sent, seen, accepted, declined or expired.
3. The area and the real journey
It's not enough for the person to say they can make it. Check where they're coming from and what time they finish. A teardown that wraps up at 5 a.m. in an area with no public transport is not the same for someone who lives ten blocks away as for someone who has to cross the whole metropolitan area.
What goes wrong if you don't check: people who live far away leave before the end, or never confirm how they'll get home. Teardown ends up short-handed right when nobody answers the phone any more.
4. That the role is really defined
"Support staff" is not a role. Each person needs to know what they do, who they report to and where they're stationed. The difference between a bartender and a barback, between a registration agent and a scanner operator, is real and decides whether the bar flows or jams.
What goes wrong if you don't check: fifteen people arrive and they all ask the same question. The producer spends the first hour of the event acting as staff coordinator instead of producing.
5. What happens if someone doesn't show up
Someone won't show up. That's a fact, not an accident. What sets a serious operation apart is that it's already planned for:
- A buffer above the minimum headcount, especially in critical roles (door, till, bar).
- A short list of replacements per role, people who already know they may be called.
- A call time earlier than when you really need people, so the gap is spotted in time.
A no-show reported two hours ahead can be covered. The same no-show discovered with the doors open can't.
6. How you record who worked
At the end of the event you need to be able to answer, without arguing: who worked, in which role and during which hours. Payment depends on that, and whether that person picks up your call next time depends on payment.
What goes wrong if you don't check: the payroll is put together from memory and screenshots. Discrepancies appear, people get overpaid or underpaid, and your relationship with good staff wears down over an argument about hours nobody wrote down.
On LABURO attendance is recorded by clocking in and out on the day of the event, so the hours are logged without depending on anyone's memory.
The underlying problem: the spreadsheet and the WhatsApp chain
All six points above fail for the same reason. Staff information is scattered: a spreadsheet that is already out of date, a group where people were confirmed, individual chats where different terms were agreed, and an email with last week's list.
Nobody is lying. There simply isn't a single version of the truth, and on the day of the event that becomes uncertainty: you don't know how many people will arrive until they arrive.
Before confirming, check this
- Can I see each person's experience and CV?
- Does each one have a written confirmation with role, date, hours, place, pay and payment date?
- Did they explicitly accept, or did they just see it?
- Do their area and finishing time work for them?
- Do I have replacements identified for the critical roles?
- How will I record who worked and for how long?
This is the filter SOMOS DER applies before confirming anyone. It works just as well if you hire on your own: what changes the outcome isn't the CV, it's having verifiable references and a written confirmation.
If you're deciding whether to outsource the team or call people in yourself, it helps to compare what an agency covers with what you'd manage directly on a platform.
Planning an event in Argentina?
LABURO is the event staffing platform built by SOMOS DER in Buenos Aires, with more than 1,200 real profiles with experience and CVs uploaded. The LABURO team builds your staff with people from your area, and each person receives an offer with pay, dates and hours that they accept with one click. 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.
