Your Bill When Volunteers Jump to 80 for a Gala

Riverside Books is a small literacy nonprofit. Most months, 12 volunteers come in to shelve donations, run reading hours, and staff the front desk. Once a year they throw a fundraising gala, and for that one night the volunteer roster balloons to 80: coat check, registration, bar runners, auction spotters, parking, cleanup. The 12 regulars are still there. Sixty-eight new faces show up for a single evening and never return as volunteers.

Here is the question that trips up every tool a coordinator looks at: what does that one night do to the bill? Let's run Riverside's actual numbers.

The quiet months: 12 volunteers, flat line

Riverside's 12 regulars put in roughly 6 hours each per week. That's about 72 hours a week, or around 310 hours a month. They clock in by tapping their name on a tablet at the front desk. No logins, no app to install, no accounts to create. The coordinator, Dana, is the only person who signs in, and she does it with a magic link.

For the first few months, Riverside pays nothing. Kangaroo Clock is free for the first 500 recorded hours, and at 310 hours a month, Riverside crosses 500 partway through month two. After that, the price is $10 a month or $100 a year, flat, for unlimited people. Dana puts a card on file and stops thinking about it. Clock-in never stops working regardless of the hour count; the card is only for the admin pages.

So the quiet-month bill looks like this:

Gala month: 80 volunteers, same $10

The gala runs on a Saturday in April. Those 68 extra volunteers show up for a four-hour evening. Dana doesn't want to stand at a tablet while 68 people line up, so she prints a QR sign-in poster and tapes it by the volunteer check-in table. People scan it on their own phones, type their name, and they're clocked in. The 12 regulars keep using the front-desk tablet as always.

Run the numbers for April. The 12 regulars log their usual 310 hours. The 68 gala volunteers log about 4 hours each, roughly 272 hours. Total: around 582 recorded hours for the month, across 80 distinct people.

The bill in April is $10.

Not $10 plus a per-volunteer charge. Not a jump to a bigger tier because the headcount crossed 50. Pricing here is not per-seat and not per-location, so 80 people cost exactly what 12 people cost. The only thing the extra 582 hours and 68 people change is the size of your report, not the size of the invoice. You can confirm the full structure on the page that explains what Kangaroo Clock costs.

What a per-head model would have done

Compare that to the common per-active-user pricing you see elsewhere. Say a tool charges $3 per active user in a given month. In January through March, Riverside pays for 12 users: $36 a month. Fine. Then April hits.

Under the per-head model, the gala month costs $240 because all 80 people were active. You pay $204 extra for 68 people who volunteered for one evening and will not log in again. The flat model charges the same $10 it charged in March. Over a full year with one gala, that's $120 flat versus $636 per-head, and the gap is entirely driven by a single night.

This is the whole reason a swinging roster punishes per-seat pricing: you get billed for your peak, not your baseline. A nonprofit that runs three or four big events a year gets hit three or four times, each time for people who are long gone by the next invoice.

Cleaning up after 80 people clock in

A big one-night crew creates a predictable mess: forgotten clock-outs. Half a dozen gala volunteers will walk out the door without scanning out. You do not want those open entries running until Dana notices them Monday morning, because that would inflate the hours. Auto-close handles it by closing a stale entry at its start time plus a cutoff, never at the current time. A volunteer who clocked in at 6pm and forgot to clock out gets a sensible capped entry, not a 40-hour shift.

When Dana pulls the month for her board report, she wants two things: total hours and how many distinct people showed up. The CSV export carries a stable column schema that includes a distinct-worker count, so "80 volunteers contributed 272 hours at the gala" is a number she can pull straight out, not something she reconstructs by hand. She can tag the gala entries separately from the weekly shelving hours, so the event shows up as its own line.

If you run a roster that swings like Riverside's, the move is simple: start a free workspace, run your next big event through it, and watch the bill not move. You can try the kiosk on a borrowed tablet first to see how clock-in feels before you commit a single volunteer to it.