Night shifts and which calendar day a punch belongs to

Overnight shifts create a date-boundary problem: the in-punch and the out-punch often sit on two civil calendar dates. HR has to define which date is the attendance day — the day the shift instance belongs to for presence, leave, weekly offs, late marks, and payroll. Without that definition, night teams argue about “Tuesday late” versus “Wednesday early” every close week.

This is a policy and recordkeeping problem, not a claim that a particular statute tells every Indian employer how to date a night shift. Applicable rules can depend on establishment type, location, employment terms, and your published roster. Write one rule, apply it everywhere the day is used, and stop treating midnight as a surprise.

Why midnight is not a natural attendance boundary

A day-shift punch pair usually lives on one civil date: in at 09:30, out at 18:30 on 12 June. A night shift that starts at 22:00 on 12 June and ends at 06:00 on 13 June has two dates on the clock. If you store punches only as timestamps and then group them by “calendar date of the punch,” you split one shift into two stub days: a few hours on the 12th and a few hours on the 13th. Late marks, weekly offs, and leave then attach to the wrong stub.

The same split appears when auto-absent or auto punch-out jobs run on civil midnight. A person still on shift looks “not punched out on the 12th” and “absent on the 13th” unless the jobs know the shift instance. Pair this with auto-absent and auto punch-out: those rules must use the same attendance-day definition, or they will close the wrong day.

Timezones add a second boundary. A shift configured in IST is not the same clock as a shift for a person working from another offset. Dayzen attendance can include timezones on shifts. That does not decide which civil date owns the instance. Timezone tells you whose clock you are reading. The attendance-day rule still has to be published.

Choose one definition and name it

Pick one primary rule. Publish examples with real clock times. Do not leave managers to infer it from last month’s spreadsheet.

Shift-start day

The attendance day is the civil date on which the shift is scheduled to start. In 22:00–06:00 starting 12 June, both the in-punch and the out-punch belong to 12 June’s attendance row, even though the out-punch’s timestamp is 13 June. Leave on 12 June, if approved for that attendance day, covers that night instance. A weekly off marked 12 June means that night is rest, not the following morning’s day shift.

This rule is easy to explain to rostered night teams: “your night is the date you report in.” It is harder if people casually say “I worked Wednesday morning” meaning the tail of Tuesday’s shift.

Fixed cutoff (for example 06:00)

Punches before the cutoff belong to the previous attendance day; punches at or after the cutoff belong to the new day. Example: cutoff 06:00. An out-punch at 05:45 on 13 June still closes the 12 June night. An in-punch at 06:10 on 13 June starts a 13 June instance if that is how you roster the next shift.

Cutoff rules need a published time and a statement of whose timezone. “06:00” without IST versus site time is how two plants disagree. Cutoff also needs a story for people whose genuine shift ends after the cutoff (extended production, delayed handover). Those cases belong in regularisation, not in silent date hopping.

Other published rules

Some sites use “the date of the majority of hours,” “the date of the roster line in the published week-off chart,” or “the production date printed on the shop floor sheet.” Those can work if they are written, if the system can store the chosen date, and if leave and payroll use it. Informal majority-of-hours guessing at month end is not a rule.

Rule	What you must write	Usual failure if you skip the write-up
Shift-start day	Attendance date = scheduled start date of that shift instance	Morning tail counted as a new day’s presence or absence
Fixed cutoff	Clock time, timezone, and how overruns are regularised	Two sites using two midnights
Roster-line date	Which published roster column is authoritative	Managers re-dating punches to match a WhatsApp roster

Apply the same day to leave, offs, late marks, and pay

The attendance day is not only a punch-grouping trick. Anything that keys off “which day was this?” must use it.

• Leave. A full-day leave on 12 June should mean the 12 June attendance instance, including a night that ends on the 13th if that is your rule. Do not deduct leave on both civil dates for one night.
• Weekly offs. Rest is a rostered attendance day, not “Saturday in the government calendar” by default. If Tuesday is the off for a night crew, Tuesday’s night instance is rest. See nonstandard weekly offs for rest-day recording; this page only insists the day definition matches.
• Late marks and grace. Grace is measured from shift start on the attendance instance, not from 00:00. A 22:15 in-punch against a 22:00 start is a late against that night, even if someone later looks at a 13 June out-punch. Pair with shift start, grace, and late marks.
• Payroll and LOP. Paid-day counts should tally attendance days, not unique civil dates that happen to contain a timestamp. One night is one day (or one shift instance) unless you have a written split-shift policy.

Half-days on night shifts need an extra sentence: which half is “first” — first four scheduled hours after start, or hours before midnight? Write it. Do not invent a nationwide legal formula here.

What HR should check in the record

Attendance management is useful for night crews only if the calendar row is the instance, not a dump of timestamps grouped by punch date. Look at one employee’s night week and confirm:

1. Each scheduled night is one row (or one shift instance) with in and out attached.
2. The out-punch after midnight did not create a second present/absent day.
3. Auto-absent did not fire on the civil morning while the person was still finishing the previous instance.
4. Leave and weekly off flags sit on the same date the floor uses in the roster.

If the system cannot store a shift that crosses midnight as one instance, you will keep repairing dates in Excel. That is a process cost, not a moral failure of the night team.

Regularisation reasons should include “wrong attendance date / shift instance” as a first-class case, distinct from “missed punch.” Moving a punch to the correct instance is not the same as inventing presence.

Handovers, overlapping crews, and double counting

Night operations often have a handover window where incoming and outgoing crews are both on site. Attendance should not treat that overlap as two full days for one person, and it should not treat the outgoing crew as late for the incoming shift. Each person has one rostered instance. Overlap is expected presence at the edge of that instance, not a second shift, unless you actually rostered a second shift and pay it that way.

Do not use handover overlap to justify dating punches “however the supervisor remembers.” Supervisors change. The rule should survive the supervisor.

Month-end close for night teams

Close week is when date errors become LOP. A punch-out at 06:10 on the 1st of the next month may belong to the previous period’s last night. If your cutoff or shift-start rule says so, that instance is in the previous freeze, not “next month’s first day absent.” Publish that example in the close note. The attendance management guide owns the system overview; this page owns the calendar-day policy you must feed that system.

Remind managers of night teams separately. A day-shift reminder “close yesterday’s absents” is the wrong prompt if yesterday’s civil date is still tonight’s shift.

If two people can look at the same two timestamps and disagree which day’s late mark it is, you do not have a night-shift policy. You have an argument scheduled for payday.

Do not cite invented factory-act hour caps or “all night work must be dated X” as if they were universal. Confirm what applies to your establishment with someone qualified if you need a legal reading. Operations still need a dating rule even when the legal reading is pending — otherwise the register cannot be closed.

---

Name the attendance day for shifts that cross midnight. Use shift-start, a fixed cutoff, or another rule you can print with examples. Apply it to leave, weekly offs, late marks, auto-close jobs, and payroll the same way. Dayzen can store shifts with timezones; it cannot guess your calendar-day policy. Write the policy, then make the calendar match the floor.