Why Event Crew Hours Never Add Up, and the Fix

Your event ran 9am to 5pm. The crew log says 9 to 5. But the truck arrived at 6:30am, three people stayed until 9pm breaking down the stage, and two volunteers you swear were there don't appear anywhere. When the grant report asks for total crew hours, the number you submit is wrong, and it's wrong low.

This happens on almost every event, and the reasons are boring and fixable. None of them require chasing people down by text the next morning.

Setup and teardown are the hours that disappear first

The published event time is the part everyone remembers. Nobody puts the 6:30am load-in or the 8:45pm teardown on the schedule, so nobody captures it. A crew of eight working two unlogged hours on each end is 32 hours missing from a single day. That is not rounding error. That is a third of the labor on a typical one-day build.

The fix is to stop treating the event as one block. Have crew clock the moment they touch a box, not when doors open. If you split your day into distinct setup, execution, and teardown shifts, the early and late hours land in their own buckets and you can report them separately for grants or invoices.

Forgotten clock-outs that inflate the numbers

The opposite problem also wrecks your totals. Someone taps in at 7am, the day gets hectic, and they never tap out. Left alone, that open entry keeps running. The next time you look, the system says they worked 19 hours because it counted up to the current moment.

The honest way to handle a forgotten clock-out is to close the entry at a sensible cutoff, not at whatever time you happen to open the report. Kangaroo Clock does this with an auto-close rule for stale entries: a forgotten clock-out is closed at its start time plus your cutoff, never at the current time. A volunteer who tapped in and walked off never shows up as a 19-hour shift that drags your average and your payroll math out of reality.

If you are reconstructing a messy day by hand, the time card calculator will at least give you clean per-person totals once you have honest in and out times.

The people who were there but never registered

Two volunteers showed up, worked, and left no trace. Usually it's because signing in was a hassle. There was one clipboard at the wrong table, or one tablet that someone walked off with, or a sign-in app that asked people to create an account they didn't have time for.

The cure is to make clocking in take three seconds and require nothing from the worker. With Kangaroo Clock, crew tap their name on a shared tablet at the gate, scan a posted QR code, or open a personal link. No app to install, no password, no account. For a fast crew sign-in setup you can print a QR sign-in poster and tape it at every entry point, so people sign in on their own phones the moment they arrive instead of hunting for the one clipboard.

When sign-in is frictionless, your headcount stops drifting. Your CSV export includes a distinct-worker count, so the number of people who actually showed is a fact you can pull, not a memory you argue about.

Multi-day events lose hours in the seams

A three-day festival multiplies every problem above. Crew rotate. Someone works Friday setup, disappears Saturday, and reappears Sunday for teardown. If you are tallying by hand, the seams between days are where hours leak out and where double-counting creeps in.

Tags and worker groups keep this straight. Label entries by day or by stage, group people by role, and filter the report to exactly the slice you need. The mechanics of tracking hours across a multi-day festival come down to good labels and a clock that never makes someone log in twice.

What an accurate event log actually requires

Three things, none of them complicated:

• Crew clock the real start, including load-in, not the published door time.
• Forgotten clock-outs close at a fixed cutoff instead of running to the present.
• Signing in is so easy nobody skips it, which keeps your headcount honest.

Get those right and the total adds up the first time. No reconstruction, no apologetic emails to the grant officer, no guessing how many people worked teardown.

Kangaroo Clock is built for crews that don't bill by the hour and don't want to hand out logins. It shows who is on the clock right now, stores every time in UTC and displays it in your local time, and exports a CSV with a column layout that never breaks between events. It is not a monitoring tool: no GPS, no screenshots, no location tracking, ever. See how it fits an event operation on the page for event organizers, then start a free workspace and have your gate set up before the next load-in.