Settings and policies

An entry rarely reaches you as it was punched: a policy may have moved the times, added a break or flagged it, and a setting may have closed it hours after the person left. This page says which surface made each decision.

​

Where each decision lives

A policy targets people, so two people on the same shift can have different rules.

​

Close a timer nobody stopped

Automatically stop timers in Settings → Timesheets ends a run that has gone past Maximum timer duration, which you set in whole hours between 1 and 24. Auto clock-out behaviour decides what the entry is left holding, and this is a real choice: A new workspace already does this, at sixteen hours, recording no hours, because a guess written into an entry is a guess somebody gets paid for. Whichever behaviour you pick, the entry lands in Needs review.

​

Keep an entry and its shift in step

Settings → Schedule → Timesheet linking holds six switches that decide how far a clock record and a planned shift follow each other. Auto-link shift on clock in is the one worth understanding. It attaches an entry to the nearest shift assigned to that person starting within three hours either side, whether they clocked in or you typed the row in by hand. On a clock-in with no shift in that window, it creates one from the entry’s own position and location, which is why shifts sometimes appear that nobody rostered. Clock in from schedule starts a shift. Auto-update shift status marks it In progress, then Completed. Auto-sync shift times and Auto-sync breaks copy timing. Auto-sync linked statuses mirrors Approved, Rejected and Cancelled both ways. Shifts update linked entries; entries update a shift only when all match. Cancellation can replace any status. Approval or rejection cannot replace Planned or In progress, but can replace Cancelled. It keeps clock times and running timers. Enabling sync, relinking, undo and bulk revert do not reconcile statuses.

​

What a policy changes before you see it

Rounding is the usual answer to “that is not the time they clocked in”. A policy rounds the clock-in and the clock-out separately, each either to an interval, with a direction of Nearest, Up or Down, or by snapping to the linked shift within an early and a late window. Totals rounding is separate again and rounds the period total rather than the punches. Wherever a policy has moved something, the entry’s own activity trail names the policy and keeps the original time beside it. Breaks decides whether breaks exist at all. Until a break policy covers somebody there is nothing to record, and deleting the last policy that reaches a person turns their break reporting off again. A policy can also add breaks by itself, triggered by worked time or by a fixed clock time. Paid breaks stay in the worked hours; unpaid ones come out of them. Clocking governs the punch itself: whether GPS is captured at all, the allowed radius around a location, what happens outside it, and which of Terminal, Web and App they may clock from. A new policy only records the position; blocking or flagging needs Pro, as does automatic clocking, where the phone punches at the workplace boundary. Leave Pro and a saved block or flag rule stops acting until you return; the setting is kept. Overtime and Premium hours are the two policy tabs that change nothing here. They shape calculated figures such as norm hours and overtime, which live in the hour columns on a report rather than on a timesheet.

​

Next

​

Still need help?