Time Tracking When You Don't Bill by the Hour

Time tracking is the practice of recording when a person starts and stops work, so those spans can be totaled into hours. That is the whole definition. A start stamp, a stop stamp, and a name attached to both. Everything else (tags, groups, reports) is arithmetic and labeling on top of those two moments.

The reason the term feels more complicated than that is most tools were built for one job: turning hours into a client invoice. If you run a tutoring center, a food truck, or a Saturday cleanup crew, you are not invoicing anyone by the hour. Your hours go somewhere else. That changes what "good" time tracking looks like for you.

What the two timestamps actually are

Every entry has two events. A clock in marks the moment someone begins, and a clock out marks the moment they stop. The gap between them is the duration. Stack up a week of durations for one person and you have their weekly hours.

Two details matter more than people expect. First, storage: times should be stored in UTC and shown to each viewer in their own local time, so a shift that crosses midnight or a report opened from another time zone still reads correctly. Second, the format of the total. Payroll usually wants hours as a decimal like 7.25, not 7:15, and a good tool hands you both instead of making you convert by hand.

Why non-billable teams need a different shape of tool

When a consultancy tracks time, the point is to bill the client for it, so the tooling is built around rates, clients, and invoices. None of that applies to you. Your hours feed two things: payroll (or a stipend, or nothing at all) and reporting to a board, a grant officer, or your own records.

That shifts the priorities. You care less about billing accuracy per client and more about three things:

• Getting people clocked in without accounts. A volunteer who shows up once a month will not remember a password, and a line cook does not want an app.
• Clean totals you can hand off. A grant report needs hours per program and a headcount, not a stack of invoices.
• Not overstating hours. A forgotten clock-out should never inflate what you report, especially for grant-funded time.

Billing tools rarely optimize for any of those, because their customers are optimizing for something else. That gap is exactly why Kangaroo Clock was built for teams like yours. Workers never sign in. Only admins do.

How clocking in works without a single login

The friction in most systems is the account. Someone has to create it, someone has to remember the password, and someone has to reset it three weeks later. For a rotating crew, that overhead is larger than the tracking itself.

You can skip accounts entirely with three options. A worker taps their name on a shared tablet at the door. Or they scan a posted QR code with their phone. Or they open a personal link you send once. All three record the same clean start and stop. No app install, no worker profiles to manage. If you want to see it move before setting anything up, the live kiosk demo shows the tap-your-name flow.

What happens when someone forgets to clock out

This is the failure mode that quietly ruins reports. A volunteer clocks in at 9:00, leaves at noon, and never taps out. If the entry stays open, it keeps running. Check it that evening and the system might show nine hours instead of three.

The fix is auto-close for stale entries. A forgotten open entry gets closed at its start time plus a cutoff you set, never at the current moment. So a 9:00 clock in with a three-hour cutoff closes at 12:00, not at 8pm when you happen to look. The hours you report stay honest without you having to hunt down and edit dangling entries.

Turning entries into a report you can hand off

The output is where non-billable teams live or die. You need a file, and it needs to survive contact with a payroll clerk or a grant officer.

A CSV export with a stable column order does that. The columns never move or get renamed between exports, so a spreadsheet formula or a payroll import you set up in March still works in November. The export includes a distinct-worker count, which is often the exact number a grant report asks for. Tag your entries by event or role and group your people by program, and you can filter a report down to just the hours a specific funder paid for.

A quick example

Say you run a reading program funded by two grants. Tag entries as reading or math, group tutors by weekday or weekend, and you can produce a total for each grant separately from one workspace. No re-typing, no second spreadsheet.

What this is not

Two boundaries keep the tool honest. It is not a payroll processor: it produces the hours, but it never moves or holds money, so you export the file and run it through whatever you already use. And it is not a monitoring tool. No screenshots, no GPS, no location tracking, no activity tracking. It records when someone worked, not what they did or where they stood. For a volunteer crew, that distinction is the difference between a tool people trust and one they resent.

If you want to test the whole loop with your own names and tags, start a free workspace and clock yourself in and out a few times. Ten minutes will tell you more than any definition.

For more, see Time tracking.