Schedule the Post First, Then Assign the Guard

A security roster that starts with names will always look full and still leave a post empty. The client bought coverage at a named location: Gate 1, basement parking, CCTV room, loading bay, or the residential tower lobby. Headcount is the wrong unit. If eighteen guards are marked present and Post 4 has nobody standing there, the contract is already in breach even though the attendance sheet looks healthy.

Build the duty roster as a grid of posts and duty windows, then drop qualified people into those cells. Example for one industrial campus on a weekday: (1) Gate 1, 06:00–18:00, unarmed, two guards; (2) Gate 1, 18:00–06:00, unarmed, two guards; (3) Material gate, 06:00–18:00, unarmed, one guard; (4) CCTV control room, 24-hour, unarmed, one operator per 8-hour block; (5) Armed cash-office post, 09:00–21:00, licensed only. Until those five rows exist, assigning people is guesswork.

Keep one employee record per guard and many post assignments over time. Indian agencies routinely move the same person across three client sites in a fortnight. If each site creates a new name in a spreadsheet, you cannot see double-booking, rest violations, or a licence that does not match the post. The post is what the client audits. The person is what you pay.

• Create a named post for every SLA location, not a site-level headcount
• Assign a duty window, skill, and headcount to the post before naming anyone
• Keep one guard identity while reporting hours and deployment by post
• Treat an empty post as a coverage failure even if overall attendance looks high

Separate Armed, Unarmed, and Licensed Duties

Armed and unarmed posts are not interchangeable staffing. An unarmed reliever cannot legally or contractually cover an armed cash-office or ATM-replenishment duty. A licensed armed guard billed at a higher rate should not be parked on a lobby post just because the grid had a gap. Mixing these categories is how agencies either under-deliver the SLA or overpay labour for work that did not need the licence.

Encode the requirement on the post, not in a supervisor's memory. Capture: armed or unarmed, weapon category if relevant, PSARA and local licence status, first-aid or fire-warden flags, gender requirement where the client specifies it, and whether the post may be covered by a trainee. Then block assignment when the guard's record does not match. The check has to happen while the roster is being built, not at 05:40 when the night supervisor is scrambling.

Rate cards follow the same split. Example: unarmed 12-hour industrial post at ₹18,000 per month billed, armed 12-hour cash-office post at a higher contracted rate, female residential lobby post at a specified rate. If payroll and billing both read the post type from the same roster, you stop the common leak where an armed guard is paid the armed rate while working an unarmed post, or the reverse complaint from the client.

• Store armed, unarmed, and licence requirements on the post template
• Block assignment when the guard's credentials do not match the post
• Keep trainee, reliever, and fully qualified statuses distinct
• Bill and pay from the post type, not from an informal chat instruction

Choose 8-Hour and 12-Hour Duties Deliberately

Indian security operations commonly run 12-hour duties (06:00–18:00 and 18:00–06:00) because two shifts cover the post with fewer handovers. Eight-hour duties (three blocks in 24 hours) reduce fatigue and make weekly-off rotation easier, but they need a larger bench and a tighter handover. Neither pattern is universally better. The wrong choice is mixing them on the same post without a rest rule, which produces 18-hour stretches when a reliever fails to arrive.

Write the duty as a template: start, end, unpaid break if any, handover overlap, weekly-off rule, and whether the shift owns the calendar date of the start. A 18:00–06:00 duty is one operational shift, not two half-days. If the roster splits it across dates, night allowances, client billing, and overtime all drift. Test three cases on paper before going live: a clean 12-hour night, a 12-hour night with a 45-minute late relief, and an 8-hour rotating block that follows a previous night duty.

Handover is part of the duty, not a courtesy. A 15-minute overlap at a gate post is cheaper than a 20-minute unmanned gap. Define who remains accountable during the overlap, and do not let the outgoing guard check out the moment the incoming guard is 'on the way.' The post is covered only when the incoming assignment is confirmed present.

• Pick 8-hour or 12-hour per post based on fatigue, bench size, and handover risk
• Keep a night duty as one shift even when it crosses midnight
• Add a defined handover overlap rather than hoping guards meet at the gate
• Never stack a 12-hour night immediately into a 12-hour day for the same person

