Skip to main content

Records and alerts

Logged readings are only useful if you can find them again. SafetyBrik keeps a full history per piece of equipment and surfaces problems on the dashboard the moment they happen.

Where temperature records live​

There are three views of the same data, each suited to a different question.

1. Per-equipment history (the daily view)​

The Temperature history side sheet on the equipment register answers "what has this fridge been doing?". Open it from the graph icon on any row at /safety/temperature-checks.

For each reading you see:

  • When - timestamp in your local time
  • Temp - the value in °C
  • Status - In range, Out of range, or - if the equipment has no range set
  • Source - the name of the checklist it came from, or Manual if logged directly
  • By - who logged it
  • Notes - any free-text added at the time, or the corrective action from a flagged checklist response

This is the view to use during the day, on the floor, with a manager.

2. Records (the reference view)​

The Records page (/safety/records) is where your reference documents live - Safe Methods, Risk Assessments and the COSHH register. It is not where you read individual temperature logs; for that, use the equipment history above or the Reports view below. See Safe Methods for what Records covers.

3. Reports (the audit view)​

For filtered, date-range queries across all equipment - "every out-of-range reading in March", "all readings from the front display chiller this quarter" - use the Reports view. See Reports for the full set of filters and export options.

How readings are stored​

Each reading is one row, with:

  • The equipment it belongs to
  • The timestamp it was taken at (not the time it was entered)
  • The value in °C
  • A computed is_in_range flag, evaluated against the equipment's min and max at the moment the reading is saved
  • A source - either manual or the checklist instance that produced it
  • The user who logged it

Editing the equipment's acceptable range later does not rewrite history. Each reading carries the judgement that applied when it was captured.

Out-of-range alerts​

The dashboard surfaces flagged temperature responses as part of its overall safety status. When a reading is logged out of range:

  • The response on the checklist is marked is_flagged = true
  • The corrective action (if recorded) is stored against the response
  • The dashboard counts it in the safety overview
  • Prove It includes it in the next bundle, with the corrective action attached

There's no separate "alert centre" to babysit - flagged items live with the records they came from, so a reviewer always sees the reading and the response in the same place.

Spot trends, not just one-offs

A single out-of-range reading is usually a stock door left open. Several over a week is a different conversation - probably the equipment. Use Reports to compare last month against this one before calling an engineer.

Exporting records​

For an EHO visit, an insurer query, or a brand audit, head to Prove It. One click bundles every reading, every flagged response, every corrective action and every signed-off checklist for the date range you choose into a single PDF / archive.

For ad-hoc CSV exports of just temperature data, use the Reports view.

Cross-references​