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. The log captures:

  • Checklists - checklist completed (on the web, the Team App or the kiosk); checklist created, updated or removed; Checklist turned off and Checklist turned back on; out-of-range readings, including readings logged by hand against a piece of equipment
  • Corrective actions - raised, which records the action as done (on the web, the Team App or the kiosk, or for a reading logged on a piece of equipment, naming the equipment), Follow-up added (with its Check again by time), Follow-up closed (with what was found) and updated. See Corrective actions
  • Equipment - added, updated, archived and restored (Equipment archived, Equipment restored), and SwitchBot sensors bound and unbound (SwitchBot sensor bound, SwitchBot sensor unbound, with the reason: Equipment archived, Moved to (equipment) or Replaced by another sensor). Saving an edit that changes nothing, or restoring equipment twice, adds no entry
  • Cleaning - cleaning signed off, a sign-off undone or voided, and cleaning tasks added, updated, archived, restored or deleted (Cleaning task archived, Cleaning task restored)
  • Diary and reviews - diary signed, 4-weekly review completed
  • Prove It - Prove It records added, with the reading, the result and any override reason, and failed checks saved as a pass by an owner or admin (Prove It manager override)
  • Safe methods - answers saved, method completed, marked not relevant, Safe method marked relevant again, reviewed, and pack completed. On a completed method, each answer that changes is logged as Safe method answer changed, with the question, what it said before and what it says now
  • COSHH - chemicals added, updated, archived and restored (Chemical archived, Chemical restored), data sheets updated, and Data sheet acknowledged once for each person recorded as having read a sheet, naming the chemical, the person and the sheet's version
  • Risk assessments - Risk assessment created (naming the template when it was started from one), Risk assessment updated (with what changed, and the hazards added, changed or removed), Risk assessment review started, Risk assessment marked current (with the version, the version it superseded and the next review date) and Risk assessment draft deleted (owners and admins, a draft only, with its title and version)
  • Training records (certificates) - added, renewed, Training record updated (with what changed, for example "What changed: Expiry date changed (was 10 Jan 2029); Notes changed"), Certificate file attached (a file added or replaced on an existing certificate), archived and restored. Archiving or restoring a certificate needs an owner or admin, and the entry (Training record archived or Training record restored) names who did it. Archiving or restoring twice adds one entry
  • Certificate types - Certificate type added, Certificate type updated (with what changed, such as a new name or renewal period, or made inactive or active again), Mandatory certificates changed ("Now mandatory" or "No longer mandatory") and Certificate type removed (saying whether it was deleted or made inactive). Only owners and admins can change certificate types
  • Safe method training - Safe method training logged, Safe method training updated (with what changed, for example "What changed: Training date 1 Oct 2026 to 2 Oct 2026; Notes changed"), and Safe method training archived and Safe method training restored, which need an owner or admin. Each names who did it
  • Labels, complaints and pests - PPDS labels printed (one PPDS label printed line per item per print, with "Copies: 3" for three copies), customer complaints, and pest control events and their reports (Pest report attached, Pest report removed)
  • Suppliers - Supplier added, Supplier updated (with what changed, for example "What changed: Delivery days changed") and Supplier deleted
  • Emergency contacts - Emergency contact added, Emergency contact updated (with what changed, for example "Contact: Camden EHO | Category: Environmental Health Officer | What changed: Applies to changed") and Emergency contact deleted
  • Menu items - Menu item added, Menu item updated (with the allergens before and after, by name) and Menu item archived, including when Promote replaces one with a recipe ("Replaced by recipe: Toasted Teacake (No Butter)")
  • Manual PPDS items - Manual PPDS item added, Manual PPDS item updated (with the allergens before and after) and Manual PPDS item archived
  • Setup imports - documents uploaded for import, and the equipment, cleaning schedules and chemicals imported from them. When an imported cleaning schedule replaces the default cleaning, Default cleaning replaced by an import is recorded as the person who imported it, naming the sites imported for and the cadences it replaced there, how many default tasks and checklists were replaced, and the sites given the default cleaning with its cadences, for example "Imported for: Burford (weekly) | Default tasks replaced: 7 | Default checklists replaced: 1 | Sites given the default cleaning: Witney (weekly), Carterton (weekly)"
  • Opening hours and closed dates - Opening hours changed, Closed date added and Closed date removed, with who did it. A change made in Settings > Locations is noted as changed in Settings, and an hours change lists the open days

For suppliers, emergency contacts, menu items and manual PPDS items, each entry names who did it. Phone numbers, email addresses and the names of the people to contact are never shown: an edit to one only says that it changed, for example "What changed: Phone changed". Saving without a change adds no entry.

Each entry shows:

  • Timestamp - the date and time the action happened, in your local time (for example "6 Oct 2026, 11:00")
  • Action - a plain label such as "Checklist completed" or "Follow-up closed"
  • Site - for businesses with more than one site, where it happened, or All sites for a business-wide record. Entries at a site that has been switched off or removed keep its name, as "Station Road (closed)"
  • Who - the name of the person who did it, System for something SafetyBrik did on a schedule, or Former team member if that person is no longer on file
  • Details - a short description in plain words, for example which checklist, equipment or method it was about, with local dates and times

System events​

Some entries are written by SafetyBrik itself rather than a person: Checklist generated, Checklist overdue, Checklist missed, Checklist not needed (site closed) and Out-of-range sensor reading (a SwitchBot reading outside its range, naming the sensor when it has a name). They are hidden by default, so the log shows what people did. Turn on Show system events to see them too, or choose one of them in the Action filter. The dashboard's Recent activity leaves them out as well.

Filtering and searching​

The filter bar lets you narrow the log down quickly:

  • Date From / Date To - bound the timeframe, by whole days in your local time
  • Action - drill into a single kind of entry, e.g. only "Checklist completed" or only "Follow-up closed". The list covers every kind of record SafetyBrik keeps
  • Show - 25, 50 or 100 entries per page
  • Show system events - include the scheduled entries described above
  • Site - if you run more than one site, switch with the site tabs at the top. Choosing a site shows that site's entries plus the business-wide ones, labelled All sites. A site that has been switched off or removed keeps its own "Station Road (closed)" tab

A Reset button clears all filters in one click.

If there are more entries than fit on a page, use Newer and Older to page through them. If the log can't be loaded, the page says so with Try again.

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 time the checklist was completed and which member of staff completed 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?
  • Which follow-ups are still open, and who closed the last one?
  • Who edited that risk assessment last Thursday?
  • How many checklists did the team complete 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, added, imported, logged and printed events are green
  • Updated, completed, reviewed, signed and renewed events are blue, and so is Follow-up closed
  • Overdue events and Prove It manager override are amber
  • Removed, deleted, voided, undone, missed and out-of-range events are red, and so are Equipment archived and Chemical archived

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.