KangarooClock

← Blog

Build a Clean 5K Roster: Water Stations and Finish

· 5 min read

You have 40 volunteers across five water stations and a finish line crew, a race that starts at 7 a.m., and no time to chase sign-in sheets at mile three. The goal is one report at the end that tells you who worked, where, and for how long, without you reconstructing it from memory. Here is the order to set it up so the day runs itself.

Set your groups before you touch any names

Start with worker groups, because groups label people and tags label time. For a 5K, make one group per crew: Water Station 1, Water Station 2, on down to Water Station 5, plus Finish Line. If you have a few floaters who cover gaps, add a Roving group too.

Why groups and not just a long list of names? Because at the end you want to filter the report to "just the finish line crew" without clicking through 40 people. A group makes that one filter. Keep the names short and consistent. Water Station 3 sorts cleanly; "WS3 (near the turnaround)" does not.

Add people to each crew

Add your volunteers and drop each one into their group. Workers never get accounts here, so you are not inviting anyone or managing passwords. You are just building a list: name, group, done. A volunteer who both pours water and later helps at the finish can sit in two groups if your plan has them moving, but for most 5Ks one person stays at one spot, so one group is right.

If a volunteer shows up unassigned on race morning, you can add them on the spot from the same admin screen. Do it before they start pouring so their first clock in lands in the right crew.

Decide how each crew checks in

Each crew needs a way to start the clock. You have three options and they mix freely across one race:

  • Shared-tablet kiosk. Good for the finish line, where there is a table, power, and a crowd. One tablet, everyone taps their name.
  • QR poster. Good for water stations out on the course with no table and no outlet. Print a poster, zip-tie it to the canopy pole, and volunteers scan it with their own phones. You can make one with the QR sign-in poster generator.
  • Personal link. Good for a station captain who wants to clock their own small crew in from one phone, or for a roving volunteer who is never near a poster.

For a spread-out course, QR posters at each water station and a kiosk at the finish is the usual split. Nobody installs an app, nobody logs in. The full picture of how crews check in at an event walks through each method side by side, including which fits a canopy on a muddy field.

Tag the race so the hours group themselves

Groups sort the people. Tags sort the time. Create one tag for the event, something like 5K-2025, so every entry from race day carries it. If your organization runs several races a year, this is how you keep April's 5K hours from blending into October's.

You can tag entries by crew too, but you often do not need to, because the worker group already tells you which station someone worked. The simplest clean setup is one event tag plus your per-crew groups. That gives you two ways to slice the same data: by race and by station.

Walk the course and post the check-in

The day before, or early that morning, physically place each check-in point. Tape the kiosk tablet to the finish line table. Zip-tie each water station's QR poster at eye level where a volunteer will actually see it when they arrive. Test one scan at each station yourself. A poster face-down in a bin helps nobody.

Open your dashboard on your phone. It shows who is on the clock right now, so as crews arrive you can watch Water Station 2 fill in and notice that Station 4 still shows nobody at 6:45. That is your cue to make a call, not a surprise you find at noon.

Handle the volunteer who forgets to clock out

Someone will tear down their station, load the truck, and drive home without clocking out. That is normal. Auto-close handles it: a stale open entry gets closed at its start time plus your cutoff, never at the current moment. So a forgotten clock-out at Water Station 5 does not quietly report 14 hours when the volunteer worked four. Set the cutoff to match a realistic shift length for your race and move on.

Export one clean report when the race is done

After the finish line clears, pull a CSV export. The column schema is stable and does not shift between exports, so the spreadsheet you hand to your grant reporter in March matches the one from last year. It includes a distinct-worker count, which is the number most charity 5K reports actually want: how many unique volunteers showed up.

Filter by the 5K-2025 tag to isolate race day. Filter by worker group to break hours out by station. If a volunteer needs proof of service for school or a program requirement, the volunteer hours certificate generator turns their total into a printable certificate.

That is the whole workflow: groups first, people into groups, a check-in method per crew, one event tag, auto-close for the stragglers, one export at the end. Build it once and the next race is a copy with new dates. When you are ready, start a free workspace and set up your first two crews before race week.

For more, see Volunteer crew check-ins at an event.

Tags: events, volunteers, setup, tags

See it in your own setup

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

Try the demo →