Managing hundreds of security guards across many posts: structure, rosters, records and payroll
How to run hundreds of guards across many posts: supervision structure, rosters within the Labour Act, leave cover, communication, records and payroll at scale.
- StrataMax team
- 10 min read
- 4 sources
On this page
Figures in this article are checked as of 15 November 2026. Rules change with each budget and gazette notice, so confirm current rates with the IRD, SSF or your tax adviser before you rely on them.
To manage hundreds of security guards across many posts, you need five things working together: a clear line of supervision for every post, rosters that respect the Labour Act with a planned relief pool for leave, one record per guard that everyone works from, fixed communication channels between posts and the office, and payroll run as checked, approved batches that can be reviewed client by client.
None of this is complicated at 30 guards, because the owner knows every guard and every post. At 300 guards it breaks, not because guards change but because no single person can hold it all in their head. This guide covers what changes as you grow, how to structure supervision, how to roster within the law with worked numbers, and how to keep records and payroll under control at scale.
What changes when a security company grows past a few posts?
| Area | At 30 guards | At 300 guards and more |
|---|---|---|
| Supervision | The owner visits posts personally | Supervisors and patrol officers need their own schedules |
| Rosters | Kept in one person’s head or notebook | Must be written, checked against the law and shared |
| Leave cover | Swap guards between nearby posts | Needs a planned relief pool |
| Records | Paper files and one spreadsheet | One record per guard, used by everyone |
| Communication | Phone calls from the owner | Fixed channels and escalation rules |
| Payroll | One sheet, one person | Batches, approvals, history, client-wise totals |
| Client reporting | Ad hoc | Regular, consistent reports per client |
The common mistake is to respond to growth by hiring more office staff to do the same manual work. That adds cost without adding control. Growth needs structure first.
How should you structure supervision?
Every post needs a clear answer to the question “who is responsible for this post right now?” A typical structure:
| Role | Responsible for | Reports to |
|---|---|---|
| Guard | Duty at the post during the shift | Post in-charge |
| Post in-charge | A multi-guard post: handovers, register, first response | Patrol officer or area supervisor |
| Patrol officer | Scheduled visits to a set of posts; findings and conclusions | Area supervisor |
| Area supervisor | All posts in an area; rosters, relief, client contact on site | Operations manager |
| Operations manager | All areas; clients, incidents, staffing | Owner or director |
| HR and payroll | Records, leave, payroll batches | Operations manager or finance |
How many posts one patrol officer or supervisor can cover depends on distances, traffic, shift pattern and the risk at each post. Set the number by what can actually be visited on schedule, then check it each month against completed and missed visits.
Patrol visits are the backbone of supervision at scale. A patrol officer visits a post, checks that the right guard is on duty and alert, inspects the post and records findings, a conclusion and photos. Our guide to patrol visits across many posts covers scheduling, what to check and how to handle missed visits.
How do you roster guards within the Labour Act?
The rules that shape every roster come from the Labour Act 2074:
- Normal hours: up to 8 a day and 48 a week (s.28(1)).
- Rest: half an hour after 5 continuous hours, given in turns in continuous work, and counted as working time (s.28(2) to (4)).
- Overtime limit: at most 4 hours a day and 24 hours a week (s.30(1)), paid at 1.5 times basic (s.31(1)).
- Weekly leave: one day a week (s.40).
- Public holidays: 13 days a year, 14 for women (s.41(1)).
- Substitute leave: a guard in continuous-operation work who works a weekly or public holiday gets substitute leave within 21 days (s.42).
- Night work by women: the employer must arrange transport for women working after sunset or before sunrise (s.33).
Worked example: a 24-hour post on 12-hour shifts
A post staffed around the clock on two 12-hour shifts needs 2 shifts a day × 7 days = 14 shifts a week.
Each 12-hour shift is 8 normal hours plus 4 hours of overtime. The weekly overtime cap of 24 hours allows at most 24 ÷ 4 = 6 twelve-hour shifts per guard per week, which also leaves the seventh day as weekly leave.
- Two guards can cover at most 2 × 6 = 12 shifts. That is short of 14, so two guards are not enough.
- Three guards can cover up to 3 × 6 = 18 shifts. Covering 14 with, say, five, five and four shifts keeps each guard at 20, 20 and 16 overtime hours a week, inside the cap.
So three guards per 24-hour post is the minimum before leave. The post also generates 14 × 4 = 56 overtime hours a week, which must be priced into the contract.
Worked example: sizing the relief pool
Weekly leave is built into the roster above. Home leave, sickness, public holidays and substitute leave are not, and they need relief guards.
Take 30 such posts with 3 guards each, 90 guards, each working about 26 days a month:
- Home leave: 1 day for every 20 days worked (s.43). 26 ÷ 20 = 1.3 days a month per guard. 90 × 1.3 = 117 days.
- Sick leave: 12 days a year (s.44), so up to 1 day a month per guard if all of it is taken. 90 × 1 = 90 days.
- Total: 117 + 90 = 207 relief shifts a month.
- Relief guards needed: 207 ÷ 26 = 7.96, so 8 relief guards.
Public holidays worked and the substitute leave owed for them add to this, as do mourning and maternity leave when they arise. This is a planning estimate: in practice leave bunches around festivals, so plan extra cover for Dashain and Tihar. Our leave rules guide covers each entitlement in detail.
Rostering habits that work at scale
- Publish the roster before the period starts, and record every change with the reason.
- Keep relief guards assigned to an area, so they know the posts they cover.
- Track substitute leave owed, so it is given within 21 days rather than forgotten.
- Never cover a gap by extending a guard beyond 4 overtime hours a day or 24 a week. Use relief.
How do you keep communication working across many posts?
At scale, communication fails when everything depends on phone calls to one person. Fix the channels:
| What | Channel | Who |
|---|---|---|
| Assignments and roster changes | Written, sent to the guard’s phone | Area supervisor |
| Leave requests | Requested in writing, approved or refused with a reason | Guard to supervisor |
| Patrol findings | Recorded at the post during the visit | Patrol officer |
| Incidents | Reported at once by phone, then recorded in full | Post in-charge to operations |
| Notices to all guards | Sent to every guard’s phone | Operations or HR |
| Client concerns | Logged, assigned, followed up | Area supervisor |
Write down an escalation rule: what a guard does if relief does not arrive, who decides, and how quickly the office must respond. Under the Labour Act s.51, only sick, mourning and maternity leave are rights; other leave can be refused or rescheduled for work needs, but with reasons given. Keep those reasons on the record.
Incidents need their own discipline: what happened, when, where, who was involved, severity and follow-up.
What records must you keep for every guard?
One record per guard, used by operations, HR, payroll and billing, is what stops the same guard appearing with different details in different files. It should hold:
- Profile: name as on citizenship, contact, address, emergency contact, bank details, PAN and SSF ID. Leave missing values blank and follow them up; never fill them with another number.
- Documents: citizenship copy, contract, police or character verification where you require it.
- Certificates and training records, with dates.
- Equipment: every item issued and returned, with dates and condition.
- Assignments: client, post and shift, with dates.
- Attendance and leave.
- Patrol findings and incidents involving the guard.
- Payslips for every month.
When a guard leaves, mark the record inactive rather than deleting it. You need the history for the final settlement, which the Labour Act s.148 requires within 15 days, and for any later query.
How do you run payroll for hundreds of guards?
Payroll is where scale hurts most, because a single wrong setting repeats for every guard. The approach that works:
- Close attendance and leave for the month, post by post.
- Apply changes with effective dates: revisions, transfers, joiners and leavers.
- Calculate basic, dearness allowance, overtime at the shift rate, SSF at 11% and 20% of basic, and TDS on the FY 2083/84 slabs.
- Review client by client. Totals per client make unusual figures stand out and give you what you need to match against each client’s invoice.
- Approve the batch before payment, and keep its version history.
- Pay by bank transfer and issue a payslip to every guard. Paydays must be no more than one month apart (s.35).
- Deposit SSF within 25 days after the end of the month (Contribution Based Social Security Act s.4(4), as amended 2082), and TDS within the same 25 days (Income Tax Act s.90).
For a guard on 13,200 basic, the SSF deposit is 13,200 × 31% = 4,092.00 a month. For the 90 guards plus 8 relief guards in the example above, all on that basic, it is 98 × 4,092.00 = 4,01,016.00 a month: a deadline that matters. Our guide to payroll software for security companies works through a full guard payslip.
Outsourcing companies have the same duties for every placed worker: under the Labour Act s.61 the supplier pays at least the statutory pay and benefits in the capacity of the employer.
What should owners review every month?
| Report | What it tells you |
|---|---|
| Posts staffed vs posts contracted | Gaps and over-staffing |
| Overtime hours by post | Posts that need relief or re-pricing |
| Patrol visits completed and missed | Whether supervision is really happening |
| Incidents by post and severity | Risk, and client conversations to have |
| Leave taken and substitute leave owed | Relief needs and legal exposure |
| Payroll by client vs invoices by client | Unbilled guards and shifts |
| Equipment issued vs returned | Losses to recover |
| Statutory deposits made and dates | SSF, TDS and VAT on time |
When a report shows a gap, trace it to the post and the process behind it, not just the person.
Common mistakes when managing large guard teams
- Adding office staff instead of structure. More people doing the same manual work adds cost, not control.
- Rostering with overtime instead of relief. It breaches the 24-hour weekly cap and tires guards on night duty.
- No record of substitute leave owed. It is forgotten, and the holiday work becomes overtime under s.30(2).
- Several versions of the guard list. Payroll, operations and billing disagree about who is where.
- Missed patrol visits deleted or quietly rescheduled. The pattern of skipped posts never shows.
- Payroll reviewed only as a company total. Errors at one client hide inside the total.
Checklist: managing hundreds of guards
- Every post has a named post in-charge or responsible guard, patrol officer and area supervisor.
- Patrol officers have schedules they can actually complete; missed visits are reviewed.
- Rosters published in advance and checked against 8 normal hours and 4 overtime hours a day, 24 a week.
- Each guard gets weekly leave; substitute leave given within 21 days.
- Relief pool sized from expected leave, with extra cover planned for festivals.
- Transport arranged for women on night shifts.
- Assignments, leave requests and notices go to guards in writing.
- An escalation rule for missed relief and incidents.
- One record per guard, used by every department; missing values left blank.
- Payroll reviewed client by client, approved before payment, with history kept.
- SSF and TDS deposited within 25 days.
- Leavers settled within 15 days.
Where StrataMax fits
StrataMax is built for running security and outsourcing companies at this scale. It keeps one profile per employee with documents, certificates and training records, and equipment issue and return. Patrol officers record patrol visits with findings, a conclusion, photos and start and end locations. Incidents are recorded in the web app with severity and follow-ups. Guards use the Android app for assignments, check-in and check-out with their location checked against the site area, leave requests and notifications. Payroll runs as approved batches with SSF, TDS, overtime at the rate set per shift, version history, payslips and a connectIPS bank file. See guard management in StrataMax, or book a demo to walk through your own posts and roster.
Frequently asked questions
How do you manage hundreds of security guards across many posts?
Give every post a clear line of supervision (post in-charge, patrol officer, area supervisor, operations manager), roster guards within the Labour Act limits with a planned relief pool for leave, keep one record per guard, run scheduled patrol visits, fix the communication channels, and run payroll as checked, approved batches that can be reviewed client by client.
How many guards does a 24-hour post need?
On two 12-hour shifts a 24-hour post needs 14 shifts a week. Each guard works 4 hours of overtime per 12-hour shift and is capped at 24 overtime hours a week, so at most six such shifts. Three guards can cover the post at five, five and four shifts a week, before allowing for home leave, sickness and public holidays, which need relief cover.
How many relief guards does a security company need?
Work it out from leave, not from a rule of thumb. Add up the leave days you expect each month (home leave of 1 day per 20 days worked, sick leave of 12 days a year, public holidays and substitute leave) and divide by the shifts one relief guard can work. For 90 guards that is roughly eight relief guards if all home and sick leave is taken evenly.
What records should a security company keep for each guard?
A profile with identity, contact, bank, PAN and SSF details; documents and certificates or training records; equipment issued and returned; assignments and attendance; leave; patrol findings and incidents involving the guard; and every payslip. Missing values should be left blank and followed up, never filled with another number.
Sources
- Labour Act 2074, Nepal Law Commission English translation (FAOLEX mirror)
- Social Security Fund: amount to be deposited in the fund (contribution rates)
- Contribution Based Social Security Act 2074, section 4: contribution to be deposited
- Inland Revenue Department: Income Tax Act 2058, as amended (consolidated)