Skip to main content

Corrective actions

A corrective action is what you did about a problem: the SFBB diary's "What did you do?". In SafetyBrik, every out-of-range reading on a checklist or logged by hand needs one, written at the time by the person who took the reading, for example "Moved stock to the back-up fridge and turned the thermostat down." A SwitchBot reading out of range can have one added from the equipment's history.

You record a corrective action:

  • on a checklist, on the web, the Team App or the kiosk, before the checklist can be submitted or signed off (see Out-of-range responses);
  • against a reading logged by hand on a piece of equipment, before the reading can be saved, or for a SwitchBot reading taken from the equipment's history (see Logging temperatures);
  • from Needs an action on the temperature reading board, for any out-of-range reading or checklist answer still without one (see Readings that need an action).

Done when it is recorded​

A corrective action records what was done, so it is complete the moment it is recorded, wherever it was recorded. There is nothing to resolve or close afterwards.

When something needs checking again later ("will recheck at 10am"), a manager adds a follow-up to the action (see Follow-ups below). Only a follow-up stays open.

A few rules keep the record honest:

  • One corrective action per reading. A second one for the same reading is refused: "This reading already has a corrective action. To check it again, add a follow-up to it in Records."
  • Only for readings that are out of range. Text typed against a reading that was then corrected back into range isn't saved as a corrective action.
  • The time is when the reading was taken. An action recorded on the Team App or the kiosk takes the time the reading was taken on the device, so one recorded offline before midnight stays on that day in the diary and the EHO Report Pack. An action on a reading logged by hand takes the reading's time.

The Corrective actions list​

Every corrective action is listed under Records > Corrective actions (/safety/records?tab=corrective-actions), newest first. Open it from the Corrective actions card on the Records page.

Each row shows:

  • Date - when it was recorded
  • Site - where it happened, or All sites for a business-wide action
  • For - the equipment, or the checklist item with its checklist's name underneath
  • What was done - the corrective action in full
  • Recorded by - the person's name, or Former team member if they are no longer on file
  • Follow-up - "-" when there is none, or the follow-up's state (see below)

Above the list:

  • Location (in a business with more than one site) - All sites, or one of your open sites. A site shows its own corrective actions plus the business-wide ones. An action at a site that has been switched off or removed is listed under All sites, with its site as "Station Road (closed)".
  • Open follow-ups only - just the actions with a follow-up still open.

Both choices are kept in the page address, so a link from the dashboard opens the same list it counted. The list shows 50 at a time; Load more shows the next 50. With nothing to show it reads "No corrective actions yet. When a reading is out of range, what was done about it shows here." (or "No follow-ups are open." with Open follow-ups only on). If the list can't be loaded, it says "We couldn't load the corrective actions." with Try again.

Follow-ups​

A follow-up is a check a manager asks for after a corrective action: "check the fridge again by 14:30".

Adding a follow-up​

Choose Add follow-up from the row's menu. It is offered on an action that has never had a follow-up.

  • Check again by - a date and time still to come, in the site's time. It starts two hours from now. When your device's clock differs from the site's, the site's zone is named beside the field, for example "Burford time (GMT)". A time that has already gone (from a page left open, say) is refused with "Choose a time that is still to come."
  • Staff member (optional) - who should do the check. Leave it blank and the follow-up stays with whoever recorded the action. If the person you choose works mainly at another site, the dialog says they'll only see the follow-up in the Team App while they're clocked in at this action's site, unless they're an owner or manager.

Clock-change days​

On the day the clocks change, some times need a second look:

  • Spring forward. A time in the hour the clocks skip (01:30 in the UK, say) doesn't exist, so it is refused: "That time doesn't exist on the clock-change day". Choose a time outside that hour.
  • Fall back. A time in the hour the clocks repeat happens twice, so the form asks which one you mean: "The clocks go back that night, so 01:30 happens twice. Which one?", with "01:30 BST (first)" and "01:30 GMT (second)". Until you choose, saving says "Choose which 01:30 you mean."

Follow-up times then show with their zone, for example "Check again by 25 Oct, 01:30 GMT", so the two are never confused.

Closing a follow-up​

Choose Close follow-up from the row's menu. What did you find? is required, for example "Back down to 4°C". A follow-up can also be closed on the Team App. Either way, SafetyBrik records who closed it.

Each corrective action has one follow-up. Once it is closed, what was found stays on the record and the row has no more actions. If the problem needs checking again after that, take a new reading.

At a closed site​

A corrective action at a site that has been switched off or removed is read only, like the rest of that site's records. Its row has no menu, so a follow-up can't be added, changed or closed there, and the Team App can't close one either. 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." Close a site's open follow-ups before you switch it off: the site closure dialog in Settings > Locations counts them. A follow-up left open there stays in that site's own records and its EHO Report Pack, but isn't counted on the all-sites dashboard.

Follow-up states​

The Follow-up column shows:

  • - - no follow-up was added
  • Open (amber) - with "Check again by 8 Oct, 14:30", and the person's name when one was chosen
  • Past its check time (red) - an open follow-up whose time has passed
  • Done (green) - with when it was closed, who closed it and what was found, for example "Done 8 Oct, 14:35 by Sam Taylor" and "Back down to 4°C". Someone no longer on file shows as "by a former team member", and a follow-up closed before SafetyBrik recorded who closed it shows no name

Who can do what​

  • Owners, admins and members can add and close follow-ups on the web. Viewers see the list, without the row menu.
  • On the Team App, the person a follow-up is for sees it and can close it, and owners and managers see every follow-up at the site they're working at.

Where corrective actions show up​

  • The dashboard - a Corrective action follow-ups card counts the open follow-ups at the site (at your open sites, in the all-sites view), and an alert reads, for example, "2 corrective-action follow-ups past their check time". Both open the list, showing open follow-ups at the same site. There is no push notification for a follow-up past its time.
  • The diary - each day's corrective actions are listed under Flagged items, with a Follow-up open or Follow-up done badge when a follow-up was added.
  • The EHO Report Pack - a Corrective Actions section lists every action recorded in the period, with who recorded it and a Follow-up column ("Open, check again by 8 Oct 10:00, for Sam Taylor", "Open, past its check time (28 Sep 16:00), for Sam Taylor" once that time has passed, or "Done 8 Oct 10:05 by Sam Taylor: Back down to 4°C"). Follow-ups still open from before the pack's dates are listed in its Still open from before this period section.
  • The Team App - a Follow-ups card and screen for the follow-ups to check at the site.
  • The 4-weekly review - its summary counts the corrective actions recorded in the period.
  • The audit log - Corrective action raised, Follow-up added and Follow-up closed.