Monday morning, three events to reconcile
The wedding ran late because the speeches overran and the band started forty minutes behind. The corporate barbecue finished early when it rained. The private dinner went as planned, except one server left early and another stayed to help the drivers load.
Now the office has a supervisor's photo of a paper sheet, two texts from staff saying 'I did till 1am', a WhatsApp voice note and the original rota. Someone spends the morning building a list of hours for payroll, messaging people to check, and trying to work out whether the late finish at the wedding is something the client agreed to pay for.
Hours are captured after the fact
On the night, everyone is busy doing the job. Recording times is the last thing on a supervisor's mind at the end of service, especially at a venue with no office, poor signal and a van waiting to load.
- Paper sign-in sheets get wet, lost or photographed at an angle.
- Start times are the rota times, not the actual arrival.
- Finish times are remembered, rounded and sometimes disputed.
- Breaks, travel time and driver hours are handled differently by different supervisors.
- Nobody links overtime back to the reason, so recharging the client depends on memory.
By the time the office sees the hours, the event is two days ago and the details are fuzzy for everyone.
Drivers make it harder again. A driver who drops the kitchen kit at 2pm, goes back to the unit, then returns at 11pm for the pack-down has a split shift that no paper sheet at the venue captures. Their hours usually come from their own message the next day, and nobody else can confirm them.
What the reconstruction costs
Payroll takes longer than it should and is more likely to be wrong. Casual staff who are underpaid notice, and some stop taking your shifts. Overpaying does not get noticed at all.
The larger leak is usually overtime you could have charged. If your terms allow you to charge for service beyond the agreed finish, you need to know how many staff stayed, how long and why, and you need it before you send the final invoice. Reconstructed on a Monday, that information is weak, and the easy choice is to let it go.
Sign in at the venue, confirm at the end
- Each confirmed shift has a link sent to the staff member's phone. At the venue, they tap to sign in. The time and, if you choose, the location are recorded.
- If there is no signal, the page stores the tap and sends it when the phone reconnects.
- At the end, staff sign out, and the supervisor's view shows the whole team's times for that event.
- The supervisor confirms or adjusts each entry, and records a reason for any finish beyond the planned time, such as 'service ran late at client request'.
- Breaks, travel and driver time follow your rules, applied the same way at every event.
- Confirmed hours export to your payroll, and overtime linked to a client reason appears on the event's invoice draft for your office to decide on.
| Situation | What gets recorded | Who decides |
|---|---|---|
| Staff arrive early to set up | Actual sign-in time | Supervisor confirms against call time |
| Event overruns | Sign-out times and reason | Office decides whether to recharge |
| Someone leaves early | Their own sign-out | Supervisor notes why |
| Phone dead | Supervisor enters time manually | Flagged for office review |
This links to the shift system if you use one, but it works on its own too, starting from your rota spreadsheet.
A quieter Monday
The hours for the weekend are waiting when the office opens, already grouped by event, with the few exceptions highlighted. Payroll is a review rather than a rebuild. When staff query their pay, you can see exactly what was confirmed and by whom.
Event invoices go out with any agreed overtime already listed, with the reason attached, so the client can see what they are paying for. Whether you charge it is still your call, but you are deciding with the facts in front of you.
Recognise any of these?
- Casual staff hours are pieced together from photos, texts and memory.
- Staff query their pay more than occasionally.
- Events overrun and you do not charge for it because the detail is unclear.
- Supervisors each handle breaks and travel differently.