We will not show you our clients. We will show you our method.
We do not publish client names, logos or testimonials. We publish the method instead — so you can judge the discipline before anyone shows you a reference.
Security contracts rarely fail on intent.
They fail on the unglamorous parts: who is accountable when something goes wrong, and whether the standard on day four hundred still resembles day one.
Organisations rarely change provider over one dramatic incident. They change because the supervisor stopped coming, because the same question was answered differently at every review, or because the person who understood the site left and nobody replaced that knowledge.
Read the full argumentClose
Intent is almost never the problem. Every provider intends to deploy trained people, supervise them and report honestly. The difference is whether there is a structure that survives the second year — a named accountability line, a written standard for this specific site, and a review cycle that produces correction rather than reassurance.
That is what this page describes. Not what we promise, but what is actually built into an engagement, and what you are entitled to ask us for once it starts.
Six failure modes
Accountability dissolves
Everyone reports upward and nobody owns the outcome. With no named level for each type of failure, escalation is a phone call to whoever answers.
Continuity is never engineered
Site knowledge lives in two or three heads. When they move on, the new team relearns it by repeating corrected mistakes — and you pay for that twice.
The standard drifts quietly
Nothing collapses. Checks shorten, the night round becomes a sign-off, the register is filled at shift end. Drift stays invisible until an incident measures it.
Reporting describes, it does not correct
A monthly report that lists incidents but never closes a finding is administration, not governance. If it changes nothing on the ground, it is theatre.
The handover is the weakest week
Provider changes get rushed to a contract end date, so the site runs unbriefed for a fortnight — exactly when it is most exposed and least observed.
Nobody says the uncomfortable thing
A provider paid by headcount will not tell you a post is unnecessary, or that the loss is probably internal. Candour has to be structural.
There is no logo wall on this page, and there will not be one — not even for our largest clientour largest client.
A security provider that publishes its client list is publishing a target list. The discipline that keeps your site layout and guard strengths out of circulation keeps your name off our website too.
So you are being asked to judge us on method rather than on names. Everything below is what we actually do, in enough detail to be held to it.
Client identities are not published
No client is named in marketing, on this site or in a tender without written permission for that specific use. Where a reference is needed, the client sets the format.
Site information stays with the site
Layouts, post plans, guard strengths, shift timings and key custody are operational security information. They are held under access control and never used as sales collateral.
Findings are the client's property
Audit findings and investigation reports belong to the organisation that commissioned them — never anonymised into a case study or shown to another prospect.
Confidentiality is contractual, not cultural
An NDA is signed before the scoping visit where you want one, and the obligation sits inside the contract. Deployed personnel sign individually at induction.
From the first call to the first review.
Eight stages, each with an output you can hold. The scoping visit carries no charge and no obligation.
Enquiry
Scoping Visit
Proposal
Contracting
Mobilisation
Transition
Steady State
Review
What happens at each stageClose
- 01
- Enquiry
- A short conversation about the site, the concern that prompted the call and the timeline you are working to. If the problem is better solved by something we do not offer, we say so at this stage rather than after a proposal.
- 02
- Scoping Visit
- We walk the site with your team — perimeter, entries, despatch, high-value areas, and the shift that worries you most. There is no charge and no obligation for this visit, and nothing you show us leaves the site with us in identifiable form.
- 03
- Proposal
- A written proposal setting out what we observed, what we recommend, the post-wise deployment or the assignment scope, the commercial basis and what is explicitly excluded. Recommendations are traceable to something we saw.
- 04
- Contracting
- Scope, service levels, reporting formats, escalation levels, notice periods, confidentiality and statutory compliance are agreed in writing before mobilisation. Nothing operational is left to be settled later by custom.
- 05
- Mobilisation
- Selection, verification and site-specific induction of the deployed team, preparation of post instructions and registers, and agreement of the joining date. Where an incumbent is being replaced, the transition plan below governs this stage.
- 06
- Transition
- The first weeks are run as a supervised transition rather than a normal month: heavier supervisory presence, daily contact with your single point of contact, and rapid correction of anything the deployment plan got wrong on paper.
- 07
- Steady State
- The agreed rhythm takes over — shift handovers, occurrence reports, supervisory checks including at night, and a monthly pack that reports performance against the plan rather than merely describing the month.
- 08
- Review
- A formal review with your team on a fixed cycle: open findings, incidents and near misses, deployment changes the site now needs, and anything we think you are paying for that is no longer earning its place.
Consulting and investigation assignments run the same sequence in a shorter form.
Replacing a provider is a project, not a date.
Replacing a provider is the highest-risk fortnight in any security contract, and it is usually run against an end date instead of a plan. We run it as a project.
Site survey and risk readBefore any date is fixed
We survey the site as it is actually being run, not as the existing contract describes it — real post occupancy across shifts, gate and despatch discipline, contractor and vehicle movement, key and asset custody, and the incidents the site has learned to live with.
What exists at the end of this phase
- Observed-state survey covering all shifts, including night
- Gap list separating contractual posts from posts that are actually manned
- Risks that must be covered from the first hour of cutover
Post-wise manning planWith the proposal
Every post is written out individually: location, hours, strength, the specific risk it exists to control, the checks it performs and who supervises it. Posts we believe are unnecessary are named as such, with the reasoning, before you are quoted for them.
What exists at the end of this phase
- Post-wise deployment chart with shift-by-shift strength
- Duty and check schedule against each post
- Supervisory coverage plan, including night supervision
Selection, verification and inductionAhead of the joining date
The deployed team is selected against the plan rather than drawn from whoever is free. Antecedent and address verification is completed before deployment, and induction is built on your site — your layout, your escalation contacts, your emergency procedures — not on a generic classroom module.
What exists at the end of this phase
- Verification records for every person deployed to your site
- Site-specific induction covering layout, procedures and escalation
- Named supervisory and reporting line handed to your point of contact
Documentation and site recordsBefore cutover
Registers, occurrence books, key and material gate-pass records, visitor and contractor systems and post instruction files are prepared in the formats agreed at contracting, so the first shift is not improvising the paperwork that later becomes your evidence.
What exists at the end of this phase
- Post instruction file issued at every post
- Register and reporting formats agreed in writing with your team
- Escalation matrix printed, issued and displayed where it is needed
Parallel runningWhere the incumbent and the site permit it
Wherever the outgoing provider and your management agree to it, our supervisors and a core team run alongside the incumbent before the handover date, so site knowledge transfers by observation rather than by anecdote. Where parallel running is not possible, we compensate with a heavier supervisory presence over the first shifts.
What exists at the end of this phase
- Shift-level familiarisation with the outgoing team where permitted
- Local knowledge captured in writing rather than left with individuals
- Cutover risks identified and covered before the date, not after
Cutover and stabilisationHandover day onward
The changeover is supervised on site, with senior presence across the first shifts and daily contact with your single point of contact. Anything the plan got wrong is corrected in the first days, in writing, rather than absorbed silently into the routine.
What exists at the end of this phase
- Supervised cutover with senior presence across the first shifts
- Daily transition report to your point of contact through stabilisation
- Written close-out of the transition, listing what was changed and why
We will run the same plan in reverse. If you ever leave us, your incoming provider gets survey access, the documentation we built and an orderly handover during the notice period.
A rhythm you can set your calendar by.
The cycles an engagement runs on — each producing a record rather than a reassurance.
Every shift
On the ground- Shift handover taken and recorded, post by post
- Attendance and post occupancy confirmed against the manning plan
- Occurrence book and gate, visitor and material registers maintained live
- Any reportable incident raised to your point of contact immediately
Daily
Supervision- Supervisory check on site, including a check during night hours
- Daily occurrence summary to the client point of contact
- Absentee cover confirmed and relief placed on post within the shift
- Open actions from the previous day carried forward, not closed silently
Weekly
Operations- Operations review of incidents, near misses and register discipline
- Spot checks on post instructions, alertness and turnout
- Refresher briefing to the deployed team on anything that went wrong
- Deployment adjustments proposed in writing where the week showed a gap
Monthly
Client review- Monthly report: performance against the plan, incidents, and open findings
- Statutory compliance pack for the deployed team, with the invoice
- Review meeting with your team, minuted, with owners against each action
- Recommendations for the coming month, including anything to withdraw
Four levels, named at mobilisation.
- L1Site Supervisor / Shift In-Charge
- Day-to-day site matters — post discipline, register queries, access disputes, immediate incident response and first notification.
- Response — Present on site; responds within the shift
- L2Site / Assignment Officer
- Manpower shortfalls, replacement requests, deployment adjustments, repeat incidents and anything L1 has not closed within the shift.
- Response — Same working day
- L3Operations Manager
- Service level failures, disciplinary matters, training gaps, unresolved client complaints and any incident with loss, injury or reputational exposure.
- Response — Within 24 hours
- L4Head of Operations / Director
- Serious incidents, suspected internal involvement, contractual disputes, and any matter the client wishes to raise above the operations line.
- Response — Immediate for serious incidents; otherwise within 48 hours
Escalation levels are roles, not individuals. The names holding each level on your account are issued in writing at mobilisation and reissued whenever they change, so nobody has to find out who to call during an incident.
Six things we need from your side.
An engagement is not a service you can buy and leave alone. These are the things we ask in return — set out now rather than raised in month three.
None of this is a condition of quoting.
A single point of contact
One named person on your side, with a named alternate, who can authorise access, confirm decisions and receive escalations. Engagements that report into a rotating cast of people lose accountability within weeks.
Honesty about past incidents
Previous losses, suspected internal involvement, disputes with the outgoing provider and the incidents that never got written up. We are not there to judge the history — but a threat picture built on a partial account will deploy people against the wrong risk.
Access to see the site as it is
Permission to observe across shifts, including nights and weekends, and to look at areas that are not on the tour. A site walked only at eleven in the morning tells you very little about the site at three.
Authority behind the standard
If a rule applies to visitors, contractors and staff, it has to apply to senior staff as well. Security personnel cannot enforce a standard that your own organisation visibly exempts people from.
Decisions on the findings
Audits and reviews produce recommendations that need an owner and a date on your side. We will keep raising an open finding, but we cannot close one that requires a decision only you can make.
Timely commercial settlement
Deployed personnel are paid monthly regardless of the state of an invoice, and their statutory dues are non-negotiable. Predictable settlement is what allows us to hold wage discipline, and wage discipline is what holds attrition down on your site.
How we would approach it.
Please read this first
The four situations below are illustrative composites written to show how SHADO approaches a category of problem. They are not client case studies. No client, site or location is described, and no outcome figures are claimed — because real findings and real results belong to the organisations that commissioned them and are not published here.
Unexplained scrap and material lossesIndustrial siteIllustrative composite — not a client
The situation
A manufacturing site records stock and scrap variances that do not reconcile. There is no single incident to investigate, no camera footage that shows anything, and a guarding contract that has been in place long enough for everyone to be comfortable with everyone.
How the problem is read
Persistent, low-volume loss with no visible incident is usually a process problem before it is a criminal one. We would read the movement of material rather than the honesty of individuals: weighbridge practice, gate-pass authorisation, scrap segregation and lot custody, vehicle turnaround, and which of those steps is observed by someone who does not benefit from the outcome.
What would be deployed
- A discreet assessment of material movement across all shifts before anything changes on the ground
- Gate, weighbridge and despatch controls rewritten as post instructions with named authorisation levels
- Rotation and supervision changes where familiarity has removed independent observation
- Where evidence justifies it, a separate and formally scoped investigation, run under its own terms
What the client can then see
- A written picture of how material actually leaves the site, step by step
- A control point for every step, with an owner and a check
- Reconciliation exceptions surfaced as they occur rather than at stock count
Visitor and tailgating control that is not holdingCorporate campusIllustrative composite — not a client
The situation
A multi-tenant corporate campus has access control, turnstiles and a visitor management system, and still cannot say with confidence who is inside the building at any given moment. Tailgating is routine, contractor entries bypass the process at peak hours, and senior staff are the most frequent exception.
How the problem is read
This is rarely a technology problem. It is an authority and throughput problem: the process fails at the times of day when it is inconvenient, and it fails for the people least likely to be challenged. We would measure where and when the process breaks before recommending anything that costs money.
What would be deployed
- Observation at peak entry and exit windows, and at contractor and service entries
- Reception and lobby posts briefed and scripted for challenge, with escalation they can actually use
- Visitor, contractor and material entry procedures reworked to be usable at peak throughput
- A policy position agreed with the client that applies to senior staff as it does to everyone else
What the client can then see
- A defensible record of who was in the building and on whose authority
- Exceptions logged as exceptions instead of quietly becoming the norm
- Evidence of where the process is failing, reviewed monthly rather than argued about
Moving from an unsupervised guard contract to a supervised oneResidential communityIllustrative composite — not a client
The situation
A residential community has guards at the gate on a long-standing contract, no supervisory layer, and a managing committee that hears about problems through residents' groups. Entry records are inconsistent, domestic staff and delivery access is informal, and no one can say what the night shift actually does.
How the problem is read
Unsupervised guarding is not cheap security; it is unmeasured security. The first task is not more manpower but a visible standard, a supervisory layer that checks it, and a reporting line to the committee that does not depend on complaints reaching a chat group.
What would be deployed
- Post instructions written for each gate and patrol, appropriate to a residential setting
- A supervisory check schedule that includes night hours, with checks recorded
- Entry procedures for residents, domestic staff, deliveries and contractors that residents can live with
- A written monthly report to the committee, with incidents and open actions
What the client can then see
- A single accountable line for the committee to raise matters through
- Recorded evidence of night-hour supervision rather than assurances
- A monthly account of what happened on site, in writing, to a fixed format
Taking over from an incumbent provider at short noticeWarehousing and logisticsIllustrative composite — not a client
The situation
A distribution centre needs to change provider at the end of a contract term. Site knowledge sits with the outgoing team, peak despatch cannot pause for a handover, and the incoming provider has limited access before the cutover date.
How the problem is read
The risk here is the handover itself. A site is most exposed in the days when the new team does not yet know the layout, the vehicles, the regular faces or the informal routes — and when the outgoing team has little reason to help. That fortnight has to be planned as carefully as the deployment.
What would be deployed
- Observed-state survey across shifts before the joining date, including peak despatch
- Post-wise manning plan and post instruction files ready before cutover, not after
- Parallel running with the outgoing team where it is permitted, and heavier supervision where it is not
- Senior presence across the first shifts, with a daily transition report to the client
What the client can then see
- A written transition plan with dates, owners and outputs before the changeover
- Daily reporting through the stabilisation period rather than silence
- A close-out document stating what was changed during transition and why
The questions buyers ask before they sign.
Contracting, notice, service levels, compliance and references — answered as we actually work, not as a brochure would answer them.
How does a contract with SHADO usually start, and how long does it run?
Engagements start with a written contract covering scope, deployment or assignment detail, service levels, reporting formats, escalation levels, confidentiality and commercial terms. Guarding contracts are commonly written for an initial term of twelve months and continue thereafter unless either side gives notice; consulting and investigation assignments are scoped to a defined deliverable rather than a term. Terms are agreed on the engagement rather than imposed from a standard template, so anything set out here is a starting position, not a limit.
What notice period applies if we want to end the contract?
Our working default is thirty days written notice from either side on a guarding contract, without penalty, and we will support an orderly handover to an incoming provider during that period, including access for their survey and a documented handover. We hold the view that a provider who needs a long lock-in to retain a client has already lost the argument. Where a client requires a different notice period, it is agreed in the contract.
What happens if a person deployed on our site is not suitable?
You can ask for any individual to be replaced without having to build a case for it. Our working standard is that a replacement is arranged within forty-eight hours of a written request, and immediately where there is a serious concern such as a safety issue, an integrity concern or misconduct. The post remains covered throughout, and the reason is recorded on our side so the same mismatch is not repeated.
What service levels do you commit to?
Service levels are written into the contract rather than left to expectation, and they are set against the specific site. The measures we normally propose are: full post coverage against the agreed manning plan, relief placed on post within the same shift where there is an absence, at least one supervisory check per shift including night hours, reportable incidents notified to your point of contact immediately by telephone and confirmed in writing within twenty-four hours, and a monthly report and review with actions and owners. Where a client needs different or tighter measures, they are negotiated before mobilisation, not afterwards.
Who do we call when something goes wrong at two in the morning?
A four-level escalation matrix is issued in writing at mobilisation and displayed on site: site supervisor, site or assignment officer, operations manager, and the head of operations or a director. The levels are roles, and the names holding them on your account are reissued whenever they change. Serious incidents move to the senior levels immediately rather than waiting to work their way up the ladder.
How do you handle statutory and labour compliance?
Private security operations in India are regulated under the Private Security Agencies (Regulation) Act, 2005, and deployed personnel attract obligations under labour and social security legislation including minimum wages, provident fund, employees' state insurance and, where applicable, the Contract Labour (Regulation and Abolition) Act. We deploy under the licensing applicable in the state of deployment and meet the statutory obligations for the personnel we employ. Licence and registration particulars are provided to clients and to tender processes on request, and a compliance pack — wage and statutory payment evidence for the personnel on your site — accompanies the monthly invoice, since as principal employer you may need to evidence it yourself.
What is your position on insurance and liability?
We maintain insurance appropriate to the nature of the engagement, and the cover in force is shared with the client during contracting rather than published here. Liability is defined in the contract, and we will neither ask you to accept a provider who carries none of it nor pretend that a guarding contract transfers all of your risk to us. Where a client requires specific cover or limits for their industry, that is discussed at contracting so it can be arranged before deployment rather than argued after an incident.
How is the engagement priced and invoiced?
Guarding is priced on the agreed post-wise deployment — the strength, hours and skill mix set by the manning plan — with statutory costs shown transparently rather than buried in a single rate. Consulting and investigation assignments are quoted against a defined scope and deliverable. Invoices are raised monthly in arrears with supporting attendance and compliance documentation. Changes to deployment are agreed and priced in writing before they take effect, so nothing appears on an invoice that you have not already seen.
Can you work alongside our existing security team or another provider?
Yes. Consulting and investigation assignments are frequently run over an existing guarding arrangement, including one provided by another firm, and we do not treat that as an opening to displace them. Where we are advising on a site guarded by someone else, the reporting line is to you, the findings go to you, and any recommendation that affects the incumbent is put to you first.
Will you tell us if we are spending money on security we do not need?
Yes, and it is written into how reviews are run — every review includes anything we believe should be reduced or withdrawn. We would rather hold a smaller contract that is correctly deployed than a larger one we cannot defend at an audit. If a post exists because it has always existed, we will say so.
Do you provide client references?
Not as a matter of routine, and never on this website. Where a procurement process genuinely requires a reference, we approach a client whose engagement resembles yours, ask their permission first, and let them decide what they are willing to say and to whom. We will not circulate a client name to win work, and the same protection applies to you once you are a client.
Start with a scoping visit. No charge, no obligation.
Tell us the site, the concern and the timeline. We will walk it and put what we see in writing — contract or no contract.
Security. Intelligence. Assurance. — Pan India Presence