A Coordinator's Sign-In Day, Hour by Hour

You are running a Saturday build. Thirty-something volunteers, one three-hour shift, a folding table by the door, and a grant report due Monday that needs a defensible headcount. Here is how one coordinator, Maria, ran her morning, minute by minute, so you can copy the parts that fit your event and skip the parts that do not.

7:40 a.m. Set the table before anyone shows up

Maria arrives twenty minutes before the first volunteer. She props a printed QR poster against a water pitcher at the check-in table and props an old tablet next to it, screen on, kiosk page loaded. Both point at the same workspace. She made the poster the night before with the QR sign-in poster generator and taped a laminated copy at the coffee station too, because the line at one table always backs up.

No worker accounts to hand out. No app for anyone to install. A volunteer either scans the code with their own phone or taps their name on the tablet. That is the whole setup, and it took Maria four minutes to lay out.

8:00 a.m. The first wave, 22 people in eleven minutes

The doors open and the first surge hits. Twenty-two volunteers arrive between 8:00 and 8:11. About two thirds scan the poster with their own phones; the rest tap their names on the tablet. Maria watches the admin dashboard on her laptop and sees the on-the-clock count tick up in near real time: 6, then 14, then 22.

One name she does not recognize appears: "Sam R." She had a Sam Rivera on the pre-list and a walk-in named Sam Reyes. She adds the walk-in as a new name on the spot, and both Sams show as separate entries. A volunteer coordinator spends half of sign-in day resolving exactly this kind of ambiguity, so having two distinct records instead of one merged blob matters when the report runs.

The double tap

At 8:07 a volunteer taps her name, does not see an obvious confirmation, and taps again. That could create two open entries. Maria sees a duplicate on the dashboard, opens the second one, and closes it immediately. Thirty seconds. She does not need to memorize a fix; she just needs to be watching the live view during the rush, which is the one time it earns its keep.

9:15 a.m. Two more arrivals and a group filter

Two latecomers trickle in at 9:15 and 9:22. Maria tags both as "Site B" because she is splitting people between the interior painting crew and the yard cleanup, and the grant reports those separately. Worker groups label the people; tags label the time entries. She uses both. When she filters the dashboard to Site B, she sees 11 people, which matches the crew lead's headcount over the radio. Good enough to trust.

By mid-morning the running total on the dashboard reads 34 distinct volunteers. Maria had 31 on her pre-list, so three walk-ins joined. She does not have to recount heads; the distinct-worker count is already tracking it for her.

11:00 a.m. Close, and the two people who forgot to clock out

The shift ends at 11:00. Most volunteers tap out or scan out on their way to the parking lot. Two do not. One left early for a family thing at 10:20 and walked straight to her car. Another simply forgot.

This is the moment that quietly wrecks a lot of hand-kept rosters. If a forgotten entry stays open, it can balloon to eight or ten hours by the time someone notices. Kangaroo Clock handles it with a cutoff that closes stale entries at the start time plus a set limit, never at the current clock. So the volunteer who arrived at 8:05 does not get credited to midnight. She gets closed at a sane cap, and Maria adjusts the one she knows about (the 10:20 early leaver) by hand to the real time. Two edits, both under a minute.

11:20 a.m. Reconcile the roster and export

With everyone gone, Maria does the reconciliation that used to take her a Sunday afternoon. She pulls up the day's entries and checks the three things that actually matter for the grant:

• Distinct volunteers: 34, matching her pre-list plus three walk-ins.
• No entries still open. The auto-close and her two manual fixes cleared them.
• Site A vs Site B split, by tag, so the two program lines report separately.

Then she runs a CSV export with a stable column layout. The columns do not move from month to month, so the formula in her grant spreadsheet keeps working without her re-mapping anything. The file lists each volunteer, their in and out times, duration, group, and tag, plus that distinct-worker count at the bottom.

The report wants totals in decimal, not hours and minutes. Her CSV shows 96 hours and 45 minutes across everyone. She runs it through the decimal and HH:MM converter and drops 96.75 into the grant form. Done before noon.

What to copy for your own event

Maria's day worked because three decisions were made before a single volunteer arrived: two sign-in points instead of one, live watching during the eleven-minute rush, and a cutoff rule she trusted so forgotten clock-outs never inflated the count. None of it required volunteers to have logins, and none of it tracked where anyone was or what they did. It only recorded time in and time out.

If you run a build, a food drive, or a race crew next weekend, set up the same table. Start a free workspace, print your poster, and try tapping through a sign-in yourself on the live kiosk demo before the real thing. The point is to get to noon on Saturday with a roster you already trust, not one you have to rebuild on Sunday.