Using the clock

Clocking in, taking breaks, clocking out, reading your own history, and requesting a correction

Attendance → Clock is one screen with one action on it at a time. What that action is depends on where you are in the day.

The four actions

Clocking out while still on a break closes the break at the same instant. You never end up with a break that outlives its shift.

The elapsed time on screen is calculated in your browser from the shift's start, so it counts up smoothly without writing to the server every second. The authoritative numbers are always the ones the server returns.

Times are server times

The instant recorded is the server's, not your device's. A laptop with a wrong clock cannot shift a punch. If a punch genuinely needs to move, that is a correction, which is reviewed, not a timestamp you can set yourself.

Clocking in from the dashboard

The dashboard shows a compact clock card when Attendance is on. Its buttons perform the action directly: pressing Clock in there clocks you in. It does not send you to the Clock page to press a second, identical button.

The one thing the card cannot do is take a confirmation. If clocking in needs one, because you have approved leave that day, the card reports the refusal and you confirm it on the Clock page.

Two tabs, two devices

If you clock in twice at once — a phone and a laptop, or a double-tapped button — exactly one shift is created. The second attempt is rejected cleanly and the screen updates to show the state that actually won. You cannot end up with two open shifts, and a retried request after a dropped connection will not create a duplicate.

Clocking in on a day off

If you have approved leave that covers the whole day, what happens depends on your workspace's policy:

• Warn — you are told, and can confirm and carry on. Working on approved leave is sometimes exactly right.
• Block — clocking in is refused with an explanation.

Pending leave never blocks anything. Partial leave reduces the day's expected time but does not claim which half of the day is free, so it will not stop you clocking in.

Forgetting to clock out

An open shift left running past the workspace's stale threshold is closed automatically. The recorded end is the moment the shift became implausible, not the moment the job noticed and not your last break, so it never credits time you did not work. You are notified, and one item appears in the Attendance review queue for a manager to acknowledge. An auto-closed shift is flagged rather than silently accepted, because a machine guess about when you went home is not a fact.

Acknowledging does not change the times. If the recorded end is wrong, request a correction on that shift yourself from My attendance; a manager approves or rejects it, and only an approved correction rewrites the record.

Your own history

Attendance → My attendance lists your days newest first, with worked, break, and expected time per day. It opens on the last 30 days; the date range picker reaches further back, up to 92 days at a time, and Load more pages through whatever range you chose. Opening a day shows the readable timeline — Work, Break, Work — with the raw punch records collapsed underneath, plus anything raised about that day and how it was decided. You only need the raw records to understand a correction; the timeline is the everyday view.

Requesting a correction

Nobody edits a punch, including admins. Instead:

1. Open the day in My attendance and choose Request correction.
2. Enter the times you believe are right, and a reason.
3. A manager or admin approves or rejects it. A rejection must carry a reason.

An approved correction appends corrective records and recalculates the day's totals. The original punches stay exactly as they were, so the full history reads as: this is what was recorded, this is what was requested, this is who decided, and this is why.