KangarooClock

← Blog

Reading Auto-Close So It Fits a Long Shift

· 5 min read

Your teardown crew clocks in at 6pm and works until 2am. Someone forgets to clock out. By morning you are staring at an open entry and wondering whether the system is about to record 14 hours, or lop the shift off at some random point. The answer depends on one number: your auto-close cutoff. Read it right and a long shift stays a long shift. Read it wrong and you either inflate hours or cut a real one short.

What time does auto-close actually fire?

Auto-close fires when an open entry gets older than your cutoff, measured from the moment the worker clocked in. It is not tied to midnight, to the end of your day, or to a fixed hour on the clock. If your cutoff is 12 hours and someone clocks in at 6pm, the entry becomes eligible to auto-close at 6am the next day, which is 12 hours after their start, not at any particular wall-clock time.

The trigger is always relative to the start of that specific entry. Two workers who clock in at different times will have their entries close at different points, each one measured from its own start.

Will auto-close change the hours it already recorded?

No. This is the part that trips people up, so here is the exact behavior: a stale open entry is closed at its start time plus the cutoff, never at the current time. If someone clocked in at 6pm with a 12-hour cutoff, the entry closes at 6am and records 12 hours. It does not record the hours between 6am and whenever you happened to notice the next afternoon.

That design exists for one reason. A forgotten clock-out should never inflate your reported hours. Without it, a single missed clock-out could turn a normal shift into a 30-hour entry and wreck your payroll or grant numbers. With it, the worst case is capped at exactly the cutoff you set. The tradeoff is the opposite risk, and it is the one worth planning for: if the cutoff is shorter than a real shift, auto-close closes the entry before the person actually left, and the extra time is gone.

How do I set the cutoff for an overnight event crew?

Set the cutoff longer than your longest realistic shift, then add a buffer. If your teardown crew can run 10 hours end to end, a 12-hour cutoff gives you room without letting a truly forgotten entry balloon. The question to ask is not "how long is a normal shift" but "how long could an honest shift run before I would call it a mistake." Set the cutoff there.

For a crew that works past midnight, the thing to remember is that the cutoff counts from each person's clock-in, so a late start pushes the close time later automatically. Someone who clocks in at 9pm with a 12-hour cutoff is covered until 9am. You do not need a separate overnight mode. You just need the number to be bigger than the real work. The full walkthrough for picking and saving that number lives in the guide on how to set up auto-close for missed clock-outs, including where the setting sits in your admin pages.

What happens if a shift runs longer than the cutoff?

If a real shift runs past the cutoff and the worker did not clock out in time, auto-close will close it at start plus cutoff, which means the tail end of the shift is not recorded. The fix is to raise the cutoff before that kind of shift, not after. Auto-close is a safety net for the entries people forget, not a cap you want hitting your actual long days.

If it already happened, you have the real start time in the entry and you know roughly when the person left, so you can correct the record by hand. Better to avoid the correction. If your crew regularly works 14-hour event days, your cutoff should sit comfortably above 14, say 16, so a genuine marathon day still records in full and only a truly abandoned entry gets trimmed.

Does auto-close touch entries that were closed normally?

No. Auto-close only ever acts on entries that are still open past the cutoff. If a worker taps out on the shared tablet kiosk or their personal link, that entry is closed by them, at the time they actually left, and auto-close never looks at it again. The setting is doing exactly one job: handling the open entries nobody closed.

How do I check auto-close is set the way I think?

Pull a CSV export after a few long shifts and look at the duration of any entry you suspect was auto-closed. If a 12-hour cutoff is working, every auto-closed entry will land at exactly your cutoff length, down to the minute, because it was closed at start plus cutoff. Entries workers closed themselves will be whatever length they actually worked. That contrast tells you at a glance which entries the system touched and whether your number is set high enough.

If you are tracking crews across setup, show, and teardown, pair the cutoff with tags so each phase reports separately, and you get a clean read on where the long days actually are. When you are ready to set your own cutoff, you can start a free workspace and tune it against your real shifts before anything counts against payroll.

Tags: auto-close, time tracking, event crews, faq

See it in your own setup

No signup needed. Add a few names, share a kiosk URL, watch hours land.

Try the demo →