ICO guidance on CCTV for organisations<\/a><\/p>\nWork out whether another resource would suit the job better<\/h3>\n
Compare the proposal with a staffed entrance, mobile visits, a monitored camera and a keyholding or alarm-response arrangement. Each control answers a different question. A staffed entrance can help manage regular arrivals. A mobile visit can provide a time-stamped observation at agreed locations. Monitoring can help triage a signal remotely. Attendance can be arranged for a site that needs a person to observe and report after a trigger. Where you use several services, write down who hands responsibility to whom.<\/p>\n
For a small fenced worksite with limited overnight access, ask how much of the requirement is a closing check and how much is attendance in response to exceptions. For an estate with open routes and several occupants, ask whether the safest dog patrol area is small enough that it should be only one part of the plan. A site that depends on continuous gate control should ask how the patrol can leave the gate and who takes responsibility while it is away.<\/p>\n
A useful comparison asks each provider to respond to the same two or three incidents from your records. How would a late arrival be handled? What would be reported if a boundary check could only be made from a distance? How would staff handle a missed check-in? Compare the answers with your staffing, response arrangements and tolerance for gaps. This gives a more useful basis for choosing cover than asking how many hours appear on the rota.<\/p>\n
Consider doing nothing new until the basics work<\/h3>\n
Some clients discover during the walk-through that the security gap sits in a repair backlog or a handover problem. If you correct those issues, the evidence for an additional patrol may change. Document the decision and set a date to review it. A site moving from demolition into a different stage may need a different approach once new access points open or the asset profile changes.<\/p>\n
Where the project proceeds with a trial, set a short review period that captures representative shifts. If ordinary weekday work and weekend shutdowns are different, include both in the review. Decide in advance what evidence would lead to continuing, changing or ending the trial. A record of the decision helps future project staff understand which risks were considered and which arrangements they inherited.<\/p>\n
Write a brief that the night team can use<\/h2>\nBuild the brief around actions and decisions<\/h3>\n
A useful brief has two audiences. The project team needs to understand the scope of the service and who owns the risk. The duty team needs to know what to do at the point of uncertainty. Use a short operating version for shifts and keep the contract and detailed assessments available for review. A handler standing outside on a wet night should be able to find the current contact, the location name and the applicable instruction without searching several documents.<\/p>\n
Start with the purpose, the hours, the areas covered and the areas excluded. Identify the site representative and the role that can authorise changes after hours. Then describe how the team checks in, reports routine work and escalates concerns. Give directions for the first arrival on site and the last handover off site. Put sensitive details in an access-controlled annex. If a printed copy is needed for a control point, agree where it is stored and how outdated copies are removed from use.<\/p>\n
Use instructions that state what to observe and what decision follows. \u201cCheck the agreed boundary and report visible changes against the handover note\u201d is easier to apply than \u201csecure the perimeter at all times\u201d. \u201cIf a route is blocked, report the location and ask the control room to log an exception\u201d gives a way to handle a familiar problem. Where the handler may decide that conditions are unsafe, state how that decision reaches the client and which alternative arrangements may be considered.<\/p>\n
Give common locations names people can recognise<\/h3>\n
Use labels that the day team, control room, handler and emergency responders can understand. A gate described informally as the old yard entrance may have a different name in the contractor\u2019s plan. A contact who reads a report from home needs enough information to locate the issue without recognising a nickname. Match the labels on the restricted drawing and in the reporting system. Where a location could be confused with a similar one, agree a short and distinct name.<\/p>\n
Update labels when the site changes. A temporary gate may become the main delivery entrance for a week and later disappear. If the incident log retains the old label for historical records, add a clear cross-reference for the new one. When calling for emergency help, use the recognised site address and the location details responders need. Ask who can meet responders at an agreed safe point if the handler is occupied.<\/p>\n
Keep the public address and the operational map in their appropriate channels. A quotation or email may travel further than the project team expects. The initial brief can identify the site and the scope for discussion. A separate approved channel can carry access information and a current layout when the recipients need them. The same care applies to end-of-shift photographs and reports that show layout changes.<\/p>\n
Write a sequence for normal, exceptional and urgent events<\/h3>\n
A routine check can be reported through the agreed log. An exception such as a blocked route or a missed check may need a quicker notification if the affected area is important. An urgent event, such as someone at immediate risk, needs the emergency procedure. Define what belongs in each category for this site and who receives the report. Include examples from actual operating conditions so the categories are usable on the first shift.<\/p>\n
An exception report should contain enough detail for the recipient to choose a next action. Say where it happened, when it was seen, what could safely be established and what the team did. Identify whether someone has already been told and whether the affected area is still out of service. The follow-up can document whether a repair is planned or whether another control will cover the gap. Keep speculation out of the initial record.<\/p>\n
An emergency procedure needs a clear path when the first contact cannot answer. Agree who takes over, how emergency services can reach the site and where people should wait or withdraw. Cover fire alarms and evacuation as well as security incidents. The handler may need to get the dog to a safe place and support communications from there. Ask the client and provider to check how their plans fit together, including at shared premises.<\/p>\n
Make the end-of-shift report useful to the day team<\/h3>\n
Choose a format that the next shift can read quickly. Routine observations can be concise, with exceptions at the top. For each outstanding issue, state who owns the next action and when it is due. A manager who begins work hours after an event should be able to see what has already been done. Where a report includes personal information, keep it to the information needed and distribute it through the approved channel.<\/p>\n
Compare two sample entries. \u201cSide area missed\u201d tells the reader very little. A better entry records the agreed location label, time, the obstruction, the check that was safely possible and who received the notification. It can also give the time the matter will be reviewed. That structure helps the client understand whether a coverage gap remained and how often it recurs. It also helps the provider show that the handler followed the agreed route-change procedure.<\/p>\n
Ask the provider for a sample report early in procurement. Have the site team try to use it to brief a colleague who did not see the event. If the recipient must ask several questions to understand the record, adjust the fields before the service starts. Keep the form short enough that it will be completed reliably while allowing space for exceptions. Review it after the first week to see where instructions were interpreted differently.<\/p>\n
Coordinate authorised arrivals and public-facing work<\/h2>\nAccount for the work that continues after closing<\/h3>\n
\u201cSite closed\u201d can mean that most work has ended while a cleaning team, lift engineer or finishing contractor remains. Ask each contractor to identify when staff are expected to leave and who signs them out. During an out-of-hours permit, establish how the handler can check whether someone has access without asking the person to produce more information than needed. Agree whether the control room or the site contact is the source of truth for last-minute changes.<\/p>\n
A practical arrangement might use a duty list held at a control point and a short message to confirm a changed arrival time. Identify who can update it and how a relief handler will receive the change. If an incoming worker cannot be verified, the plan should say where they can wait safely and whom they can contact. If a verified worker needs access through the patrol area, coordinate the crossing and separation before the worker enters.<\/p>\n
Check how shift changes affect the list. A night contractor may finish just as a delivery is due, when the duty team is already preparing a handover. Allow enough time for the handler and control point to confirm what changed, which routes are open and who remains on site. A small set of named checks can prevent conflicting instructions from being passed between shifts.<\/p>\n
Separate delivery work from patrol movements<\/h3>\n
Use the site\u2019s traffic arrangements to identify suitable access and a safe waiting point. Agree how the gate team will tell the handler about an early lorry, a reversing movement or a change in unloading location. The dog team needs a route and a safe place to pause during the movement. Ask the person who manages logistics whether the plan also covers short-notice collections and vehicles that arrive at the wrong entrance.<\/p>\n
When the site uses a shared delivery yard, clarify whose instructions apply to drivers who are attending another premises. A handler working for one occupier should know when to refer the issue to the estate manager. If a contractor makes a change that affects a shared route, coordinate through the person responsible for the common area. Record the agreed operating periods and how they are reviewed.<\/p>\n
Consider how the plan works when the expected person is absent. A security team should know whether a delivery may wait until a site representative arrives and which areas stay clear in the meantime. The control room can record the arrival time, who was contacted and whether access was confirmed. The aim is to preserve a safe arrival process even when the schedule has slipped.<\/p>\n
Protect the transition at opening time<\/h3>\n
A patrol can become unsuitable quickly when the first shift starts. Early workers may assemble at the gate, traffic flows may change, and other contractors may unlock routes that were previously closed. Set a clear transition point and state who calls it. Agree where the handler and dog will be while the site reopens, how any checks that run late will be reported and who takes responsibility once day operations resume.<\/p>\n
Include last-minute changes in the morning handover. If an overnight event closed an entrance, the first arriving workers need a safe alternative. If a welfare issue meant some locations could not be checked, the site team needs to know which ones require a daylight inspection. If a late worker is still on site, verify that their work has been handed over to the relevant supervisor. The morning transition is a practical test of whether the brief is understood across teams.<\/p>\n
On a project with neighbours or other occupiers, the same timing can affect them. A residential entrance may become busy before site work begins. A yard may be used by another company earlier than expected. Ask the relevant people how their routines vary through the week. The patrol window should fit the actual operating pattern, with room for holiday and weekend exceptions.<\/p>\n
Prepare a consistent way to handle questions or complaints<\/h3>\n
Give the control point a concise explanation it can offer about the service and an appropriate contact for follow-up. A neighbour who reports barking or a person who is anxious about passing the site should be able to reach someone who can respond. Record the concern, the time and the location, and follow the client\u2019s procedure for handling personal information. The response should give the person a practical next step without exposing details of the patrol.<\/p>\n
Review recurring concerns with the site and provider. The pattern may suggest a change in timing, a different resting location or a problem with access arrangements. Check observations against the shift records and talk to the relevant occupier. A complaint can show that part of the operating plan relies on an assumption that no longer holds.<\/p>\n
Where the team works close to homes, discuss ordinary noise as part of mobilisation. Consider transport movements, radios, gates and the dog\u2019s rest arrangements. Agree what the handler should do if the location becomes unsuitable. Ask who has authority to change the plan and how a revised instruction will reach each shift. A reliable feedback process can address a local concern before it becomes a repeated disruption.<\/p>\n
Plan the response before the first incident<\/h2>\nDecide who observes, who verifies and who acts<\/h3>\n
A useful patrol observation answers what can be seen safely. An unusual noise, a gate left ajar or a light in a room may have several explanations. Set the reporting threshold and agree the role of the control room. The person who receives the observation can compare it with authorised activity, alarm records or camera footage and decide who needs to respond. The handover should distinguish what was observed from what is suspected.<\/p>\n
The handler should have a defined safe position and communication route for uncertain situations. The brief should state when to withdraw, whom to call and when urgent help is needed. Agree how the provider will continue covering the site if the dog team must step away. A suitable response may include waiting in a secure place, arranging a separate resource or having the client defer an inspection until safe access is available.<\/p>\n
A named decision-maker is particularly valuable when a temporary repair or closure is needed. The control room may record the incident and notify the client, while the client arranges a contractor. If a damaged section borders a public area, the people responsible for safety may need to take immediate action to manage the boundary. Keep roles clear before the shift begins so the report is acted on.<\/p>\n
Rehearse a boundary defect, an unverified visitor and a missed check-in<\/h3>\n
Use three short exercises rather than a long presentation. In the first, the handler sees damage at an agreed location and cannot tell whether it is recent. The control room records the observation and checks for related activity. The site contact decides how to manage the area and authorise repairs. The exercise finishes when each participant knows who will check that the repair has been completed.<\/p>\n
In the second, a person arrives and says a supervisor has authorised access. The team follows the agreed verification route, keeping the person at a safe location if possible. The exercise tests what happens when the named supervisor cannot be reached, and whether the person has a way to contact their employer or wait safely. It also tests how a different occupier\u2019s visitor will be treated in a shared yard.<\/p>\n
In the third, the expected check-in is missed. The control room follows the agreed sequence, tries the designated communication channels and escalates as required. Test the procedure with a relief operator who may be unfamiliar with the site. Ask what information the operator needs to identify the team, the last known location and the next contact. Make any missing information easy to find while protecting access to it.<\/p>\n
Prepare for a change that affects several teams at once<\/h3>\n
A water leak, power outage or road closure can affect the patrol, CCTV coverage and the expected delivery route at the same time. The emergency procedure should make it clear who sets priorities for the site. The security team can report conditions and follow its instructions. The site team can coordinate with people responsible for safety, building services and access. The control room can keep a shared record as the situation changes.<\/p>\n
Discuss what can happen during a change of shift. A contractor arriving in response to a fault may need instructions from a manager who is about to go off duty. Agree which role remains responsible until the next person acknowledges the handover. Document any gates, routes or communications that are temporarily unavailable. If the incident changes the scope of coverage, ask who will decide when the normal plan can resume.<\/p>\n
One way to test the arrangement is to give the same scenario to the project manager and the overnight control room. Ask them to explain what they would do first and who makes the next decision. Compare the answers with the actual contact list and response agreements. Write the agreed decision path into the brief using language the relief team can follow.<\/p>\n
Keep a record that can support follow-up<\/h3>\n
An incident note should preserve the sequence of events. Record local time, location, observations, relevant communications and any immediate change in coverage. Where appropriate, refer to a separate record for photos or footage rather than distributing copies widely. Keep the original record available to the people who need it for review. Mark later information as a separate update so a reader can distinguish what was known at the time.<\/p>\n
Make a practical decision about what evidence is needed. A maintenance defect may require a location and a brief description. A serious incident may require a longer account and a defined process for handling evidence. Where other businesses share the site, decide what each should receive and who is authorised to share it. The provider and client should agree how they will correct errors in a report without obscuring the original entry.<\/p>\n
Ask for a consistent format even if the site uses a mix of security resources. A camera operator and a handler may record different observations about the same incident. Shared time references and location labels make those records easier to compare. A final note can record who closed the matter and whether a change was made to the site plan, the staffing or the agreed procedure.<\/p>\n
Build a practical mobilisation plan<\/h2>\nTwo weeks out, settle the scope and decision-makers<\/h3>\n
Start with the expected dates, the hours, the reason for the service and the people who can make decisions. If the work is short notice, compress the timetable while preserving the essential checks. Arrange a visit that includes the provider\u2019s operational representative and someone who can answer questions about the site after hours. Identify any separate landlord, managing agent or principal contractor approval that affects access to the relevant areas.<\/p>\n
Agree what information the provider needs before it can assess the job. A current layout, normal opening and closing times, legitimate late activity and any recent changes will usually help. Share specific access arrangements through an appropriate channel at the right point. Ask the provider how it will select a suitable team and what it needs from the site for welfare, parking and communications.<\/p>\n
Give the client and provider a single place to record open decisions. A missed agreement about a parking space can delay a start just as effectively as an unresolved licence check. Separate decisions needed before deployment from information that can be reviewed during the trial. Confirm who can authorise a change when the normal decision-maker is away.<\/p>\n
A few days out, test access and communications<\/h3>\n
Arrange a visit during conditions similar to the proposed shift. Test the duty telephone or radio where the handler will need to use it. Check that routes are accessible during the agreed periods and that someone can respond if they become unavailable. Review lighting, traffic and welfare locations. Make sure warning notices and instructions are in place as applicable before any deployment begins.<\/p>\n
Ask the provider to demonstrate how a shift starts and how a replacement handler is briefed. Follow the process as if it were the first night. Verify that the contact list identifies roles and out-of-hours routes, including what happens if the primary contact is unavailable. Where access involves more than one occupier, have each party confirm how its staff and contractors should move through the site.<\/p>\n
Check how the team will record an exception. A report that cannot be submitted because the site has poor coverage or the relief team lacks access to an app needs an agreed alternative. Set out when a call should be made and when an entry can be made later. Keep a way to cross-reference a telephone notification with the written record once the system is available.<\/p>\n
On the first night, verify the arrangement in operation<\/h3>\n
Start with a handover that covers changes since the walk-through, people still on site and any new restrictions. Check the duty team\u2019s contact route early in the shift. The provider can confirm that the deployed team is suitable and briefed. The client can confirm the site conditions, access and any permit restrictions. If an essential condition is missing, decide how to cover the site while it is resolved.<\/p>\n
Look at what is happening in the first hours. Does the report identify the right site areas? Did a late arrival reach the correct point? Could the control room contact the handler when needed? Did work that was meant to have ended continue into the patrol window? Record practical issues and share the changes with the next shift. Keep the team informed if a route or instruction is revised.<\/p>\n
After the first handover, ask the site representative what they could act on. If the report was clear but the next steps were unclear, the issue may sit in the escalation arrangements. If staff had to rely on a private message to learn of a change, establish how that change will be shared with relief personnel. Small adjustments are easier to make early, when the agreed process is still being established.<\/p>\n
Before relief cover, check that instructions transfer<\/h3>\n
Have a relief handler or supervisor read the brief and explain how the shift would start. Ask about a route closure and an unexpected visitor. Check whether they can find the current layout, the safe waiting point and the escalation contacts without asking someone who was present at mobilisation. If the knowledge sits with one person, use this exercise to capture what needs to be written down.<\/p>\n
The client should know which personnel changes require notice and which records will be checked. The provider can confirm that the relief team meets the relevant requirements and understands the deployment. If a replacement cannot work to the same plan, agree an alternative with the client before the shift. A report should show when temporary cover differed from the normal arrangement so it can be considered during review.<\/p>\n
Test the same transfer on the client side. A new site manager may inherit an established patrol without knowing why certain areas are excluded or why a particular contact is needed overnight. A short record of decisions and open actions can save them repeating the original assessment. Update that record when a site phase or responsibility changes.<\/p>\n
Compare three London worksite scenarios<\/h2>\nA live construction project beside an active pavement<\/h3>\n
Imagine a building project that occupies a corner plot with scaffolding, changing hoarding and an entrance used for deliveries. The pavement outside remains busy after the site closes. A late concrete operation can move the normal closing time, and a neighbouring business still takes deliveries from the same street. The client is concerned about damage to temporary boundaries and wants someone to check conditions after the last site departure.<\/p>\n
The assessment starts at the change of use between day and night. The delivery lead explains where people queue and where traffic marshals stand. The site manager identifies sections of hoarding that are likely to move. The handler supervisor checks whether a route can stay inside the private compound and clear of vehicle movements. Together they identify an internal observation point for the entrance. Where the layout prevents a direct check, the team records the limitation and agrees a different source of information.<\/p>\n
The site decides that the gate team will remain responsible until the last planned vehicle leaves. The patrol will then work within the private area until the opening handover. An engineer sometimes works late, so the site manager assigns a duty role to confirm when that person is present. The brief includes an alternative if the route is unavailable following an unusual delivery. If an approved area has to be left unchecked, the report shows the reason and when it can be reviewed.<\/p>\n
A first-week review finds that traffic movement was handled safely, but a planned closing time was routinely being recorded before the last person had left. The project moves the patrol start to a confirmed handover instead of relying solely on the programme. It also asks the logistics lead to update the next week\u2019s late-work plan. The patrol gives the site a better record of after-hours conditions, while the client resolves the timing problem through its own procedures.<\/p>\n
Consider how this scenario changes when a new entrance opens. The person overseeing the works should confirm which route is in use, whether warning notices are visible as applicable and whether the patrol plan still separates people from the dog team. The control room should receive the revised location label and know when the old instruction ends. Ask whether the day team and emergency responders have the same understanding of the entrance.<\/p>\n
A phased refurbishment in an occupied building<\/h3>\n
Imagine an office refurbishment near a transport hub. Several floors remain occupied, the building manager operates a shared reception and some contractors work evenings. The client wants to check a private storage area and yard after the works close. People using the office and cleaners have separate routes, but some movement crosses the yard. On some evenings the facilities team also receives an engineer for building maintenance.<\/p>\n
The client maps three kinds of area. There are places where the project can control access, areas where the building manager retains responsibility and routes used by other occupiers. The inspection checks doors, lifts and stairs from the perspective of someone who has never been to the building. A person can follow a familiar route without knowing they have crossed from the building\u2019s common space into the project\u2019s zone. The plan needs physical and operational separation that works even when somebody makes a wrong turn.<\/p>\n
In this example, the approved route is confined to a controlled external area for an agreed period. The reception team holds the legitimate visitor information and keeps responsibility for the occupied part of the building. The handler receives a clear point of contact for any movement through the yard. If a building service call requires access, the patrol pauses while that movement is coordinated. The control room records the period during which the route could not be used.<\/p>\n
At the first review, the building manager finds that a cleaning contractor starts earlier on Fridays. The schedule changes to keep that route available. The client also asks for a concise report on handover gaps rather than a list of all ordinary movements. This lets the building manager resolve the recurring issue without expanding routine reporting to information about people who have no bearing on the patrol.<\/p>\n
A future phase may put more work in a shared corridor and less in the private yard. If that changes the purpose of the service, the client can review whether the same deployment still fits. A different combination of reception cover, monitoring and scheduled checks may suit the next phase. The decision is based on the layout and duties the night team will actually encounter.<\/p>\n
A mixed-use yard with irregular vehicle movements<\/h3>\n
Imagine a west London estate where a workshop, a small warehouse and a contractor\u2019s compound share a vehicle entrance. The contractor keeps equipment in a fenced area. Workshop staff sometimes finish late, and the warehouse can receive an early collection. The client wants a better picture of what happens around its own boundary after closing, while the estate manager needs the common routes to remain available.<\/p>\n
At the joint walk-through, the parties compare their records and discover that the names used for the gates are inconsistent. The client\u2019s staff refer to a location by the former tenant\u2019s name. The estate manager uses a numbered plan. The provider agrees to use the estate\u2019s labels in the restricted brief and records which locations are the client\u2019s responsibility. The control room can now report a change without sending someone to the wrong area.<\/p>\n
The proposed patrol uses only the client\u2019s private areas. Vehicle movements in the common yard are managed through the existing estate arrangement. The handler can report a condition that affects the client\u2019s site and refer issues in shared areas to the right contact. An agreed safe waiting point lets legitimate visitors reach someone while the team verifies access. Responsibility for admission is documented rather than left to whoever is nearest the gate.<\/p>\n
The client\u2019s first reports show several interruptions from vehicle movements. Each one was handled safely, but the interruptions reduce useful coverage. The estate adjusts the timing of one collection, and the provider proposes a different sequence inside the client\u2019s boundary. The client agrees a short follow-up review. If the same problem continues, a different control may be more effective at the relevant times.<\/p>\n
There is also an insurance consideration. If the client\u2019s policy or contract mentions a condition relating to security, the client should ask its broker or insurer how the wording applies to the proposed model. A provider\u2019s visit report may help demonstrate what happened during a shift. The client needs separate confirmation of what evidence is required and how it must be retained.<\/p>\n
What changes across the three scenarios<\/h3>\n
All three clients need a defined purpose, a way to control public and authorised access, and a route for the handler to report concerns. The operating details differ. The live build has a boundary that moves. The refurbishment has people using the building long after construction work ends. The mixed-use yard has more than one party with responsibility for access and traffic. Each client should make decisions based on those conditions.<\/p>\n
Use the scenarios to test your own assumptions. Ask which part of your site looks clear on a drawing but is ambiguous in use. Identify a task you expect the handler to do while something else is happening. Check whether a person with authority to act will be reachable throughout the shift. The answers often reveal where the contract needs specific instructions and where the site needs to improve an existing control.<\/p>\n
Brief and compare potential providers<\/h2>\nAsk the same questions of every provider<\/h3>\n
A clear request for a proposal gives each provider the same information about the purpose, hours, coverage, legitimate access and constraints. Say what is still provisional, especially if the layout or the start date may change. Ask the provider to explain assumptions and exclusions in its response. A proposal that assumes nobody will be on site after closing is difficult to compare with one that includes a process for recurring late access.<\/p>\n
Include the outcomes you want to see rather than a detailed prescription for work the provider needs to assess. Ask which parts of the proposed route appear suitable and what would need further examination. Ask what alternatives the provider would propose if parts of the site were unsuitable. A credible proposal can explain how its team will work with the existing control room, gate team and site supervisors.<\/p>\n
Ask for a sample shift report, a sample exception report and a description of the escalation process. The reports can be anonymised and should avoid details from someone else\u2019s site. Compare how easy each report is to interpret and how clearly it distinguishes a planned check, a completed check and an exception. Ask whether the format changes when a replacement team attends.<\/p>\n
Find out who will attend and who will supervise them<\/h3>\n
Ask who employs or supplies the team, how substitutions are arranged and who has operational responsibility during the shift. If a subcontractor may attend, understand how the main provider checks competence, licence requirements, insurance and the site brief. Agree what notice the client receives when the personnel or operating arrangements change. The night manager should know whom to call regardless of how the service is supplied.<\/p>\n
Check how the provider assesses a team\u2019s suitability for a new environment. Ask what experience is relevant to your site, including work near traffic, occupied premises or other contractors. The provider can explain how it verifies that an individual handler and dog are ready for the assignment. Request evidence that relates to the proposed duties and deployment. Keep the records needed for procurement and avoid collecting personal information beyond the purpose.<\/p>\n
Ask how the provider supports a handler who raises a concern. A team that needs to stop a patrol should have someone available to help agree the next step. Identify who can arrange cover if the problem affects the rest of the shift. Ask for a recent anonymised example of how the provider handled a site change or an operational restriction. The aim is to understand how the process works when the proposed plan can no longer be followed.<\/p>\n
Review insurance and contractual requirements<\/h3>\n
Ask for current evidence of the insurance relevant to the work, then check the named entities, activity, terms and any applicable conditions with the appropriate people. If the service includes subcontractors or the use of shared areas, ask how that arrangement is reflected. A certificate can be a starting point. A person responsible for the contract or the relevant insurer can help confirm what documentation is needed for this particular deployment.<\/p>\n
Compare the contract with the brief. The scope should explain which hours and areas the price covers, how relief cover works and what happens when the site requests a change. Ask whether the quoted model includes control room support, reports and mobilisation. Confirm how call-outs or work outside the agreed scope are authorised. A clear change process can prevent confusion during a live incident.<\/p>\n
If the project has specific obligations to an insurer, client or landlord, record who has checked them and what evidence will be retained. Ask for an agreed record of attendance or completed checks where the wording requires it. The provider should know which records matter before service begins. The client can then review the first reports against the requirement while any adjustment is still straightforward.<\/p>\n
Compare the full cost of workable coverage<\/h3>\n
Compare quotations against the same service assumptions. An hourly rate tells you little about the arrangements for handover, supervision or replacement. Check which hours attract different charges, what happens if a shift is extended, and whether mobilisation or additional attendance is included. Ask providers to state where their pricing depends on the site supplying facilities or taking responsibility for another task.<\/p>\n
A useful comparison includes how often the team can safely perform the checks you need and how quickly exceptions can reach someone who can act. A lower-cost option may fit when the requirement is a defined visit and the site already has a suitable alarm arrangement. If the requirement is simultaneous gate coverage and checks elsewhere, a different staffing model may be needed. Evaluate each quotation against the work it can actually deliver.<\/p>\n
Consider the costs the client will retain. These may include maintaining barriers, providing safe access, resourcing a gate function or making an out-of-hours decision-maker available. A proposal can be clear about what it provides while relying on assumptions about what the site will do. Bring those assumptions into the comparison. The budget should reflect the arrangements required for the service to operate safely.<\/p>\n
Agree how to change or end the service<\/h3>\n
A project can move into a less exposed phase, change its boundaries or extend work into the night. Agree when the scope will be reviewed and how the client can request a change. Ask what notice is needed, how temporary changes are confirmed and when the price will be revisited. The provider should be able to identify a named contact who can agree changes with the client.<\/p>\n
Agree how to close the arrangement when it ends. Identify who receives the final reports, how access is returned or cancelled and which information will be retained. If another provider or a different control will take over, set a clear handover time. Review open defects and unresolved access issues before ending the existing coverage. Confirm who owns those matters from that point onwards.<\/p>\n
Where the purpose of the service is tied to a project phase, put that trigger in the plan. It might be a change in occupation, completion of a permanent boundary or an adjustment to work hours. The review date should arrive before the change takes effect so the client has time to decide what is needed next.<\/p>\n
Keep a useful record without collecting too much<\/h2>\nSeparate routine attendance from incident evidence<\/h3>\n
Most shifts need a straightforward record of attendance and checks. Incident evidence may require a different level of detail and access. Ask who owns each record, where it will be stored and who can receive it. This is particularly important where multiple contractors, a separate control room and an estate manager may all receive notifications. A shared situation does not automatically require everyone to have the full report.<\/p>\n
Agree how photos are handled. An image of a damaged barrier can help the site team locate the issue and organise repairs. The same image may also show a person, a registration number or details of the site layout. Ask what needs to be photographed and which channel is appropriate for sharing it. Set expectations for records taken on site equipment and for reports created on a provider\u2019s system.<\/p>\n
Give records consistent times and location labels. If the site uses automatic events from a monitoring system, check whether the local time display aligns with the shift log. A routine review may only need broad timing, but an incident review can be harder when systems use different references. Ask the provider how it handles corrections if a time or location was recorded incorrectly.<\/p>\n
Give clients a report they can use without wide distribution<\/h3>\n
Send a short operational summary to the people who need to act. Detailed records can remain accessible to appropriate staff for follow-up. A maintenance lead may need to know that a barrier requires repair, while the incident lead may need information about observations, contacts and related footage. Agree how to link the records without copying the same details into several messages.<\/p>\n
Set an appropriate retention approach for the types of records used. The relevant period depends on the purpose, requirements and circumstances. Determine who can make decisions about retention and how records are managed if an incident, complaint or claim needs investigation. Apply the agreed process to copies held by the provider and the client as appropriate.<\/p>\n
Decide how new authorised users will receive access and how access will be removed when someone changes role. A new project supervisor should know where to find the latest brief. Someone who leaves the project should no longer receive overnight records without a reason. Review shared distribution lists as part of handover. Practical arrangements of this sort are easier to maintain when responsibilities are named.<\/p>\n
Review reporting when the site changes<\/h3>\n
A temporary incident form can become a permanent process by habit. During the first month, ask which fields have helped someone make a decision. Remove redundant steps where the responsible people agree. Add a field if a recurring issue is being recorded inconsistently, such as which route was unavailable or what time a repair was requested. Keep the form usable on an ordinary shift.<\/p>\n
Look for recurring differences between what clients ask for and what the handler can see safely. A report may refer to an area observed from a distance. If the client treats that as a full inspection, the report needs clearer language. Ask the provider to describe the observation point and any limits on what could be seen. Use those records to decide whether another inspection method is needed.<\/p>\n
An efficient reporting process makes it easier to spot operational changes over time. It helps the day team distinguish one unusual night from a recurring pattern. It also gives the provider a clear basis for discussing a revised route, schedule or method. The process earns its place when it leads to decisions that someone can carry out.<\/p>\n
Review the first month against the original problem<\/h2>\nUse the first week to check that the plan works<\/h3>\n
The first week should establish whether the shift can run as described. Check that the team can reach the agreed areas, communicate reliably, report what it sees and hand over changes. Include quieter and busier shifts where they differ. Ask the handler supervisor what assumptions turned out to be wrong. A blocked approach, late cleaning work or an unusable welfare location may show up more quickly in conversation than in a summary of patrol totals.<\/p>\n
Look at what the client did with the reports. Were urgent issues received by someone who could act? Did unresolved defects reach the person responsible for repairs? Did the day team know what to check when it arrived? The answer can reveal a weakness in the surrounding process even when the patrol itself ran to plan. Record any changes to the contacts or reporting format and tell the relief team.<\/p>\n
Ask the provider to identify any welfare or safety issue that affected the work. A shift can be well managed even when a patrol has to stop or use an agreed alternative. The review should acknowledge whether the response was appropriate and whether the fallback maintained enough coverage for the client. The aim is to make exceptions visible and manageable.<\/p>\n
Compare measures that describe the service<\/h3>\n
Begin with a small group of measures. Look at shifts covered, checks completed as agreed, significant exceptions, time to notify the right person and time for the client to close outstanding defects. Add a measure for repeated gaps if access changes often. The provider can help define how each is counted. Make sure the client and provider agree which events appear in each measure.<\/p>\n
Use counts with their context. Five reported defects might show that a new patrol is finding problems that went unrecorded. They could also reflect five reports about the same damaged barrier. The fix depends on whether the conditions are improving and how quickly reported defects are resolved. An increase in reports soon after introducing a service may reflect better visibility into existing problems.<\/p>\n
A quiet month is useful evidence about what was observed, but it is not enough to prove the patrol prevented incidents. Look at changes in the site phase, operating hours and other controls before drawing conclusions. Use the measures to choose the next practical action. A report showing fewer missed checks after a route change is stronger evidence about the operation of that route than an unsupported claim about overall deterrence.<\/p>\n
Check that the reporting has enough detail to support decisions<\/h3>\n
Pick a few real exceptions and follow them through the record. Find the first observation, who received it, what decision was made and how the matter was closed. If the sequence cannot be reconstructed, decide whether the reporting format needs a change. A missing timestamp may matter for one type of incident and be irrelevant for another. Focus on the details that help resolve the problem.<\/p>\n
Ask whether the next shift had enough information to avoid repeating a check that was unsafe or pointless. If a blocked route stayed in the instructions for several shifts, identify who should have issued a revised plan. If a temporary route caused complaints, review its effect on other users. The monthly meeting can assign a change owner and set an effective date for the revision.<\/p>\n
Use the same process for concerns raised by the team. If the handler reported a welfare problem, check the response and how any alternative coverage was arranged. If a worker reported an access issue, check whether they could reach the relevant contact. A complete review looks at whether the arrangement remains workable for everyone affected by it.<\/p>\n
Decide what to keep, change or stop<\/h3>\n
At the first monthly review, return to the one-sentence purpose. The client may find that the original concern is better understood, that the site has moved on or that an assumption about the need for cover was mistaken. Use the current evidence to decide whether the deployment should continue. Agree the specific changes if the service needs to be altered, along with who will make them and when they take effect.<\/p>\n
A useful review can have several outcomes. The client may continue the patrol while fixing a handover issue. It may reduce the hours because another control now covers the early evening. It may reassign part of the brief to a separate gate team. It may suspend the route until a safe alternative is agreed. Document the reason so people joining later understand the basis for the decision.<\/p>\n
If the arrangement will continue, agree when it will next be reviewed and what changes should prompt an earlier discussion. The site programme, tenancy arrangements or the condition of the boundary can all change the assumptions that supported the original plan. Establish who can raise a review and what information they need to provide.<\/p>\n