A useful handover starts with what the next person must do. The history matters, but the unresolved item is what can be lost between shifts.
The idea in view · Planning diagram
Open work should survive the shift boundary
- Current condition
- Action already taken
- Remaining uncertainty
- Next required action
- Incoming owner
- Acknowledgement
Prioritize unfinished work
Start with unresolved safety concerns, unsupported views and actions awaiting a decision. Link to restricted incident records rather than copying footage or sensitive contact information into the handover. Give each item an owner and next action.
Include temporary operating context
List approved maintenance, exceptional deliveries and rule changes with expiry times and zones. Distinguish a planned camera outage from an unexplained loss of video. Remove expired notes so they do not become permanent exceptions.
Confirm receipt
The receiving role should acknowledge the open items and ask about unclear responsibility. Record the handover time and any item that could not be transferred. Escalate a missing recipient through the agreed staffing procedure.
Write for the incoming shift’s first ten minutes
Put open incidents, coverage gaps and time-sensitive exceptions before routine summaries. Reference the restricted source record rather than copying footage or private contact details. Give the receiving person the next action and the evidence needed to find the context. A long narrative can be accurate and still make an urgent item hard to spot.
The PSA training material describes handover and functional checks as parts of monitoring-centre work. Adapt the principle to the actual duties: confirm what is open, what equipment is impaired and who accepts responsibility. If a receiving role is unavailable, use the approved staffing escalation rather than marking the handover complete because a note was left.
Lead with the work the next shift inherits
A handover should begin with open incidents, unavailable views, temporary instructions and actions awaiting acknowledgement. The next person needs to know what they own now, not read the entire previous shift before finding an unresolved duty. Use concise descriptions with controlled evidence references and an explicit next action.
Separate background information from changes that affect current operation. A completed delivery may need no further action, while an unconfirmed repair or temporary camera exclusion may change what the next team can rely on. Record the relevant expiry, owner and decision needed. Do not treat a long activity log as proof that a clear handover occurred; volume can hide the important exception as easily as an empty note.
Reference context: Private Security Authority: monitoring centre training requirements (2018)
Make acceptance of the handover observable
Identify the outgoing and incoming roles, handover period and method used to acknowledge open work. The organization should choose an appropriate process for its service. A sent note is different from confirmation that the receiving role understands and accepts a duty. Keep those facts separate where the distinction matters.
If the incoming role cannot accept a required action, route the issue through the agreed owner instead of leaving it attached to an unavailable person. This is especially important for work crossing a provider and site boundary. An external reviewer may hand an incident to the site's duty manager, while a technical fault remains with IT. One acknowledgement should not silently close both responsibilities.
Keep current instructions and historical logs distinct
Temporary changes should point to the active rulebook version and expiry. Do not require the next shift to search old messages to discover that a delivery route or contact has changed. The handover can highlight the change, but the controlled operating instruction should carry the accepted detail. Retain the historical reference separately for interpretation of earlier events.
Use minimum necessary personal information and store sensitive footage or contact details in approved systems. The handover worksheet can identify roles and evidence references. A good note gives the next person enough context to continue the work without distributing an unrestricted copy of every incident attachment or private contact list. Where information is missing, state the gap and who can resolve it.
A fictional outage that crosses the morning boundary
An overnight camera outage remains unresolved when the day team begins. Local recording status is not yet confirmed, and the technician has not acknowledged a visit. A weak handover says camera issue reported. A useful handover identifies the affected duty, last confirmed working time, evidence available, temporary limitation, technical owner and next required confirmation.
The incoming role acknowledges the open work and knows which site contact owns the temporary arrangement. If the view returns before the technician arrives, the issue still needs the agreed restoration check. The handover should not erase the uncertainty about the gap or assume that a green status means the event path is correct. The record follows the duty through acceptance and verified closure rather than disappearing at shift change.
Make the call
Which items need an explicit receiver?
| Situation | Decision to make | What to ask for |
|---|---|---|
| An incident awaits a site decision | Who owns the follow-up now | Acknowledgement from the incoming role |
| A camera remains unavailable | Who knows the accepted coverage gap | The fault reference and current fallback |
| A temporary rule expires tonight | Who checks normal operation resumes | Expiry, time zone and assigned check |
Before you move on
- List open incidents and coverage gaps first.
- Add temporary conditions with expiry.
- Record receiving-role acknowledgement.
A worksheet you can actually use
Start with the blank sheet. Add one row per item, assign an owner and mark anything unresolved as pending. The completed example shows the level of detail to aim for.
Keep completed security plans private. Use aliases; keep passwords, access codes, personal contacts and footage links in your approved systems.
How to fill the worksheet
- Open item
- Lead with the unresolved condition that affects the next shift, rather than burying it in routine completed activity.
- Restricted reference
- Point to approved incident or technical records without duplicating footage, credentials or private contact lists in the handover.
- Next action
- State what the next owner must do and what evidence or decision will close the work.
- Due time and zone
- Keep the relevant time and zone explicit, distinguishing a planned deadline from an observed completion.
- Receiving role
- Identify the role that can accept the remaining duty and route any authority gap through the agreed owner.
- Acknowledged
- Record actual acceptance where required. Sending a handover note is different from confirming ownership of the action.
A worked example
Fictional handover: a gate camera awaits a lighting repair and a delivery exception expires at 22:00. The incoming duty lead acknowledges both and owns the next checks.
| Open item | Restricted reference | Next action | Due time and zone | Receiving role | Acknowledged |
|---|---|---|---|---|---|
| Gate lighting fault | FAULT-01 | Check installer update | To agree | Duty-B | Pending |
Questions readers bring to this task
What else should you know?
Does every closed incident belong in the handover?
Include the context needed for the incoming work, with links to the full record. Repeating every closed item can obscure the open tasks. Follow the agreed reporting requirements and keep the handover focused on current duties, exceptions and ownership.
Link to this answer ↗What belongs at the top of a handover?
Open work that affects the next shift's decisions: unresolved incidents, unavailable views, temporary scope changes and actions awaiting acceptance. Put routine completed activity later or link to the log. The receiving person should find the current responsibility quickly.
Link to this answer ↗Does a shift handover close an incident?
No. It transfers or confirms ownership of remaining work under the agreed process. The incident closes only when its completion condition is met or an authorized decision records another outcome. Keep the owner, next action and evidence reference with the open item.
Link to this answer ↗How much detail is enough?
Enough for the next authorized person to understand the condition, accepted duty, action already taken, uncertainty and required next step. Link to controlled supporting records instead of copying everything into the handover. Concise does not mean leaving the decision or owner implicit.
Link to this answer ↗Notes & sources
This is a proposed operating template, not a claim about a certified monitoring-centre process.
Reviewed October 27, 2026. The examples and worksheets are planning aids, not customer results or a statement of contracted service.
- Private Security Authority: monitoring centre training requirements (2018)
Historical operational handover context; local licensing requirements need separate review.