Give Every Guard, Supervisor and Officer a Clear Line of Command
Security work is spread across many client premises, often with nobody senior in sight for most of a shift. Our organisation design service sets out who reports to whom, how many posts a supervisor can truly look after, and what each level may decide without calling the office. You decide the structure; we draw it, test it against your sites and write it down so it holds when people change.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsThe starting point
Does Your Structure Hold When You Are Not at the Site?
Agencies usually grow one contract at a time, and the reporting lines grow the same way. A guard reports to whichever supervisor is closest, a supervisor to whichever officer is available, and the owner is called for anything that needs a decision. It works until the number of sites passes what a few people can carry in their heads.
We help you work out where authority sits and make it visible to everyone on the roster.
You may be experiencing:
- Guards unsure whom to obey when a client's facility manager and the agency supervisor give different instructions.
- Field officers each looking after a different number of sites, some close together and some far apart.
- Night posts that are visited rarely because nobody owns the night round.
- Decisions on a replacement, a transfer or a leave request that wait for the owner by phone.
- Supervisors who are also standing a post, so supervision happens only when time allows.
- No named deputy when an area manager is away, so a region goes quiet.
- A head office whose roles blur between operations, HR, accounts and billing.
What we can help with
Our Organisation Design Services for Security Agencies
Structure Review Across Sites
Map the present chain from guard to owner, by client and region, and note where lines cross, double up or stop. The picture often differs from the chart that is pinned at head office.
Span of Control by Site Type
Set how many guards a supervisor can reasonably oversee on a campus, at scattered single-post sites and on night rounds, and how many sites a field officer can inspect with proper frequency.
Role Definitions From Guard to Area Manager
Write short role sheets for guard, senior guard, supervisor, field officer, control-room operator, area manager and head office roles, covering what each owns and what each hands up.
Authority Matrix for the Site
Define who can approve a shift swap, a reliever call-out, a short leave, a post reassignment or an incident report to the client, and the limit at each level.
Night and Weekend Command
Decide who holds authority outside office hours, how the on-call officer is chosen, and what a guard does when nobody answers.
Client-Facing Roles and Escalation
Clarify who speaks to the client's facility team, who owns the relationship, and the route a client's complaint takes inside your organisation.
Deputy and Handover Arrangements
Name a deputy for every supervisory and area role, with a simple handover note, so that leave or a resignation does not leave a region without a decision-maker.
Head Office Structure
Separate operations, HR, payroll, billing and compliance responsibilities so each task has an owner, particularly where the owner has been covering several functions.
The deliverables
What You Receive
Depending on the agreed scope, your engagement can include:
- A map of the current chain of command by region and client.
- A proposed structure with levels and reporting lines.
- Span-of-control guidance by site type.
- Role sheets for each field and head-office position.
- An authority matrix for site-level decisions.
- A night and weekend command note.
- A deputy and handover register.
- A client escalation route, drawn as a simple flow.
Step by step
How We Work
Draw What Exists
We interview owners, area managers, officers and a sample of supervisors, and draw the chain as it works in practice.
Test It Against Your Sites
We put the picture against site types, shift patterns and distances, and find where supervision is thin or duplicated.
Propose and Discuss
We suggest a structure and authority limits, and discuss each with you. Where your judgement differs, yours prevails.
Write It Down
We prepare role sheets, an authority matrix and the escalation flow, in language the people on the roster will follow.
Introduce and Review
Before the change we record how decisions travel and how often supervisors visit sites, and we review these after the structure has run for a while.
The difference
Make Decisions Travel Faster Than Phone Calls
A clear structure helps you to:
We do not promise outcomes. We record a baseline before work starts, covering decisions referred upward, night rounds done and supervisor visits per site, and report against it, so you can see what changed and what did not.
- Give each guard a named person to obey and approach.
- Share supervision more evenly across sites.
- Free the owner from decisions that a supervisor can take within limits.
- Keep nights and weekends covered by someone who can decide.
- Handle client conflicts with one agreed route.
- Absorb a resignation without a gap in command.
Find your fit
Who This Service Is For
Agencies Spread Across Many Sites
Hold the structure together as the site count rises.
Owner-Run Security Companies
Delegate in stages without losing control of the contract.
Industrial and Campus Security Providers
Organise large guard strengths under clear supervisors.
Agencies Opening a New Branch or City
Plan the structure for a new region before the first guard is deployed.
Companies Merging or Taking Over Contracts
Fit an incoming team into your reporting lines.
How it usually shows up in security services
Most security agencies grow by adding sites, and the structure follows the contracts rather than a plan. A branch or operations head sits at the top, field officers cover groups of sites, site supervisors run a post or a campus, and guards report to whoever is nearest. In practice, the span of control is uneven. One field officer may be responsible for a handful of nearby sites while another covers a spread of distant ones. Night posts see a supervisor rarely. Decisions on a guard's removal, a swap between sites, overtime or a client complaint are often taken by phone and recorded nowhere. Deputy arrangements are informal, so when a supervisor is on leave, the post runs on goodwill. The result is slow escalation, inconsistent decisions between regions and clients who do not know whom to call.
Common challenges
Where it goes wrong in security services
Spans are uneven
Some field officers can visit every post often, while others cover too many sites to see any properly.
Night posts go unsupervised
The structure is drawn for the day, and those who stand alone through the night are visited least.
Decisions sit on the phone
Removals, swaps and overtime are agreed verbally, with no limit or record.
Deputies are assumed
When a supervisor is away, nobody has been told who holds authority.
A better process
What a working version looks like
- 01
Draw the field line clearly
Guard, senior guard, site supervisor, field officer, area or branch manager, with one reporting line each. The organisation design work sets out the chart and role definitions.
- 02
Set spans by travel and risk
Fix how many posts a field officer covers by distance, shift mix and client sensitivity, not by the next contract that arrives.
- 03
Write an approval matrix
State who may sanction overtime, move a guard between sites, remove someone from a post or commit to a client, and up to what limit.
- 04
Name a deputy for every supervisory role
Record who acts, for what, and for how long, so absence does not leave a site without authority.
- 05
Define the client-facing contact
Give each client one named person and one escalation, so a call at night reaches someone who can act.
What to check this week
- Count the posts each field officer is actually responsible for.
- Ask who visits the night posts, and how often.
- Find the last guard removed from a site and who approved it.
- Check whether each supervisor has a named deputy.
- Ask a client whom they would call at two in the morning.
What this looks like in security services
The parts of organisation design that are specific to this sector, rather than general.
Deployment and Supervision Structure
Field officers, site supervisors and guards.
What this coversHide
Deployment and Supervision Structure
Field officers, site supervisors and guards.
What this coversHide- Organisation structure
- Field officer coverage
- Site supervisor role
- Guard hierarchy
- Span of control
- Reporting and escalation
- Approval matrix
- Staffing per post
Questions on this, in security services
There is no single answer. It depends on whether the posts are in one campus or scattered, how long the shifts run and how much reporting is needed. We work out a range for each site type from your own pattern and test it with your officers.
Usually a named officer on call, with a clear limit to what can be decided and a second contact if the first does not answer. We help you set that out and give the guards one number to remember.
Sometimes, where sites are large and supervision is on the spot. Where posts are scattered, extra layers of field officers are often needed. We show the options and the cost of each before you decide.
The core stays the same, but some clients ask for their own reporting lines or a dedicated site manager. We design a base structure and show how to add client-specific roles without breaking it.
Yes. Reporting lines and approval limits can be configured as workflows on the GullyHR platform or on your own system, so that a request goes to the right person. The design comes first, and the configuration follows it.
We design roles and reporting, not employment terms. Where role changes affect terms of employment, confirm the obligations that apply with a qualified professional. GullyHR does not give legal advice.
It depends on distance, shifts and how sensitive the clients are. Set a number from the visits you want each post to get, then test it against travel time.
Not at every one. Small posts can be grouped under a roving supervisor, but anything round the clock with several guards needs someone accountable on the ground.
Overtime, moving or removing guards, spending on site needs and client commitments. Each line should say who can approve it and when it goes higher.
Give each location a manager with clear authority and a common set of rules, and review them together on a fixed cycle so decisions do not drift apart.
Put a Clear Structure Behind Every Post
If decisions wait for the owner's phone or supervision thins out as you add sites, start with a plain picture of who is responsible for what.
Prefer to talk first? Call +91 80958 58589 or write to hello@gullyhr.com.
Book an Organisation Design Consultation
Tell us about your agency and where decisions get stuck.
The general method — what organisation design covers, the questions it answers and what an engagement produces — is the same whatever the sector, and is set out on the organisation design page. What is above is the part that differs for security services.
Other HR topics for security services
Where to start
Most engagements begin with a review of how this runs in your business today, then a written process and the sequence to implement it.
See all HR topics for security services, or another industry.