What a Roster Actually Is in a No Login Time Clock

A roster is the list of people your team can clock in as: every worker's name, ready to be tapped on a tablet, matched to a scanned QR code, or opened through a personal link. It is not a plan for who works when. It is not a record of hours worked. It is the pool of identities that time entries attach to.

That distinction sounds pedantic until a Saturday morning when three new volunteers show up, none of them are on the tablet, and the line at the sign-in table stops moving. The roster is the one thing that has to be right before anyone can record a minute.

Roster, schedule, and timesheet are three different things

People use these words loosely, and it causes real confusion. Keep them separate:

• The roster is who. Maria Alvarez, James Okafor, the four kitchen staff, the twelve tutors. It is a directory of the people who might work, with nothing about time attached.
• The schedule is when. Maria on Tuesday from 4 to 8, James on the Saturday event crew. It is a plan made in advance.
• The timesheet is what happened. Maria clocked in at 4:02, clocked out at 7:51, worked 3.82 hours. It is the record after the fact.

Kangaroo Clock handles the roster and the timesheet. It does not build schedules or plan shifts. If you need to lay out who works which day, that is a separate job, and a simple weekly shift schedule maker covers it without pretending to be a time clock. The roster feeds the sign-in step; the timesheet comes out the other end as your report.

Why the roster is the thing that makes login-free clock-in work

With a normal time system, each worker has an account. They log in, and the system knows who they are because they authenticated. That model breaks the moment you are running volunteers or seasonal event crew. Nobody wants to create an account to give you two hours on a Saturday, and you do not want to manage password resets for people you may never see again.

Strip out logins and something has to stand in for identity. That something is the roster. When a worker walks up to the shared tablet, the kiosk shows the roster and they tap their own name to clock in. When they scan the posted QR code or open their personal link, the system already knows which roster entry that link belongs to. No password, no account, no app install. The roster is what lets the system say "this entry belongs to James" without James ever proving who he is.

Which is exactly why a messy roster hurts you. Two entries for the same person ("Jim O." and "James Okafor") split his hours across two names, and your report undercounts him. A name that is misspelled or missing means a worker taps the wrong entry or gives up and does not clock in at all. The cleaner the roster, the more the login-free flow just works.

What a clean roster looks like in practice

A good roster is boring, and that is the point. One entry per real person. Full names, not initials, so two Sarahs never blur together on the tablet. No duplicates left behind when someone comes back after a break. People who no longer work with you removed or set aside so the list stays short enough to scan quickly.

Length matters more than you would guess. A tablet showing 40 names in alphabetical order is fine. A tablet showing 200 is a slow tap-and-scroll that pushes people to grab the wrong name. If your list is long, worker groups help: label people by program, role, or location so a tutor at the east center only sees the tutors at the east center, and reports filter the same way.

Groups pair with tags. A worker group labels the person on the roster; a tag labels the time entry. Group your people by "Kitchen" and "Front of house," tag entries by event or shift, and your CSV export splits cleanly by either one. Grant reports want hours by program. Payroll wants hours by person. A roster organized with groups gives you both without hand-sorting a spreadsheet.

The roster protects your hours in one more way

Because each entry ties to one person, forgotten clock-outs stay contained. When someone taps in and never taps out, the system does not leave the clock running against their roster entry forever. Auto-close ends the stale entry at its start time plus your cutoff, not at the current time, so one person's forgotten clock-out never quietly inflates the hours on their name. The roster keeps the mistake attached to one entry instead of poisoning the whole report.

Start by writing down every person who might work in the next month, one name each, spelled the way you want it to appear on payroll or a grant report. That list is your roster. Load it, post the QR code or set up the tablet, and let people tap their own name. If you want to see the tapping flow before committing anything, the live kiosk demo runs off a sample roster you can click through in a minute.