What a Timesheet Is and What Belongs in Each Row

A timesheet is a record of the hours a person or team worked across a defined period, broken into individual entries with a start and an end. It answers one question your payroll run or your grant report keeps asking: who worked, when, and for how long. When you manage a tutoring center or a Saturday event crew, you are not billing clients by the hour, but you still owe someone a clean count of hours. That count comes from a timesheet.

A timesheet is a collection of entries, not a single punch

People mix up two words. A time card is the pair of stamps for one shift: Priya clocked in at 8:02 and out at 12:15. A timesheet is every one of those pairs, gathered for a pay period, a program, or an event, and totaled. One row per shift. Many rows per person.

The distinction matters the moment you total hours. A single card tells you Priya worked about four hours Saturday morning. The timesheet is the full run of shifts that adds up to the number you hand to payroll or attach to a report. If you only ever look at one card at a time, you are doing the addition in your head, and that is where errors creep in.

Where the raw entries come from

Each row starts when someone marks the beginning of a shift. In Kangaroo Clock, a worker does that by tapping their name on a shared tablet or scanning a posted code, with no login. That action is a clock in, and the matching stamp at the end of the shift is the clock out. Two stamps, one row. Do that all week and you have a timesheet without anyone typing a start time by hand.

The columns that actually carry weight

A timesheet can have twenty columns. Most are noise. These are the ones that decide whether your total is correct and your report survives review.

• Worker name. Who the row belongs to. If two people share a first name, you need a way to tell them apart, so a last initial or a group label earns its space here.
• Date. The calendar day the shift started. A single date per row keeps totals honest and makes a pay period easy to filter.
• Start time and end time. The two stamps. Store or read them carefully across time zones. Kangaroo Clock keeps all times in UTC internally and shows them in your local time, so a stamp does not shift when a different person opens the report.
• Duration. End minus start, minus any unpaid break. This is the number that gets summed. If you need it in decimal for payroll, a converter between decimal and HH:MM saves you the arithmetic.
• Tag or program. The label that says which event, role, or grant the hours belong to. Without it, you cannot split a timesheet by program later.

Anything past those is optional. Notes help. A pay rate matters if you are calculating pay, but Kangaroo Clock does not move money, so that column lives in your payroll system, not here.

The duration column is where mistakes hide

A forgotten clock out is the classic failure. Someone leaves without tapping out, the entry stays open, and if the tool closes it at the current time the next morning, that one row can read fourteen hours. Kangaroo Clock uses auto-close for stale open entries instead: a forgotten shift closes at its start time plus a cutoff you set, never at the current moment. A missed clock out shortens the row rather than inflating it, so your total never balloons overnight.

How to fill one out and hand it off cleanly

You have two honest paths. Print a blank grid and have people write times by hand, or capture the stamps digitally and export them. If you want the paper version for a wall clipboard or a backup, the printable timesheet template gives you the columns above already laid out, ready to print.

The digital path removes the handwriting and the addition. Workers clock in and out, the durations calculate themselves, and you pull the whole period as a file. Kangaroo Clock exports to CSV with a fixed column order that does not change between runs, plus a distinct-worker count for grant reports that ask how many people served, not just total hours. Because the column schema stays stable, the formula in your spreadsheet keeps pointing at the right column every pay period. No re-mapping.

Read a timesheet before you trust the total

Before you send anything to payroll, scan the rows for three things. Any duration over about ten hours is worth a second look, because a real shift that long is rare and usually signals a mis-stamp. Any row with a start but no end is an open entry that auto-close will handle, but you should confirm the cutoff is right for your longest real shift. And any name that appears once when you expected it five times means someone forgot to clock in on four days.

Those three checks take under a minute on a filtered report and catch most of what goes wrong. A timesheet is only as good as the review you give it before the numbers leave your hands.

Start with real entries, not a blank grid

If your team is tracking hours on paper or in a shared spreadsheet, the fastest fix is to capture the stamps at the source and let the timesheet build itself. You can set up a free workspace in a few minutes, post a name-tap kiosk or a QR code, and have real rows to export by the end of the first shift. From there, the columns above are already filled, and your only job is the one-minute review.