The roster management cycle
Roster management is a loop, not a document. It starts with demand (how many people of which skill are needed at each post, in each shift, on each day), converts that into a pattern (rotation, weekly offs, shift lengths), assigns named individuals, publishes the result, absorbs changes (leave, swaps, no-shows), and finally compares actual attendance against the published plan to improve the next cycle.
Most Indian SMEs perform the first four steps in Excel or on paper and skip the last two entirely, which is why the same posts are short every month and overtime keeps rising. The comparison step is where the value is: it tells you which posts are structurally under-staffed and which employees are unreliable.
- Demand: coverage requirement by post, shift and day, including client contract minimums.
- Pattern: shift lengths, rotation direction and speed, weekly-off placement.
- Assignment: names against slots, respecting skills, licences, hours limits and leave.
- Publication: a frozen version visible to every employee, with change control.
- Adherence: actual punches compared with rostered shifts; exceptions handled.
KPIs that matter
Coverage rate is the share of rostered slots actually filled by a present employee; for a security contract it is the number that decides whether the client pays in full. Schedule adherence is the share of shifts where the employee worked the rostered shift within tolerance, and it exposes wrong-shift punches and late starts. Unplanned overtime as a share of total hours shows how much of the roster is being rescued at double rate.
Track also the reliever ratio (relievers per rostered slot), the number of open shifts raised per week and how quickly they are filled, and the count of hours-limit breaches. Together these tell you whether the roster is realistic or being propped up by the same few people.
Tools and how they differ
Excel handles the grid but not the loop: it cannot notify, cannot compare with punches and cannot stop two people editing the same file. WhatsApp adds distribution but destroys version control. A roster software adds shift templates, a builder with draft and publish, employee-facing publication, swap and open-shift workflows, and the adherence comparison against attendance.
For multi-site businesses and security agencies, the tool also needs site-wise views so a client's posts can be rostered and reported independently. Our WhatsApp roster alternative guide explains what to look for when moving off the group chat.
An agency with 12 client sites and 60 guards builds next month's roster in the last week of this month. Demand: 45 posts per day across two 12-hour shifts. Pattern: fixed posts, rotating weekly offs. Assignment: 52 guards on posts, 8 relievers. Published on the 25th. During the month, 14 open shifts are raised for absences and filled within an average of 40 minutes; 3 swaps are approved. Adherence at month end is 94%, and two sites show repeated shortfalls on Monday nights, so the next roster adds a reliever to that cluster.
Attend Mitra covers the whole cycle: shift templates and roster presets for the pattern, a weekly builder with draft-to-publish for assignment, app publication with notifications, shift swap and open-shift workflows for changes, warnings for leave conflicts, and a live monitor plus reports that compare actual attendance to the published roster for coverage and adherence.