One Sunday: 30 Church Volunteers, One Tablet
· 5 min read
Thirty people serve at the 9:00 and 11:00 services: 14 in the nursery, 10 greeters, and 6 on the parking team. Nobody has a company email. Nobody is going to install an app on their phone to log 90 minutes. The coordinator, Dana, needs two things by Tuesday: total hours for the quarterly ministry report, and a headcount of distinct people who showed up. Here is exactly how one Sunday runs.
Saturday night: building the roster in about ten minutes
Dana opens the admin dashboard on her laptop after dinner. The sign-up sheet from last week gives her the names. She adds the 30 volunteers and sorts them into three worker groups: Nursery, Greeters, and Parking. Groups are how she filters the report later, so a greeter's hours never get mixed into the nursery total.
She also sets one tag she will apply to the whole morning: Sunday-AM. Groups label the people; tags label the time. Both exist so that when the report comes out, she can slice it by team or by event without retyping anything.
Workers never get accounts here. Dana is the only one who signs in, and she does it with a magic link, no password to reset at 10pm. If you run a volunteer program and this is the part that usually stalls you, the setup built for volunteer coordinators is designed around exactly this: people with no logins, tracked by someone who does.
8:40 Sunday: one tablet on the welcome table
Dana props an old iPad on a stand by the front doors in kiosk mode. The screen shows every name as a tappable tile. A volunteer walks up, taps their name, and they are on the clock. No scanning a code, no typing. The nursery lead walks in at 8:42 and clocks in with one tap before heading downstairs.
Parking team arrives first because they direct the lot, so by 8:45 all 6 of them have tapped in. Greeters trickle in between 8:50 and 9:05. The nursery crew for the first service is in by 8:55. Dana does not chase anyone. She glances at the dashboard on her phone, which shows who is on the clock right now, and sees 27 of her 30 names are green. Two nursery volunteers are second-service only, and one greeter texted that she is running late.
At 9:10 that late greeter arrives, taps her name, and the count hits 28. The two second-service nursery folks will tap in around 10:40. Dana never had to mark anyone present by hand. The tablet is the attendance record.
Clock-out, and the two people who forget
First-service nursery hands off to second-service nursery at 10:45. Those volunteers walk past the tablet and tap their name to clock out. Most do. Two do not, because they are carrying a toddler and a diaper bag and they just leave.
This is the moment that used to wreck Dana's numbers. A volunteer who clocked in at 8:52 and forgot to clock out would otherwise sit on the clock until she noticed, maybe Monday, logging seven hours for a 90-minute shift. Kangaroo Clock handles it with auto-close for forgotten clock-outs: a stale open entry is closed at its start time plus a cutoff Dana set, not at the current time. So the forgotten nursery shift records as the length she configured, never as a phantom seven hours. A missed clock-out costs her nothing on the report.
The parking team clocks out together at 9:20 once cars stop arriving. Greeters clock out at 9:15 and the second-service greeters repeat the pattern at 11:15.
By the numbers, this Sunday
When both services wrap, the dashboard shows the morning in plain figures:
| Team | People | Typical shift | Team hours |
|---|---|---|---|
| Nursery | 14 | ~2.0 hrs | 28.0 |
| Greeters | 10 | ~1.5 hrs | 15.0 |
| Parking | 6 | ~0.75 hrs | 4.5 |
That is 47.5 volunteer hours from 30 distinct people in one morning, with two auto-closed entries counted at their real length instead of ballooning the total. The distinct-worker count matters because Dana's board wants to know how many people serve, not just the hours, and the same volunteer who covered both services should count once.
Tuesday: the report that writes itself
Dana filters the week to the Sunday-AM tag and pulls a CSV export of the hours. The column schema never changes, so the spreadsheet she built last quarter still works this quarter without edits. She drops in the distinct-worker count for the board summary and she is done. If she wants a tidy per-person recap for the volunteer appreciation mailing, the monthly volunteer summary tool turns the same data into a readable sheet.
No one on the nursery floor logged into anything. No app got installed. No screenshots, no location tracking, nothing watching anybody; the tablet only records the taps people choose to make. That is the whole point for a volunteer setting, where the people serving are donating their time and would walk away from anything that felt like surveillance.
The free tier covers the first 500 recorded hours, so a program at this size runs for a while before the admin pages ever ask for a card, and clock-in keeps working regardless. If you want to see the kiosk your volunteers would tap, open the live kiosk demo and tap a name yourself.
Tags: volunteers, example, time tracking, church
See it in your own setup
No signup needed. Add a few names, share a kiosk URL, watch hours land.