From incident to evidenced, audited, actionable, without the CCTV-review hour.
Police-ready retail incident reporting. Every confirmed event auto-builds a structured incident record, face, clip, prior events, timestamps, reviewer notes, audit chain. Police forward is one outcome. The lifecycle is the product.
The full lifecycle, not just the paperwork.
Most 'police report' tools just generate a PDF. Incident Reporting handles the workflow that comes before, around, and after that PDF, the bit your managers actually live in.
Auto-build the incident record
The moment an event is confirmed, the record assembles: face image, video clip, multi-camera handoff chain, timestamps, confidence scores, attached prior events.
Notes, evidence, multi-party review
Store manager adds context. Regional manager reviews. QE Administrator approves. Every contribution is timestamped and attributed.
One-tap police forward (optional)
Local force email configured per-store. Manager reviews, adds context, taps Forward. The PDF + evidence pack lands in the right inbox.
Detect. Review. Approve. Forward. All logged.
Five steps in the lifecycle. Each one role-gated server-side. Each one written to the append-only audit log. Each one Alex-queryable.
Detection auto-creates the record
Shoplifting Detection, Face Recognition or Safety Events fires, an incident is opened in Pending state. Face, clip and prior events attached automatically.
Human-in-the-loop review
Store Manager marks Confirmed / FalseAlarm / Skipped. Notes added. Multi-party review supported for high-value incidents.
Every action logged, append-only
Detect → review → approve → forward. Each step writes to EventAuditLog. Append-only, defensible in court, defensible against ICO.
21:18, concealment confirmed. Incident record assembled immediately after.
Illustrative scenario. Concealment detected, item recovered, event confirmed. By the time the manager opens the app, the incident is half-built. They add two lines, tap Approve. Optional forward to the local force.
Incident IR-0C6F98B4AD34
AutoTheftConfirmedTheft / Shoplifting · Northgate Convenience · 16 May 2026, 12:06
- ✓Face capture
- ✓Clip · 00:42
- ✓Multi-camera chain · CAM-04 → 06 → 08
- ✓Prior matches · 2 stores
- ✓Append-only audit trail
- 12:06:14DetectedShoplifting · CAM-04 · concealment
- 12:06:22Evidence pack assembledFace, clip and camera chain bundled
- 12:11:03ReviewedStore Manager opened the event
- 12:11:40ConfirmedWritten to the append-only audit log
- 12:12:10Report draftedAwaiting your forward to local force
Pairs well with
Shoplifting Detection
Behaviour-based concealment, grab-and-run and till incidents, flagged on the alert track, not in a CCTV review.
GuardFace Recognition
Whitelist and watchlist matching across your estate. Human-reviewed, GDPR-safe.
GuardAfter-Hours Guard
Zero-touch arming. Night-vision detection. Floodlights, siren, evidence pack, all before the call.
The system writes the draft. The human signs every step.
QuantumEye builds the structure. Every consequential action, confirm, approve, ban, forward, requires explicit human authorisation, with RBAC enforced server-side.
Police forward is admin-only
QE Administrator role required. Server-side enforced. Store Managers can review and prepare, but cannot send.
Every step audited
Confirm, approve, edit, forward, each writes to the append-only audit log. The chain of custody is provable.
Edits preserve the original
If a manager edits the incident before forwarding, the AI-drafted original is preserved. Both versions auditable.
Forwarding records the recipient
The local-force email used, the time of forward, and the user who authorised it are all on the audit chain.
Minutes, not the better part of an hour. Per incident, per store, per estate.
Pilot feedback flags this as one of the bigger time-savers, and one of the bigger reasons managers actually report incidents in the first place.