Skip to main content
Blog·Strategy

Why CCTV review time is the wrong KPI, and what to measure instead

'How long does it take a manager to find a clip?' is the wrong question. The right question is how long until a forward-ready evidence pack is in the right inbox. Two different problems.

SESam Erpik · Co-founder & CTO4 min read

When loss-prevention leaders talk about productivity wins, the metric you hear most often is 'CCTV review time'. The benchmark goes: we used to spend 45 minutes scrubbing through footage to find an incident; now we spend two. The implied story is that the AI made the search faster.

That story is roughly right but operationally incomplete. The interesting question isn't how long a manager takes to find the clip, it's how long from the moment something happens until a forward-ready evidence pack is in the right inbox.

What 'forward-ready' actually requires

A police force won't act on a clip alone. They want context: which camera, what time, who was involved, what happened before and after, and, critically, whether this person has been involved in prior events you can evidence.

A forward-ready pack therefore has three components:

  1. Multi-camera chain, the subject tracked from detection through to exit, with all camera IDs and timestamps logged.
  2. Append-only audit log, every status change since the event was created, with the user, role, and timestamp.
  3. Prior-event linkage, if the face matches one we've seen before, the prior events are attached automatically with their own evidence.
app.quantumeye.io/incidents/IR-0C6F98B4AD34

Incident IR-0C6F98B4AD34

AutoTheftConfirmed

Theft / Shoplifting · Northgate Convenience · 16 May 2026, 12:06

Forward to police →
Suspect
Face redacted
Watchlist match94%
Clip · CAM-04
Clip redacted
Duration00:42
Evidence pack
  • Face capture
  • Clip · 00:42
  • Multi-camera chain · CAM-04 → 06 → 08
  • Prior matches · 2 stores
  • Append-only audit trail
Prior encounters
#QE101 · Riverside09 May
#QE101 · High St02 May
Audit trail
Append-only · tamper-evident
  1. 12:06:14DetectedShoplifting · CAM-04 · concealment
  2. 12:06:22Evidence pack assembledFace, clip and camera chain bundled
  3. 12:11:03ReviewedStore Manager opened the event
  4. 12:11:40ConfirmedWritten to the append-only audit log
  5. 12:12:10Report draftedAwaiting your forward to local force
The output that actually matters: a police-ready incident pack, not hours of footage scrubbed. Illustrative.

Why the KPI matters

Measuring 'CCTV review time' tells you about manager efficiency. Measuring incident-to-forward time tells you about whether you'll actually get a prosecution. The two are correlated but the second one is what your board cares about.

If your incident workflow ends at 'I found the clip,' you're optimising for the wrong step. The clip is an input to a report. The report is what matters.

The QuantumEye take

Our Incident Reporting module assembles the pack the moment an event is confirmed: face, clip, multi-camera chain, audit log, prior matches. The manager reviews, adds context, and one-taps Forward to the local force email. The pre-existing 'find the clip' problem becomes a non-problem because the clip is already attached.

How Incident Reporting works
Detect, review, approve, forward, all audit-logged

Get the monthly brief.

One email a month. The post-of-the-month, the retail-trends summary, and one customer-success snippet. No sales pitches, no event invites. Opt out in one click.