Skip to main content

4-weekly review

The 4-weekly review is the rhythm at the heart of SFBB management. Every four weeks, the person in charge steps back from the day-to-day, looks across the diary and the safe methods, and asks: is everything still working as it should? SafetyBrik does this on a single page at /safety/review.

Why four weeks​

The SFBB pack picks four weeks for a reason. It's:

  • Short enough to spot a pattern before it becomes a habit (a fridge that drifts warm three Saturdays running)
  • Long enough that you have meaningful data to reflect on, not just one or two days
  • Predictable - it lands on the same weekday every time, so it can fit into a manager's routine

The 4-weekly review is also one of the documents an EHO is most likely to ask for, because it's where management oversight is recorded. A signed run of 4-weekly reviews is strong evidence of due diligence.

What's in the review​

The review page shows the current period's draft (or creates one if you're due) and walks through five parts:

1. Auto-generated summary​

A panel at the top pulls live counts from the period:

  • Diary days signed vs total days
  • Number of corrective actions taken
  • Number of Prove It records logged
  • Overdue checklists

This is the "what actually happened" snapshot - no typing required, just numbers from your real data.

2. Observed problems​

A yes/no question: "Did you observe any problems or did the same issue occur in the diary 3 times or more?"

If you answer yes, two free-text boxes open:

  • What did you observe?
  • What did you do about it?

This is where patterns get caught. The same fridge flagging warm three times in a month, the same supplier sending late deliveries, the same allergen near-miss happening twice on a Friday night - all of these need to be named and acted on.

3. The 12 SFBB review questions​

The review asks the standard 12 SFBB management questions, the same ones you'd answer on the paper pack. Each is a yes/no with optional context:

  • Are your safe methods still working?
  • Has anything changed in the business that needs new safe methods?
  • Has there been any new staff training?
  • Is your supplier list up to date?
  • ...and so on

If you answer no to any question (or the system flags an issue), an action plan box appears so you can write what you'll do about it before signing off.

4. Additional details​

A free-text box for anything else worth recording - a planned change, a piece of training booked, a supplier you're trialling.

5. Sign-off​

When you're ready, click Sign and complete review. The review locks, the date and signing user are stamped, and it becomes part of your audit history.

Auto-save while you work

The form auto-saves as you type. You can leave the page mid-review and pick up where you left off, then sign when you're ready.

Review states​

The page handles four states cleanly:

  • Loading - skeleton placeholders
  • Not due yet - friendly message with the next due date
  • Draft - editable form with auto-save and a draft badge
  • Completed - read-only with a green completion banner showing who signed and when

If the current review is overdue, it shows with an amber warning so it doesn't quietly slip past.

Where the review shows up​

Once signed, the 4-weekly review surfaces in three places:

  1. Diary overview - the review status card on /safety/diary shows whether your current review is in progress, completed, or due, and links straight to it.
  2. Prove It - the signed review is part of your Prove It pack, demonstrating ongoing management oversight.
  3. Reports and exports - signed reviews are included in PDF exports of your SafetyBrik records, ready to hand to an EHO.
Don't skip a period

Even if it has been a quiet four weeks with nothing unusual, sign the review off anyway. A short, clean review that says "no issues observed, all methods still in use" is stronger evidence than a missing one.

Per-location reviews​

Each location has its own 4-weekly review on its own cycle. Use the location tabs at the top of the review page to switch. This matters because what happens at one site (an equipment failure, a staffing gap) shouldn't muddy the record at another.