Using safe methods
This page walks through how to navigate sections, fill in a method, mark it as complete, and handle reviews when a method falls due.
Navigating sections and methods
Open Safe methods in the SafetyBrik sidebar, under Records and evidence, or the Safe methods card on the Overview (/safety/safe-methods). You'll see a card for each of the five SFBB sections (Cross-contamination, Cleaning, Chilling, Cooking, Management).
- Click a section card to open the section page at
/safety/safe-methods/:section - The section page lists every method in that section with a status badge
- Click any method to open the detail page at
/safety/safe-methods/:section/:method
The pack, section and method pages all have site tabs, and the site you are on travels with you from the pack to a section to a method (it's part of the page address, ?location_id=), so a link someone sends you opens the right site's copy. If you switch site on a method page while an answer is still saving, SafetyBrik waits for it to save first, then switches. An answer that can't be sent just then is kept on this device and sent next time you open the method. If this device can't keep it either, you stay where you are: "Your answers aren't saved yet, and this device can't keep them. Stay on this site until they're saved." Answers never carry over to another site's copy of the method.
If your sites can't be loaded, each page says "We couldn't load your sites." with Try again.
Closed sites
A site that has been switched off or removed keeps its pack under a read-only "Station Road (closed)" tab, with "Station Road is closed. Its records can be read and printed but not changed." Its pack, sections and methods open as they were, with your answers, but nothing can be changed: the answers can't be edited, and there is no Mark as complete, Mark as not relevant, Record review or Prove this method. A change sent from a page left open is refused with "This site is closed, so its records can be read and printed but not changed."
A closed site that never started a pack says "No safe methods pack was kept for this site." If Brikly can't check just then which of your sites are closed, a closed site's pages say "We couldn't load this site's safe methods." with Try again.
Each section card shows the section's own icon beside its name, so the sections are easy to tell apart.
Filling in a method
A method detail page has a few parts:
- Status bar - shows whether the method is not started, in progress, completed or not relevant, or its review is due or overdue. On the seven temperature-control methods (Cooking Safely, Reheating, Hot Holding, Chilling Down Hot Food, Chilled Storage, Freezing and Defrosting), a Last proved badge shows when the method last passed a check in Prove It, and Prove this method opens the Prove It form already filled in. Other methods don't show either.
- Safety points - the points you respond to, each with a Why is this important? link. Most are short text or Yes / No answers describing how your business handles that step.
- Collapsible sections - SFBB-style guidance: Check it, Think twice!, What to do if things go wrong, How to stop this happening again and Manage it. Where a method asks questions under Check it (Handwashing, Chilled Storage, Cooking Safely and Reheating), the answer fields are right there and the section opens automatically, so these methods can be completed like the rest.
- Action buttons - Mark as complete, with the saving status beside it. Mark as not relevant is in the status bar at the top. There is no Save button: answers save themselves (see Answers save as you go).
A yes/no question has two buttons, Yes and No, and neither is pressed until it is answered, so an unanswered question never looks like a No. Tap the other button to change an answer. Once answered, a question can't be set back to unanswered.
When every required response is filled in, Mark as complete becomes active. An answer of only spaces doesn't count, and an answer still saving does: Mark as complete waits for your answers to save first. If one can't be saved, nothing is completed and the page says why.
Until then, beside Mark as complete the page says how many are left, for example "3 questions still to answer", with a link to each one named by its question (the first five, then "and 2 more"). A link opens the section the question is in and moves you to its answer box. The links update as you answer. Check it, Think twice! and Manage it open by themselves when they hold questions, and each one's header shows how many of its questions are left, for example 2 to answer. Completing the method records the date and sets a next-review date. Saving answers updates the pack's progress straight away.
On a completed method you can still change an answer, but not empty it: "A completed safe method needs every answer, so '(question)' can't be left empty. Change the answer instead of clearing it." Each answer you change on a completed method is in the audit log as Safe method answer changed, with the question and what it said before and after.
If a method genuinely doesn't apply to your business (for example, hot holding when you only make food to order), use Mark as not relevant and add a short reason, then Confirm. EHOs prefer a documented "not relevant" with reasoning over a blank field, and the reason is printed in the EHO Report Pack ("Not relevant: we only make food to order").
Answers save as you go
Each answer saves by itself: a Yes or No as soon as you tap it, and text after a second's pause in typing. The status beside Mark as complete says how saving is going: Saving..., then Saved at 14:32 (the site's time). If an answer can't be sent (the connection dropped, say), it reads Not saved. Retrying... and keeps trying by itself, with Retry to try straight away.
- Changed elsewhere. If someone saved the same method in another tab or on another device after you opened it, your latest answers aren't saved over theirs: "Changed elsewhere. Your latest changes aren't saved.", with Reload to show the method as it is now (dropping your unsaved answers) and Keep mine to save yours over the other change.
- Refused. An answer the method can't take (a completed method's answer left empty, say) isn't saved. The status says why, with Discard to put the saved answer back.
Nothing you type is lost. Every answer is kept on this device until it has saved, so going Back, reloading the page or closing the tab loses nothing. Open the method again on the same device, signed in as the same person in the same business, and what hadn't saved is sent. If someone else saved the method in the meantime, you get Changed elsewhere with Reload and Keep mine, as above. Answers from an earlier visit that overlap what you have changed since (the same question, say) are never mixed in: they show as "Unsaved changes from an earlier visit", listed one by one, with Use these (they replace yours) and Discard. Nobody else signing in on that device sees them.
Leaving the method while an answer hasn'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 method." If the device can't keep unsaved changes (some private browsing windows, say), the status 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.
Marking a method relevant again
A method marked not relevant says "This method is marked not relevant to your business: (reason)". If things change (you start hot holding, say), anyone who can edit the pack can click Mark as relevant again. It asks:
Mark as relevant again? Hot Holding comes back into your safe methods pack. Your answers are kept, and it needs completing again.
Your earlier answers are still there, and the method is back to in progress (or not started, if it had no answers), ready to check and complete. The change is in the audit log as Safe method marked relevant again. Until then, answers or completion sent for it from a page left open are refused with "This method is marked not relevant. Mark it as relevant again to change it."
Reviewing a completed method
Methods aren't fill-and-forget. SafetyBrik tracks a next review date for every completed method. Seven days before that date, the method shows Review due and Record review becomes available, so you can review it in good time. Once the date has passed it shows Review overdue.
You get two reminders for each review date, never more: one when the 7-day window opens, and one the day after the date has passed. Several methods at one site that come due together are one reminder, for example "5 safe methods due for review at Station Road", and Review Safe Methods opens that site's pack. A single method's reminder ("Safe method review due: ...") opens the method at its site. Recording a review sets a new date and starts again. After the second reminder, the SafetyBrik Overview's alert is the reminder, for example "Safe method 'Hot Holding' review overdue". A site that has been switched off or removed gets no review reminders.
A review can't be recorded before its review opens. One sent from a page left open is refused with, for example, "This method isn't due for review yet. Its review opens on 27 Aug 2027."
To review:
- Open the method
- Read through your existing responses and check they still describe how you actually work
- Edit anything that has changed
- Add optional notes in the review box (for example: "Updated to reflect new dishwasher")
- Click Record review
Record review waits for the answers you edited to save first, then records the review, so the review always confirms the answers as they now stand. If your answers can't be saved, nothing is reviewed and the page says why. Once recorded ("Review recorded"), the review is an entry in the review history that can't be changed afterwards. To change an answer later, edit it on the method: the change saves by itself and is in the audit log.
The review is logged in the Review history card on the method page, with the date and any notes. This gives you an audit trail showing the method has been kept current. The EHO Report Pack prints each method's last review, with who did it and its notes, and the next review date (marked overdue once it has passed).
A method is reviewed once a day. Clicking Record review twice records one review. A different review sent the same day from another tab is refused with "This method was reviewed earlier today. Reload the page to see that review."
Safe method training
SFBB asks you to record that each member of staff has been shown your safe methods. In SafetyBrik that record lives in two places:
- The Training tab on the Safe methods page (
/safety/safe-methods?tab=training): a grid of everyone on your staff list against every safe method, with the date each person was trained and their initials, and an Overdue refreshers list underneath - The Training card on each safe method's page: everyone on your staff list, with Trained on, Initials and a status (Up to date, Overdue, Refresher not needed, or Not trained). People not yet trained on the method are listed after those who are
Both list everyone employed on your Employees list, trained or not, so a new starter shows as Not trained from their first day. Anyone else with training on file, such as someone who has since left, stays listed with their training.
Training on any site's copy of a method counts: a method's Training card shows each person's training on that method at every site, and training again at any site clears an overdue refresher. Dates read, for example, "12 Apr 2026".
Reading the Training tab
- N of M trained - under each name, how many of the safe methods on the grid that person is trained on, for example "3 of 27 trained". It is amber for someone with none.
- Not trained cells - a dash in a method's column means the person hasn't been trained on it.
- Overdue - a cell whose refresher has passed is shaded red and marked Overdue above the training date. Hovering over it says when the refresher was due, for example "Overdue. Refresher was due 12 Apr 2026".
- People with no training at all - when anyone on the grid has none logged, a prompt above it says so, for example "3 people have no safe-method training logged.", with Log training for those who can log it. Under it, Everyone and Not trained (3) switch between the whole grid and just those people. Once everyone has some training logged, the prompt and the switch go and the grid shows everyone again.
With no safe methods set up yet, there is nothing to be trained on, so the Training tab says "Set up your safe methods first" and "Training is logged against each safe method. Set up your pack on the Pack tab, then log training here.", with Go to the Pack tab. Log training is hidden until then. With safe methods but nobody to list (nobody employed and no training logged), the tab and each method's Training card say "No training recorded yet."
When something can't be loaded
- If the training can't be loaded, both say "We couldn't load the training records." with Try again.
- If a refresh fails while the grid or card is already showing, it stays, with "We couldn't refresh the training records, so this may be out of date." and Try again.
- If your staff list can't be loaded, both say "We couldn't load your staff list, so only people with training logged are shown." with Try again. Until it loads, anyone with no training yet is missing from the list.
- If the overdue refreshers can't be loaded, the Training tab says "We couldn't load the overdue refreshers, so this page can't show who needs one." with Try again. If they can't be refreshed, the last list stays with "We couldn't refresh the overdue refreshers, so this may be out of date."
Logging training
Owners, admins and members can log training: Log training on the Training tab, Log training for this method on a method's card, or click an empty cell on the grid. Viewers can read the training but not change it.
- Employees - choose people from your Employees list, each with their initials. Training is recorded only for people on that list. With nobody on it, the form says "Certificates and training are recorded for people on your Employees list. Add your team on the Employees page first.", with a link to the Employees page. If the list can't be loaded, it says "We couldn't load your Employees list." with Try again. Two people with the same name are told apart by their main site, then their email. The Training grid, its Overdue refreshers and Archived training lists, a safe method's Training card and the Certifications grid tell them apart the same way.
- Safe methods - one or more, with Select all for each section
- Trained on - the date. It can't be after today: "The training date can't be after today. Check the date and try again."
- Refresher due (optional) - when they should be trained again. It can't be before the training date: "The refresher date can't be before the training date. Check both dates and try again."
- Trained by - filled in with your name, which you can change. It can't be left empty: "Add who gave the training."
- Notes (optional)
The form says what is missing before it saves, for example "Choose who was trained." or "Add the initials of everyone trained." Each save is in the audit log as Safe method training logged.
Editing, archiving and restoring training
Click a trained cell on the grid, or a trained row on a method's card, to open Edit safe method training. Everyone who can log training can change the date, the trainer, the trainee's initials, the refresher date and the notes, with the same date rules. Each change is in the audit log as Safe method training updated, with what changed.
Training is never deleted. Owners and admins can Archive a record logged by mistake. It asks "Archive this training?", and says the record "comes off the training matrix and out of the EHO Report Pack. You can restore it from Archived training." Members can't archive or restore.
When anything is archived, Show archived (N) appears on the Training tab. Anyone can tick it, viewers included, to see the Archived training table, greyed out with an Archived badge. Owners and admins can Restore a record from there. Archiving and restoring are in the audit log as Safe method training archived and Safe method training restored.
Overdue refreshers
A refresher is overdue once its date has passed, following the same rules as the EHO Report Pack:
- Training on the same method again, at any site's copy, clears it
- A refresher isn't overdue for someone who has left. They stay on the grid with their training
- A refresher isn't overdue for a method marked not relevant where the person works
Where a refresher date has passed but doesn't count for one of these reasons, the method's card shows Refresher not needed rather than Up to date.
Closed sites
Training recorded at a site that has been switched off or removed is read only: it can't be edited, archived or restored ("Site closed" shows in place of Restore), and any change is refused with "This site is closed, so its records can be read and printed but not changed." A closed site's method pages show the Training card read only, with no Log training for this method. On the Training tab for all sites, each method's column is an open site's copy of it, so training logged there is recorded against an open site.
Audit logging on edits
Every change to a method is recorded in the audit log:
- On a completed method, each answer that changes is logged as Safe method answer changed, with the method, the question, what it said before and what it says now, who changed it and when
- Completion, recorded reviews, "not relevant" decisions and marking a method relevant again all carry the user, timestamp and any notes
- The review history is visible directly on the method page
This audit trail is what turns SafetyBrik from a tick-box exercise into actual evidence of due diligence.
Only users with edit permissions on SafetyBrik can change responses, mark methods complete or not relevant, mark them relevant again, or record reviews. Viewers can read the pack but cannot make changes.
Allergens
SFBB deals with allergens in the Food Hypersensitivity (Allergens) method, in the Cross-contamination section. It covers checking ingredient information when deliveries arrive, and telling customers about any of the 14 regulated allergens in the food and drink you serve.
Your answers there should say where customers see allergen information (menu, app, verbal, written sheet). The detail behind it - which dishes contain which allergens, ingredient by ingredient - lives in the allergen matrix, which reads your CostingBrik recipes automatically.
Because the allergen matrix reads your costed recipes, you don't keep a second allergen list for them. When a recipe ingredient changes, the matrix follows. A recipe with an ingredient whose allergens haven't been declared shows as Not fully known, and anything you sell without a CostingBrik recipe can be added to the matrix by hand.