GC SurgeDocsAlarm Closure & Audit Trail
2 min read

Alarm Closure & Audit Trail

Alarm closure is the final action that records the handling outcome and releases the workload back to the site. Every closed alarm captures enough information for audit and performance analysis without forcing unnecessary typing. Covers: Alarm Closure, What You Enter at Closure, After Closure.

alarm-closure-tags-descriptions-and-release-01.png

Alarm Closure

alarm-closure-tags-descriptions-and-release-02.png

What You Enter at Closure

  • Closure tag — a label that categorizes the outcome (examples: False Alarm, Resolved, Escalated to Police, Technical Fault). Tags are configurable by admins.
  • Optional description — free text for context the tag alone does not capture.
  • Closure timestamp and operator identity are recorded automatically.

After Closure

The site view updates immediately once an alarm is closed. If the operator releases the site or ends their session, the site becomes available for another operator to take. All alarms remain in their closed state — no work is lost and no alarm is left open.

Managing Closure Tags

Admins configure the available tag set from the Settings area. Tags appear in Analytics breakdowns and audit exports — consistent tags make performance analysis meaningful. Define your tag set before operators start handling alarms. Changing tags mid-deployment creates gaps in historical data.

Audit Trail

Every alarm has a traceable record that follows it from receipt through classification, operator handling, and closure. This trail supports customer trust, internal quality review, and any dispute about whether an alarm was received, shown, or handled on time.

alarm-closure-tags-descriptions-and-release-03.png

The Full Chain

  1. Alarm received from camera.
  2. Normalized — site, camera, tenant, and timestamp attached.
  3. Classified by NOVA99x as real or false (if enabled).
  4. Delivered into the operator monitoring workflow (ZenMode).
  5. Taken by an operator — site ownership timestamp recorded.
  6. Closed, escalated, or forwarded — tag, description, and closure timestamp recorded.

What the Trail Preserves

  • Receipt time and camera source — regardless of downstream delays.
  • Classification result and the basis for the decision.
  • Operator identity and session context at every action.
  • Closure outcome, tag, and any escalation or forwarding events.

Audit Log Guarantees

  • Immutable — audit records cannot be edited or deleted by any user, including admins. Every entry is write-once.
  • Minimum 1-year retention — audit data is retained for at least 12 months. Records older than the retention window are no longer accessible.
  • Searchable and exportable — filter by user, date range, action type, and entity. Export as CSV for compliance or external audit purposes.

The full Audit Logs interface is in the Audit & Compliance section.

GC Surge