Reports
Reports is where you make the EHO Report Pack - the single PDF you hand to an inspector, or that you review yourself once a month. Open it at /safety/reports. Choose the dates and the site, check the preview of what the pack holds, then download the PDF.
EHO Report Pack
Choose Start date and End date (the last 90 days to start with) and a site, then click Download PDF. SafetyBrik compiles a single document with these sections, in this order:
- Cover and Summary - the site, the period, what the registers and training show (see Which dates each section covers) and when the pack was made. The summary counts checklists signed off, signed off late (every signed-off checklist whose last answer came after its deadline, whenever it was signed off), answered but not signed off, missed and still open, those not needed because the site was closed, the completion rate, the temperature readings, the out-of-range readings (from checklists, readings logged by hand and SwitchBot sensors, each counted once), corrective actions, safe methods completed, equipment registered, chemicals registered and risk assessments
- Safe Methods - each site's pack, with when and by whom each method was completed, the reason for any marked not relevant, the last review and your answers to each method's questions (see Safe methods)
- Daily Diary - a weekly grid of each day's notes, printed in full, and who signed the day (see Daily diary)
- 4-Weekly Reviews - each signed review in full, with each action's follow-ups, any additional details and who signed it (see 4-weekly reviews)
- Prove It Records - your cooking, chilling, hot-holding and probe calibration checks, with who recorded each one (see Prove It records)
- Temperature Log - every reading in the period (see Temperature log)
- Checklist Completion Log - every checklist in the period with when it was done (Done at), who did it (Done by) and its status (see Checklist completion log)
- Corrective Actions recorded in the period, with who recorded each one and any follow-up (see Corrective actions)
- Equipment Register - each piece of equipment, its type and its limits (see Equipment and COSHH)
- COSHH Chemical Register - each chemical, what it is used for, the PPE, whether its data sheet is on file and who has read it
- Cleaning Schedule and the Cleaning Sign-off Log (see Cleaning schedule and sign-offs)
- Risk Assessments - each current assessment, with every hazard in full and each further action's follow-ups (see Risk assessments)
- Safe Method Training, Overdue Refreshers and Staff Training Records (see Staff training)
- Suppliers' List and Emergency Contacts (see Suppliers and emergency contacts)
- Customer Complaints and Pest Control Events dated in the period, and any voided in it (see Complaints and pest control)
- Follow-ups - every follow-up opened, closed or voided in the period, whatever it came from, with who it is for, when it is due and how it stands (see Follow-ups)
- Still open from before this period - follow-ups opened before the pack's first day and still open, pest control and complaint follow-ups among them (see Still open from before this period)
Every section is printed. One with nothing in it keeps its heading and says so in one line, for example "No chemicals are on file." or "No pest control events were logged in this period.", so an inspector can see it was looked at.
Throughout the pack:
- Every "who" is a name - who signed the diary and the reviews, who recorded a Prove It check, a reading or a corrective action, who did a checklist, who completed and reviewed a safe method, who signed off or voided a cleaning task, who reviewed a risk assessment, who read a COSHH data sheet, who logged or voided a complaint or a pest event, and who a follow-up is for and who closed or voided it. Someone no longer on file is named as "Former team member". Empty cells print as "-".
- Records made on a kiosk say which tablet - a checklist reading, a corrective action, a checklist's "done by" and a cleaning sign-off made on a kiosk print the person's name followed by "on" and the tablet, for example "Sam Taylor on Burford tablet". The tablet's current name is used, so a renamed tablet shows its new name on old records. Records made on the web or the Team App show the name alone.
- Text is printed in full, never cut short, with its line breaks kept. A long entry carries on to the next page.
- Names and notes with accents, and Greek or Cyrillic letters, print as typed, for example Łukasz or Ştefan.
This is the artefact most EHOs want to see, packaged the way they expect to read it.
Which dates each section covers
- Dated records keep strictly to the pack's dates, in local days: diary days, Prove It checks, temperature readings, checklists, corrective actions (by when they were recorded), cleaning sign-offs, customer complaints, pest control events and follow-ups (by when they were opened, closed or voided). A diary day, checklist, complaint or pest event is always its own site's day. A complaint or pest event voided within the pack's dates is included too, whatever its own date. Times (Prove It checks, readings, corrective actions and sign-offs) are judged in the site's time zone, or in your business's own time zone for a pack covering all sites. A 4-weekly review is the one exception: it is included when its 28-day period overlaps the pack's dates, or when it was signed within them.
- Registers show what is on file on the day you make the pack, because they keep no history: safe methods (with your answers), equipment, COSHH, risk assessments, the cleaning schedule, suppliers and emergency contacts.
- Training is shown as at the pack's last day (or today, for a pack that ends later): who was on your staff that day, the certificates they held and the training they had done by then, and which refreshers were overdue.
The cover says this in one line. For a pack that ends today it reads "Registers and training are shown as on file today, 7 Oct 2026." For a past period it reads, for example, "Registers (safe methods, equipment, COSHH, risk assessments, cleaning schedule, suppliers, emergency contacts) are shown as on file on 7 Oct 2026, the day this pack was made. Training is shown as at 30 Sep 2026."
Anything logged before the pack's first day that is still open is not left out: it has its own section at the end, judged on the day you make the pack.
Safe methods
The Safe Methods section is always printed, one block per site, in the SFBB order: Cross-contamination, Cleaning, Chilling, Cooking, Management.
- The count - completed out of the methods that apply, for example "21/21 completed (6 not relevant)". Methods marked not relevant are left out of the count.
- Pack completed - for example "Pack completed 12 Sep 2026 by Ann Lee.", once every method is completed or marked not relevant.
- The register - every method with its Section, Safe method, Status (Completed, In progress, Not started or Not relevant), Completed (for example "12 Sep 2026 by Ann Lee"), Last review (for example "3 Oct 2026 by Sam Taylor") and Next review. A next review date that has passed reads, for example, "1 Oct 2026, overdue" in red.
- Not relevant - a method marked not relevant shows "Not relevant:" with the reason you gave ("Not relevant: no reason given" if you left it blank).
- Your answers - after the register, under "Answers as recorded on 7 Oct 2026" (the day the pack is made), each completed or in-progress method is printed with its title, section and status, then each question with your answer: Yes, No or what you typed, in full. An unanswered question reads "Not answered" in red. The last review's notes follow, for example "Last review notes, 3 Oct 2026 by Sam Taylor". Methods not started have no answers to print.
A site that hasn't started its safe methods pack prints "Safe Methods pack not started for Carterton." In an all-sites pack each site you run has its own block under its name, with the count in its heading, for example "Burford: 21/21 completed (6 not relevant)".
Daily diary
The diary prints one grid per week, with a column for each day and rows for the date, the day's Notes, the opening and closing checks and Signed by. Each week is printed with its heading on one page; a very long week carries on to the next page.
- Notes are printed in full, with their line breaks. A very long day carries on to the next page.
- Notes from the team - notes added on a kiosk are printed in the same cell, under the day's own notes, each on its own line with the time (site time), the author and the tablet, for example "09:40 Sam Taylor on Burford tablet: Delivery late". See Notes from the team. Every day with team notes prints them, including a closed day.
- Signed by names who signed the day and when, for example "Signed by Sam Taylor, 7 Oct" (the date it was signed, which can be later than the diary day). An unsigned day reads "Not signed" in red.
- A day the site had checklists but no diary (SafetyBrik makes each day's diary during the morning, so this can be today, or a day whose diary was never made or was removed) prints its date and "No diary", with no checks and no signature. Like the Diary overview, the safety score and the reminder, the pack doesn't treat it as an unsigned day.
- A day the site was closed prints "Closed" (with the reason, for example "Closed: Christmas Day") and "Not needed", also for a site that was closed for the whole period.
- A day in the pack's dates with no checklists, or an unsigned day whose checklists were removed, prints "No checklists" (with any note saved on it) and "Not needed", and isn't an unsigned day.
- Days outside the pack's dates, and days still to come (other than a day the site is closed), are blank ("-"). A week with no checklists, no diary and no closed day at the site isn't printed.
4-weekly reviews
Each signed review is printed in full when its 28-day period overlaps the pack's dates, or when it was signed within them. So a review signed a few days after its period ended still appears in the pack for the month it covers. Each review shows:
- its period (and its site, in an all-sites pack)
- the summary counts for the period: Checklists signed off, Signed off late and Answered, not signed off (a review signed before these were counted apart keeps Checklists completed and Completed late)
- every question, the answer (Yes, No, N/A or Not answered) and the action plan, with the questions the review was started with (a review started before the questions were reworded prints its original 13)
- the observed-problems question and its answer, for a review with the reworded questions ("Was this period free of problems, with no issue in the diary 3 times or more? No")
- any problems observed and the actions taken
- under each action (an action plan, or what was done about the observed problems), its follow-ups, as they stand on the day the pack is made (see Actions and their follow-ups)
- the Additional details, if any
- who signed it and when, for example "Signed by Olive Owner on 5 Oct 2026"
Prove It records
The Prove It section starts with a summary line, for example "Total records: 12 | Failed: 1 | Last passed probe calibration: 28 Sep 2026", worked out as of the pack's last day. With no passed calibration it reads "None on record". A failed calibration never counts as the last calibration. In an all-sites pack each site has its own last passed calibration, for example "28 Sep 2026 (Burford); None on record (Witney)".
Each row has the date and time, the site (in an all-sites pack), the category, what was proved, a Reading column (for example "76°C", "Ice 0.2°C, boiling 99.8°C" or "72°C to 7°C in 85 min (3 readings)"), the result and Recorded by, the person's name. The result is Pass, Fail (in red) or Pass (manager override), with "Manager override: ..." underneath an override.
Under a failed check, the pack prints what was done about it, as on the day the pack is made: what was typed with the check, for example "What was done: Cooked it for 5 more minutes and checked again", or the closing note of its follow-up, with the day and who added it, for example "What was done: Binned the batch and cooked a fresh one, added 12 Nov by Sam Taylor". A fail whose follow-up is still open has no line; the follow-up is in the Follow-ups section. See When a check fails.
A chilling-down check shows how long it took to reach 8°C, and a passed chill that took longer than 90 minutes, or whose time isn't known, carries its warning in the Reading cell, for example "72°C to 7°C in 6 h 30 min (3 readings). Took longer than 90 minutes." or "7°C. How long it took to reach 8°C isn't known." It is still a Pass. See Chilling down.
Temperature log
The Temperature Log lists every checklist reading and every reading logged by hand on a piece of equipment in the period, each with the limits in force when it was taken. Its introduction says so: "Every checklist and manual reading in the period, with the limits in force when it was taken and any corrective action. SwitchBot sensors show each day's lowest and highest reading, and every reading that was out of range. Times are local to each site; a reading typed in more than an hour later also says when it was entered. Out-of-range readings are shaded." Readings are grouped by equipment (or by checklist item, when the item has no equipment), oldest first. Each row has:
- When - the date and time the reading was taken, in the site's local time. A reading typed in by hand more than an hour after it was taken also says when it was entered, for example "Entered 7 Oct 10:15". A checklist answer that used a reading already taken more than 5 minutes before it was answered also says when the reading was taken, for example "Reading taken 07:58"
- Reading - the value in °C (number items show no unit)
- Limits - for example "1°C to 5°C", "Min 63°C", "Max -18°C" or "Not set". These are the limits in force when the reading was taken, so changing a fridge's range later doesn't change what its earlier readings were judged against. Readings logged before SafetyBrik started keeping each reading's limits show the range their equipment or checklist item had when it started
- Result - In range, Out of range or Not judged. Out-of-range rows are shaded red
- Source - "Checklist: (name)", "Checklist (SwitchBot): (name)", "Manual" or "SwitchBot sensor"
- Logged by - the person's full name, "Sensor" for a SwitchBot reading, or "-" when no one was recorded
- Corrective action - what was done, or "None recorded" in red for an out-of-range reading without one
Each SwitchBot sensor also gets a table with one row per day: its lowest and highest reading, the number of readings and how many were out of range. Every out-of-range sensor reading is listed on its own as well.
In an all-sites pack each group names its site, for example "Walk-in Fridge (Station Road)". A period with no readings prints "No temperature readings were recorded in this period."
Checklist completion log
Every checklist in the period, oldest first, with its Checklist name, Category, Status, Done at and Done by:
- Status - Signed off, Signed off late (its last answer and its sign-off both after the deadline, an amber row), Answered after its deadline, signed off (signed off by the deadline, but its last answer came after it: late, an amber row), Answered, not signed off (an amber row when its last answer came after the deadline), Answered by end of period, signed off later (answered by the deadline and signed off after it, which isn't late), Missed (in red, on a red row), Closed (with the reason), Overdue (in red), In progress or Due
- Done at - the time it was signed off, for example "07:42", or "6 Oct 15:02" when it was signed off on a later day. A checklist closed as Answered, not signed off shows "-"
- Done by - who signed it off, or "Answered, not signed off" for a checklist whose period ended with every answer in but nobody signed it off. It counts as done, but is printed and counted apart from the signed-off ones (see Answered, not signed off)
Corrective actions
Corrective actions are chosen by when they were recorded. Each row has the date and time, the site (in an all-sites pack), For (the equipment or checklist item it was for), What was done, Recorded by and Follow-up. Each corrective action is done when it is recorded, so the Follow-up column shows only a check a manager added afterwards:
- - - no follow-up was added
- Open, check again by 8 Oct 10:00, for Sam Taylor - a follow-up still open, in red, and who it is for
- Open, past its check time (28 Sep 16:00), for Sam Taylor - a follow-up still open whose check time had already passed when the pack was made, also in red
- Done 8 Oct 10:05 by Sam Taylor: (what was found) - a follow-up that was closed, and who closed it. A follow-up closed before SafetyBrik recorded who closed it shows no name
Times are in the site's local time. The Date column always gives the year; a follow-up's time gives it only when it isn't this year (for example "Done 2 Nov 2025 10:05"). There is no Resolved column. See Corrective actions.
Each re-check added or closed in the pack's dates is also in the Follow-ups section, with every other follow-up.
Equipment and COSHH
- Equipment Register - each active piece of equipment with its Type (Fridge, Freezer, Hot Hold, Display or Other) and its minimum and maximum temperature. Archived equipment isn't listed, but its readings stay in the Temperature Log.
- COSHH Chemical Register - each chemical with its Use and PPE, printed in full, and Data sheet: "On file" with the version (for example "On file (v1)" for a first sheet), or "Missing" in red. Read by lists each person who has read the current sheet, one to a line, with the day, for example "Sam Taylor, 3 Oct 2026". It reads "Not yet read" in red when a sheet is on file and nobody has read it, and "-" when there is no sheet.
Cleaning schedule and sign-offs
The Cleaning Schedule is always printed. It is grouped by frequency (After use, Every shift, Daily, Weekly, Monthly, Other), with each item's PPE, Chemical and Method (its numbered steps, then "Notes: ..."). An Other item has a Frequency column with how often it repeats, for example "Every 3 months (Quarterly)" or "Every 6 weeks" (an older Other item without an interval prints "Other: Quarterly"). When there is nothing to list it says why:
- "Cleaning schedule not set up." - the business has no cleaning schedule
- "No items on the cleaning schedule for this site." - the schedule has no items for this site or for all sites
- "No items on the cleaning schedule." - an all-sites pack whose items have all been archived
Making a pack never creates a cleaning schedule for you. Set one up on the Cleaning schedule page.
The Cleaning Sign-off Log covers the pack's period and site, whenever the business has a cleaning schedule. Each sign-off shows the item, how often it is cleaned (in the same words, for example "Weekly" or "Every 3 months (Quarterly)"), when it was logged (for example "1 Jun 2026 08:30", in the site's local time; a Team App sign-off saved offline and sent later shows when it was done), By (who signed it off) and Note. A sign-off with a photo reads "Photo on file in Brikly" in the Note column: the photo itself isn't printed, and neither is a link to it. A voided sign-off stays in the log, greyed out with its note struck through, followed by who voided it and why, for example "Voided by Sam Taylor: logged by mistake". A period with none prints "No cleaning sign-offs were recorded in this period."
Risk assessments
Each current risk assessment starts with its title, then a line such as "Category: Slips, Trips & Falls. Version 2. Last reviewed 1 Oct 2026 by Sam Taylor. Next review: 1 Apr 2027." ("Not reviewed yet." or "Next review: not set." when that's the case), then its notes. Every hazard follows in full, in six columns:
- Hazard
- Who at risk
- Existing controls
- Risk (L x S) - likelihood times severity and its band, for example "3 x 4 = 12" and "High", shaded as in the builder: Low (1 to 4), Medium (5 to 9), High (10 to 14) or Extreme (15 to 25)
- Further action
- Who and by when - for example "Head chef, by 3 Nov 2026"
Who and by when shows who was chosen for the further action (from your Employees list, or a template's role title) and its date, or "-" when neither is recorded. Under each further action, the pack prints its follow-ups (see Actions and their follow-ups). An assessment with no hazards prints "No hazards recorded." See Building risk assessments.
Actions and their follow-ups
A signed 4-weekly review's actions and a risk assessment's further actions are printed exactly as they were signed. Under each one, the pack adds its follow-ups from the follow-up list, newest first, as they stand on the day the pack is made:
- Follow-up: Open (or "Open, past its date (8 Oct)"), then who it is for and when it is due, for example "Sam Taylor, due 17 Nov"
- Follow-up: Done 8 Oct 10:05 by Sam Taylor: (what happened) - a closed one
- Follow-up: Voided 8 Oct by Sam Taylor: (the reason) - a voided one, kept as history
An action with no follow-ups prints as signed, with nothing added under it. Follow-ups from a risk assessment's earlier versions are in the Follow-ups section.
Staff training
All three training sections are headed with the day they are as at, for example "Staff Training Records, as at 30 Sep 2026": the pack's last day, or today for a pack that ends later.
In a site's pack, Safe Method Training and Overdue Refreshers are for the staff on its Staff Training Records (below), each with their training recorded at any site, as their certificates are. This includes a site that hasn't started its own safe methods pack. Safe Method Training lists only those with training on file, plus any leaver trained within the pack's dates. Training recorded under a name that isn't linked to your staff list is listed by the site it was recorded at (or in every site's pack, if it was recorded for no site).
Safe Method Training is laid out like the FSA's SFBB Staff Training Record, one person at a time. Each person has a heading row, for example "Sam Taylor: trained on 18 of 21 safe methods (6 not relevant)", counting only the safe methods that apply at their site. Under it is one row for each safe method they were trained on: Section, Safe method, Trained (the date), Initials (the trainee's) and Refresher due. A refresher that is overdue reads, for example, "1 Sep 2026, overdue" in red. Safe methods a person has no training record for are not listed; the count in the heading shows the gap. Training on a method now marked not relevant is still listed, with "(not relevant)" after its title, and its refresher is never shown as overdue.
Overdue Refreshers lists each safe method refresher that was overdue on that day, with the person, the method, when they were last trained, when the refresher was due and how many days overdue it was. A refresher for a method marked not relevant where the person works (the pack's site, or their main site in an all-sites pack) isn't listed.
Staff Training Records lists everyone on your staff on that day whose main site is the pack's site (or who has no main site), with their latest certificate of each type from any site: the certificate, when it was issued and when it expires, its status (Current, Expiring, Expired or Missing, with Expired and Missing in red), who verified it and whether the certificate file is on file. Every mandatory certificate someone doesn't have gets a Missing row. A Level 3 Food Hygiene & Safety certificate counts for Level 2: someone with Level 3 and no current Level 2 of their own gets a Level 2 row with the Level 3 certificate's dates, for example "Current (via Level 3 Food Hygiene & Safety)", never a Missing row. A business with nobody on its staff list that day lists the names on its training records instead, as the Certifications page does.
Archived certificates and archived safe method training aren't in the pack, for any period. A certificate of a type that has since been made inactive is still printed: each person's latest certificate of that type comes after the rest, with "(no longer in use)" after its name. It is never shown as Missing or in red, and isn't counted as expired in the summary. See Inactive certificate types.
People who had left before that day are not in Staff Training Records or Overdue Refreshers. In Safe Method Training a leaver appears only if they were trained within the pack's dates; their heading says when they left, for example "Sam Taylor (left 12 Sep 2026)", and none of their refreshers shows as overdue. Names are the person's current name.
Suppliers and emergency contacts
- Suppliers' List - each supplier's business name, contact, phone and email, address, delivery days, lead time (for example "1 day" or "3 days") and goods supplied.
- Emergency Contacts - grouped by category in the same order as on the Emergency contacts page, with each contact's name, contact person, phone, email, address and notes. A site's pack lists that site's contacts and those kept for all sites. An all-sites pack lists the All sites contacts and your open sites' contacts; a switched-off or removed site's are in its own pack.
Complaints and pest control
Customer Complaints and Pest Control Events list what is dated in the pack's period, and anything voided within the pack's dates whatever its date (a complaint dated in August and voided in September is in September's pack): the site's own, plus those logged without a site. Each section is always printed: with nothing dated in the period it says so in one line, for example "No customer complaints were logged in this period." Whether a complaint is resolved, and how each pest event's follow-ups stand, is as on the day you make the pack. Each section says so in a line under its heading, for example "Resolved is as on 7 Oct 2026, the day this pack was made."
- Customer Complaints are grouped by category, the serious ones first (an Other complaint under its own label, for example "Other: Cleanliness"). Each row has the date, Summary (with a line about its photos, which show under the row: see Photos in the pack), Action taken, EHO notified ("Yes, 3 May 2026", "Yes" or "No"), Resolved (who resolved it and when, for example "Resolved 12 Nov by Sam Taylor", or "No" in red while it is open; a reopened complaint lists its earlier outcomes under it, newest first, for example "Resolved 10 Nov by Sam Taylor: Refunded", with an outcome from before complaints joined the Follow-ups list as "Resolved earlier: Refunded"; one resolved before then with no follow-up reads "Resolved"), Outcome notes (how it was resolved, "No outcome recorded" for one resolved without one, or "-" while it is open) and Logged by. See Resolving a complaint.
- Pest Control Events are grouped into Sightings, Contractor Visits and Proofing Actions. Each row has the date, Pest and area, Summary, Action taken, Follow-up (each of the event's follow-ups, newest first: how it stands, "Open" in red while it is open, then what needs doing, then who it is for and its due day, for example "Sam Taylor, due 17 Nov"; an older event's note follows as "Original note: ...", and an event with neither reads "-") and Logged by. Contractor visits also name the contractor. A report attached to a pest event is mentioned under its summary, never linked: "Contractor report on file in Brikly" for a contractor visit, "Report on file in Brikly" for a sighting or proofing action. Its photos show under the row, as for complaints. See Pest control.
- Voided complaints and pest events are printed, not left out. A voided complaint reads "Voided" under Resolved, and a voided pest event "Voided" under Follow-up, with a line under the summary saying when, by whom and why, for example "Voided 8 Oct 2026 by Sam Taylor: Logged twice". The day is the record's own site's. A complaint or pest event dated in the period and voided after it, by the day you make the pack, prints as voided too. See Voiding a complaint and Voiding a pest event.
Photos in the pack
Customer complaint and pest event photos are printed in the pack as small pictures, upright as they were taken, in a row under the record, four to a line. The record's summary says how many show: "Photo below" or "3 photos below".
The pack shows up to 10 photos a record and 60 in the whole pack. The rest, and any photo it can't show (a HEIC photo, a damaged or very large file, or one that couldn't be fetched in time), are counted instead of shown: "2 more photos on file in Brikly" under photos that do show, or "Photo on file in Brikly" and "3 photos on file in Brikly" when none of the record's photos can be shown. A pack with a lot of photos takes a few seconds longer to make.
Cleaning sign-off photos and pest control reports are never printed: the pack says they are on file in Brikly. If an inspector asks, a pest control report can be opened from its pest event, and a cleaning sign-off photo from its task or from Records > Cleaning sign-offs. The pack never contains a link to a photo or a file.
Follow-ups
The Follow-ups section lists every follow-up opened, closed or voided in the pack's dates, oldest opened first, whatever it came from (for now, re-checks of a corrective action, failed Prove It checks, pest events, customer complaints, and 4-weekly review and risk assessment actions). A site's pack holds that site's follow-ups and the business-wide ones; an all-sites pack holds them all. Under the heading, a line says when each outcome was judged: "Each outcome is as on 7 Oct 2026, the day this pack was made."
Each row has:
- Opened - when it was added, for example "6 Oct 2026 10:05"
- Site - in an all-sites pack, its site, or "All sites" for a business-wide one
- From - where it came from, with the detail under it: for a re-check, the equipment or checklist item, then the reading, for example "Walk-in fridge" over "9.0°C at 07:58 on 6 Oct, limit 5°C"; for a Prove It check, what was proved, then the kind of check, when it was taken and the reading, for example "Checked chicken breast after cooking" over "Cooking at 12:05 on 6 Oct, 61°C"; for a pest event, its summary, then its kind, day and pest, for example "Mouse droppings by the back door" over "Pest sighting on 6 Oct, Rodents"; for a complaint, its summary, then its day and category, for example "Hair in the soup" over "Complaint on 6 Oct, Foreign object in food"; for a review action, the question (or "Observed problems"), then the review and its period, for example "Is the cleaning schedule up to date?" over "4-weekly review, 12 Oct to 8 Nov 2026"; for a risk action, the hazard, then the assessment and its version, for example "Hot oil splash from fryer" over "Kitchen Food Safety Risk Assessment, version 2"
- What - what needs doing, for example "Check Walk-in fridge again"
- Owner - who it is for. Someone who has left reads, for example, "Sam Taylor (left)", and someone no longer on file "Former team member"
- Due - when it is due, for example "8 Oct" or, for a re-check, "8 Oct 14:30". One moved to another day shows both: "8 Oct 14:30, moved to 9 Oct 10:00"
- Outcome - how it stands on the day the pack is made:
- Open - not closed yet, in red
- Open, past its date (8 Oct 14:30) - not closed and its time has gone, in red
- Done 8 Oct 10:05 by Sam Taylor: Back down to 4°C - closed, with who closed it, when and what they said
- Voided 8 Oct by Sam Taylor: (the reason) - voided, with who voided it and why
A follow-up closed before SafetyBrik recorded who closed it, or when, shows only what was recorded, for example "Done: Back down to 4°C".
Each follow-up's times are in its own site's local time, or your business's for a business-wide one, even in an all-sites pack, so a due date reads as the day it was set for. A date gives the year only when it isn't this year; Opened always gives it. With no follow-ups in the period, the section says "No follow-ups were opened, closed or voided in this period." See Follow-ups.
Still open from before this period
The last section is always printed, so an inspector can see the check was made. It opens with when "open" was judged and what "before" means, for example "Open on 7 Oct 2026, logged before 9 Jul 2026.", then lists, oldest first, the Follow-ups opened before the pack's first day and not yet closed on the day the pack is made, with the same columns as the Follow-ups section and the outcome in red. Corrective action re-checks, pest control follow-ups and complaint follow-ups are among them, so complaints and pest events have no list of their own here: a complaint still unresolved is listed by its open follow-up.
Voiding a complaint or a pest event voids its open follow-up, so neither is listed here once voided.
When nothing is open, the section is one line: "No customer complaint or follow-up from before this period is still open."
Summary tiles
Below the date picker, four tiles give you the headline numbers for the selected dates and site:
- Checklist completion - completed checklists as a share of finished ones: completed / (completed + missed). Checklists still open in their day, week or month aren't counted yet, and checklists that weren't needed because the site was closed aren't counted at all. A late checklist counts as completed here (the pack marks it Signed off late, or Answered after its deadline, signed off), and so does a checklist closed as Answered, not signed off. The tile shows "-" when none have finished.
- Out-of-range readings - readings that fell outside their safe band, from checklists, readings logged by hand and SwitchBot sensors
- Corrective actions - how many were recorded
- Safety score today - SafetyBrik's overall score for the site today (the same number that appears on the Overview). It is today's score, not the score for the dates you chose. On a closed site's tab it shows "-"
Use these as a quick health check before downloading the PDF. If checklist completion is unusually low or out-of-range readings have spiked, it is worth investigating before an EHO does.
Report sections
Below the tiles, Report sections shows what each part of the pack holds:
- Safe methods - completed out of the methods that apply, with how many are marked not relevant, for example "21/21 completed (6 not relevant)". It reads "Pack not started" when there is no safe methods pack, and an all-sites view adds, for example, "1 site not started"
- Checklists - for example "24 completed, 2 missed (3 still open)"
- Temperature log - for example "86 readings, 2 out of range"
- COSHH register - chemicals with data sheets out of the total
- Risk assessments - how many are current
- Equipment - how many are registered
- Corrective actions - for example "4 in this period"
- Customer complaints - for example "2 in this period (1 open), 1 voided". The number in this period, and the open count, leave voided complaints out; "1 voided" counts the voided complaints the pack prints
- Still open from before this period - for example "3 follow-ups", or "None". A complaint still open from before is counted by its follow-up
If something reads "0/12 completed", that is a gap to close before you generate the pack for real.
Dates and sites
- Start date and End date - the dates start as the last 90 days, up to today on the site's clock. You can choose any dates up to a year apart, or zoom in to a single week. Dates can run from 1 Jan 2000 to 31 Dec 2099.
- The start date can't be after the end date. The calendar won't offer it, and if you type one, the page says "The start date must be on or before the end date." in red. The preview is hidden and Download PDF is greyed out until the dates are put right.
- Both dates are needed. While a date box is empty or half typed, the page says "Choose a date in both boxes to see the pack." and Download PDF is greyed out.
- Dates before 2000 or after 2099 - the page says "Choose dates between 1 Jan 2000 and 31 Dec 2099." in red, with the preview hidden and Download PDF greyed out.
- A pack covers a year at most. If the dates are more than a year apart, the page says "Choose dates no more than a year apart." in red, with the preview hidden and Download PDF greyed out. A full year is fine: 7 Oct 2025 to 7 Oct 2026, for example. For a longer stretch, make one pack per year.
- Site - the site tabs list your open sites, then each switched-off or removed site with SafetyBrik records as "Station Road (closed)". With two or more open sites there is an All sites tab; with one open site the page opens on that site and has no All sites tab.
The cover names the site ("Site: Station Road"), or reads "All sites" for a pack covering a business with several open sites. A business with one open site gets that site's pack, whatever closed sites it has, and its cover names the site.
A closed site's pack. A site that has been switched off or removed can still have its own pack: pick its "(closed)" tab, which shows "Station Road is closed. Its records can be read and printed but not changed." The pack holds its records as they were kept, for any dates you choose.
A site's pack holds that site's records plus those kept for all sites. In an all-sites pack every record names its site, and anything kept for all sites (or logged without a site) is labelled "All sites":
- the safe methods and the diary are printed site by site, each under its own heading
- the Prove It records, Checklist Completion Log, Corrective Actions, Equipment Register, COSHH Chemical Register, Cleaning Schedule, Cleaning Sign-off Log, Emergency Contacts, Customer Complaints, Pest Control Events, Follow-ups and the still-open lists have a Site column
- each Temperature Log group, 4-weekly review and risk assessment names its site
- in the training sections each person is named with their main site, and Staff Training Records groups people by main site, then "No main site"
In an all-sites pack, the registers (the Equipment Register, COSHH Chemical Register, Risk Assessments, Cleaning Schedule and Emergency Contacts, like the Safe Methods section) list your open sites' rows and the All sites rows only: a switched-off or removed site's are in its own pack. The dated sections (the diary days, checklists, readings, corrective actions and so on in the pack's dates) keep a closed site's rows.
Dates and times
Every date and time in the pack is in its site's local time (UK time for a UK site). The period runs from midnight to midnight: in the site's time zone, or in your business's own time zone for a pack covering all sites. The cover shows the period (for example "1 Jun 2026 to 14 Jun 2026") and when the pack was generated, marked BST or GMT.
If something can't be loaded
- If the preview can't be loaded, the page says "We couldn't load the report preview" with Try again, and the reason when SafetyBrik has one.
- If the site asked for isn't one of yours (from an old link, say), the page says "We couldn't find that site. Choose another site and try again." A site that was removed but has SafetyBrik records has its own "(closed)" tab and pack.
- If the PDF can't be downloaded, a message tells you so you can try again.
- The pack needs your staff list to check training. If the staff list can't be loaded at that moment, the PDF is not produced and you're asked to try again in a moment, rather than getting a pack without its Missing training rows.
- The pack also needs your suppliers. If they can't be loaded (CostingBrik doesn't answer), the preview and the PDF are not made: "We couldn't load your suppliers just now, so the EHO pack wasn't made. Try again in a moment." A business with no suppliers still gets its pack.
Reports vs Prove It
These two pages do different jobs:
| Prove It | Reports | |
|---|---|---|
| Purpose | Live proving log | The EHO Report Pack |
| Time horizon | Right now and this month | Any dates you choose |
| Use case | Logging cooking/chilling/calibration checks | Monthly review and EHO inspection |
| Output | On-screen records and pass/fail | A preview of the pack and the PDF |
Use Prove It to capture data as it happens. Use Reports to bundle that data, plus everything else in SafetyBrik, into a single document.
Generate the EHO Report Pack on the first of each month for the previous month. It takes seconds and gives you a permanent record of where the business stood at month-end - useful for 4-weekly reviews and for board or owner reporting. Making it on the first matters: registers such as equipment, COSHH and your safe methods show what is on file on the day you make the pack.