The sector decides the security design.
Nine environments, nine different ways of failing — and a deployment built for each.
A guard at a gate is not a security plan.
Identical posts, identical strength — two entirely different things being protected.
Founded by a Military Intelligence veteran of the Indian Army. Reading an environment before committing resources to it is the discipline that produced this company, and it is the reason our sector pages describe exposures rather than services.
The same gate, four different jobs
A plant gate exists to reconcile material against paperwork. An office gate exists to prove who was inside. A hospital entrance exists to limit how many attendants a ward can hold. A residential gate exists to handle four hundred deliveries without a queue. Identical posts, incompatible purposes — and a manning plan copied from one to another will fail quietly in all the ways that matter.
Risk is specific long before it is severe
Sector knowledge is what lets a deployment start from a hypothesis rather than from a blank page. We expect weighbridge exposure on a plant, refund exposure in a store, attendant crowding in a hospital and diesel loss on a project site — so the assessment goes looking, and the post instruction is written against the exposure rather than against a general idea of vigilance.
The wrong temperament is a real failure mode
The person who is right at a scrap gate at two in the morning is often wrong in a hotel lobby or on a paediatric floor. Selection, induction and supervision are set by sector, because a deployment that is technically correct and socially wrong costs a hospital its calm, a hotel its reviews and a school its parents' confidence.
Compliance obligations differ by sector
A logistics client answers to a customer audit, a technology office to a certification assessor, a hospital to an accreditation body, a school to parents and an inspecting authority, and a project to statutory safety reporting. The records a deployment produces are only useful if they are the ones your sector is actually asked for.
Find the environment you are protecting.
Each sector page sets out the threat picture we expect to find, how the deployment is structured against it, and which of our three disciplines does the work.
Operating in something not listed here? Tell us about the site and we will tell you honestly whether we are the right firm for it.
Six questions that turn a sector into a manning plan.
The variables we settle before a single post is proposed.
What is worth taking, and in what unit
A pallet, a laptop, a drum of diesel and a strip of tablets each imply a different route out and a different post. Value that leaves by vehicle is controlled at a gate; value that leaves in a pocket is controlled by process.
Who is entitled to be inside
A closed population with issued credentials is a different problem from a site the public may enter at will. Between those extremes sit the sectors that must admit strangers and still account for them — hospitals, hotels, retail and communities.
When the site is at its weakest
Shift change on a plant, dispersal at a school, the closing routine in a store, a banquet at midnight, the second hour after an adverse clinical outcome. Manning is weighted to those windows rather than spread evenly across the clock.
What a failure actually costs
A production stoppage, a customer-audit finding, a medico-legal notice, a review that outlives the incident, or a call from a parent. The consequence decides how much control is proportionate — and where discretion is worth more than visibility.
Who the officer has to speak to
A transporter, an auditor, a distressed family, a resident committee member, a child or a delivery rider. The interaction defines the selection profile, the language of the induction and the escalation the officer is expected to use instead of confrontation.
What the record has to prove
Reconciliation, access history, visitor accountability, patrol compliance or custody of material. Reporting is designed backwards from the question your sector will eventually be asked to answer.
Sector knowledge is a hypothesis, not a template.
Knowing the sector tells us where to look first. Your site tells us what is actually there — and the manning plan is written from the second, not the first.
Sector baseline
Site reading
Manning plan
Measured review
What happens at each stageClose
- 01
- Sector baseline
- We begin from what the sector reliably produces — the exposures, the pressure hours, the compliance obligations and the temperament the posts demand. It is a hypothesis to be tested on your site, not a template to be imposed on it.
- 02
- Site reading
- The baseline is checked against your ground: your gates, your material movement, your working clock, your existing procedures and the distance between what is written and what happens on the night shift.
- 03
- Manning plan
- Posts, strength, supervision, shift pattern, escalation lines and reporting formats are written down and agreed before induction, so that the deployment can be measured against something rather than judged by impression.
- 04
- Measured review
- Performance is reviewed against that plan on a fixed cycle. Incidents and exceptions feed back into the sector picture, and the plan is corrected on evidence — including where it means reducing a post rather than adding one.
Every site is a sector and an exception.
Tell us the sector, the site and what you believe is going wrong. The scoping conversation costs nothing.
Security. Intelligence. Assurance. — Pan India Presence