A night shift ends at 6am. Which day does that attendance belong to?
If your system files a 6am punch-out under the day it happened, your muster roll shows an absence on a night somebody worked. Here is how cross-midnight shifts should be recorded.
A security guard starts at 10pm on Tuesday and clocks out at 6am on Wednesday. Ask most attendance systems what happened and you get two half-records: a clock-in on Tuesday with no clock-out, and a clock-out on Wednesday with no clock-in. The muster then shows an incomplete Tuesday and a strange Wednesday, and the guard has worked a full shift that the report cannot describe.
The rule: a shift belongs to the day it started
For any shift whose end time is earlier than its start time, the whole shift — both punches, the hours worked, the status — belongs to the calendar day on which it began. This is not a preference. Payroll counts shifts, not calendar days, and a shift is one unit of work.
- The 6am Wednesday punch-out closes the Tuesday record.
- The hours worked are eight, recorded against Tuesday.
- Wednesday remains free for the shift that starts on Wednesday night.
- The muster roll shows one worked cell on Tuesday, not two broken cells across two days.
What breaks when this is wrong
- 01The muster shows an absence, or a blank, on a day somebody worked a full shift.
- 02Hours worked cannot be computed, because the system sees a clock-in with no clock-out.
- 03The overtime figure is wrong, because the shift's length cannot be measured.
- 04If the person's weekly off is Wednesday, a punch filed on Wednesday looks like unauthorised work on a rest day.
- 05Over a month these compound, and somebody eventually reconciles the difference by hand — which is exactly the job the software was bought to remove.
How to check whether your system gets it right
You do not need a trial to find out. Ask the vendor one question: if a shift runs 22:00 to 06:00, which calendar day does the attendance record sit on? A system that handles it will answer immediately and specifically. A system that does not will answer with a description of how flexible its configuration is.
Then ask the second question, which catches more systems than the first: what happens on the employee's weekly off? If the night shift starting Saturday at 10pm ends on Sunday morning, and Sunday is their off day, the correct behaviour is that Saturday's shift was worked and Sunday remains their rest day. Systems that file by punch time get this backwards and start flagging rest-day violations that never happened.
Why this is a good proxy for everything else
Cross-midnight shifts are not exotic. Security, manufacturing, healthcare, logistics and hospitality all run them, which is most of the companies that need attendance software in the first place. A product that has not solved this has, almost by definition, not been deployed anywhere with a night shift — and that tells you what else to check carefully.