Running Crew Check-Ins Across a Multi-Day Festival

You have 40 crew working a three-day festival. Some run the main stage Friday, the merch tent Saturday, and parking Sunday. A few never touch the same post twice. Nobody is going to install an app or remember a password at 6 a.m. while unloading a truck. Here is the order to actually do this in, from the week before to the spreadsheet you hand finance on Monday.

Set up locations and groups before anyone arrives

Decide how you want the final report sliced, then build the labels to match. For a festival, two cuts usually matter: where someone worked and what they did. Use worker groups for the people (Main Stage Crew, Merch, Parking, Box Office) and tags on time entries for the location or activity. If your festival has three stages, a tag per stage lets you answer "how many crew-hours did the South Field stage cost?" without re-sorting anything by hand.

Crew who rotate are the reason this works. A parking attendant Friday who runs merch Saturday gets one tag on Friday's entry and a different tag on Saturday's. You are not creating two versions of that person. The same name carries across every day and every post.

If you are also splitting build day and strike, keep those separate from show days. The approach for tracking setup, execution, and teardown shifts separately works cleanly alongside per-stage tags, and it keeps your load-in overtime from hiding inside show hours.

Pick the check-in method for each post

Different posts need different check-in methods. A staffed crew tent can run a shared tablet: crew tap their name on the kiosk to clock in, no login, no account. A remote gate with no power and no table is better served by a printed QR code taped to the booth. A scattered crew (sound techs roaming between stages) does best with a personal link each person opens on their own phone.

You can mix all three across one festival. Print the codes ahead of time with the QR sign-in poster generator and post one at each gate. Lay out the whole plan, which posts get a tablet, which get a code, which get links, on the guide for tracking hours across a multi-day festival so your stage managers know what to do when crew show up.

Walk a stage manager through it once. Tap name, confirm, done. Clock-out is the same tap at the end of the shift. The whole point is that a 17-year-old volunteer and a veteran rigger both do the identical thing without being told twice.

What each method looks like in practice

• Shared tablet kiosk: best for a crew check-in tent with a person nearby. Crew tap their name from the list.
• Posted QR code: best for unstaffed gates and remote posts. Crew scan with their own camera.
• Personal link: best for roaming roles who never pass a fixed station.

Try the tap-to-clock flow yourself on the live kiosk demo before you commit a method to a post. Two minutes there saves a confused line on Friday morning.

Watch the floor while the festival runs

During the event, open the dashboard to see who is on the clock right now. This is your live headcount per post. If the South Field stage shows three crew on the clock when the rotation says six, you know to send someone before the set starts, not after.

Forgotten clock-outs are the predictable mess of any multi-day event. Crew finish a shift, get pulled into striking the stage, and walk off without tapping out. Kangaroo Clock handles this with auto-close for forgotten entries: a stale open entry gets closed at its start time plus your cutoff, never at the current moment. So a crew member who clocked in at 8 a.m. Saturday and forgot to clock out does not show up Monday with 41 straight hours. The auto-close caps it at a sane number instead of letting one missed tap wreck the report.

You still want to skim the open entries at the end of each night. Catching a missed clock-out while you remember the shift beats reconstructing it from memory three days later.

Export clean hours when the festival ends

After strike, export to CSV. The column schema is stable and does not change between events, so the file you pull this year drops into the same spreadsheet you used last year. The export includes a distinct-worker count, which is exactly the number a grant report or a sponsor recap asks for: how many unique people worked the festival, not how many shifts they covered.

Filter before you export. Pull just the Parking group, or just the South Field tag, and you get that slice's hours without manual sorting. Because all times are stored in UTC and shown in your local time, a crew member who clocked in during a late set after midnight lands on the right calendar day.

If finance needs hours as decimals for a flat stipend, run the figures through the payroll hours converter to turn HH:MM into decimal. Kangaroo Clock records the hours and hands you a clean file; it does not run payroll or move money, so the conversion and the payout stay on your side.

The short version of the order

Build groups and tags, assign a check-in method per post, post the codes, watch the live board during the festival, let auto-close handle the missed tap-outs, then filter and export. Do the setup once and a 40-person rotating crew tracks itself for the rest of the weekend. When you are ready, start a free workspace and build your stage groups before load-in.