Skip to main content

Completing checklists

This is the staff-facing half of the system - the part that replaces the clipboard. A team member opens a due checklist, works through the items, and signs it off. SafetyBrik takes care of filing it into your records and the EHO Report Pack.

Starting a checklist​

There are four ways in:

  • From Today, the SafetyBrik home, where each of today's checklists is a row: one tap opens it, and after you sign it off you come back to Today
  • From the templates list at /safety/checklists, by clicking a card, then Start checklist on its detail page
  • From the Team App on a phone, where today's checklists for the site they are working at appear on the Safety screen (see Which sites staff can do checks at)
  • From the kiosk, the shared tablet at a site, after signing in with a kiosk passcode

On the web, Start checklist opens this period's checklist: the same one staff see on the Team App and the kiosk. It never makes a second copy, so two people starting the same checklist end up on the same record. At a site that has been switched off or removed nothing new is made: there is no Start checklist, and a checklist made there before the site closed opens read-only from Open checklist (see Switched-off or removed sites). If the checklist runs at every site and your business has more than one, it first asks Which site is this for? A business with one site never sees that question.

The completion screen is at /safety/checklists/:id/complete. If it can't be opened, you see a calm message with Try again.

Checklist overdue notifications, and Temperature alert notifications for a reading on a checklist, open the checklist itself (read-only if it has been signed off since). An overdue notification gives the deadline in the site's local time, and names the day for a weekly or monthly checklist, for example "Opening Routine was due at 09:00 and hasn't been signed off." or "... due at 12:00 on Mon 5 Oct", with View checklist. It arrives within 15 minutes of the deadline, at any time of day (a 21:00 closing check by 21:15), once per checklist, and never for a site that is closed today. None is sent for a checklist's first day, week or month without a deadline (see A first period with no deadline).

A Temperature alert for a reading logged directly on a piece of equipment opens that equipment's history in Temperature checks instead. See Records and alerts.

The completion screen​

At the top: the template name, the site and date, and breadcrumbs. Below: each item rendered as the right input for its type.

  • Tick - three buttons, Done, Not done and N/A. Nothing is pressed until the item is answered. Not done asks Why wasn't it done? (see Not done needs a reason)
  • Temperature - a numeric input in °C, with the acceptable range shown beside it, for example "Acceptable: 1 to 5°C", "Acceptable: Max -18°C" or "Acceptable: Min 63°C"
  • Number - a numeric input, with any range shown beside it
  • Text - a small textarea for free-text responses
  • Photo - a "Take / choose photo" button that opens the camera on mobile or a file picker on desktop. A photo item is answered only with a photo, so a required photo item needs its photo before the checklist can be signed off

Items that don't need an answer are marked Optional; every other item is required. Items linked to a piece of equipment show the equipment name underneath the question. Guidance text - if the template has any - sits below the input. Times on the checklist are the site's time, whatever time zone your device is in.

A number too large to store (over 999,999.99 on a checklist, a typing slip such as 12345678 for 12.3) is refused with "That number is too large to record. Check the reading and enter it again." and nothing is saved. A reading for a piece of equipment is limited to 999.99°C: see Equipment. A reading that isn't a number shows "Enter the reading as a number." and isn't saved.

Each answer saves as you go​

On the web there is no Save button for a checklist. Each answer is saved as it is given:

  • a tick when you tap it;
  • a reading when you leave the field or press Enter;
  • text when you leave the field, or after a second's pause in typing;
  • a photo once it has uploaded.

A line in the bar at the foot of the screen 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. Nothing is lost while it retries.

Answers stay changeable until the checklist is signed off. Tap a different tick or type a new reading and the new answer is saved. A changed reading is kept as a new reading, so every reading taken stays on the record, each with its time.

Someone else can carry on. A checklist is one shared record for the site, so one person can start it and another finish it, on the web, the Team App or the kiosk. An answer given by someone else shows who gave it and when, for example "Answered by Sam at 10:42". One given on a kiosk also names the tablet, for example "Answered by Sam on Burford tablet at 10:42". Answers given on the Team App or the kiosk count towards the required items, and you can change them like any other answer until sign-off.

Nothing typed is lost​

Everything you type is kept on this device until it has saved, so going Back, reloading the page, closing the tab or signing out loses nothing. Open the checklist again on the same device, signed in as the same person in the same business, and what hadn't saved is sent or put back. Something half-finished (a Not done with no reason yet, a reading still waiting for what you did) comes back marked "Restored, not saved yet:", with Save and Discard. Nobody else signing in on that device sees it.

