What Auto-Close Means and Why It Protects Hours

A volunteer taps their name to clock in at 9:00 a.m., works a four-hour shift, and walks out at 1:00 p.m. without tapping out. Nobody notices. The entry keeps running. By the time you pull your report on Friday, that one open entry reads as 96 hours, and your total is garbage.

Auto-close is the rule that closes a stale open time entry at its start time plus a fixed cutoff, rather than at the current time. Instead of assuming the volunteer worked until the moment you happened to look, it assumes the shift ran no longer than a reasonable maximum and stops the clock there. The forgotten clock-out stops distorting your numbers.

Why closing at "now" is the wrong answer

The naive fix is to close a stuck entry at the current time. That is worse than doing nothing, because it feels correct while being badly wrong. Consider the 9:00 a.m. volunteer. If the system closes the entry when you open the dashboard at 4:30 p.m., you get 7.5 hours logged for a 4-hour shift. If you don't check until the next morning, you get 24-plus hours. The reported number now depends on when you looked, which is not information about the shift at all.

Closing at the start time plus a cutoff removes that dependence. Say your cutoff is 12 hours. The 9:00 a.m. entry gets closed at 9:00 p.m. at the latest, no matter when you run the report. The number is a ceiling tied to the shift itself, not to your habits. You still want to correct it to the real 1:00 p.m. departure, but you are correcting a bounded overstatement instead of an open-ended one. For the exact mechanics, see the definition of auto-close in the glossary.

When auto-close actually matters

It matters most in the settings where nobody is watching the clock for the workers. On a shared-tablet kiosk, a tutor taps in, gets pulled into a session, and forgets the screen exists. At an event, a crew member clocks in at load-in and leaves at teardown without a second tap. Volunteers, by definition, are not thinking about their own timesheet. These are exactly the people Kangaroo Clock is built for, because they clock in without a login and often without any reminder to clock out.

The stakes rise when the hours feed something official. If you export for payroll, one runaway entry can push a part-timer into a phantom overtime bracket or throw off a tip split. If you report volunteer hours to a grant funder, an inflated total is not just embarrassing, it can put a reimbursement or a compliance figure in question. A clean export with a stable column layout is only as trustworthy as the entries inside it.

How auto-close works in practice

You do not run auto-close by hand. A stale open entry, one that has been running past the cutoff without a matching clock-out, gets closed automatically at its start time plus that cutoff. The record still shows what happened: the entry exists, it has a start, and it has an end that the system supplied. When you review the day, a shift that ends on a suspiciously round boundary is your signal to check with the worker and correct the out-time to what really happened.

That is the workflow to build. Auto-close is a guardrail, not a data-entry substitute. It guarantees a forgotten tap-out can only ever overstate hours by a known, capped amount, and it keeps that overstatement from growing every hour the entry sits open. Your job shifts from hunting for impossible 96-hour entries to spot-checking a handful of capped ones.

Setting a cutoff that fits your shifts

Pick a cutoff a bit longer than your longest realistic shift. A tutoring center running two-hour sessions might use a short cutoff so a stuck entry closes fast. A festival crew working 10-hour days needs a longer one, or a real long shift gets truncated. The trade-off is simple: too short and you cut legitimate long shifts, too long and a forgotten tap-out overstates by more before it caps. Match the cutoff to the pattern you actually run.

What to do before your next report

Before you pull hours for payroll or a funder, scan the day for entries that end exactly at a cutoff boundary and confirm the real out-times with the people involved. If you want to see how clock-in and auto-close behave together, try the live kiosk demo, then start a free workspace and set your cutoff to match your longest shift. A forgotten tap-out will still happen. With a cutoff in place, it stops being a number you have to explain.