The Punch That Was Never Closed
Somebody clocked in on Tuesday and went home without clocking out. The system will not invent an end time for that day — not at midnight, not at the shift end, not ever. Here is why that refusal is the most valuable thing about it.
An open punch is a question, and the worst thing a payroll system can do with a question is answer it itself.
Every attendance module in the world has to decide what to do with a day that has a start and no end. There are three available answers and only one of them is honest.
-
Close it at the shift end
The tempting one. It produces a tidy record and a plausible number of hours, and it is a guess wearing the clothes of a measurement. The employee who left two hours early and the employee who worked three hours late are both recorded as having worked exactly their shift.
-
Close it at midnight
Worse. It produces a specific, wrong, and often enormous duration, and it does so on a record that payroll may read without anybody looking at it again.
-
Leave it open and tell somebody
What actually happens here. The record keeps its start, keeps no end, and the hours stay unmeasured. A nightly sweep finds it and raises it with the people who can resolve it.
Unmeasured is a value; invented is not
A day with no recorded hours is visibly a day nobody has resolved. A day with invented hours is indistinguishable from a day that was measured, and the difference only becomes apparent when somebody disputes a payslip months later. The whole design here rests on that distinction: an empty field can be found and fixed, a plausible wrong number cannot.
What the nightly sweep does
At half past five in the morning — the earliest job in the daily reminder batch, ahead of the task reminders and well ahead of the nine o'clock block — the system looks for attendance records from a day that is already over which have a clock-in and no clock-out. Days still in progress are never included, so nobody gets chased about a night shift they are halfway through.
What it produces is a digest, one per organisation, and it can go to two different audiences with two independent switches.
| Recipient | What it says | Controlled by |
|---|---|---|
| HR | Which employees have an open day and when | Its own notification setting and its own cadence |
| The employee | That their own day is open and needs a correction | A separate setting and a separate cadence |
The two are genuinely independent — an organisation can chase HR and leave employees alone, chase employees and leave HR alone, or run both. Each has its own reminder clock, so switching one on does not reset the other.
The same refusal appears elsewhere, for the same reason
This is not an isolated piece of caution. The attendance module refuses to infer twice, and the second refusal explains the first.
When a day's end time appears to be earlier than its start, that is either a night shift or a pair of transposed times, and the two look identical on the record. The system does not decide by comparing the times. It reads the roster: a shift that somebody defined as running from ten at night to six in the morning is a declared fact about the shift, and that flag is what marks the day as crossing midnight. Where there is no roster to consult, the hours come back unmeasured rather than guessed — because, in the words of the code itself, deciding from the times alone would turn a typo into sixteen hours of recorded work, silently, on a record payroll may later read.
A roster is evidence somebody reviewed. A pair of times is an observation nobody has.
Closing the day properly
The route from an open punch to a paid day is a correction, and it has exactly the shape you would want if you were ever asked to justify it.
- The employee states what happened — the date, the status, the clock-in and clock-out times they are asking for, and a reason.
- Somebody with authority decides, and the decision carries their identity, the moment they made it, and a comment they can use to say why.
- An approval writes the requested values into the attendance record, so the corrected day is a real attendance day rather than an annotation beside one.
- A daily reminder chases decisions that are sitting, at five to ten each morning, so a correction filed on Tuesday does not wait until payroll day.
What that produces is a record with two authors: the employee who claimed the hours and the manager who accepted them. On a normal day the record has one author and a device signature behind it. Both are legitimate; they are simply different kinds of evidence, and the system keeps them distinguishable rather than flattening them into one.
The operational habit that makes this cheap
Open punches are not a software problem to be solved once. They are a steady trickle produced by flat batteries, forgotten phones and people who left in a hurry, and the organisations that handle them well do the same three things.
You want them resolved within a day
Send the digest to employees, not only HR
The person who knows what time they left is the employee. Routing the reminder only to HR turns a thirty-second correction into an investigation.
Approvals are the bottleneck
Check the approval reminder is on
Corrections sit in a queue that has its own daily chase. An organisation with a growing backlog usually has that reminder switched off rather than a shortage of approvers.
The same people are open every week
Look at clock-out friction, not discipline
A clock-out that requires walking back to a specific door, at a site with a tight radius, at the end of a shift, is a clock-out that will be forgotten. The refusal log usually shows this before anybody notices the pattern.
Payroll is imminent and days are still open
Resolve, do not close in bulk
A batch closure at the shift end is exactly the guess this design refuses to make on your behalf, and doing it by hand is not better for having a person's name on it if that person was not there.
Shortening the loop, without inventing a time
The refusal to guess is settled and stays. Everything worth building here is about getting an open day in front of the person who can answer it, faster.
A prompt at the next clock-in
The employee's own portal asking about yesterday's open day when they arrive this morning, with the correction pre-filled to the point of one confirmation.
A suggested time, clearly labelled
A proposed clock-out drawn from the roster or from the last activity on the record, offered to the employee as a starting point they must accept rather than written for them.
An open-day queue
A screen showing every unresolved day with its age, so the backlog is a number somebody owns rather than a line in a morning email.
We publish scope, not dates.
Scope attendance correctionsWhat AWRA OpsHub does today
- A nightly sweep at half past five that finds attendance records from a completed day carrying a clock-in and no clock-out, and leaves the record exactly as it found it.
- A digest to HR and a separate digest to the employee, each governed by its own notification setting and its own reminder cadence, dispatched one job per organisation.
- Days still in progress excluded from the sweep, so a night shift under way is never chased as an error.
- Hours left unmeasured on an unresolved day rather than filled with a plausible duration, so an open day stays findable.
- A midnight-crossing flag taken from the roster that governed the day, never from comparing the row's own clock times, so a transposed pair is not read as a sixteen-hour shift.
- A correction path carrying the requested status, times and reason, with the approver, the moment of the decision and a comment recorded, and approval writing the values into the attendance record.
- A daily reminder at five to ten chasing corrections awaiting a decision.
- A source recorded on every attendance day — a clock-in, a manual entry, an import or a system action — so a corrected day is distinguishable from a punched one.
More we can add to your workspace
- A prompt at the next clock-in asking the employee about yesterday's open day at the moment they are standing there with their phone out.
- A suggested clock-out time offered for confirmation, drawn from the roster and presented as a proposal the employee accepts rather than a value written on their behalf.
- A queue of open days with their ages, so an unresolved backlog is a figure somebody owns rather than a line in a morning digest.
- An escalation when a day stays open past a threshold you set, reaching a manager rather than repeating to the same inbox.
- A report of open days by site and by shift, which is where a pattern of forgotten clock-outs usually turns out to be a door in the wrong place.
- A payroll-cutoff warning listing days still open before a pay run is finalised.
Where we point you to a specialist
- We will not write a clock-out time nobody stated. An invented duration is indistinguishable from a measured one on the record, it reaches payroll without further review, and it removes the only signal that anybody needed to look. This refusal costs an organisation a correction workflow and is worth every minute of it.
- We will not infer a night shift from the times on a row. Where a roster is silent about a midnight crossing, the hours stay unmeasured, because the alternative is a typo becoming a sixteen-hour day on a record that payroll may read.
- How an unresolved day is treated in a pay run is a payroll policy matter and belongs to you and your advisers. We will make the open days visible before the run and record whatever decision is taken; deciding on your behalf whether an unclosed Tuesday is paid is not ours to make.
The next-clock-in prompt is the highest-value contained piece here, because it puts the question in front of the only person who knows the answer at the one moment they are already holding their phone.
Our take
The instinct to tidy an open punch is strong and it should be resisted, because the tidy version is a fabrication that looks like a measurement. What this design does instead is accept a slightly untidy register in exchange for one that never lies: an unresolved day is visibly unresolved, a corrected day carries the name of whoever approved it, and a punched day carries a device signature. Three kinds of evidence, all distinguishable. The cost is real — somebody has to run a correction workflow, and an organisation that ignores the morning digest will find a fortnight of open days on payroll morning. The benefit is that when a shift is disputed a year later, the record answers the question rather than being the question.
Check which digest you are receiving
The most common reason open days pile up is that the reminder is going to HR alone, or is switched off entirely. Both are two clicks in notification settings, and they usually clear the backlog without anything else changing.
Talk through attendance correctionsFrequently asked questions
Why not just close open punches at the end of the shift?
Because the result is a number that looks measured and is not. Every employee who left early and every employee who stayed late would be recorded as having worked exactly their scheduled hours, on a record payroll may read without further review. Leaving the day unmeasured is untidier and it keeps the day findable, which is the only property that lets it be corrected properly.
Does an open day show as zero hours or as nothing?
As nothing — the hours are unmeasured rather than set to zero. That distinction matters in reports, because zero is a claim that no work happened and nothing is a statement that the question is unresolved. The nightly sweep is looking for exactly this state.
What if the employee genuinely worked past midnight?
Then the roster should say so. A shift defined as running from, say, ten at night to six in the morning carries a declared midnight crossing, and days worked on that roster are interpreted accordingly. Where no roster covers the day, the times alone are not treated as evidence of a night shift, because a transposed pair looks identical and the wrong reading produces sixteen recorded hours.
Who gets told about an open day?
Either HR, or the employee, or both — the two are separate notification settings with separate cadences. Organisations that resolve these quickly almost always have the employee digest switched on, because the employee is the only person who knows what time they left.
Can a manager just fix the record directly?
An administrator can amend an attendance day, and the record keeps a source showing it was a manual entry rather than a punch. The preferable route is the correction workflow, because it captures the employee's account of what happened as well as the approver's decision, and the pair of them is what answers a dispute later.
What happens if nobody ever resolves it?
The day stays open indefinitely and continues to appear in the nightly digest. It will not close itself, age out, or acquire a duration. Whether an unresolved day is paid is a payroll decision your organisation makes; what the system guarantees is that it never quietly becomes a number nobody chose.
