A month without incidents does not, by itself, establish that every part of a security service is working well. More reports do not necessarily mean deterioration either: personnel may be making previously unrecorded problems visible. Managers need to interpret activities and outcomes together. Performance indicators support this assessment, but do not replace knowledge of the site or professional judgement.
Monitor Outcomes and Processes Together
HSE's HSG254 guidance discusses using leading and lagging indicators for process safety. It is not a ready-made KPI list tested specifically for private security. It nevertheless provides a useful management approach: monitor whether important controls are being carried out, as well as counting events that have already occurred. HSE indicator development guidance.
For example, the number of gate faults is outcome information. Reporting a fault to the correct department and communicating interim arrangements to the next shift reflect process quality. Attributing a technical repair delay beyond the security team's control to officer performance, without explanation, produces a poor assessment.
Select a Small Set of Clearly Defined Indicators
For each measure, explain what is counted, where the data comes from and the period covered. Plan changes and justified exceptions should remain visible. The following examples can be adapted to the agreed service:
- Completion of planned duties, with reasons for incomplete tasks.
- Whether sampled handovers include outstanding work and relevant notifications.
- Accuracy of required information in sampled visitor records, without unnecessary data collection.
- Owners, target dates and closure evidence for agreed corrective actions.
- Processes associated with recurring complaints or record errors.
There is no single success percentage suitable for every facility. Targets should reflect the starting position, workload and assignment conditions. Where transaction volumes are low, the report should also explain that one error can change a percentage considerably.
Measuring Speed Must Not Undermine Safe Behaviour
Time to notify someone and time to arrive at an incident are different measures. An average can mislead unless the start point, recipient and incident category are defined. A speed target must not create an expectation that personnel rush unsafely or present incomplete information as certain.
A digital patrol record does not, on its own, prove the quality of an observation. Visiting a checkpoint and reporting its condition correctly are separate matters. Sampling records and discussing actual duties with personnel can help explain what the numbers mean.
Complete the Report with Decisions and Follow-Up
NPSA's security planning guidance emphasises cooperation between the site operator and private security provider, including review of contractual performance. A monthly meeting should therefore cover actions needed from the operator as well as the supplier's report. NPSA security planning guidance.
The meeting should establish priorities, action owners and review dates. When discussing security service scope with Titan Savunma, you can define reporting expectations at the outset. The purpose is to understand how the service operates and make necessary corrections, rather than simply generate more tables.
