Fichaloto

Blog Time and attendance

The clock ran all night. Now what?

6 min read

Forgetting to clock out — or to punch out, if your team says it that way — is the single most common incident in any time-and-attendance system, and the way a product handles it tells you most of what you need to know about it.

Three bad answers

Somebody clocks in on Tuesday morning and goes home without clocking out. On Wednesday they open the app. What happens next is a design decision, and there are three common ways of getting it wrong.

  • Close it with the current time. The day is now twenty-six hours long. If clocked time feeds project costs, twenty-six hours just landed on a job, and the margin is wrong until somebody notices.
  • Let them fix it themselves. Quick, painless, and it destroys the point of the record. A working-time register each person can edit at will proves nothing about anybody.
  • Block them until it is fixed. Now they cannot clock in on Wednesday either. You have punished the same slip twice and created a second missing day while somebody chases an approval.

What a good answer looks like

The workable design has four parts, and each one exists because one of the bad answers above is tempting.

First, an expiry rule. After some number of hours — sixteen is a reasonable threshold, comfortably above any real shift including nights, well below a forgotten day — an open entry stops being an entry and becomes an oversight. It counts as zero, and it stays at zero.

Second, it stops blocking today. Yesterday being broken is not a reason to lose today as well. The clock offers a normal clock-in and the unfinished day is shown separately, in red, with the button that fixes it.

Third, the clock-out button stops working on it. Not out of strictness: closing it now would stamp the moment they remembered as the moment they left, and that is a number that must never reach a project or a payslip.

Fourth, a correction circuit. They say what time they actually left and why, somebody with permission approves it, and the approved correction is recorded as a correction — visible as such, signed, with the original still there. Nobody is asked to remember a Tuesday four weeks later, because the reminder went out on Wednesday morning.

Reminders are half the feature

The correction circuit only works if people are told the same day. That means an email the following morning to the person, an in-app notification waiting when they next log in, and — this is the part usually missed — the same warning to whoever approves time. An oversight only its author can see is an oversight nobody chases.

It also means not sending it when it would be wrong: nobody on approved leave should get an email asking why they did not clock in.

The unclosed break

A subtler cousin, and the one that slips through most. Somebody starts a break and never comes back. The day looks perfectly normal — it has a start and an end — and only the total is wrong.

The honest handling is to count the day up to the start of the break and flag it as incomplete, rather than inventing a return time so the arithmetic looks tidy. Inventing a time to make a day add up is precisely what a record with evidential value cannot do.

Frequently asked questions

Why sixteen hours and not midnight?

A night shift crosses midnight while somebody is genuinely working. Expiring at the date change would void a real shift every night. Sixteen hours sits above any lawful working day — nine ordinary, twelve with extensions under Spanish rules — and still catches an oversight, which never lasts less than a day.

Can a manager just close it for them?

A manager can enter the day by hand with the real times, and it is recorded as manually entered, with their name on it. What nobody can do — manager included — is close it with the current clock and have it look like a normal day.

All of this is built into Fichaloto. See how it works.

Keep reading