Build Relief That Protects the Client SLA

Client SLAs in facility and security contracts are written around the post remaining staffed, not around an individual employee remaining healthy. Leave, sickness, court dates, and transport failure are normal. A roster without a named relief bench is a roster that will be patched on WhatsApp at 05:30. That patch is how the wrong person ends up on an armed post, or nobody ends up there at all.

Maintain three layers: (1) the primary guard on the published duty; (2) a designated reliever who already knows the post, the client standing orders, and the geo-fence; (3) a floating bench that can be pulled across nearby sites without creating a second empty post. When the primary is on approved leave, assign the reliever in the roster before the week publishes. When the primary no-shows, the supervisor should see qualified, rested, and not-already-assigned candidates, not a group chat.

Relief must inherit the post's rules. If Gate 2 requires face verification inside a 150-metre fence, the reliever marks against that post, not against a generic 'office' location. If the duty is 12 hours, the reliever's rest clock starts from their previous duty, not from the moment someone typed their name into the chat. Record the substitution as a roster change with a reason, so billing still shows the post covered and payroll pays the person who actually stood there.

• Name a trained reliever for every critical post before the week starts
• Keep a floating bench that is not already committed to another SLA post
• Assign relief in the roster so the post's verification and pay rules follow the person
• Never cover an armed or licensed post with an unqualified stopgap

Stop No-Shows Before They Become Empty Posts

A no-show is an operations event with a clock. If the duty starts at 06:00 and the grace period is ten minutes, the supervisor needs an alert at 06:10, not a monthly absence report. The cost is the unmanned post, the client complaint, and the emergency overtime you will pay whoever you can find. Agencies that wait for the outgoing guard to phone head office are already late.

Run a simple escalation: (1) at shift start minus 30 minutes, the incoming guard receives the duty reminder; (2) at start plus grace, the post is flagged uncovered and the designated reliever is offered the duty; (3) if the reliever is more than a defined travel time away, the floating bench at the nearest site is pulled; (4) the original assignment stays on record as a no-show, not overwritten, so counselling and payroll deductions have evidence. Overwriting the name hides the pattern.

Track no-shows by post, by time of day, and by transport corridor, not only by employee. A 06:00 industrial-belt post with repeated empty starts often has a bus or housing problem, not a discipline problem. A 22:00 cash-office post with repeated gaps may be an unpopular armed duty that the rotation is dumping on the same three people. The roster software should make that concentration visible.

• Alert the supervisor when a post has no confirmed check-in after grace
• Offer the duty to a pre-qualified reliever instead of broadcasting a chat plea
• Keep the original no-show on the record when a substitute takes the post
• Review repeated empty starts by post and time window, not only by person

Close Multi-Site Agency Operations Against One Roster

A typical Indian security agency is running dozens of client sites, mixed 8-hour and 12-hour duties, a mix of armed and unarmed posts, and a bench that moves. The failure mode is three systems: a spreadsheet for the roster, a WhatsApp group for changes, and a biometric dump for payroll. None of them can tell you whether Post 7 was covered last night, who stood there, or which client should be billed.

Close each day with three questions: Was every published post filled? Did the person who marked attendance match the person assigned, including relievers? Do payroll hours and client billing hours reconcile to that assignment? A guard who worked Gate 1 until 10:00 and was moved to the material gate must show two post segments, not one blurred 12-hour block that neither client can audit.

Attend Mitra is built for this operating model: reusable shift templates per post, weekly duty rosters that stay in draft until coverage and leave checks pass, employee-visible published assignments, and attendance that can be verified against the post's location. Supervisors see an uncovered duty in time to use the relief bench. Payroll and client reports then read the same roster instead of reconstructing the night from chat history. Coverage patterns continue in how to manage 24/7 employee rotas. Prove the post with how to verify guards are on site, and treat empties as how to handle security guard no-shows. Multi-site books use how to track security guards on multiple sites and security guard software.

• Publish one duty roster as the source of truth across all client sites
• Record intra-day post moves as new assignments, not informal verbal shifts
• Reconcile coverage, attendance, payroll, and client billing from the same posts
• Keep draft changes off phones until the week's coverage check is complete