What a Shift Is and How It Differs From a Time Card Entry

A shift is a planned block of time a worker is expected to be on duty, like Saturday 9am to 1pm at the registration table. A time card entry is the record of what actually happened: the moment someone clocked in, the moment they clocked out, and the hours in between. Those two things sound identical until the Saturday when your 9am volunteer shows up at 9:18 and leaves at 12:45. The shift said four hours. The time card entry says three hours and twenty-seven minutes. Only one of those numbers belongs in your grant report.

The shift is the plan; the entry is the evidence

Think of a shift as an intention set in advance. You decide that the dinner rush needs three servers from 5pm to 10pm, and you post that. Nobody has worked yet. No hours exist. The shift is a slot on a plan.

A time card entry is created by real events. It starts when a worker taps their name or scans a code, and it closes when they clock out. The entry carries a start timestamp, an end timestamp, and a duration. A single planned shift can produce zero entries (the person never showed), one entry (they worked it straight through), or several entries (they clocked out for a break and back in twice). The plan and the record are not the same object, and treating them as one is how reports drift away from reality.

A quick worked example

You schedule Maria for a 5-hour tutoring block, 3pm to 8pm. She arrives at 3:05, steps out for dinner from 5:30 to 6:00, and leaves at 7:50. That one shift yields two time card entries: 3:05 to 5:30, and 6:00 to 7:50. Total clocked time is 4 hours and 15 minutes, not the 5 hours the shift implied. If you pay from the shift, you overpay by 45 minutes. If you pay from the entries, you pay for time worked.

Where clock-in and clock-out fit

Every time card entry is bracketed by two actions. A clock in marks the start of an entry, and a clock out closes it. Kangaroo Clock stores both timestamps in UTC and shows them in your local time, so an entry that crosses a daylight-saving boundary still adds up correctly.

The gap between the two is the duration, and that duration is what feeds your totals. This is why a forgotten clock-out is dangerous. An entry with a start but no end is open, and left alone it would count every hour until someone noticed. Kangaroo Clock handles that with auto-close for stale entries: an abandoned open entry is closed at its start time plus a cutoff you set, never at the current moment. A volunteer who forgot to tap out on Friday does not silently rack up 60 hours over the weekend. The entry reflects a plausible end, and your hours stay honest.

When the distinction actually matters to you

Most of the time you do not care about the plan once the day is over. You care about the entries, because those are what you report and what you pay. The distinction bites in a few specific moments.

• Payroll and stipends. Pay from entries, not shifts. A person scheduled for four hours who worked three should be paid for three.
• Grant and volunteer reporting. Funders want delivered hours. A shift that nobody covered contributed zero, and your report should say zero, not the four hours you hoped for.
• Coverage review. Here the shift matters. Comparing the planned block to the actual entries tells you who ran short, who stayed late, and which slots keep going uncovered.
• Overtime and breaks. Breaks split one shift into multiple entries. Your totals should reflect worked time, so the split entries are the accurate source.

Kangaroo Clock does not plan shifts for you. It records what happens. If you want a printed grid to hand out for the week, the free weekly shift schedule maker builds one, and then the kiosk captures the real entries against it. Two tools, two jobs.

How the entries turn into a report

Each closed entry has a start, an end, a duration, and any tags you applied (by event, role, or program). When you pull a CSV export for payroll, every entry becomes a row with a stable column layout, plus a distinct-worker count so you can see how many people, not just how many hours, showed up. That count comes straight from the entries. A shift that produced no entry adds nobody to it.

If you need to convert those durations into decimal for a spreadsheet, the decimal and HH:MM converter does the arithmetic, so 4 hours 15 minutes becomes 4.25 without you counting on your fingers.

The one-sentence test

When you are unsure which number to trust, ask whether it came from a plan or from a punch. If you decided it in advance, it is a shift, and it can be wrong the moment reality intervenes. If it came from someone tapping their name on the tablet, it is a time card entry, and it is what actually happened. Report the entries. Use the shifts to plan the next week and to spot the gaps.

Want to see entries appear as people clock in? Open the live kiosk demo and tap a name to watch one start.