What a Time Card Is and What Belongs on It

A time card is the record of one person's worked hours for a defined period, built from the times they started and stopped and the totals those times add up to. That is the whole idea. Everything else on it exists to answer two questions: who worked, and how long.

For a team that does not bill by the hour, the time card is what you hand to payroll, staple to a grant report, or file when someone asks how many hours a volunteer put in last quarter. If the fields are wrong or missing, you find out at the worst possible moment: the Friday before payday, or the week a funder wants numbers.

The fields a time card actually needs

A usable time card carries a small, fixed set of columns. Add more and you create work; drop one and you create a dispute. Here is the core set for a team where workers never log in.

That last row is what separates a time card you can report on from a pile of raw times. A tag on the entry lets you pull every hour worked at the spring fundraiser without hand-sorting rows. A worker group on the person lets you split tutors from front-desk staff in one filter.

Notice what is not on the list: no location, no screenshots, no activity log. A time card is a record of hours, not surveillance. Kangaroo Clock keeps it that way on purpose, and there is no plan to change it. If you want the full definition and a few adjacent terms, the glossary lays them out.

When the time card matters most

The time card earns its keep at three moments.

Payroll. Someone converts hours to pay. They need clean totals per person for the period, usually in decimal hours instead of HH:MM, because 7 hours and 45 minutes has to become 7.75 before it multiplies against a rate. Kangaroo Clock is not a payroll processor and does not move money, so the handoff is a file: you export, they run it.

Grant and board reporting. A funder wants total volunteer hours and how many distinct people gave them. A time card that carries tags and a distinct-worker count answers that without a spreadsheet marathon.

Disputes. A worker says they stayed until 6. The card says 5:15. The clock-out time on the record settles it, or shows you where the gap is. That only works if the times are the real ones and nobody guessed after the fact.

The last case is where forgotten clock-outs do damage. If someone taps in at 9 and walks out without tapping out, a naive system leaves the clock running and reports a 15-hour day. Kangaroo Clock uses a cutoff that closes stale entries at the start time plus a set limit, never at the current time, so a forgotten tap never inflates the total.

Time card versus timesheet

People use the words interchangeably, and it causes confusion when you are trying to build a report. The distinction is scope.

A time card is the record for one person over a period. A timesheet is usually the collection: everyone's hours laid out together, often as a grid of names down the side and days across the top. You approve time cards. You submit a timesheet. When payroll asks for "the timesheet," they generally want the combined view; when a worker asks about "my time card," they mean their own line.

In practice you build one from the other. Individual entries roll up into per-person totals (the time cards), and those totals sit side by side as the timesheet. A clean export with a stable column layout gives you both: one row per entry that you can pivot into per-person cards or a full grid, without a column ever moving on you between exports.

How the record gets created without logins

The reason forgotten details end up on time cards is that the recording step is friction. If a volunteer has to install an app or remember a password, they skip it and someone reconstructs the hours later from memory. That is where errors enter.

Kangaroo Clock removes the login entirely. A worker taps their name on a shared tablet, scans a posted QR code, or opens a personal link, and the start and end times land on the record as they happen. No account, ever. You can see how the tablet flow feels in the live kiosk demo before you set anything up.

Times are stored in UTC and shown in each viewer's local time, so a card never drifts because someone opened it from a different time zone. When you need the numbers, filter by tag or group, check the distinct-worker count, and export.

If you want to see what your own cards would look like, start a free workspace, add a few names, and clock a test entry in and out. The file you export is the time card, and now you know exactly what should be on it.