Short answer: a useful mobile-security patrol brief should state why the patrol is needed, which areas may be checked, what the officer is authorised to do, which hazards and access restrictions apply, how concerns are escalated and what evidence must be recorded. It should be precise enough to produce consistent visits without publishing patrol times, routes, access codes or other sensitive information.
A mobile patrol can add a visible, recorded security presence to a commercial property, warehouse, construction compound or vacant building. It is not automatically a substitute for a permanently staffed post. The right arrangement depends on the site, operating hours, assessed risks and the decisions a responder may need to make.
Start with the purpose of the patrol
“Patrol the site” is too vague to measure. Begin with the outcome the facilities or property team needs. That might be checking the external condition of a closed building, observing agreed access points, identifying visible signs of damage, confirming that specified doors appear secure, or reporting an unexpected person or vehicle.
Define priorities without describing predictable routes in documents that are widely circulated. The controlled operational brief can identify the authorised checkpoints and access method, while a general service description should avoid revealing the order or timing of visits.
Identify the areas that are in and out of scope
Mark the site boundary and distinguish between public approaches, car parks, yards, external compounds, loading areas and internal spaces. If internal entry is permitted, state which buildings or zones may be entered and which remain out of scope.
Include any physical limits that could affect a safe inspection: locked plant rooms, roof areas, fragile surfaces, unlit ground, live construction zones, moving vehicles, water damage, exposed wiring or locations where two-person attendance is required. The officer should know when to stop, withdraw and escalate rather than improvise.
Separate routine patrols from alarm attendance
A planned patrol and an alarm response are different tasks. The brief should say whether the officer is completing a routine condition check, responding to a specific notification or doing both under separate instructions.
For alarm-related work, identify who receives the activation, who authorises attendance, which alarm zone or device is involved and who can make decisions after the first inspection. Do not assume that every alarm produces police attendance, and do not instruct an officer to place themselves at risk to obtain evidence.
Define what can be checked
A proportionate patrol checklist may cover:
- visible damage to agreed doors, gates, fences or windows;
- signs of forced entry or unauthorised occupation;
- unexpected people, vehicles or deliveries observed from an authorised position;
- specified lighting, alarm or access-control faults that are visible without technical testing;
- obstructions, dumped materials or obvious hazards affecting the agreed patrol area;
- evidence of water ingress, fire, smoke or another urgent condition; and
- whether previously reported defects appear unresolved.
The checklist should not turn a security patrol into a technical inspection. An officer should not be expected to diagnose electrical, fire, lift, alarm or building defects unless that work is separately assigned to a competent person.
Set authority and escalation limits
State what the officer may do after finding a concern. Can they contact an on-call facilities manager, request a contractor, secure an agreed secondary barrier, remain at a safe observation point or call the emergency services when there is immediate danger? Which actions need prior authorisation?
Use primary and backup contacts with role-based responsibilities. A useful escalation matrix deals with unavailable contacts, conflicting instructions and conditions that require the officer to withdraw. It should never place alarm codes, key-safe details or private mobile numbers in a public or broadly shared document.
Address lone-working risks
Mobile patrol work may involve people working without close supervision. The Health and Safety Executive’s lone-working guidance says employers must manage the risks before people work alone; it specifically includes security staff among its examples.
The site brief should support that risk assessment. Record known hazards, communication expectations, welfare considerations, restrictions on entry and the process for missed check-ins or loss of contact. Site owners should provide current information about changes that could affect safe attendance, such as new construction activity, damaged structures or altered vehicle movements.
Check the licence required for the actual duties
The correct SIA licence depends on what the person will actually do, not simply the title used in a proposal. Current Security Industry Authority guidance describes security guarding as guarding premises or property against damage, theft, unauthorised access or disorderly behaviour. Keyholding is a separate licensable activity where the work involves keeping or controlling access to a key or locking device.
Before appointing personnel, organisations can use the official SIA licence-checking service to verify the relevant licence. Procurement checks should also consider supervision, insurance, incident management, lone-working arrangements and how changes to the site brief are controlled.
Specify the patrol record
Reports should be factual, consistent and limited to information needed for the purpose. A useful record may include the date, visit reference, agreed checkpoints completed, observations, faults or damage found, actions taken, people notified and the owner of any follow-up task.
Photographs should have a clear purpose. Avoid unnecessary images of neighbouring properties, passers-by, vehicle registrations or private documents. Where reports contain personal data, the organisation should decide who may access it and how long it is needed. The ICO’s data-minimisation guidance explains that personal data should be adequate, relevant and limited to what is necessary.
Review the brief when the site changes
A patrol brief can become inaccurate after a tenant change, construction phase, altered opening hours, a new gate, alarm work or changes to vehicle movements. Give one person responsibility for maintaining the controlled version and removing obsolete instructions.
For a commercial property in Watford, for example, a new contractor compound may change which boundary can be approached safely and who is authorised to be present outside normal hours. The response is not to add generic checks: update the risk information, authorised areas, contact ownership and reporting requirement for that site.
Practical commissioning checklist
- Define the security outcome and the limits of the service.
- Map authorised areas without publicly exposing routes or times.
- Separate routine patrol instructions from alarm-response instructions.
- Provide current hazards, access restrictions and withdrawal points.
- Set clear authority, escalation and backup-contact rules.
- Confirm the licences needed for the duties actually assigned.
- Use a factual report with proportionate photographs and data retention.
- Review the brief after operational or physical changes to the premises.
Discussing a site-specific patrol brief
ZimCos Security lists mobile patrols and related security services among its current services. The appropriate arrangement depends on the premises, risks, access requirements, operating hours and feasibility. To discuss a commercial property in Watford or another practical nearby location, contact ZimCos Security with the site type and outcome required—without sending access codes, patrol schedules or sensitive key information in the initial enquiry.