Skip to main content

Audit log

The audit log is the read-only timeline of everything that has happened in SafetyBrik. Open it at /safety/audit-log.

If Prove It is the snapshot and Reports is the monthly review, the audit log is the forensic record - who did what, and when. You cannot edit it, you cannot delete entries from it, and that is the point.

What gets logged​

Every meaningful action across SafetyBrik is recorded as an entry. Today the log captures:

  • Equipment - created, updated, deleted
  • Templates (checklists and safe methods) - created, updated, deleted
  • Instances - created and completed
  • Responses - submitted against a checklist
  • Corrective actions - created and resolved

Each entry stores:

  • Timestamp - the date and time the action happened
  • Action type - which of the categories above it falls into
  • Employee - the name of the person who performed the action (or "System" for automated actions)
  • Details - a structured payload describing the change (e.g. which template was edited, which response was submitted)

Filtering and searching​

The filter bar lets you narrow the log down quickly:

  • Date from / Date to - bound the timeframe
  • Action type - drill into a single category, e.g. only "Instance completed" or only "Corrective action resolved"
  • Show - 25, 50 or 100 entries per page
  • Location - if you run multiple sites, switch with the location tabs at the top

A Reset button clears all filters in one click.

If the result set is larger than the page size, a Load more button appends the next batch.

Why the audit log matters​

EHO defence​

If an EHO challenges a record - "this checklist looks like it was filled in after the fact" - the audit log is your evidence. It shows the exact timestamp the response was submitted and which member of staff submitted it. You cannot fake that without leaving traces, and an inspector knows it.

Management oversight​

The audit log is also a management tool. A weekly skim through it answers questions a conventional ops report cannot:

  • Who actually completed the opening checklist on Tuesday?
  • Did anyone delete a corrective action before it was resolved?
  • Who edited that risk assessment last Thursday?
  • How many checklist responses came in across the team this week?

Accountability without surveillance​

Because the log records action-level events rather than continuous activity, it gives you the accountability you need for compliance without crossing into staff monitoring. It only logs the things that matter for food safety and audit.

Action badges​

Entries are colour-coded so you can scan the log quickly:

  • Created events are green
  • Updated and completed events are blue
  • Deleted events are red
  • Resolved events are amber

Retention​

Audit log entries are retained as long as your SafetyBrik tenant is active. You should not need to archive or rotate them yourself - the data sits in the same audit table that an EHO request would draw from, and SafetyBrik does not expose a delete route.

caution

The audit log is read-only by design. There is no edit or delete UI, and there will not be one. If you spot an entry that looks wrong, treat it as a signal to investigate the underlying data, not as something to clean up.