How to organise event staff payments without arguments
For people hiring: what to put in writing before the event, how to measure the working day, when to pay, how to handle overtime and dropouts, the closing sheet.
Almost every argument with staff after an event is about money, and almost none is down to bad faith. They're about things that weren't said: whether the meal was included, whether teardown was paid separately, from what time overtime started. This guide is for people who hire and want to close the event with a clear calculation, not an angry WhatsApp group.
We won't give you amounts: they depend on the role, the area and the event. For a reference there's how much event staff cost. Here's the method.
1. Put everything in writing before you book anyone
What isn't written down gets remembered differently on each side. Before sending a single offer, define:
- Amount. Per day, per shift or per hour. One, and clear.
- What it includes. How many hours that amount covers, whether it includes setup or teardown, whether there's a meal, whether there are travel expenses or transport.
- Call time and estimated finish time. With setup and teardown included, not just the event's hours.
- Overtime. How it's paid and who authorises it.
- Dropouts. Until when people can give notice and what happens if someone doesn't show up.
- When and how payment is made. A specific date and payment method. "After the event" isn't a date.
- What paperwork you need. If you're going to ask for an invoice, say so from the start. The name and requirements depend on your country; in Argentina, workers usually invoice under the simplified tax scheme explained in monotributo for event workers in Argentina, and for the hiring side there's paperwork for hiring temporary event staff.
On LABURO, each offer carries the role, date and time, venue, amount and a conditions field for hours, tasks and anything else you want to make clear. The person reads it in full and accepts from their phone. Use that field to write everything above: everyone gets the same information, in writing.
2. Measure the working day with a record, not with memory
If pay depends on hours, you need to know what time each person arrived and left. A paper sheet signed by the coordinator works until it gets wet, gets lost or someone signs for someone else.
LABURO has clock-in: each person confirmed for the event clocks in and out from their phone, with their GPS location. On the event board you see who clocked in and at what time. If someone forgot to clock out, you correct it by hand and write the reason; corrected entries stay marked, so it's clear the person didn't clock it themselves.
Two rules that help:
- Say at the briefing that people clock in, and who to tell if their phone isn't working.
- Check the clock-ins before the team leaves, not the next day. Correcting with the person in front of you avoids the argument.
If the event has long shifts or relief staff, it's worth planning them beforehand with shift planning for long events: each shift with its own hours makes measuring and paying simpler.
3. Overtime: authorised and noted on the spot
The event runs over: the client asks to stay longer, teardown takes more time, the truck arrives late. Overtime itself isn't the problem. The problem is overtime nobody authorised and everyone counts differently.
- One person authorises overtime (you or whoever is coordinating) and says it out loud to the team: "we're staying an extra hour, it's paid as agreed".
- The rule for how it's paid is written in the offer from the start.
- It's noted at closing, with the clock-in record as backup.
4. Dropouts and absences: the same rule for everyone
Someone will drop out. What matters is that the rule is written beforehand and applied the same way to everyone. Some points to define:
- Until when a dropout can be notified.
- What happens with someone who doesn't show up without notice.
- What happens with someone who had to leave early for a valid reason: they're paid for the time worked according to the clock-in.
The day of the event isn't the time to do sums: the urgent thing is covering the position. That's what what to do when event staff don't show up is for. The calculation goes on the closing sheet.
5. The closing sheet
When the event ends, put together a sheet with one row per person. The minimum columns:
| Column | What goes in it |
|---|---|
| Name | Who worked |
| Role | Which position |
| Agreed amount | The one in the offer |
| Clock-in and clock-out | From the record (mark if corrected) |
| Extras | Authorised hours and amount |
| Travel expenses | If applicable |
| Deductions | Only if they're in the written rule |
| Total | The sum |
| Paid | Date and method |
On LABURO, the Payments screen shows what you've committed to the staff who confirmed: the amount per person and per event, and the total. That's your base: you transfer it to your sheet, add the extras and travel expenses columns and your closing is ready.
Send each person their row before paying. If someone spots a mistake, it gets corrected before, not after.
6. Pay when you said you would
What weighs most in getting the same team to want to work with you again isn't the amount: it's paying on the date you promised. If something is delayed, tell them before the date, not after. A team that trusts it will be paid is a team that doesn't drop out.
And when you close, take the chance to note who worked well: how to evaluate event staff explains how.
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.
