Short answer: A useful security shift handover records what changed, what remains unresolved and what the incoming officer must know to work safely. It should cover access changes, incidents, alarm or equipment faults, transferred keys, expected contractors and clear escalation actions—without circulating unnecessary personal data or sensitive security details.

For a facilities manager, the handover is where the written assignment meets the condition of the site at that moment. A generic note such as “all quiet” is rarely enough. The incoming officer needs a concise, factual picture of the site and any action that is still open.

Why does the handover need a consistent format?

Commercial sites change throughout the day. Contractors arrive and leave, doors are taken out of use, deliveries are expected, access lists change and faults are reported. If these points remain only in one person’s memory, the next shift may start with an incomplete brief.

A standard handover format makes important information easier to find and review. It also helps the site manager distinguish a completed action from an unresolved issue. The format should match the assignment: a warehouse, construction compound and multi-tenant office will not need identical fields.

Seven points worth recording

1. Site status and temporary changes: Record closures, restricted areas, temporary barriers, lighting faults or other changes that affect the agreed security task. State who authorised the change and when it should be reviewed.
2. Access and expected visitors: Note authorised contractors, unusual delivery arrangements and expired or withdrawn permissions. Use an approved access list rather than copying unnecessary personal details into a general log.
3. Incidents and observations: Record what was observed, when and where, the action taken and who was informed. Keep the language factual. Separate an observation from an assumption.
4. Alarms, CCTV and communications: Identify faults, isolations or maintenance visits that affect the assignment. The entry should say what has been reported and what interim instruction applies; it should not expose alarm codes or technical details to people who do not need them.
5. Keys, passes and equipment: Confirm controlled items transferred between shifts and record any discrepancy immediately. A count or identifier is more useful than a vague statement that equipment was handed over.
6. Outstanding actions: Give every open issue an owner or escalation contact and a clear next step. “Monitor this” is weaker than stating what should trigger a call and who should receive it.
7. Officer welfare and working arrangements: Record changes that affect safe working, communication or supervision. The Health and Safety Executive’s lone-working guidance specifically includes security staff and says employers must manage health and safety risks before people work alone.

What should stay out of a general handover log?

A handover record should not become a store of access codes, detailed patrol patterns, private contact information or unrelated personal data. Sensitive instructions need controlled storage and access appropriate to their purpose.

If a log contains names, vehicle details or other personal information, the organisation responsible for it should decide why the data is needed, who may see it and how long it should be kept. The ICO’s data-protection principles include data minimisation, accuracy, storage limitation and appropriate security. A longer log is not automatically a better log.

How can a facilities team check the handover process?

Start with a short template that reflects the assignment. Require a time, author and acknowledgement from the incoming officer. Where practical, combine the written record with a brief verbal handover so that questions can be resolved before responsibility changes.

Review a sample of records regularly. Look for repeated vague entries, unresolved faults carried forward without an owner, unexplained key discrepancies and instructions that no longer match the site. Update the assignment when the building, tenant mix, operating hours or access arrangements change.

For licensable private-security work, confirm that the operative holds the correct licence for the activity. GOV.UK provides the official SIA licence-checking service. Licence checking is one procurement control; the site brief, supervision and handover process still need to be appropriate for the job.

A practical commercial-site example

Imagine a commercial property in Watford where a contractor has completed work late in the day. The useful handover is not simply “contractor left”. It records that the contractor signed out, the temporary pass was returned or cancelled, one area remains closed pending inspection, and the facilities contact has been told. The incoming officer can then work from the current position rather than reconstructing it.

The same principle applies to sites elsewhere: record the change, the action already taken and the next authorised step. Avoid publishing client details, routes or predictable timings.

Questions to ask a security provider

• What handover fields are used for this type of site?
• How are urgent issues escalated when the usual contact is unavailable?
• How are keys, passes and equipment accounted for?
• Who reviews the records and closes outstanding actions?
• How are sensitive records stored, accessed and retained?
• When is the handover template revised after a site change?

If you are reviewing guarding arrangements for a commercial, construction or vacant property, explore ZimCos security services or contact ZimCos Security with the site type, location and outcome you need. The team can discuss a suitable brief subject to the site, scope and feasibility.