Security & facilities mobilisation
Good mobilisation starts when security and facilities agree the interfaces.
Before the first shift, security and facilities teams should agree the responsibilities, contacts, information flows and escalation routes that apply to the site. A clear coordination plan makes day-to-day handovers easier and reduces uncertainty when conditions change.
A measured approach
Agree the interface before the first operational handover.
Security and facilities teams often touch the same operating environment but have different responsibilities. A mobilisation conversation should identify who owns site access information, which contacts can make decisions, how changes are shared, what needs to be handed over and how the client wants exceptions raised.
This is a planning framework, not a claim that SSS provides every facilities function. The final division of responsibilities is always agreed through the client’s site plan and service proposal. It can support conversations about Corporate Security, Residential Estate Security, Mobile Patrol or Event Security.
The mobilisation agreement
Four interfaces to make clear and workable.
The purpose is not to create more process. It is to make sure the people involved know what information matters, who can make a decision and how the next person receives the relevant context.
Site and people information
Agree the current site contacts, access arrangements, induction information, relevant areas and how changes are communicated.
Operational continuity
Define the handover items that matter to the agreed security scope and how outstanding actions will be carried forward.
Checks and exceptions
Set the agreed operational priorities, exception route and the information the client wants the security team to record.
Service governance
Agree the regular client/provider discussion where scope, site changes and relevant service evidence can be reviewed.
Responsibility matrix
Use a simple matrix to prevent assumptions.
The table below is a planning prompt. It should be completed for the actual property and proposal, with responsibilities assigned in writing.
| Interface | Agree with the client/facilities team | Confirm in the security site plan |
|---|---|---|
| Site access and induction | Which current site information, contacts and access boundaries are needed before the service begins. | What the security team needs to know for the agreed role and how updates reach it. |
| Handover and contacts | Who can make decisions, who receives exceptions and what handover information must be retained. | How relevant shift or patrol handover information is recorded and escalated. |
| Patrol or coverage priorities | Which areas, times or agreed operational priorities are relevant to the scope. | How the agreed priorities appear in site instructions without publishing sensitive detail. |
| Contractor and visitor interfaces | Which party owns the process and what security-support role, if any, is included. | The boundaries of the agreed security role and the route for exceptions. |
| Defects, incidents and review | Which issues need to reach facilities, the client or another nominated owner. | What will be recorded, how material matters are escalated and when the service is reviewed. |
A four-step mobilisation conversation.
Start with the operating context, agree the interfaces and then preserve the decisions in the site-specific documentation.
Map the contacts
Confirm operational, facilities and client contacts, decision authority and after-hours communication routes.
Share current information
Provide the site information, access boundaries and agreed priorities required for the security scope.
Write the interfaces
Make responsibility, handover, escalation and review expectations explicit in the site plan.
Review after launch
Use the first service review to confirm that the agreed information flow works in practice.
Operational coordination
Security is stronger when the site’s information flow is clear.
SSS can discuss operational records, client reporting, compliance documentation and agreed service visibility through the Application. The exact facilities interface is always confirmed for the specific site and proposal.
Questions answered
Useful answers before you make contact.
These answers are general operational guidance. The final scope should be agreed through a site, event or client-specific discussion.
Does the security provider automatically manage all facilities responsibilities?
No. A security provider’s responsibilities must be agreed in the client-specific service scope. Do not assume ownership of keys, access systems, visitor records, contractor controls, defects or facilities escalation.
What should be agreed at the first mobilisation meeting?
Agree the client and site contacts, operating context, information needed for the security role, handover expectations, exception routes, responsibility boundaries and service-review process.
Can the same framework work for a commercial property and an estate?
The framework can be adapted, but the final responsibilities, access arrangements and operating priorities will differ. It should be completed for the specific site.
Guide notes
Clear guidance. Sound boundaries.
Reviewed 23 September 2026. This page is an SSS mobilisation planning framework. It does not establish a particular facilities, fire, access-control, data-protection or legal responsibility; those matters must be agreed and documented for the site.
SSS Corporate Security Services SSS Residential Estate Security SSS Application
Start with a practical conversation
Set the interfaces before the service starts.
Discuss a corporate, estate or property-security mobilisation with SSS and begin with a clear view of responsibilities and information flow.
Important: This page provides general operational and procurement information. It is not legal, safety, licensing, employment, tax or data-protection advice, and it does not confirm a site, event, person or service as compliant. Agree the final scope through an appropriate client-specific assessment and written service proposal.