Skip to main content

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.

From the SafetyBrik Records page, open the Safe methods tab. You'll see a card for each SFBB section (Cross-contamination, Cleaning, Chilling, Cooking, Management, Customer information).

  • 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

Each section is colour-coded to match the SFBB pack so it feels familiar to anyone who has used the paper version.

Filling in a method​

A method detail page has a few parts:

  1. Status bar - shows whether the method is not started, in progress, completed, or due for review. A "Last proved" badge shows when this method was last evidenced in Prove It.
  2. Safety points - the numbered points you respond to. Most are short text or yes/no answers describing how your business handles that step.
  3. 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.
  4. Action buttons - Save Changes, Mark as Complete, and Mark as Not Relevant.

When every required response is filled in, Mark as Complete becomes active. Completing the method records the date and sets a next-review date.

Not relevant is fine

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. EHOs prefer a documented "not relevant" with reasoning over a blank field.

Reviewing a completed method​

Methods aren't fill-and-forget. SafetyBrik tracks a next review date for every completed method. When that date passes, the method status flips to Review due and an amber Review Due banner appears on the detail page.

To review:

  1. Open the method
  2. Read through your existing responses and check they still describe how you actually work
  3. Edit anything that has changed
  4. Add optional notes in the review box (for example: "Updated to reflect new dishwasher")
  5. Click Confirm Review

The review is logged in the Review History at the bottom of the page, with the date and any notes. This gives you an audit trail showing the method has been kept current.

Audit logging on edits​

Every change to a method is recorded:

  • Response edits are versioned so you can see what changed and when
  • Completion, review confirmation, and "not relevant" decisions 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.

Permissions

Only users with edit permissions on SafetyBrik can change responses, mark methods complete, or confirm reviews. Viewers can read the pack but cannot make changes.

Customer information and allergens​

The Customer information section is where SFBB asks you to document how customers find out what's in your food - especially the 14 regulated allergens. SafetyBrik takes this further with a dedicated allergen feature.

Your safe method here should reference 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 auto-syncs from your CostingBrik recipes.

One source of truth

Because the allergen matrix is generated from your costed recipes, you don't have to maintain a separate allergen list. When a recipe ingredient changes, the matrix follows.