Without a roster, the same punch supports three different answers
The published schedule allocating employees to shifts — and the document that makes attendance data interpretable at all.
What It Does
Allocates who works which hours, on which days, at which location, across a period.
It Makes Punches Meaningful
A punch at 22:15 is late for one shift, early for another and overtime for a third.
Constraints Belong In It
Minimum rest between shifts, limits on consecutive nights, the weekly off within its span.
A shift roster allocates employees to shifts across a period — who works which hours, on which days, at which location. In a single-shift office it is barely visible. In a factory running three rotating shifts, it is the document that everything else depends on.
The roster is what makes attendance data interpretable. A punch at 22:15 is late for one shift, early for another, and overtime for a third. Without a roster, the same raw punch supports several different payroll outcomes.
Rostering also carries legal constraints that are easy to breach inadvertently: minimum rest between shifts, limits on consecutive night shifts, the weekly off falling within the permitted span, and restrictions on night work for certain categories of worker.
A roster built purely around production demand will breach at least one of these sooner or later — not through indifference, but because the person building it is solving for coverage and the constraints are not in front of them. That argues for putting the constraints into the rostering step rather than reviewing for them afterwards, when the roster has already been published and people have arranged their lives around it.
The other reason to publish early is simpler. Employees on rotating shifts organise childcare, transport and second jobs around the roster. A roster issued two days in advance, or changed after publication, imposes a cost on them that no attendance policy will recover — and it shows up as absenteeism on exactly the shifts that were changed.
Shift Roster FAQs
How far in advance should a roster be published?
As far ahead as the operation allows, and consistently. Employees arrange transport and childcare around it, and late changes reliably produce absence on the changed shifts.
Does the roster affect overtime calculation?
Directly. Overtime is measured against scheduled hours, so the roster determines what counts as overtime and what is simply the shift.
What constraints apply to night shifts?
Minimum rest between shifts, limits on consecutive nights, and restrictions for certain categories of worker. The specifics depend on the establishment type and the state.
How far ahead should a roster be published?
Far enough for people to plan, and any applicable rules on notice for shift changes take precedence over convenience. Late rosters are the most common cause of avoidable absence.
What happens when someone swaps a shift?
The swap belongs on the roster before it happens. Reconstructing swaps at month end from memory is where attendance and pay start disagreeing.
Does a night shift crossing midnight count as two days?
It should be treated as one shift, not split. Splitting it is the single most common roster error and it distorts both attendance and overtime.
Stop working this out by hand
Klok applies these rules on every payroll run, from your own attendance and salary data, with the working shown.