What a Guard Duty Roster Must Show
A security guard duty roster is not a list of names against dates. It is a commitment to a client that a specific post will be manned by a specific, verified person during a specific window, every day of the month. If any one of those five elements is missing, the roster cannot be used for attendance, for billing, or for a PSARA inspection.
The minimum columns are: site, post (Main Gate, Basement B2, Reception, Patrol), shift with exact timings (08:00–20:00, not just 'Day'), the guard assigned by name and ID, and the reliever who covers that guard's weekly off. Add the supervisor responsible for the site and the week-off day for each guard, and you have a roster that a client, a labour inspector and your payroll executive can all read the same way.
Most agencies still keep this in an Excel grid with guards down the left and dates across the top, filled with D, N and WO codes. That works for one site. It breaks down when the same guard appears on two site sheets, when a reliever moves between three clients in a week, or when the field supervisor changes the roster on WhatsApp at 19:30 and the sheet is never updated. The duty roster glossary entry covers the vocabulary; this article covers the method.
- Site and post, named exactly as they appear on the client contract and deployment letter
- Shift with start and end time, including shifts that cross midnight
- Guard name and employee ID, never a nickname or a phone number
- Reliever assigned for each week-off slot, with their own ID
- Supervisor of record and the roster version or publish date
8-Hour vs 12-Hour Posts: The Guard-Count Maths
Before you draw a single grid, calculate how many guards a post actually consumes. A 24×7 post needs 168 hours of cover per week. On 8-hour shifts that is 21 shifts per week; on 12-hour shifts it is 14. A guard who works six days and takes one weekly off covers six shifts per week. Divide the shifts needed by six and you have the guards needed per post.
For a 12-hour post: 14 ÷ 6 = 2.33 guards. For an 8-hour post: 21 ÷ 6 = 3.5 guards. This is why a single 12-hour post is usually staffed as 'two guards plus a shared reliever', and a single 8-hour post as 'three guards plus a shared reliever'. The fraction is the reliever load, and it only works out neatly when you pool it across posts.
Take a housing society with three 24×7 posts on 12-hour shifts. 3 × 2.33 = 7 guards. Six regular guards each hold one shift on one post for six days, and the seventh guard rotates through the six week-off slots (one per day, six days) and takes the seventh day off. On 8-hour shifts the same three posts need 3 × 3.5 = 10.5, so you deploy 10 guards and cover the half with overtime or a floating reliever shared with a neighbouring site. Never round down without deciding who absorbs the gap.
- Weekly shifts per 24×7 post: 21 on 8-hour, 14 on 12-hour
- Guards per post with one weekly off: 3.5 on 8-hour, 2.33 on 12-hour
- Three 12-hour posts = 7 guards (6 regular + 1 rotating reliever)
- Two 8-hour posts = 7 guards; three 8-hour posts = 10.5, so plan the half
- Every 0.33 or 0.5 you round away becomes unpaid overtime or an unmanned post
Step-by-Step: Building the Roster
Start from the deployment plan, not from the list of available guards. Write down every site, every post and the hours each post must be manned. Some posts are 24×7; a school gate may be 07:00–15:00 six days a week; a construction site may need a night watch only. Convert each into shifts per week using the maths above and total the guards required per site.
Next choose the shift pattern per site. Clients often push for 12-hour posts because two guards look cheaper than three, but a 12-hour shift is 8 hours of normal duty plus 4 hours that must be paid as overtime at twice the rate under the Factories Act and the Code on Wages. Price that honestly in the contract; the security guard billing calculator shows the cost difference between the two models. Then fix the rotation cycle and the week-off cycle, assign relievers, and only then place names.
Finally, publish. A roster that exists only in the supervisor's head or in a WhatsApp forward is not a roster. Print or share the published version with the client and each guard, and record the version date so that a later change is visible as a change. Dedicated security guard duty roster software keeps the draft and published versions separate, which is exactly the discipline a paper process lacks.
- Site strength: list every post and its manning hours before touching names
- Shift pattern: 8-hour or 12-hour per site, with overtime priced in for 12-hour
- Rotation: decide how day and night swap (weekly, fortnightly, or fixed)
- Week-off: assign one fixed off day per guard so relievers can be planned
- Relievers: one rotating reliever per six week-off slots; then publish and version
Rotation Patterns That Work for Guards
The most common pattern for 12-hour posts is a weekly day-night swap: guard A works 08:00–20:00 Monday to Saturday, guard B works 20:00–08:00, and on the following Monday they swap. The swap needs a rest gap; a guard finishing at 08:00 Sunday cannot start a day shift at 08:00 Monday and a night shift the same evening. Give the swap at least 24 hours of rest, which is why many agencies place the weekly off on the swap day itself.
For 8-hour posts the classic three-shift cycle is morning (06:00–14:00), evening (14:00–22:00) and night (22:00–06:00), rotating forward every week. Rotating forward (morning to evening to night) is easier on sleep than rotating backward. Under the Factories Act benchmark the working week is capped at 48 hours and the spread-over at 10.5 hours, and the Code on Wages keeps the 48-hour weekly cap, so a six-day 8-hour pattern sits exactly at the limit with zero overtime.
Six-on-one-off is the standard week-off cycle because it aligns with the 26-day wage month. Some clients ask for fixed off days (every guard off on Sunday) which is impossible at a 24×7 post; instead stagger offs across the week so exactly one guard is off each day and one reliever covers the whole site. The rotating roster guide goes deeper on rotation cycles for other industries.
- Weekly day-night swap for 12-hour posts, with a rest day placed on the swap
- Forward-rotating three-shift cycle for 8-hour posts
- Six-on-one-off week-off cycle, staggered so one guard is off per day
- Never schedule a night shift ending at 08:00 followed by a day shift at 08:00
- Keep the same post for a guard as long as possible; familiarity is security
Handling Leave, No-Shows and Last-Minute Changes
A roster that assumes perfect attendance fails in its first week. Approved leave should be visible when you build the roster: if guard C has sanctioned leave from the 12th to the 15th, the grid must show a reliever on those days, not C's name. This is the single most common reason a post goes unmanned and a client complaint follows.
No-shows are different. At 07:45 the day guard has not arrived and the night guard has been on post since 20:00. The rule most agencies follow is: night guard continues (and is paid overtime at double rate), supervisor dispatches a reliever within a fixed window, and the no-show is recorded against the absent guard for LOP. The escalation chain (guard, site supervisor, area officer) must be written down and known to the client. See how to handle security guard no-shows for the operational playbook.
Every change to a published roster should leave a trace: who changed it, when, and why. Without that trace, month-end attendance reconciliation becomes an argument about whose memory is correct. In Attend Mitra the weekly roster is built in draft and published in one step, it warns you when you place a guard who already has approved leave, and open shifts can be offered to eligible relievers from the app, so the change history exists without anyone maintaining it.
- Block approved leave in the roster before assigning relievers
- Write the no-show rule: who continues, who is called, within how many minutes
- Pay the continuing guard overtime at twice the rate; do not bank it informally
- Record every change to a published roster with a timestamp and a reason
- Review no-show patterns monthly; repeat offenders need a conversation, not a reliever
Common Roster Mistakes That Cost Money
Double booking across sites is the mistake that only becomes visible when two clients are invoiced for the same guard on the same day. It happens because each site keeps its own sheet. A consolidated roster, or software that refuses to assign one guard to two overlapping shifts, is the only reliable cure.
Continuous duty beyond 12 hours is the second. A guard who finishes a 12-hour night and 'helps out' on the day shift has now worked 16 or 24 hours. This violates the spread-over limit, exposes the agency to an accident liability it cannot defend, and produces an overtime bill that was never quoted to the client. The third mistake is having no reliever pool at all, which guarantees the first two.
The fix is structural rather than heroic. Build the reliever load into the guard count, keep one roster per company rather than one per site, and make overtime visible per guard per week before payroll, not after. Attend Mitra's security guard scheduling software flags overlapping assignments and long continuous duty at roster stage, and the published roster feeds attendance, so a guard marking in at the wrong site or wrong time is caught on the same day.
- One guard on two sites in the same window: consolidate rosters to catch it
- More than 12 hours continuous duty: enforce a rest gap between shifts
- No reliever pool: budget 0.33 guards per 12-hour post, 0.5 per 8-hour post
- Unpriced overtime: quote 12-hour posts with the double-rate hours included
- Unversioned changes: keep draft and published rosters separate
Moving From Excel and WhatsApp to a Roster App
Excel and WhatsApp are not the enemy; they are simply tools that do not know what a shift is. Excel cannot tell you that guard D is on two sheets. WhatsApp cannot tell you that the roster the client is looking at is three versions old. Both depend on one person remembering to update everything.
A roster application built for security agencies knows about posts, shifts, relievers, and week-offs. It lets you build the week once from a preset, publish it to every guard's phone, and lets attendance check itself against the roster. If you want to start on paper, download the security guard duty roster template and fill it using the steps above. When you outgrow it, the migration is a matter of importing the same columns.
The guide to managing security guard shifts covers day-to-day shift operations once the roster is live, and the deployment letter and plan format explains how to document the strength chart the roster is built from.