Skip to main content

Recording events

Most of what ends up in the diary gets there automatically - checklists, temperature readings, Prove It records and corrective actions all flow in as your team works. This page covers the bits you log by hand, and the design choices behind how SafetyBrik captures them.

Recording an incident or note​

To add a free-text entry:

  1. Open the day in the Daily diary at /safety/diary/:date
  2. Scroll to Incident notes
  3. Type into the notes box - things like "Fridge 2 reading 7.5C at 14:00, food moved to walk-in, engineer called, back in range by 16:30"
  4. Optionally tap Add photo to attach up to five images (a photo of a delivery, a thermometer reading, a damaged box). Photos can be JPEG, PNG or WebP, up to 5 MB; a HEIC photo is refused with "This photo is in HEIC format. Save it as a JPEG and try again." A day holds five photos at most: "A diary day can hold up to 5 photos. Remove one before adding another."
  5. There's no Save button: notes save as you type, sent after a pause or as soon as you click out of the box. The status line under the notes says how saving is going: Saving..., then Saved at 14:32 (the site's time), or Not saved. Retrying... if the connection dropped, with Retry to try straight away. A note that's refused (because the day was signed meanwhile, say) says why, with Discard, and the page shows the day as signed.

Notes written on a kiosk don't go in this box. They show beside it under Notes from the team, read-only: see Notes from the team.

Nothing you type is lost. Your notes are kept on this device until they have saved, so going Back, reloading the page or closing the tab loses nothing. Open the day again on the same device, signed in as the same person in the same business, and what hadn't saved is sent. Notes from an earlier visit that overlap what you have typed since show as "Unsaved changes from an earlier visit", with Use these (they replace yours) and Discard. On a day that has been signed since, unsaved notes show under "These notes weren't saved before this diary was signed off", with Discard, so you can copy them first.

Leaving the diary while your notes haven't saved yet asks Leave this page?, with Leave and Stay, for example "Your latest changes haven't been saved yet. We'll try to send them now, and anything that doesn't get through is sent next time you open this diary." If the device can't keep unsaved changes (some private browsing windows, say), the status line says "Can't keep unsaved changes on this device. Keep this tab open until they're saved." and the leave prompt warns they'll be lost.

Sign off saves exactly what is on screen, notes, ticks and photos included, with the signature (see Sign-off).

Diary photos are private to your business. Brikly opens them through links that work for an hour, and the diary page gets fresh ones each time it refreshes. When an owner or admin removes a photo from a day that hasn't been signed, the file is deleted too, unless another record uses it; when a team member removes one, Brikly keeps the file privately until the account is deleted. A signed day keeps its photos.

Photos count as evidence

A clear photo of a fridge thermometer, a delivery temperature probe, or a damaged carton is worth more in an EHO inspection than a sentence describing it. Use the camera icon on a phone to capture in the moment.

AI suggestions​

If a checklist already flagged something earlier in the day, you can use Generate AI suggestion to draft notes from the activity summary as a starting point. The draft names what each corrective action was for, and mentions a follow-up still open ("follow-up still open, check again by 14:30") or one that was closed ("Follow-up done: back down to 4°C"). An overridden Prove It check is written as "passed (manager override)".

  • Use as starting point saves the suggestion into your notes straight away, below anything you had already written.
  • Check the suggestion against what happened and change anything that isn't right. You may sign it unchanged once you've checked it: what you sign is what goes on the record.
  • When there is nothing to draft from, it says "Nothing to summarise for this day yet." When suggestions can't be made at that moment, it says "Suggestions aren't available right now. Try again later."

Fitness-to-work: logged on exception​

The paper SFBB diary asks every staff member to declare daily that they're fit to work. SafetyBrik does this differently: fitness-to-work is recorded in the diary on exception only, not as a daily ritual.

You log a fitness-to-work entry when something actually changes:

  • A team member calls in sick
  • Someone is sent home mid-shift after reporting symptoms
  • A staff member returns to work after a stomach bug or other notifiable illness
  • Anyone declares an injury or condition that affects their work

This is a deliberate product design choice for two reasons:

  1. Less fatigue, more meaning. Tick-box daily declarations turn into noise within a week. The day someone is genuinely unwell is the day the record needs to be solid - and a week of "I'm fine" entries doesn't help an investigation, but a clear "Sarah went home at 11:30 with vomiting; cleared stations she'd touched; not to return until 48 hours symptom-free" does.
  2. It matches what EHOs actually want. The expectation is that you can show what you did when someone was unwell - which dishes they touched, when they were sent home, when they were cleared to return - not that you have a stack of "I'm well today" tickboxes.

To log a fitness-to-work exception, use the Incident notes box on the day in question. Be specific about who, what, when, and what action was taken (sent home, deep-clean of station, etc.).

StaffBrik absences aren't copied into the diary

If you record absences in StaffBrik, they are not copied into the diary. When someone is off sick with symptoms, log the sickness exclusion and their return-to-work date in Incident notes as well, so the food safety record is complete.

Returning from sickness

The standard rule for foodborne-illness symptoms (vomiting, diarrhoea) is 48 hours symptom-free before returning to food handling. Record both the absence and the return-to-work date so the gap is visible.

Supplier and equipment issues​

Same pattern: type into incident notes with enough detail to reconstruct what happened. Examples:

  • "Delivery from XYZ rejected - chilled goods at 9C on arrival, rebooked for tomorrow"
  • "Walk-in fridge alarm overnight, reading 6C at 07:00, stock checked and within safe time, engineer booked"
  • "Probe thermometer dropped, calibration check failed, replacement in use"

Photos help here too - a picture of the delivery temperature reading or the faulty equipment is hard to argue with later.

How diary entries feed the 4-weekly review and EHO visits​

Diary content isn't an end in itself - it's the raw material for two other things:

  • 4-weekly review. When you open the 4-weekly review, the auto-generated summary counts the period's diary days signed, corrective actions, Prove It records, overdue or missed checklists, checklists signed off (and signed off late), and checklists answered but not signed off. The review then asks you to reflect on patterns: was the period free of problems, with no issue three or more times? Your incident notes are where you find them.
  • EHO visits. The EHO Report Pack prints each day's notes in full and who signed the day, and the photos stay on each day in SafetyBrik to show an inspector. Your Prove It checks are the separate record that shows your safe methods are followed in practice, not just on paper.

In short: a well-kept diary makes both the four-weekly review and an EHO visit much shorter conversations.