Leaving the checklist while something hasn't saved yet asks Leave this checklist?, with Leave and Stay, and says what will happen, for example "We'll send your answers as you leave. Any that don't get through are sent next time you open this checklist." If the device can't keep unsaved changes (some private browsing windows, say), the status line 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.

A photo is the exception: one still uploading, or one whose upload failed, isn't kept. Next time, the item says "This photo didn't upload last time. Take the photo again.", and the checklist can't be signed off until the photo is taken again or the reminder is discarded.

Not done needs a reason​

A tick item answered Not done asks Why wasn't it done?, for example "Ran out of sanitiser." (up to 300 characters). The reason is required: the answer saves once the reason is in, and until then the item says "Say why it wasn't done." Signing off waits for it too. On the record, the answer reads Not done with "Reason: ran out of sanitiser" under it.

Ticks answered Not done before reasons were asked for show "No reason recorded".

N/A is for an item that doesn't apply that day (no deliveries, so nothing to check). It counts as an answer, and is never shown as Not done.

Using a reading already taken​

On the web, a temperature item linked to a fridge or other unit can use a reading the unit already has. When the unit has a reading from its current check (see Today's checks), recorded on the board or in its history or pulled from its SwitchBot sensor, that is in range and not used by another answer, the empty item shows a button such as Use the 07:58 reading (3.2°C). Nothing is filled in until you tap it. The tap records the answer straight away, so it needs a connection: offline, the button is greyed out with "Needs a connection". If the reading can't be used any more (another answer used it meanwhile, say), the item says "That reading can't be used any more. Type the temperature instead.", and if it doesn't save, "Not saved. Tap to try again or type the temperature." The offer goes once you type in the field, and when that check's time ends. An out-of-range reading is never offered: type it in and say what you did, as for any reading. A unit set to Not checked daily has no checks, so it is never offered one. The reading is recorded once, as the checklist's answer, and when it was taken more than 5 minutes before the answer, the record says so beside the answer's time, for example "Answered 08:20 · Reading taken 07:58". The Team App and the kiosk don't offer readings yet.

Out-of-range responses​

For temperature and number items with a range, entering a value that falls outside that range:

  • Turns the input border red
  • Surfaces an inline warning ("Temperature out of acceptable range")
  • Holds the reading, with "(reading) is out of range." and a required What did you do? box

Write what you did, then press Save reading: the reading and what you did save together. Pressing Save reading with the box empty says "Say what you did before you save." Discard this reading throws the reading away. If you correct the reading back into range, the page says "This reading is in range, so it needs no action." If you leave the page while a reading is held, the reading is saved without its action, and the checklist asks for one before it can be signed off.

A range can have a minimum only, a maximum only, or both, and each side is judged on its own: a freezer with only a -18°C maximum flags a -16°C reading.

An out-of-range reading already saved without a corrective action (from the Team App, say) gets its own What did you do? box, with "Add what you did about this reading before you sign off." What you type there is kept on this device and saved when you sign off.

The corrective action is free text. The staff member writes what they did - "Moved stock to back-up fridge, rang engineer". SafetyBrik saves it as a corrective action against the reading, which shows wherever the reading does.

  • It is recorded as done straight away. A corrective action records what was done, so there is nothing to close afterwards.
  • If something needs checking again ("will recheck at 10am"), add a follow-up: a By when time, and optionally the person who should check. It stays open until someone closes it with What did you find?, and is listed on the Follow-ups page until then. See Adding a check-again time below.
  • A reading has one corrective action. If someone else recorded one for the same reading first, yours isn't saved: "Someone else already recorded what they did. Your note wasn't saved:", with your note and Discard.

This is the digital version of the SFBB "What went wrong / what did I do about it" column, and it is required: a checklist can't be signed off on the web or the Team App, or submitted on the kiosk, until every out-of-range reading has a corrective action. The Team App and the kiosk say: "Add what you did about each out-of-range reading before you sign off this checklist." (or "... before you submit this checklist."). This needs the latest Team App and Brikly Kiosk app.

Don't backfill from memory

Capture the corrective action while you're standing in front of the fridge, not at the end of the day. The whole point of the digital record is that it's contemporaneous.

Adding a check-again time​

On the web, a checklist's corrective action is saved with the checklist: with its reading when you press Save reading, or at sign-off for one typed into an already-saved reading's box. The box itself has no quick choices or Check again switch, unlike the temperature board.

Once the action is saved, it shows under its reading ("Corrective action: ..."), with Add a check-again time underneath. It opens the same dialog as Add follow-up in Records: By when, two hours on by default, and an optional Who (see Adding a re-check). It is there on a checklist still being filled in and on a signed-off one, for owners, admins and members, at a site that is still open. An action still on this device, waiting to be sent at sign-off, doesn't have it yet.

When the action already has a follow-up, the row shows it instead: Check again with when it is due and who it is for, its state (Open, Past its date or Done), and Open in Follow-ups. Close or change it from the Follow-ups page or Today.

Photos and evidence​

Photo items use the device camera on phones (rear camera by default, for capturing what you're looking at). On desktop, the file picker is used. Images are pre-processed before upload so they're fast on patchy café Wi-Fi. The photo is stored against the response and stays with the checklist record.

On the web, photos can be JPEG, PNG or WebP, up to 5 MB. A photo in the iPhone's HEIC format is refused with "This photo is in HEIC format. Save it as a JPEG and try again." When a photo is refused, the page says why; if the upload fails for another reason, you see "Photo upload failed. Please try again." Signing off waits until the photo is uploaded or discarded.

Photos are private to your business. The web and the Team App show them through links that work for an hour, and reopening or refreshing the checklist gets fresh ones; the kiosk shows "Photo added" rather than the picture. A photo that isn't one of your business's own uploads is refused with "That photo couldn't be found. Remove it and add it again."

Common uses:

  • A photo of the fridge thermometer display
  • The cleaned area, before and after
  • The label on a delivery
  • A handover whiteboard at end of shift

Notes and exception flows​

Text items act as the catch-all. If a checklist needs "anything we should flag for the next shift?" or "name of duty manager", a Text item handles it. For a task that wasn't done, answer its Tick item Not done: the checklist asks why, so you don't need a separate "If not done, why?" text item.

Required items can't be skipped. If a piece of equipment is genuinely broken and a temperature reading isn't possible, log the reading you can get and use the corrective action or a text item to explain. If it is out of use for good, edit the checklist to remove or unlink its item. Archiving the equipment doesn't take it off the checklist: the item keeps adding readings to it, and the builder shows "The equipment linked to this item has been archived. Unlink it..." until you edit the checklist.

Signing off on the web​

Sign off sits in a bar at the foot of the list, which stays on screen as you scroll and settles after the last item at the end. The bar shows your progress, for example "3 of 8 answered", and the saving status. While something is still missing, a sentence says what, for example "To sign off, answer 2 required items and add a corrective action for 1 out-of-range reading.", with a link to the first such item, for example "Go to Fridge 1 temperature". The link moves on as each one is answered. A text answer of only spaces doesn't count as an answer.

Pressing Sign off with something still missing signs nothing off. Instead, every required item without an answer is outlined in red with "Answer this item to sign off." under it, and the page takes you to the first thing missing. Each mark clears as you answer it. A checklist can't be signed off until every required item has an answer, every Not done has its reason and every out-of-range reading has a corrective action.

When nothing is missing, Sign off asks Sign off this checklist? with "Once signed off this checklist can't be edited." Confirm with Sign off. The page then waits for every answer to finish saving and signs the checklist off with your name. It says "Checklist signed off" and takes you back to the templates list, or to Today when you opened the checklist from there (its back button then reads Back to Today). If an answer can't be saved, nothing is signed off and the item is marked, for example "Some answers didn't save, so the checklist wasn't signed off. Check your connection and try again."

Sign off also waits when:

  • another tab on this device has unsaved changes to the same checklist: "Another tab has unsaved changes to this checklist. Finish them there or close that tab." Finish them in that tab, or close it, then sign off;
  • a photo is still uploading, or one didn't upload and needs taking again;
  • answers from an earlier visit on this device turn up: "Answers from an earlier visit turned up and are being saved. Sign off again once they are."

If the checklist was signed off somewhere else in the meantime (on the Team App, say), the page says "This checklist was signed off elsewhere. Your last answers weren't saved." and shows them with Discard, for example "Not saved: Sam signed off at 10:42."

If an item's type or linked equipment changed after the checklist was opened (a tick item made into a temperature item, say), an answer for it in its old form is refused. An item that already had answers is replaced by a new one when it changes, so the old one is no longer on the checklist: "One of these answers is for an item that isn't on this checklist. Reload the checklist and try again." An answer of the old kind for an item whose type changed before anyone had answered it is refused with "This answer doesn't suit this item, which may have changed since the checklist was opened. Reload the checklist and answer it again." Either way, the page reloads the checklist's items and the answers already recorded, and keeps what you typed for the other items, so you can answer the changed item and sign off. The same happens when a refusal means the checklist changed in another way, with the reason shown. The same answer for an item sent twice (from a phone retrying, say) is kept once, with no second reading, alert or corrective action.

At a site that has been switched off or removed, answers, photos, sign-offs and new corrective actions are refused on every surface with "This site is closed, so its records can be read and printed but not changed." See Switched-off or removed sites.

Doing a checklist late​

A checklist can be done at any point in its period: its day for a daily, its week for a weekly, its month for a monthly. Once its Due by time has passed it shows as Overdue, with a line such as "Can still be done until Sun 12 Oct". Fill it in as normal. It counts as done, with the time it was really signed off.

A checklist is late only when its last answer came after the deadline. When it was signed off doesn't make it late, and doesn't change the safety score:

  • Last answer after the deadline: it is late and counts half in the safety score. It reads Signed off late on the web and in the diary (for example "Signed off late 09:12") when it was signed off after the deadline too, or Answered after its deadline, signed off when the sign-off was by the deadline. The Team App and the kiosk show a Late pill.
  • Every answer in by the deadline, signed off after it: it isn't late and keeps full credit. It reads Answered by end of period, signed off later, with the real sign-off time.

See Late checklists.

The exception is a checklist's first day, week or month when it starts after its Due by time has passed (a checklist added at 14:00 with a 09:00 deadline, say): it has no deadline that time, so it is never Overdue or late, and is Missed only if it isn't done by the end of its period. See A first period with no deadline.

See Deadlines and periods for how long each kind of checklist stays open.

Answered, not signed off​

If every required item is answered (with every Not done's reason and every corrective action in) when a checklist's day, week or month ends, but nobody signed it off, it is closed as Answered, not signed off. The work was done, so it counts as done: in the safety score, the checklist counts and the 4-weekly review, never as Missed. It is on time when its last answer was given by its Due by time (or it has no Due by time). If the last answer came after the deadline, it is late, signed or not: half credit in the safety score, as for any late checklist. It shows "Answered, not signed off" where a signer's name would be: on the checklist ("Every answer was in at the end of its period, but nobody signed it off. It counts as done."), the templates list, the diary and the EHO Report Pack's Checklist Completion Log. When its last answer came after the deadline, the checklist itself, its card on the templates list and the template's page add, for example, "The last answer came after its 09:00 deadline.", and the banner on the checklist itself is amber. Like a signed-off checklist, it can't be changed afterwards.

A Team App or kiosk sign-off tapped inside the period that reaches Brikly late, because the phone or tablet was offline, still signs it if it arrives within 48 hours of the period ending. The checklist then names the signer and the real sign-off time. As for any checklist, its answers decide whether it is late, not the sign-off. If its answers were in by the deadline, it keeps its on-time credit and reads Answered by end of period, signed off later, with the real sign-off time: on the checklist itself, its card, the template's page, the diary and the EHO Report Pack. If they weren't, it reads Signed off late. See Late checklists.

Missed checklists​

If a checklist isn't signed off by the end of its day, week or month, and isn't fully answered either, it is recorded as Missed. A missed checklist can't be filled in. The web, the Team App and the kiosk all say so plainly, for example:

This checklist was missed. It needed doing by the end of Sun 12 Oct, so it can't be filled in now.

Missed checklists leave the Team App's list and the kiosk's list. They show as Missed in the Team App's History, the diary, the 4-weekly review and the EHO Report Pack, so the record stays honest. One-off checklists are never missed.

Closed checklists​

On a day a site is closed, its checklists nobody had started show a grey Closed pill. A closed checklist opens read-only: "The site was closed that day, so this checklist wasn't needed." It is neither done nor missed, and it is left out of the safety score and the Missed counts, unless answers taken offline before the closure arrive later (see Closed today). Closed checklists leave the Team App's and the kiosk's lists, and show as Closed in the Team App's History, the diary and the EHO Report Pack.

Signed-off checklists​

Opening a signed-off checklist shows what was recorded, read-only, under a banner with its status and when it was signed off and who by, for example Signed off with "Mon 6 Oct 2026 at 09:12 by Maya Patel" ("by Maya Patel on Burford tablet" when it was completed on a kiosk). A late one reads Signed off late, adding "after its 09:00 deadline", or Answered after its deadline, signed off (signed off by the deadline, but its last answer came after it), adding "The last answer came after its 09:00 deadline." Both have an amber banner. One answered by the deadline and signed off after it reads Answered by end of period, signed off later. See Late checklists. An answer given on a kiosk is listed with its time and the tablet, for example "on Burford tablet", beside the person's name. Tick answers read Done, Not done with its reason, or N/A. Every reading for an item is listed, with its time when there are several and its corrective action, and under the action its follow-up or Add a check-again time (see Adding a check-again time). Temperatures are written as they were taken (4.5°C).

A signed-off checklist is locked on every surface: the web, the Team App and the kiosk. No more answers, photos or sign-offs can be added, and it can't be reopened. Answers that hadn't saved before it was signed off show under "These changes weren't saved before this checklist was signed off", with Discard.

On the Team App​

Staff see today's checklists for their site on the Safety screen. Weekly and monthly checklists stay on the list for their whole week or month, and one-off checklists from their date until they are done. Each one shows a status (Not started, In progress, Overdue, Completed or Missed) and a line such as "Due 14:00", "Due by Sun 11 Oct" or "Can still be done until Sun 11 Oct". A one-off shows its own deadline, or "One-off, no deadline". A checklist whose last answer came after its deadline shows a Late pill and "Completed late, after its 09:00 deadline". Pull the list down to refresh it.

History lists the last 30 days of completed, missed and closed checklists, with the day or week each one was for. Open it from the History card on the Safety screen ("Completed, missed and closed checklists from the last 30 days."), which is there even when today's list couldn't be loaded. Closed ones have a grey Closed pill. With nothing to show it reads "No completed, missed or closed checklists in the last 30 days."

Which sites staff can do checks at​

The Safety screen shows checklists, cleaning and history for one site. Staff can do checks at:

  • their primary location, set on their employee profile;
  • the site they are clocked in at right now, even if it isn't their primary location or they have none;
  • the only site, in a business with one site.

Staff with Owner or Manager Team App access can do checks at every active site, without clocking in.

When someone can do checks at more than one site, Change site appears beside the site name, listing each site with why it is there ("You're clocked in here", "Your primary location", "Your business's only site" or "You can check every site"). A choice lasts until they clock in or out somewhere else. Clocking out ends access to a site that isn't their primary location straight away.

A site someone isn't set up for says so, with Retry, rather than showing an empty list: "You're not set up to do checks at this site. Clock in here to do its checks, or ask a manager to make it your primary location." Someone with no site at all sees "You're not set up to do checks at any site yet. Clock in at a site to do its checks, or ask a manager to set your primary location." If Brikly can't check at that moment, the app says "Couldn't check which sites you can work at. Try again shortly."

Closed today​

On a day the site is closed, the Safety screen says Closed today (or, for example, "Closed today: Christmas Day"). Under it, "No checklists are needed today." when nothing listed is still open, or "Nothing new is due today. The checklists below can still be done." when a weekly, monthly or one-off checklist is still open.

If someone recorded answers offline before the site was marked closed, and they reach Brikly afterwards, they still count if they arrive within 48 hours of the end of the checklist's day, week or month. The checklist goes back to In progress, with each answer at the time it was taken, and takes the rest of its answers as usual. If nobody finishes it, it is Closed again at the end of its day, week or month, never Missed, and answers that arrive after that aren't recorded. Answers taken after the site was marked closed count too once answers taken before the closure have put the checklist back to In progress, as they would have had those earlier answers arrived first. A phone sends its saved answers in the order they were taken, so its earlier ones go first. While the checklist is still Closed, answers taken after the closure aren't recorded (from another phone that reconnects first, say): they stay under Saved records with "The site was closed that day, so this checklist can't be filled in." Answers that had already reached Brikly keep the checklist open, so it can still be finished.

Readings and corrective actions​

  • Temperature and number fields take a minus sign and a decimal point: the iPhone keyboard has a minus key, and Android uses its signed number pad. A comma works as a decimal point ("3,5"). Readings are rounded to 2 decimal places, as they are saved. Anything that isn't a number shows "Enter a number, such as -18 or 4.5." and is not sent.
  • Each field shows its range, for example "Acceptable: 1°C to 5°C", "-18°C or colder" or "63°C or hotter".
  • A number too large to record is refused with "That number is too large to record. Check the reading and enter it again."
  • An out-of-range reading taken on an earlier day of a weekly or monthly checklist names the day, for example "9°C at Mon 5 Oct, 08:10 was out of range."
  • Tick items: tapping YES, NO or N/A again on the answer just sent (or already saved) sends nothing, and tapping a different one always sends it, so an answer mis-tapped offline can be put right by tapping the right one.
  • An out-of-range reading is held with "(reading) is out of range (acceptable: ...). Say what you did, then save the reading." and a required What did you do? box, with Save reading and Discard this reading. The field is locked while it waits. The reading and what was done are saved together, also offline, with the time the reading was taken. Saved on the phone, it shows "What was done: ..." and "Saved on this device. It will be sent when you're back online."
  • An out-of-range reading already saved without a corrective action (from another phone, say) gets its own What did you do? box.
  • A corrective action is recorded as done, with the time the reading was taken on the phone, so one given offline before midnight stays on that day in the diary and the EHO Report Pack.

Photos​

Take another photo records a new answer for a photo item. Another photo needs a connection: offline, the app says "Another photo needs a connection. Try again when you're back online." before the camera opens.

Offline answers​

Answers, photos and corrective actions given without a connection are saved on the phone with the time they were given, and sent when the connection returns. They still count if they were given inside the checklist's period and reach Brikly within 48 hours of the period ending. An answer recorded while clocked in at a site still counts after clocking out, as long as it was given during that shift. Sending one again that Brikly already has is always confirmed, never refused. Anything that doesn't count stays under Saved records, marked as needing review, with the reason, so a manager can note it. That includes answers for a site switched off since ("This site is closed, so its records can be read and printed but not changed."), an answer for an item changed since ("One of these answers is for an item that isn't on this checklist. Reload the checklist and try again." when the item already had answers and was replaced, or "This answer doesn't suit this item, which may have changed since the checklist was opened. Reload the checklist and answer it again." when its type changed before anyone had answered it) and a number too large to record ("That number is too large to record. Check the reading and enter it again."). See Saved records and offline working.

If SafetyBrik is switched off for the business, or the business account isn't active, records saved on the phone are not thrown away and not refused. They stay under Saved records as Waiting to sync, with "SafetyBrik is switched off for this business, so this hasn't been sent yet. It will be sent when SafetyBrik is switched back on." (or the account's own sentence), and are sent by themselves once it is back: straight away when the app sees it, otherwise within about five minutes, or when someone taps Retry sync. Brikly then judges them by the rule above. Online, a check refused because SafetyBrik is off says "SafetyBrik is switched off for this business, so safety checks can't be recorded. Ask your manager.", and the Safety tab and the Safety card on Home go.

Signing off​

The sign-off sheet says what is still to do, for example "To sign off, answer 1 required item and add what you did about 2 out-of-range readings." If Brikly refuses a sign-off, the checklist reloads and marks the items that still need something. One that had already gone through says "Already signed off".

Signing off needs a connection. The sign-off is not saved on the phone. If Brikly can't be reached, the app says, for example: "Can't reach Brikly. Sign off again once you're connected. It needs signing off by the end of Sun 11 Oct." Tap Sign off again as soon as you're back online. If the app stays open, a sign-off first tapped inside the period still counts when it reaches Brikly within 48 hours of the period ending. Arriving after the deadline doesn't make it late: only when the answers came in decides that. If the app has been closed in between, the sign-off has to reach Brikly before the period ends. Otherwise the checklist is closed as Answered, not signed off when every answer is in, or recorded as Missed when it isn't.

Follow-ups​

When someone adds a follow-up to a corrective action on the web ("check again by 14:30"), it shows on the Team App for the people who need to check it.

  • On the Safety screen, a Follow-ups card sits above Cleaning while there are follow-ups to check at the site, for example "2 follow-ups to check · 1 past its check time". The Safety today card on Home mentions them quietly, for example "2 open · 1 follow-up · tap to view". The card is hidden when the count couldn't be refreshed, rather than showing an old number. Pull the Safety screen down to refresh it.
  • Who sees which. Each person sees the follow-ups that are for them, whether a manager chose their staff record or their Brikly web login. Staff with Owner or Manager Team App access see every follow-up at the site. A follow-up left without a person is for whoever recorded the corrective action. The list covers the site they are working at, plus follow-ups for all sites.
  • The Follow-ups screen lists them soonest first. Each one shows what it is for (the checklist item with its checklist, or the equipment with "Temperature reading"), What was done, the time to check by ("Check again by 14:30", or "Check again by Thu 8 Oct, 09:00" on another day), a red Past its check time pill once that time has passed, and "For you" or "For (name)".
  • To close one, write what you found in What did you find? and tap Mark done. A note is required: "Say what you found before you mark it done." The follow-up leaves the list straight away.
  • Closing needs a connection. Nothing is saved on the phone: offline, the app says "Can't reach Brikly. Check your connection and try again." and keeps your note.
  • Already closed. If the follow-up was closed already (often your own earlier Mark done that did go through), the app says "Already closed" and "This follow-up has already been closed."
  • Site closed. At a site that has been switched off since, the app says "Site closed" and "This site is closed, so its records can be read and printed but not changed."
  • With nothing to check, the screen reads "No follow-ups to do here." If it can't be loaded, it says so with Retry.
Keep the apps up to date

The site choice, the Closed today screen, corrective actions on the phone, follow-ups, minus signs in temperature fields, the History card, cleaning sign-offs that keep the time they were done offline, and sign-off photos on the phone need the latest Team App. Staff on an older version won't see the Follow-ups card or screen. The 48-hour allowance for offline answers, and keeping saved records while SafetyBrik is switched off, need the latest Team App and Brikly Kiosk app. Older versions can't send offline checklist answers once the checklist's day, week or month has ended, so ask your team to update.

On the kiosk​

The kiosk lists its site's checklists for today, with weekly and monthly checklists listed for their whole week or month, and one-off checklists from their date until they are done, with their deadline. Missed and closed checklists are not shown. When the list is empty it reads "No checklists to do here today." Each checklist shows when it is due ("Due today 12:00", "Due by Sun 11 Oct") or, past its deadline, Overdue (adding "Can still be done until ..." for a weekly or monthly). One whose last answer came after its deadline shows a Late pill, and "Completed late" on its screen.

On a closed day the list says Closed today (with the reason, for example "Closed today: Christmas Day") and "The site is closed today, so no checklists are needed." If a weekly, monthly or one-off checklist is still open, it reads "Today's checklists aren't needed. Anything still open below can still be done." A closed checklist opens read-only with a grey Closed banner.

Signed in on the kiosk​

While someone is signed in, a bar across the top of every screen, Home included, reads "Signed in as Maya Patel" with Sign out, so whoever is at the tablet can see whose name their answers will carry. Sign out signs them out straight away.

While their checklist answers are sending, the button reads Sending answers and waits until they have gone, so they land and the person sees how it went. A submit only takes a few seconds. If the person is signed out some other way while it is still sending (after a minute without a touch, say), whatever hadn't gone yet is never sent under whoever signs in next: answers are saved on the tablet under the person who pressed Submit and sent later, and a photo that hadn't gone is not saved.

Filling in a checklist on the kiosk​

  • Temperature and number fields take a minus sign and a decimal point, and read a comma as the decimal point. Anything that isn't a number shows "Enter a number, such as -18 or 3.5." and is not sent. A comma before exactly three digits ("1,000") could mean a thousand or one, so the kiosk asks again rather than guessing.
  • The expected range shows under the field, from the linked fridge or freezer when there is one: "Expected range: 1 to 5°C", "Expected at most -18°C" or "Expected at least 63°C".
  • An out-of-range reading turns red, says Out of range and asks What did you do?. The same box appears under any out-of-range reading already recorded without one, including readings from the Team App. Submit stays greyed, with "To submit, add what you did about the out-of-range reading.", until each box is filled. What was typed is saved as the reading's corrective action, and shows as "What was done: ..." under the reading.
  • Photo items have Take photo, which uses the tablet's camera, with Take again and Remove photo. The first time, the tablet asks for permission: "Brikly Kiosk uses the camera to add a photo to a food safety checklist." With camera access turned off, the kiosk says how to turn it on. A required photo item says "A photo is needed before this checklist can be completed." Photos need a connection: offline, the camera doesn't open and the kiosk says so. Photos are sent when Submit is pressed.
  • Answers already recorded show their value and when they were recorded, marked where they were out of range. An item removed from the checklist since it was started shows "No longer on this checklist".
  • A cleared field doesn't count as an answer. Pressing Submit with nothing to send says "Nothing to submit".
  • Answers not yet submitted are kept on the tablet for the person who typed them when the kiosk signs them out (after a minute without a touch, or at the end of the session). When the same person signs in and opens the checklist again, they are put back, with "Your earlier answers are back" and "Check them, then press Submit." Photos are not kept, so a photo item asks for its photo again: "Check them, take the photo again, then press Submit. Photos aren't kept on the tablet.", or "Take the photo again" when a photo was all there was to put back. Kept answers are dropped 12 hours after anything was last entered, once the checklist is completed, missed, closed or signed off elsewhere, and when the tablet is unpaired or paired again. An item answered since on the Team App, the web or another kiosk keeps that answer. Someone else signing in never sees them. Submit is still the only way to save.

There is no separate sign-off step on the kiosk. When someone presses Submit and every required item has an answer (and every out-of-range reading has a corrective action), the checklist is completed. It shows Completed and "This checklist is complete.", and a panel at the foot of the screen says Checklist complete and "Saved as Maya Patel.", with two buttons:

  • Next checklist goes back to the list, still signed in.
  • Done, sign out signs the person out.

If nobody chooses, the panel says "Signing you out in a few seconds." and the kiosk signs the person out after 8 seconds, so the next person at the tablet never answers under their name.

If some required items are still empty, the answers given so far are saved, the kiosk names what is left, for example "This checklist isn't complete yet. Still to do: Delivery area clear.", and goes back to the list. A submit saves everything in it, or nothing.

Without a connection, Submit saves the answers on the tablet to send later:

  • Every required item answered. The panel reads Saved on this tablet, waiting to sync, "Your answers will reach Brikly when the tablet syncs." and "Saved as Maya Patel.", with the same Next checklist, Done, sign out and sign-out after 8 seconds. The list still shows the checklist as not done until the answers reach Brikly.
  • Required items still empty. The person stays on the checklist, with no panel and no countdown. A notice above Submit reads Saved on this tablet, waiting to sync, "Your answers will reach Brikly when the tablet syncs." and names what is left, for example "This checklist isn't complete yet. Still to do: Fridge 1 temperature." The answers just saved show as read-only rows marked Saved on this tablet, waiting to sync, so they are never sent twice. They can carry on and press Submit again.
  • A photo that couldn't go. Photos need a connection, and a required photo item counts as still to do until its photo is sent. When the person stays on the checklist, the photo stays on the screen and the notice adds "Photos need a connection, so the photo wasn't sent: press Submit again once the tablet is back online." When everything required is answered and only an optional photo was held back, the panel says instead "Your answers will reach Brikly when the tablet syncs. Photos need a connection, so the photo wasn't saved: take it again once the tablet is back online."

Answers saved on the tablet without a connection count as long as Submit was pressed inside the checklist's period and they reach Brikly within 48 hours of it ending. Answers waiting on the tablet when SafetyBrik is switched off are kept, with "SafetyBrik is switched off for this business, so this hasn't been sent yet. It will be sent when SafetyBrik is switched back on.", and are sent within minutes of it being switched back on, when the same rule decides whether they count. Photos are not saved on the tablet: if the connection drops before Submit, the other answers are saved and the kiosk asks for the photo again once back online. See Kiosk devices for how saved records work on the tablet.

A new kiosk app is needed

Corrective actions, photos, minus signs, the Closed today screen, the signed-in bar and the done panel on the kiosk need the latest Brikly Kiosk app.

Where signed-off checklists go​

A signed-off checklist is filed automatically:

  • The templates list and detail page - Last done on the card and the detail page shows when the checklist was last signed off and by whom, in any period, so yesterday's daily stays there once today's copy is made: for example "2h ago by Sam Taylor", or "12 Mar 2025 by Sam Taylor" for one from an earlier year. One answered but never signed off reads, for example, "2h ago, answered, not signed off". On the All sites view, an all-sites checklist also names the site it was done at
  • The diary - the day's checklists, with their status, appear in that day's diary for the manager to sign off
  • Reports - the EHO Report Pack's summary and Checklist Completion Log
  • The Team App - under History for the last 30 days

You don't need to "file" or "archive" a checklist. Signing it off does it.

What an EHO sees​

The EHO Report Pack in Reports has a Checklist Completion Log: every checklist in the period, by date, with its category, the time it was done, who did it and its status (Signed off, Signed off late, Answered after its deadline, signed off, Answered, not signed off, Answered by end of period, signed off later, Missed, Closed, Overdue, In progress or Due). The pack's summary shows how many were signed off, how many of those were late (counted as Signed off late: their last answer came after the deadline, whenever they were signed off), how many were answered but not signed off, how many were missed, how many weren't needed because the site was closed, and how many are still open. Every checklist reading is in its Temperature Log, and corrective actions have their own section.

The answers and photos themselves stay on each checklist in SafetyBrik, so you can open any one on screen if an inspector wants to see it. It's the same evidence the paper SFBB pack provides - except it's legible, time-stamped at source, and you don't have to hunt through a folder to find last March.