Auto-absent and auto punch-out: what policies usually do

Auto-absent and auto punch-out are policy outcomes written onto a day’s attendance record when a punch never arrives or a session never closes. They are not eyewitness evidence of what the person did. Auto-absent typically means: no in-punch by a published rule, so the day is marked absent. Auto punch-out typically means: an open session past a cutoff, so the system stamps an out-time and closes the day. HR should review the exception list those jobs create before payroll freeze. Employees should still have a path to attendance regularization when the default is wrong.

Missing an out-punch is not the same as absence. An in-punch with no out means the person started a session the policy does not yet consider finished. Treating that as a full absent day without a published rule is how genuine presence becomes surprise LOP. This page owns those default outcomes and the review before freeze. Day-status to pay conversion remains in attendance to payroll and LOP. The monthly order of close still follows the monthly HR operating loop.

Auto-absent: no in-punch, a default day status

Write the trigger in one sentence employees can repeat. Examples of triggers teams actually use (pick and publish; do not run all of them silently):

• No in-punch by shift end (or by shift start plus a long window).
• No in-punch by a fixed clock time in the site timezone (for example, end of the attendance day).
• No in-punch and no approved leave, weekly off, or holiday on that calendar date.

The last bullet is the important filter. Auto-absent should skip days that are already weekly offs, public holidays your calendar treats as off, or approved leave. If it does not, you will generate false absence on every Sunday and every Diwali, then spend close week deleting it. Joiners whose punch access is not live and exits whose last day was yesterday also need roster and status hygiene, or auto-absent will nag ghosts and miss new people.

What the mark means: “absent pending exception” versus “absent as final” is a policy distinction. Operationally, keep the day editable through regularization until cutoff. After cutoff, the absent stands for this pay period unless you run a named off-cycle exception. Do not hide a second, unofficial status in a spreadsheet.

On-duty, outdoor, and work-from-home day types: if those days do not require the same in-punch, auto-absent must honour the day type. Otherwise field staff who were never asked to hit the lobby reader will look absent every working day. Shift codes and day types are the switch; auto-absent is only the default when the expected punch is missing.

Auto punch-out: closing an open session

An open session is an in-punch without a matching out. Left forever, hours-worked reports, overtime stories, and “still in” dashboards become fiction. Auto punch-out stamps an out at a published time so the day can close. Typical policy choices for the stamped time:

1. Shift end.
2. Shift end plus a cap (maximum paid or counted hours).
3. A fixed clock (midnight, or the attendance-day boundary you use for night shifts).
4. In-time plus a maximum session length.

Say which one you use, and say whether the stamp is “assumed present until shift end” or “hours unknown, closed for processing.” Those two interpretations disagree in disputes. If you assume shift end, you may overstate hours when the person actually left at lunch and forgot to punch. If you close with zero extra hours or a minimum, you may understate a genuine long day. Many SME policies stamp shift end for forgotten outs and let regularization correct the time when it matters. That is coherent only if people know they must regularize true early outs, and managers watch for a pattern of “always auto-closed at 18:30.”

Auto punch-out should not flip the day to absent. The person punched in. The problem is the close, not the start. Half-day rules based on short hours can still apply after the stamp if you published a short-hours threshold — that is a hours rule, not an absence rule. Keep the vocabulary clean on the calendar: present (auto-closed), present (regularized out-time), half-day, absent.

What HR should review before freeze

Background jobs will keep writing defaults as the month runs. Close week is when you treat the queue as a closeable list, not as background noise. Review, in roughly this order:

1. Auto-absent on working days for people who should have punched. Age the list by manager. A cluster at one site on one date is often a device or network incident, not mass absenteeism.
2. Auto-absent that should have been skipped — weekly offs, holidays, leave, exits, joiners not yet in the roster. Fix master data first; do not regularize fifty Sundays.
3. Auto punch-out volume by team. High volume means forgotten outs, a painful out-reader, or a shift end that does not match how people leave. Decide whether that is a device/UX problem or a behaviour problem before you threaten LOP.
4. Open sessions that have not yet been auto-closed if your job runs at a daily cutoff you have not reached for the last days of the period. Do not freeze while yesterday is still hanging unless the job has run or you have a manual close procedure.
5. Pending regularization that would replace auto-absent or rewrite an auto out-time. Approvals must finish before freeze, on the same cutoff calendar as other attendance exceptions.

