KangarooClock

← Blog

Keep Festival Setup, Show, and Teardown Hours Apart

· 5 min read

It is Monday after the festival and you are staring at one long list of clock-ins. A rigger who built the stage Thursday morning also pulled a teardown shift Sunday night. A box office volunteer covered gates during the show and then helped strike the merch tent. On the list, all of it looks the same: a name, a start, an end. You need to tell the grant funder how many hours went into setup, pay the stage crew for show days only, and figure out who to ask back for next year. Right now you cannot, because setup, show, and teardown all blend into one pile.

That blur is not a reporting problem you fix at the end. It starts the moment people clock in, and the fix starts there too.

Why festival hours run together in the first place

A multi-day event is really three or four jobs stacked on one calendar. Load-in and build. The show itself, maybe across several days. Strike and load-out. The same people often work more than one phase, and the phases overlap at the edges. Teardown on the main stage can start while a side stage is still running.

If every one of those shifts lands in the same bucket with nothing to separate them, the only thing distinguishing a Thursday build shift from a Sunday strike shift is the date. And dates lie to you here, because a single calendar day can hold two phases. Sunday morning is still show. Sunday night is teardown. The clock does not know the difference unless you tell it.

The second cause is the forgotten clock-out. A volunteer taps in for setup Thursday, gets pulled into a hundred small fires, and never taps out. Left alone, that entry runs until someone notices, sometimes days later, and now one build shift reads as 40 hours. For more on why that happens and how a sane cutoff fixes it, see our explanation of how a missed clock-out gets closed cleanly in the entry for auto-close.

Tag each shift by phase as it happens

The clean report starts with a label on every entry. In Kangaroo Clock, tags mark time entries and worker groups mark people. For a festival that means a tag per phase: setup, show, teardown. A rigger who works all three gets three entries with three different tags, not one undifferentiated block.

Workers do not manage any of this. They clock in three ways with no login and no app: tap their name on a shared tablet, scan a posted QR code, or open a personal link. You decide how the phase label gets attached, and the worker just taps in. If you run separate kiosks or separate QR posters at the build site and the show gates, the entries sort themselves by where people actually were.

Worker groups do the other half. Put stage crew, box office, and food in their own groups, and you can pull hours by role across the whole weekend or inside a single phase. "How many teardown hours did the stage crew log" becomes a filter, not an afternoon with a highlighter. We walk through the full setup for a weekend event on the page about tracking hours across a multi-day festival.

What a clean phase report looks like at the end

When every entry carries a phase tag and a worker group, the export does the sorting. Kangaroo Clock gives you a CSV with a stable column schema that never breaks between events, including a distinct-worker count, so the file you pull this year lines up with last year's. Filter by the setup tag and you have build hours for the grant report. Filter by show and the stage crew group and you have exactly the hours to pay. Filter by teardown and you know who stayed to the end.

QuestionFilter
Total build hours for the fundersetup tag
Pay for stage crew, show days onlyshow tag + stage crew group
Who to ask back for strike next yearteardown tag, distinct workers

The distinct-worker count matters more than it sounds. A funder usually wants both hours and headcount, and one person who worked three phases should count once as a person and three times in hours. The export keeps those straight so you are not deduplicating names by hand.

Handle the overlap days before they bite you

The messy part of any festival is the day a phase ends and the next begins. Sunday is the classic. The safest habit is to treat a phase change like a real clock-out and clock-in, not one continuous shift. A volunteer who works gates until 6 and strike until 11 should have two entries, tagged show and teardown, with a gap or a hard break between them. If you are fuzzy on the terms, the glossary covers what a clock-out records in plain language.

That split is also your defense against the inflated-hours trap. If someone forgets to tap out of a setup shift, the stale entry closes at its start time plus your cutoff, never at the current time, so a Thursday build does not quietly eat Friday. You see a flat, honest number instead of a 30-hour ghost shift.

Set the phases up before load-in starts. Make your tags, sort people into groups, and print a QR poster for each location. Our QR sign-in poster generator gives you a printable sheet you can tape at the build gate and the front gate. Then on Monday the report is already sorted, and you spend the morning on next year instead of a spreadsheet.

Tags: festivals, events, time tracking, tags

See it in your own setup

No signup needed. Add a few names, share a kiosk URL, watch hours land.

Try the demo →