From Clock-Ins to a Board Report in One Month

Riverbend Food Share runs a Tuesday and Saturday grocery distribution out of a church basement. Two paid staff, a rotating cast of about 40 volunteers, and a board that meets the first Monday of every month and wants one number: how many volunteer hours went into the program. Last quarter the number came from someone eyeballing a clipboard, and the grant officer asked how it was calculated. Nobody had a clean answer.

Here is one full month at Riverbend, from the first shift to the report the board reads, with the actual counts and the small decisions that made the total defensible.

Week one: setting up so volunteers never sign in

The setup took the volunteer coordinator, Dana, about 20 minutes on a Sunday. She created a workspace, added the 40 volunteer names she already had in a spreadsheet, and put an old tablet on a stand by the basement door. Volunteers tap their name to clock in and tap it again on the way out. No app, no password, no email invite. That last part mattered: half of Riverbend's volunteers are retirees who will not install anything, and a third are high schoolers logging service hours who churn out every semester.

Dana also printed a QR poster for the loading dock, where the produce crew comes and goes through a side door and never passes the tablet. Anyone back there scans the code with their phone camera and lands on the same clock-in screen. If you want to see how that flow looks before you set it up, the live kiosk demo runs the exact screen a volunteer taps.

She grouped people while she was at it. Two worker groups, Distribution and Warehouse, plus a tag she applies to special one-off events. That grouping is what turns a flat list of punches into a report the board can read by program, which is the whole point of the month.

Weeks two through four: what the shifts actually looked like

Tuesdays drew a steady 9 volunteers for a four-hour window, 3pm to 7pm. Saturdays were bigger, 14 to 18 people across a six-hour morning. Add a mid-month food drive on the third Saturday that pulled in 11 extra volunteers who had never clocked in before.

The raw activity for the month came out roughly like this:

That works out to about 144 hours on Tuesdays, 384 on Saturdays, and 55 for the drive, a little over 580 volunteer hours before any corrections. But the raw numbers are never that tidy, and the corrections are where most hand-kept logs quietly fall apart.

The three forgotten clock-outs

Three volunteers tapped in and left without tapping out. On a clipboard that is an open-ended entry someone guesses at later, usually generously. Kangaroo Clock closes a stale open entry using auto-close, which caps it at the start time plus a cutoff rather than at the current time. A volunteer who clocked in at 9am Saturday and forgot to leave does not show up Monday with a 50-hour shift. The entry closed at a sane length, and Dana saw it flagged so she could confirm it. Nobody inflated the total by accident, which is exactly the question the grant officer had asked about.

One volunteer in two groups

One retiree, Marcus, works the warehouse most weeks but jumped to distribution during the food drive. Because groups tag the person and tags tag the entry, his warehouse hours and his drive hours land in the right buckets without Dana editing anything. When the board asks "how many hours went into distribution specifically," the filtered answer is real, not a guess.

The first Monday: turning punches into two lines the board reads

Board night, Dana opened the dashboard, filtered to the month, and pulled a CSV export. The column schema is stable, so the file she downloads this month has the same columns as next month, which means the grant reporting spreadsheet she built once keeps working. The export includes a distinct-worker count, and that number surprised her: 47 individual volunteers, not the 40 on her roster, because the food drive brought in new faces who each clocked in once.

So the report to the board was two lines:

582 volunteer hours in October across 47 distinct volunteers. Distribution accounted for 528 of those hours; the food drive added 54.

Both numbers trace back to timestamps, not to memory. If a board member asks how the 582 was reached, the answer is a CSV with one row per session. Dana also ran the distinct-volunteer figure and the hours split through the monthly volunteer summary so the version in the board packet was formatted and printable without hand-building a table.

The parts that made this work are specific to how nonprofits actually operate: volunteers who never hold accounts, a headcount that changes every event, and a total that has to survive a grant officer's second look. Those are the same constraints behind the way time tracking built for volunteer programs handles reporting, and they are the reason a clipboard eventually breaks.

One more practical note on cost. Riverbend logged 582 hours in October and expects to stay under the free ceiling for a while; recording is free for the first 500 hours, then a flat monthly or yearly rate with no per-person charge, so adding 11 food-drive volunteers changed nothing on the bill.

What to copy for your own month

Start with names, one shared tablet, and one QR poster for the door people skip. Set two or three groups that match how your board thinks about the work. Let auto-close handle the forgotten tap-outs instead of guessing. Then, on report night, export, read the distinct-worker count, and write the two lines. If you want to run your own month the same way, you can start a free workspace and have the tablet ready before your next shift.