Shift vs Roster: What New Coordinators Confuse

A roster is the list of people who are allowed to work under your organization: the twelve volunteers signed up for the food bank, the eight cooks and servers on your restaurant's staff, the tutors on your center's payroll. A shift is one continuous block of time that one of those people actually worked: Maria, Saturday, 9:04 a.m. to 1:12 p.m. The roster is a list of people. A shift is a record of worked time. That is the whole distinction, and getting it wrong is the most common reason a new coordinator's hours report comes out garbled.

You will hear both words used loosely, sometimes to mean the same thing. That looseness is fine in a hallway conversation. It stops being fine the moment you export numbers for payroll or a grant report, because a roster and a shift answer two different questions and live in two different columns.

The precise definitions

A roster is the roll of people attached to your workspace. It answers "who can show up and be counted?" Adding someone to the roster does not create any hours. It just puts their name on the kiosk so they can tap it. Removing someone does not erase the hours they already worked; it only stops new entries under that name.

A shift is a single time entry: a start, an end, and the person it belongs to. It answers "who worked, and for how long?" When Maria taps her name to clock in at 9:04 and taps again at 1:12 to clock out, that pair becomes one shift worth four hours and eight minutes. She might work five separate shifts in a week. She is still one line on the roster.

Two ways to see it clearly:

• Your roster count does not change when people work. Twelve volunteers on the roster stay twelve whether they clock 0 hours or 400.
• Your shift count and total hours change every time someone clocks in and out. That is the moving number.

Where new coordinators mix them up

The confusion usually shows up in three places.

The first is scheduling. A weekly schedule assigns planned shifts to people on your roster: Maria on Saturday morning, Devon on Sunday. But a planned shift is a guess about the future, not a worked shift. Devon might call in sick. If your report counts planned shifts as worked hours, you are reporting time nobody put in. Kangaroo Clock does not plan shifts for you; it records the ones that actually happened. If you need a plan on paper, the weekly shift schedule maker builds one, and you keep it separate from your recorded hours.

The second is the headcount. A grant officer asks "how many volunteers served this quarter?" That is a roster-flavored question, and the honest answer is a count of distinct people who actually clocked in, not everyone on your list and not the number of shifts. Your CSV export includes a distinct-worker count for exactly this, so you never have to hand-tally names or accidentally report 140 shifts as 140 people.

The third is a forgotten clock-out. Someone taps in for a shift and leaves without tapping out. That is a broken shift, not a roster problem. Kangaroo Clock's auto-close for forgotten clock-outs closes that stale entry at its start time plus your cutoff, never at the current time, so one open shift does not silently balloon into a 30-hour figure on your report.

Why the difference matters for a login-free clock

When workers have no accounts and no app, the roster is the only thing standing in for identity. There is no username. There is a name on a kiosk, a QR code on the wall, or a personal link. So the roster does double duty: it is both the list of who counts and the set of buttons people tap. Keep it clean. A name that appears twice, once as "Maria" and once as "Maria G.", splits one person's shifts across two roster entries and quietly undercounts everyone.

Worker groups sit on top of the roster to sort people by program or role. Tags sit on top of shifts to label the time itself by event or task. So you might group the roster into "Tutors" and "Front Desk," then tag individual shifts as "SAT Prep" or "Intake." When you filter a report, you are combining a roster filter (which people) with a shift filter (which blocks of time). Knowing which lever is which is the difference between a report that takes two minutes and one that takes an afternoon.

A quick test to keep them straight

Ask yourself whether the number should change when someone works an extra hour. If yes, you are talking about shifts and hours. If no, you are talking about the roster. Your roster of eight cooks stays eight all week. Their combined shifts might total 210 hours by Friday. Same people, two entirely different numbers.

Once the vocabulary is clean, the reporting follows. Add people to the roster, let them tap in and out, and each pair of taps becomes a shift. Total those shifts and you have payroll or grant hours; count the distinct names behind them and you have your headcount. If you want the full vocabulary in one place, the glossary of time-clock terms defines each word the same way your export uses it, so the report and your explanation of it never drift apart.

The next time someone on your team says "roster" when they mean "shifts," you will catch it before it reaches a spreadsheet. Set up your roster of names first, then watch the shifts stack up on their own.