Shift roster vs duty roster
The two overlap, and many teams use the words interchangeably, but the emphasis differs. A duty roster starts from posts or locations and asks who fills each one. A shift roster starts from shift codes and asks which team or person is on A, B, C or N shift on a given date. A factory with 200 workers on three shifts cares about the shift roster; a security agency with 40 posts cares about the duty roster.
In practice a large operation needs both: the shift roster fixes the rotation pattern for the whole workforce, and department-level duty rosters place individuals against machines, wards or gates within their shift.
Common shift codes and rotation
Indian factories typically run A (06:00–14:00), B (14:00–22:00) and C (22:00–06:00) with a G or general shift (09:00–17:30) for staff. Teams rotate weekly or fortnightly, usually forward (A to B to C), because moving the body clock later is easier than moving it earlier. See 3-shift roster patterns and rotating shift schedule examples for ready-made cycles.
The roster must also show weekly offs. Under the Factories Act each worker gets one day of rest in seven, and a rotating roster has to move the off day with the shift so that no one works more than ten consecutive days without a rest day (s.52 allows substitution within limits).
- Keep codes short and consistent: A, B, C, N, G, WO, L, H (holiday).
- Print the timing legend on every copy of the roster.
- Show the full rotation cycle (3 or 4 weeks) so people can plan ahead.
- Never place a C shift ending at 06:00 followed by an A shift starting at 06:00 the same day.
Publishing and tracking adherence
A roster that lives only in a supervisor's notebook cannot be enforced. Publish it where every employee can see their own line, and keep the published version frozen so that later changes are visible as changes. Then compare actual punches against it: an employee rostered on C shift who punches in at 09:00 is not 'present', they have worked the wrong shift and the night post was short.
This comparison is what turns a roster into schedule adherence data, which feeds overtime approvals, no-show reports and payroll. Our guide on how to manage rotating rosters covers the publishing and change-control routine.
A packaging unit runs A, B and C shifts with four teams of 15. In week 1, Team 1 is on A, Team 2 on B, Team 3 on C and Team 4 is the off/reliever team whose members take their weekly offs and cover absences. Each week the teams move forward one step. Over four weeks every team has done each shift once and had one lighter week. Each worker's weekly off rotates within the team so that every shift stays at 12–13 present on any given day.
In Attend Mitra you define shift templates once (with grace period, break rules and whether the shift crosses midnight), then build the weekly roster by assigning templates to people or whole departments. The roster is published to the mobile app, and the live monitor compares actual punches against the rostered shift so late marks and wrong-shift punches are flagged automatically.
