Violation Log

The Violation Log is the complete audit trail of every safety alert Lokawatch has detected. Use it to review incidents, take action on open alerts, and export records for compliance reporting.

Understanding Alert Statuses

Every alert in Lokawatch has one of three statuses:

Status Meaning
Pending A new alert that has not yet been reviewed by a Safety Officer. Requires action.
Acknowledged A Safety Officer has reviewed the alert and confirmed it as a real incident. It has been logged and actioned.
False Alarm A Safety Officer reviewed the alert and determined the AI detection was incorrect — no real violation occurred. These are used to calculate the False Alarm Rate on the dashboard.

Filtering Alerts

The top of the Violation Log page has four filter controls:

Filter Options
Search Free-text search across camera name, location, and rule name
Camera Filter to alerts from a specific camera
Severity Critical, High, Medium, Low
Status All, Pending, Acknowledged, False Alarm

At the start of each shift, filter by Status → Pending to see only unreviewed alerts that need your attention.

Reviewing an Alert

Click any row in the table to open the violation detail modal. The modal shows:

  • Snapshot — the frame captured at the moment of detection, with timestamp overlay
  • Camera name — which camera captured the violation
  • Site and Location — where the camera is placed
  • Rule Violated — the safety rule that was breached
  • Severity — how serious the violation is (Critical / High / Medium / Low)
  • Timestamp — exact date and time of detection

Acknowledging an Alert

When you have reviewed an alert and confirmed it is a real violation that has been or is being addressed:

1

Open the violation detail

Click the alert row to open the detail modal.

2

Click Acknowledge

Tap the teal Acknowledge button. The alert status immediately changes to "Acknowledged" and the button is replaced with a green confirmation indicator.

Acknowledging an alert records the time of acknowledgement and your user identity. This creates an audit trail for compliance purposes.

Marking an Alert as False Alarm

If you review an alert and determine the AI made an incorrect detection — for example, a reflection triggered the "no helmet" rule, or a shadow was classified as a person in a restricted zone:

1

Open the violation detail

Click the alert row to open the detail modal.

2

Click False Alarm

Tap the False Alarm button. The alert is marked accordingly and its status changes to "False Alarm".

False alarms are counted in the False Alarm Rate statistic on the main dashboard. A consistently high false alarm rate is a signal to adjust your detection sensitivity.

Both Acknowledge and False Alarm actions are permanent — they cannot be undone from the dashboard. Contact your system administrator if an alert was incorrectly actioned.

Exporting to CSV

Click the Export CSV button (top-right of the filter bar) to download the currently filtered view as a CSV file. The export respects all active filters — if you have filtered to "Pending" alerts from Camera A, only those records will be exported.

The CSV includes: Timestamp, Camera, Site, Location, Rule, Severity, Status.

Use CSV exports for:

  • Monthly HSE compliance reports
  • Incident documentation for insurance or audits
  • Offline analysis in Excel or Google Sheets

Talk to Our Team

Tell us about your operation — we'll respond within 1 business day.