Shift start, end, grace, and late marks

A shift is the window when a workday is supposed to start and end. Grace is a published number of minutes after that start (and sometimes before end or around breaks) that still counts as on time. A late mark is what the record becomes after grace is exhausted. Those three, plus break windows, produce the day’s attendance status. If you publish only “office is 9:30 to 6:30” and argue minutes in the corridor, you do not have a shift policy — you have a rumour with a punch device.

This article is for HR writing the rule so punches, exceptions, and payroll inputs mean the same thing. It is not a product tour of every punch method; that lives in how attendance management works. Night shifts that cross midnight need an extra calendar-day rule, covered separately in night shift punch and calendar day. Here the job is the daytime (and ordinary overnight) relationship: window, grace, late mark, breaks, day’s record.

Shift window: start, end, and what “the day” means

Write clock times against a timezone. “9:30” without IST versus a plant in another state is how two people punch correctly and still look late. A shift also needs a name or code employees will see on the roster (General, First, Second, Site A day). The roster assignment for that date is what the in-punch is judged against. A person moved to a late shift without a roster change will collect late marks against yesterday’s start.

End time matters as much as start. Some policies only police in-punches. That is a choice, but then do not surprise people with short-hours deductions at month end. If you care about a full day, say how an early out is treated: grace before end, a half-day after a threshold, or manager confirmation. If you only care that people arrived, say that too, so auto punch-out and regularization do not become a second, unofficial end rule.

Weekly offs and holidays sit on the same calendar. A window on a weekly off should not generate late marks unless the person was rostered to work. Roster changes need a named effective date. Backdated shift changes after punches exist are exceptions, not casual admin.

Grace minutes: a buffer you can explain, not a secret

Grace is the published slack after shift start during which an in-punch is still on time. Fifteen minutes after 9:30 means 9:45 is on time and 9:46 is late — or 9:45 is the last included minute, depending on how you define the cut. Write the inclusion rule. Employees will test it on the first tense Monday.

Common design choices:

• Start grace only. Simplest. Late marks attach to in-punches after grace. Out-punches are separate.
• Start and end grace. A few minutes early-out still counts as a full day. Useful where lobby queues exist at both ends.
• No grace. Valid if the work is strictly timed. Then every minute after start is late, and you must be ready for the volume of marks and disputes.
• Different grace by shift or site. A plant gate is not a city office with basement parking. Different numbers are fine if they are written per shift code, not negotiated per person.

Grace is not permission to arrive late every day as a lifestyle. If you need a cap (for example, grace applies only N times a month, after which the next late in-punch is a mark even inside the buffer), write the cap. If you do not want a cap, do not invent one in close week because a director is annoyed. Unwritten caps destroy trust in the clock.

Do not hide grace from employees. If only HR can see “grace = 10,” every 9:41 punch becomes a hallway case. Show the shift window and grace on the same screen people use to punch or to read the month.

Late marks: the record after grace, and what they do

A late mark is a recorded fact: in-punch after grace against that day’s shift. What the mark does is a second sentence in the same policy. Options teams actually use:

1. Informational only: the mark exists for the manager; no pay or leave effect.
2. Count toward a threshold: N late marks in a month convert to a half-day or a full-day deduction, or to a warning process.
3. Immediate half-day after a larger delay (for example, more than X minutes after start, regardless of monthly count).
4. Leave or LOP only after a human decision — the mark is input, not auto-deduction.

Pick one primary path and publish the numbers. Mixing “sometimes we ignore it” with “sometimes we cut a day” is how regularization queues explode. If conversion to half-day or LOP exists, employees must see the running count during the month, not only on the payslip. The conversion rule should recompute if a late in-punch is later regularized to an on-time in-punch. Sequence: correct the punch, then apply the late-mark policy, then freeze for payroll.

Late marks are not leave. Do not deduct Casual leave for each late arrival unless that trade is explicit in both attendance and leave policy. Prefer attendance consequences on the attendance record.

Break windows

A break window is a period during the shift when an out-and-in, or a marked break, is expected or allowed without treating the person as having ended the day. Without a window, a canteen punch-out can look like an early out, and a return punch can look like a second in. Write:

• Whether breaks are unpaid, paid, or not timed at all.
• Whether employees must punch for lunch or only for start and end of day.
• How long the window is, and what happens if they exceed it (a note, a short-hours flag, or nothing).

Many Indian SME offices do not punch lunch: one in, one out, break untimed. Do not enable a break-punch requirement only because the setting exists. Field staff often cannot break at a fixed clock. If you time breaks, grace on return like start grace, and keep those flags distinct from shift-start late marks.

How the pieces produce the day’s record

Think of a pipeline, not four unrelated settings:

1. Roster says which shift (start, end, timezone, break rule) applies to this employee on this date.
2. Punches arrive (office device, phone, or other allowed method) with timestamps.
3. In-punch is compared to start + grace → on time, late mark, or beyond the half-day threshold if you have one.
4. Out-punch is compared to end and any end-grace → full day, early out, or open session if missing.
5. Break punches, if used, are compared to the break window.
6. Day status is stored: present, late-present, half-day, absent, on-duty, and so on — whatever codes you actually configured.
7. Exceptions (regularization, shift correction) may rewrite inputs; the pipeline should run again on the corrected punches before freeze.

Dayzen attendance supports shift timings, grace periods, break windows, and timezones on the attendance record. You still have to choose the numbers and the late-mark consequence. The software will not invent a fair policy from a blank shift named “General.”

Setting	Question it answers	What to write in policy
Shift start / end	When is this rostered day?	Clock times, timezone, shift code, who is assigned
Grace	When is “on time”?	Minutes, inclusion rule, any monthly cap
Late mark	What is the fact after grace?	Whether it is informational, counted, or converting
Break window	Is lunch timed?	Punch required or not; length; overrun treatment
Day status	What does the calendar show?	Codes for present, half-day, absent, on-duty

How-to: HR writing the policy without painting into a corner

Draft a version a new joiner can read on day one. Park edge cases in an HR SOP.

1. List live shift codes this quarter, including sites and night teams. Delete unused codes so nobody is assigned a ghost window.
2. For each code, write start, end, timezone, and whether weekly offs rotate.
3. Choose one grace number per code (or a company default plus documented exceptions). Put true individual exceptions on the employment file, not as a silent toggle.
4. Write the late-mark consequence in one paragraph with numbers, including any half-day conversion count and reset period.
5. Decide lunch punching. Default to not punching lunch unless a site has a reason.
6. State which late marks may be regularized, by whom, and until when.
7. Put the same numbers in the employee-facing attendance policy template, not only in admin settings.
8. Walk a sample day: on-time in, late in, missed out, weekly off. Confirm calendar, manager view, and what payroll would read.

If First ends at 15:00 and Second starts at 15:00, a 15:02 in-punch for Second is judged on Second’s grace, not First’s — assignment of the code for that date is the switch. Hybrid days with no in-time expectation need a different shift code or day type, or you will late-mark people who were never asked to punch at 9:30.

Attendance management stores this pipeline. Changing grace on the 28th without notice is a mid-period rule change: publish an effective date, and usually do not recompute past days.

---

Start, end, grace, late mark, and break windows are one policy, not five folklore rules. Write the numbers, show them where people punch, recompute after allowed corrections, then freeze. The day’s record should be explainable from those settings without a manager reconstructing the month from chat.