The short answer
Measure security against defined objectives and leading indicators, not only whether crime occurred. A month with no reported incidents could reflect effective controls, low exposure, or poor detection. Start by documenting the problems the program is meant to address and the current baseline.
What to know
Useful measures can include post and shift coverage, patrol completion, report timeliness and accuracy, access exceptions, open-door or gate findings, hazards identified and corrected, alarm response, client-notification time, recurring incident patterns, training completion, supervisor inspections, complaint resolution, and completion of corrective actions. Outcome measures may include changes in documented theft, vandalism, trespassing, safety events, or business disruption, but interpret them with context. More reporting immediately after launch can indicate better visibility rather than worsening conditions.
Review data at an agreed interval with Arrow. Compare actual activity to post orders, identify locations and times driving risk, and decide whether staffing, patrol routes, lighting, cameras, access controls, training, or procedures need adjustment. Record action owners and due dates, then check whether the change worked. Include qualitative feedback from employees, residents, guests, or managers without substituting impressions for evidence. Avoid claims that a guard or camera “guarantees” prevention; security reduces and manages risk. Arrow’s GPS reporting and supervisor checks can contribute evidence if their current functions and review methods are clearly defined.