Dayzen attendance includes auto-absent and auto-punch-out background jobs. They apply the defaults you configured; they do not replace a written trigger, a skip list, or review. Know when they run in your environment, and put that time on the close-week checklist so you are not freezing before the last stamp.

Assign owners. Managers confirm presence or push people to regularize. HR or operations owns site outages and roster errors. Payroll consumes the closed calendar; they should not be the first people to notice a hundred auto-absents. If only payroll sees the list, you have inverted the attendance management loop.

Regularization still applies

Defaults exist so the month can close without infinite open days. They are not a ban on correction. Allowed corrections:

• Auto-absent → present, half-day, or on-duty, with reason and evidence, when the person worked and the punch missed.
• Auto-absent → leave, when the person was away and should have applied leave instead of staying blank. That is a leave application (or a documented late leave path), not a pretend punch.
• Auto punch-out time → actual out-time, when the stamp is wrong and policy still accepts a correction before cutoff.

Refuse regularization that is actually “please remove LOP because I forgot for three weeks with no story.” Cutoff exists so the default can stand. Publish that standing default so it is not a shock. A first missed in during a documented office-device outage is a different case from a silent month of auto-absents.

Do not let auto-absent double-count against approved leave. If leave is on the day, absence should not also feed LOP. If both appear, your skip logic or your leave–attendance interface is wrong; fix the join, do not ask the employee to regularize a day they already had approved off.

Writing the policy so jobs and humans agree

Put these lines in the employee-facing attendance policy, not only in admin settings:

1. If you do not punch in on a working day, the system will mark you absent after [trigger]. You may request regularization until [cutoff].
2. If you punch in and do not punch out, the system will close the day at [stamp rule] after [when the job applies]. That close is not an accusation you left at that minute. Correct it through regularization if policy allows.
3. Weekly offs, holidays, and approved leave are not auto-absent days.
4. Outdoor or WFH day types follow the punch rules for that type, not the lobby rule by accident.
5. Uncorrected auto-absent at freeze is an unpaid day under our attendance-to-pay rules, unless a written off-cycle exception says otherwise. That unpaid treatment is policy plus payroll input, not a separate moral verdict.

Night shifts: the auto-absent “by when” must use the same calendar-day rule as late marks and leave, or a 22:00 in-punch will mark the wrong civil date. Multi-site: “midnight” needs a timezone. Prefer shift-relative cutoffs over one HQ wall clock when sites actually spread.

During the month, not only at freeze

If managers only open the auto-absent list on the last working day, every genuine device failure becomes an emergency. A weekly glance is enough for a small team: who is auto-absent, who is auto-closed every day, who never is. Patterns:

• Same person auto punch-out daily: they never punch out; coach or fix the out-path.
• Whole line auto-absent on Tuesday: reader or power.
• Only field roles auto-absent: wrong method on the shift code.
• Only new joiners: access provisioning, not discipline.

Self-service visibility matters. People should see “absent (auto)” or “out time auto-closed” on their month view in time to act. A status that only HR can decode will miss the cutoff every cycle. Pair visibility with a reminder in close week, not with daily panic mail that everyone ignores.

Do not convert auto-absent straight to LOP with no exception window, auto-reject regularization after a hidden hour, or auto-present from WhatsApp. The jobs close records; they do not skip management.

---

Auto-absent fills a missing in-punch with a default absent. Auto punch-out closes a missing out-punch with a default time. Review both before freeze, keep regularization open until cutoff, and never treat a forgotten out as a no-show. The record is a policy stamp until a human exception replaces it — then freeze, then pay.