Skip to main content

Burglaries queue

When a control-room operator confirms an event as a burglary in CleverCommand, a permanent burglary case opens (with a case number like BC-00042) and lands here — the Burglaries tab of the Review Queue. The tab has two views, switched at the top with a Live cases / Vault control (each shows its case count): Live cases is the working queue described on this page — cases arrive while details are still being captured, move through review, and leave when a manager signs them off; Vault is the permanent archive of every case ever opened — see Burglary Vault.

Burglary cases are deliberately separate from the main Queue tab — they are a compliance record with their own lifecycle, not a Brain suggestion you resolve or snooze.

Advanced Alarm Handling module

Confirmed-burglary casework is part of the Advanced Alarm Handling module, same as the rest of the Review Queue. Operators only see the Confirm burglary action in CleverCommand when the module is on.

Case lifecycle​

Every case moves through four stages:

  1. Capturing details — freshly confirmed. The operator (and you) can still add the OB number, SAPS CAS number, police details, narrative and photos. The case shows how much time is left in the capture window (72 hours by default), which is how long the case stays reachable from the CleverCommand events board after the event closes.
  2. Awaiting review — someone pressed Submit for review; the case is ready for a manager.
  3. In review — a manager pressed Start review and is working through the file.
  4. Reviewed — signed off with an outcome. The case locks and lives permanently in the Burglary Vault.

Cases can never be deleted — a wrong confirmation is corrected at review time by signing it off as Reclassified — false alarm, and every change along the way is written to an append-only activity log on the case.

The queue​

The Live cases view opens with a hero count of cases in progress and stage chips (Capturing details, Awaiting review, In review). Below that:

  • Stage switch — Needs attention (everything not yet signed off, the default), Capturing, Awaiting review, In review.
  • Search — case number, site, OB number, CAS number, confirming operator or event number.

Each row shows the case number and event, the site, when and by whom it was confirmed, the captured police refs (OB / CAS chips — or not captured if still missing), the evidence count (with responder photos broken out), the remaining capture window, and the stage.

Click any row to open the case file.

The case file​

The case drawer is the full record for one burglary:

  • Police & official record — OB number, SAPS CAS number, police station, investigating officer, officer contact, when police arrived on scene, insurance reference.
  • Incident details — point of entry, items taken, damage, suspect description, and the narrative.
  • Evidence — every photo and document on the case. Alarm images from the event and photos the responder took on scene attach automatically; anyone can add more with Add photo or document. Evidence bytes are archived into a private storage vault (the archived badge) so they outlive the original links; removing an item needs a reason and is only a soft-remove — it stays in the audit trail.
  • Responder reports — the incident report(s) filed from the CleverResponder app, with their forced-entry / property-damage flags, notes and photos.
  • Dispatch history — which units rolled, when they arrived, response times.
  • Review & sign-off — see below.
  • Activity log — the append-only trail: who opened the case, every field change (as a field-level diff), evidence added or removed, submission, review and sign-off.
  • Frozen event snapshot — a copy of the event, site, dispatches and responder reports captured the moment the case was opened. Live event rows are pruned from the platform over time; this snapshot is the permanent record.

All details stay editable until the case is signed off. Print case file produces a print-ready case file (police record, incident details, evidence photos, responder reports, dispatch history and the activity log) for hand-over to SAPS, insurers or auditors.

Reviewing and signing off​

  1. Open the case and press Start review (or work straight from Awaiting review).
  2. Check the details, evidence and responder reports; fix or complete anything still missing.
  3. In Review & sign-off, choose the outcome:
    • Confirmed burglary — the classification stands.
    • Reclassified — false alarm — the confirmation was wrong.
    • Inconclusive — could not be established either way.
  4. Add optional review notes and press Sign off case.

Signing off locks the case and moves it to the Burglary Vault. If something arrives later (for example the CAS number only comes through the next week), open the case in the vault and press Reopen case — a reason is required, the previous sign-off is preserved in the activity log, and the capture window re-opens.

Where cases come from​

Operators confirm burglaries in CleverCommand — from the event detail page while handling the event, or within the capture window after it closed (via the Burglary casework rail on the events board). See the CleverCommand guide: Event Details → Confirming a burglary.

The Review Queue nav badge includes burglary cases that are not yet signed off, alongside the regular review items.