Attendance

Why night and overnight shifts get miscalculated

Attendance · 7 min read

A shift starting at 22:00 and ending at 06:00 the next morning breaks almost every manual attendance method. Here are the four most common failures, and how to check the system you run today.

A shift that ends after midnight belongs to which day?

This is the root question. A worker clocking in at 22:00 on the 5th and out at 06:00 on the 6th has worked eight hours. But is that the 5th's attendance, or the 6th's?

Manufacturing convention: the work day follows the day the shift starts. A night shift running 5th into 6th is attendance for the 5th. If that rule is not settled before configuration, everything downstream drifts — day counts, overtime hours, night allowances, and reconciliation against leave requests.

A spreadsheet has no concept of this. It only sees two rows on two different dates. That is why almost every manually produced timesheet needs the night-shift section fixed by hand.

Mistake 1: assigning punches by calendar date

The system reads a punch at 06:00 on the 6th and files it under the 6th. The result:

• The 5th has an in punch and no out punch, so it flags as incomplete or scores zero hours.
• The 6th has an out punch and no in punch, so it flags too.
• The worker did a full eight hours but the timesheet shows two broken days.

The correct handling is to attach each punch to the work day implied by the assigned shift, not the date on the device clock. Which means the system must know which shift that person was scheduled for — you need shift assignment, not just logs.

Mistake 2: the wrong punch-collection window

Every shift needs a window around it inside which punches count. Too narrow or too wide both break:

• Too narrow: a worker arrives 40 minutes early, badges in, then changes into uniform. That punch is discarded and the day scores as missing a clock-in.
• Too wide: in a three-shift plant, an eight-hour window picks up punches belonging to the next shift, stretching the clock-out time and manufacturing phantom overtime.

In practice four to six hours either side works for eight-hour shifts spaced apart, but it has to be declared per shift rather than as one global number for the whole plant.

Mistake 3: mid-shift breaks read as leaving for the day

Night shifts usually include a break. If workers badge out and back in for it, the system sees four punches in one shift. A system that simply takes the first and last punch is fine, but one that pairs punches sequentially reads it as: in, out (shift over), then a new shift starting.

The result is one eight-hour shift split into two short ones, or the middle stretch counted as leaving early and then arriving late. The shift definition needs the mid-shift break declared so the system knows those middle punches are a break, not the end of the shift.

Mistake 4: night hours and overtime double-counted

These are two different things and they get conflated constantly:

• Night hours are hours falling inside the legally defined night window, even when they are ordinary hours inside a scheduled shift.
• Overtime is time beyond the scheduled shift, whether it happens in daylight or darkness.

An hour can be both overtime and inside the night window — in which case it belongs in a distinct "night overtime" bucket, not added to both columns. The timesheet needs the tiers separated up front: overtime on a normal day, on a rest day, on a public holiday, and the night portion of each.

Note: the night window and the premium rates are set by law and by company policy. Check the regulation in force at the time you run payroll rather than trusting a number hard-coded in software.

How to check your current system

No tooling required. Take one day with a night shift and compare three numbers:

1. Open the raw log on the device and count the actual punches for one night-shift worker.
2. Open the daily timesheet in your software for the day the shift started, and check both a clock-in and a clock-out are present.
3. Add the hours by hand according to your pay policy and compare with what the software calculated.

If they diverge, the cause is usually one of the four above. Repeat with a day that has overtime after a night shift and you will surface almost everything.

Night shift configuration checklist

When setting up a night shift in any system, make sure all of these are declared:

• Start time, end time, and the flag for running into the next day
• Mid-shift break, plus any secondary breaks
• Hours of log collection before and after the shift
• Whether pre-shift overtime counts, and from how many minutes
• Whether post-shift overtime counts, and from how many minutes
• Grace minutes for lateness
• Who the shift applies to, and on what rotation

Miss any line and the software has to guess — and guessing is how you end up recalculating payroll.