PSF / SS Overview
Some requirements sit beyond what standard security provision is designed to handle. Specialist security brings carefully selected, verified professionals together under a defined scope, clear accountability and a lawful framework.
This page sets out how we distinguish specialist from standard requirements, what the specialist domains involve, and how the work is structured and governed.
PSF / 01 Reading the requirement
Most security needs are well served by standard provision: established procedures, familiar settings and straightforward arrangements. Specialist provision becomes appropriate when the nature, environment or consequences of a requirement exceed what routine arrangements are designed to handle.
The distinction is analytical, not a matter of prestige. Specialist does not mean heavier, more visible or more expensive by default — it means better matched to a requirement that is genuinely unusual.
Table 01 — Comparative profile
| Dimension | Standard provision | Specialist provision |
|---|---|---|
| Nature of requirement | Stable, well understood and largely routine. | Changing, unusual or carrying serious consequences if mishandled. |
| Environment | Familiar premises and predictable settings. | Unfamiliar jurisdictions, multiple sites or significant public exposure. |
| Planning horizon | Established procedures are largely sufficient. | Bespoke planning, advance preparation and considered contingencies. |
| Personnel | General security roles and competences. | Individuals selected for experience specific to the environment and role. |
| Coordination | A single provider with simple reporting. | Several parties, partners or disciplines working to one plan. |
| Confidentiality | Ordinary commercial discretion. | Heightened sensitivity about people, movements or information. |
| Accountability | Standard contractual terms. | A written scope with defined roles, change control and review points. |
PSF / 02 Specialist domains
Specialist engagements draw on some or all of the following domains. Each is defined by what it takes in and what it produces, so that its contribution to the whole is clear.
Translating an assessed requirement into a coherent written plan: objectives, arrangements, roles, communication and contingencies, set out in terms the client and every specialist involved can follow and question.
Structured identification and prioritisation of the risks relevant to a person, organisation or activity, weighing likelihood against consequence so that attention and resources go where they matter most.
Identifying individuals whose experience is specifically relevant to the requirement, then verifying their background and their legal eligibility to undertake that work in the jurisdiction concerned.
A consented review of premises, residences or venues: how they are used, how people arrive and leave, and whether physical, technical and procedural measures are proportionate to the risks identified.
Analysis of destinations, itineraries and traveller profiles, leading to travel plans, briefings and — where lawful and justified — coordinated support through appropriately licensed partners.
Security that fits alongside governance, culture and operations — leadership, premises, visitors, information handling and incident response — aligned with legal, human resources and facilities functions.
Protective arrangements for individuals and families with an assessed requirement, built on advance preparation and discretion, with visible presence used only where it is proportionate and lawful.
Independent advice on complex or sensitive security questions, including second opinions on existing arrangements or other providers’ proposals, with options and trade-offs set out plainly.
Decision-making structures, communication arrangements and practical plans for medical, environmental and security emergencies, tested through facilitated, discussion-based exercises.
Bringing specialists, client teams, venues, licensed partners and other advisers to a single plan, with one accountable lead, agreed reporting lines and changes that are controlled rather than improvised.
PSF / 03 Selection of specialists
Specialist provision is only as sound as the people who deliver it. Selection therefore starts from the requirement, not from a roster: the question is never who happens to be available, but whose experience is genuinely relevant to this environment, this client and this scope.
Experience from former special forces, military, law-enforcement or specialist security careers can bring valuable discipline, planning ability and composure. It is never accepted on reputation alone, and it never carries any current military or government authority into a private engagement.
Fig. 02 — Selection gates
A candidate who does not clear every gate is not engaged for that assignment.
Roles and competences are derived from the assessed requirement and the written scope, before any individual is considered.
Candidates are considered for experience specific to the environment and role, not for general reputation or former titles.
Identity, professional history and references are verified by lawful means before any engagement is confirmed.
Service restrictions, government permissions, licensing and work authorisation are confirmed for the jurisdiction concerned.
Responsibilities, standards of conduct and confidentiality obligations are agreed in writing.
Personnel are briefed on the scope, reporting lines, legal boundaries and the conduct expected of them before delivery.
PSF / 04 Scope & accountability
Specialist work involves more parties and more judgement than routine provision, which makes ambiguity costly. Scope and accountability are written down, agreed and understood by everyone with a role.
Written scopeGoverns every relationship shown
A typical allocation of responsibility. The exact allocation for any engagement is fixed in its written scope.
| Activity | Client | Engagement lead | Specialists | Partners |
|---|---|---|---|---|
| Approving the written scope | Approves | Prepares | — | Consulted where relevant |
| Plans and contingencies | Reviews | Owns | Contribute | Contribute |
| Personnel verification | Informed | Owns | Provide documentation | Confirm local requirements |
| Day-to-day coordination | Informed | Owns | Deliver within role | Deliver within licence |
| Changes to scope | Approves | Proposes | Raise concerns | Consulted |
| Post-engagement review | Participates | Leads | Contribute | Contribute |
PSF / 05 Lawful framework
Private security is regulated differently in every jurisdiction, and specialist engagements often cross more than one. Each layer below is a precondition. It is checked before delivery and revisited whenever circumstances change.
Where a layer cannot be satisfied, the consequence is fixed in advance — so that no one is tempted to improvise around it under pressure.
The activity is legally permitted in every jurisdiction concerned.
If not satisfiedThe engagement, or that element of it, does not proceed.
The organisation and any partner hold the licences and registrations the work requires.
If not satisfiedDelivered through appropriately licensed local partners, or not delivered.
Required approvals, notifications and consents are in place.
If not satisfiedDelivery waits until they are confirmed.
Each individual is authorised to work in the location, with any service restrictions and government permissions satisfied.
If not satisfiedThe individual is not engaged for that assignment.
Identity, professional history and references have been verified by lawful means.
If not satisfiedNo engagement until verification is complete.
Scope, responsibilities, confidentiality and insurance are addressed in writing.
If not satisfiedDelivery does not begin.
PSF / 07 Analyse the requirement