Skip to main content

Building templates

A template is a reusable definition of a checklist - its name, category, schedule, and the list of items the team will work through each time it runs. Build it once, run it daily.

The builder lives at /safety/checklists/new (create) or /safety/checklists/:id/edit (edit). Click Create new checklist from the templates list to start.

Template details​

Every template has:

  • Name - what staff will see, for example "Morning opening checks"
  • Description (optional) - a sentence of context for new starters
  • Category - Opening, Closing, Cleaning, Safety or Custom (drives the colour and icon on the card)
  • Frequency - Daily, Weekly, Monthly or One-off
  • Date (one-off only) - the day the checklist is for. It starts on today and can't be a day that has already passed. See One-off checklists
  • Due by (optional) - a local time of day (HH:MM). After it, an unfinished checklist shows as Overdue, but it can still be done until the end of its day, week or month. For a one-off it is the time on its date. A checklist's first day, week or month has no deadline if it starts after this time has passed. See Deadlines and periods
  • Day of week (weekly only) - which day the instance is generated for
  • Day of month (monthly only) - 1 to 28, so every month gets an instance
  • Location - if you have multiple sites, scope the template to one site or All sites. A checklist for all sites can only link equipment shared by all sites, such as a probe: for a site's fridges, make a checklist for that site. See Which equipment a checklist can link
Pick the right category

Category isn't just decoration - it drives the filters on the templates list and the urgency colour on each card. Use Opening for first-thing checks, Closing for end-of-day, Cleaning for any cleaning schedule, and Safety for things like fire and allergen audits. Use Custom sparingly.

Item types​

Each item on a checklist is one question for the person completing it. Five types are supported:

TypeWhat it capturesUse it for
Tick (Done / Not done)Done, Not done (with the reason it wasn't done) or N/A"Is the hand-wash sink stocked?", "Bin emptied?"
TemperatureA numeric °C value with an acceptable range and an optional linked piece of equipmentFridge / freezer / hot-hold readings
NumberA numeric value with an optional rangeStock count, dishwasher rinse temperature
TextFree textHandover notes, name of duty manager
PhotoA single image, captured or uploadedEvidence of a clean, packaging photos, label checks

For Temperature and Number items, you can set a Min, a Max, or both. A range with only one side is judged on that side: a hot hold with only a 63°C minimum flags a 40°C reading, and a freezer with only a -18°C maximum flags -16°C. A reading outside the range turns the input red, and the person completing the checklist has to add a corrective action (what they did about it). The checklist can't be submitted or signed off until every out-of-range reading has one.

An item's Min can't be higher than its Max (the same number for both is fine, for an exact count). Once you leave the fields, the item says "The minimum can't be higher than the maximum. Check the range and try again.", a note above the items says "One item's minimum is higher than its maximum. Fix the range on the items flagged below to save." (or how many items, when there are several), and Save waits until it is fixed.

Probe calibrations belong in Prove It, not on a checklist: a calibration answered on a checklist doesn't count towards the Last passed calibration card, the Overview's alert, the safety score or the EHO Report Pack.

Linking temperature items to equipment​

A temperature item can be linked to a piece of equipment from your equipment register. When linked:

  • The acceptable range comes from the equipment, so the item has no Min and Max of its own
  • The reading flows into that equipment's temperature history when it is recorded
  • Updating the equipment's range updates every checklist item that's linked to it, from the next reading on - no need to edit each template

This is how you wire up a "Morning opening checks" template for one site that checks each of that site's fridges against its own range.

Equipment belongs either to one site or to all sites (shared kit, such as a probe that moves between sites). Which equipment a checklist can link depends on its Location:

  • A checklist for one site can link that site's equipment and equipment shared by all sites.
  • A checklist for All sites, in a business with several sites, can only link equipment shared by all sites. A fridge belongs to one site, so make one checklist per site for your fridges, freezers, displays and hot holds.

The builder only lists equipment that fits. If you switch a checklist to All sites while an item is linked to a site's fridge, the item is flagged, for example "Station Road's Counter Fridge can only be checked on a Station Road checklist. Make a checklist for that site, or link equipment that's shared by all sites.", and Save waits until you fix it. Brikly refuses the same thing however the checklist is saved.

A business with one site can link its own fridges and freezers to a checklist for all sites, because that checklist only ever runs at its one site. If you add a second site later, the builder flags those links and asks for a checklist per site before the items can be saved again. Until then, readings at the new site are judged against the range the item was saved with, never against another site's fridge.

Archived equipment​

Equipment that has been archived can't be newly linked to an item. An item still linked to archived equipment keeps judging its answers against that equipment's range, and keeps adding readings to its history, until you unlink it. The builder shows "The equipment linked to this item has been archived. Unlink it to choose other equipment or set a range, or ask an owner or admin to restore it in Temperature checks." with an Unlink button. It never stops you saving other changes.

Item-level options​

For each item:

  • Description - the question, for example "Front display chiller within range"
  • Type - one of the five above
  • Required - if ticked, the item must have an answer before the checklist can be signed off. Items that aren't required show Optional on the completion screen
  • Guidance text (optional) - shown below the input on the completion screen, useful for new starters or for items that need a specific procedure
  • Min / Max (number / temperature only) - acceptable range, up to 999,999.99. A bigger number is refused with "That range is too large to record. Check the minimum and maximum and enter them again." The minimum can't be higher than the maximum
  • Equipment (temperature only) - link to a registered piece of equipment

Items can be reordered with the up and down arrows. Drag-and-drop is on the roadmap.

Editing a checklist​

Open a template and click Edit to change its details or its items: add, remove or reorder items, change ranges, Required and guidance, or link other equipment.

  • Changes reach checklists nobody has started. Future checklists, and the current day's, week's or month's checklist if nobody has answered anything on it yet, pick up every change.
  • Changing the schedule reaches the current checklist at once. A new Due by time, site, frequency or day reaches today's (this week's, this month's) checklist straight away if nobody has started it. A new Due by time moves its deadline: if the new time has already gone, a checklist made before that time counts as Overdue, and an overdue notification follows within 15 minutes. A new site or a new frequency or day replaces that checklist with the new one, made straight away, with no deadline this time if its due time has already passed.
  • No change clears an Overdue. A checklist already past its deadline stays as it is, whatever you change: it is still Overdue, its alert stays, and it is Missed at the end of its period if nobody finishes it. Turning a checklist off and back on, or changing its schedule and back, never swaps it for one with no deadline.
  • A started checklist runs to the end of its period on the old settings: it keeps its deadline, its site and its period. After a change of frequency or day, the new schedule starts once it ends.
  • A checklist someone has already started keeps its items. An item added after it was started doesn't appear on it, so a newly required item never blocks its sign-off. An item removed since drops off it, unless it already has an answer.
  • Removing an item hides it from new checklists. Clearing an item's text counts as removing it. Answers already recorded against it stay in your past records. Before you save, the builder says: "The item you removed or left blank will be hidden from new checklists when you save. Answers already recorded stay in your past records, and checklists someone has already started keep their items."
  • A removed item never blocks completing a checklist, on the web, the Team App or the kiosk. Answers already given for it are still shown, and the kiosk marks it "No longer on this checklist".
  • Changing an item's type or linked equipment after it has answers swaps in a new item. The old answers stay with the old item, so a fridge's temperature history never picks up another fridge's readings. A checklist already started shows the item in its new form, unless it already has an answer for the old one, which it keeps. Someone who opened the checklist before the change and then answers the old item is refused, as it 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." On the web, the page reloads the checklist for them, with the item in its new form, and keeps what they typed for the other items. An item with no answers yet is changed in place instead, so only an answer of its old kind 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."
  • Range and Required changes apply from the next answer. Readings already recorded keep their in-range or out-of-range result, and the limits they were judged against.

The edit form fills in once the checklist has loaded, never before, so a slow or failed load can't be saved over the real checklist. If the checklist can't be loaded, the page says "We couldn't load this checklist, so it can't be edited yet." with Try again and Back to checklists. If it no longer exists, the page says "This checklist template could not be found." and "It may have been deleted, or the link is out of date.", with Back to checklists.

Your edits are never overwritten while you work. If the checklist is saved somewhere else after you opened it (in another tab, say):

  • With no edits on your page, the builder quietly takes in the latest version.
  • With unsaved edits, the builder keeps them and shows a notice: "This checklist was changed somewhere else after you opened it, so your edits here can't be saved over it. Loading the latest version replaces your unsaved edits on this page." Load the latest version fills the form with the saved checklist, so you can make your changes again.

A save made from an out-of-date page changes nothing, and the builder says: "This checklist was changed after you opened it, so your changes haven't been saved. Reload the page to see the latest version, then make your changes again." The notice with Load the latest version then appears, so you don't need to reload the page.

The builder isn't saved until you press Create checklist or Save changes, so leaving with changes you haven't saved asks first: Leave without saving?, "Your changes to this checklist haven't been saved. If you leave now, they'll be lost.", with Leave and Keep editing. Reloading the page or closing the tab gets your browser's own prompt instead. While a save is on its way, the form can't be changed, so nothing you type then is lost.

Schedules and recurrence​

The frequency you pick decides when new checklists are made.

  • Daily + Due by 10:00 - one checklist a day, overdue if not complete by 10am
  • Weekly + Day of week Monday + Due by 12:00 - one checklist a week, made on Monday and overdue if not complete by midday on Monday
  • Monthly + Day of month 15 + Due by 17:00 - one checklist a month, made on the 15th
  • One-off + Date Thu 8 Oct + Due by 15:00 - a single checklist for that day, overdue if not complete by 3pm; useful for a deep clean before an inspection, or project work. See One-off checklists

Deadlines and periods​

Every daily, weekly and monthly checklist has a period: the days it can be done on.

FrequencyPeriodExample
DailyIts own dayToday's opening checks can be done any time today
Weekly7 days, from its scheduled day to the day before it next comes roundA Monday weekly runs from Monday to Sunday
MonthlyFrom its scheduled date to the day before the same date next monthA monthly on the 15th runs to the 14th of the next month
One-offFrom its date, with no endIt stays on staff lists until someone signs it off or it is cancelled

A checklist can be done at any point in its period. Due by is the time it should be done by, in the site's local time (for a weekly or monthly, on its scheduled day):

  • Before the Due by time it shows as Due.
  • After the Due by time it shows as Overdue, but it can still be done until the end of its period. See Late checklists.
  • If it isn't signed off by the end of its period it is recorded as Missed, unless every answer is in: then it is closed as Answered, not signed off, which counts as done (see Answered, not signed off). A missed checklist can't be filled in afterwards, and it shows as Missed in the diary, the 4-weekly review and the EHO Report Pack.

A checklist with no Due by time is never overdue. It stays Due until the end of its day, week or month, then becomes Missed if nobody has done it. A one-off has no end: it is never Missed, and with a Due by time it shows as Overdue once that time has passed.

A first period with no deadline​

A checklist's first day, week or month has no deadline when it starts after its Due by time has passed. For example:

  • a new business setting up at 14:00, whose Opening Routine is due by 09:00;
  • a weekly checklist added, or turned back on, after its day's Due by time;
  • a checklist moved to another site, or given a new frequency or day, part-way through its period;
  • the first day at a new site;
  • a one-off saved for today after its Due by time.

That checklist shows Due, can be done straight away, and is Missed only if it isn't done by the end of its period. It is never Overdue or late, and no overdue notification is sent for it. From the next day, week or month it has its Due by time as usual.

Weekly and monthly checklists stay on the Team App and the kiosk for their whole week or month, so the team can do them on whichever day suits. Days and times follow the site's local time.

The builder's help text under Due by spells out the period for the frequency you have picked, for example "until the day before the same date next month" for a monthly.

Late checklists​

A checklist done after its Due by time still counts as done, with the time it was really signed off. Whether it is late depends on when its answers came in, not on when it was signed off:

  • On time - its last answer was given at or before its Due by time. Signing it off after the deadline doesn't make it late.
  • Late - its last answer came after its Due by time. Signing it off before the deadline doesn't make it on time.

A checklist with no Due by time is never late. A checklist signed off with no answers at all (every item optional and left blank) is judged by its sign-off time, as that is all there is. The same rule covers a checklist closed as Answered, not signed off: it is late only when its last answer came after the deadline.

A signed-off checklist reads by both times:

AnswersSigned offReadsLate?
By the deadlineBy the deadlineSigned offNo
By the deadlineAfter the deadlineAnswered by end of period, signed off laterNo
After the deadlineAfter the deadlineSigned off lateYes
After the deadlineBy the deadlineAnswered after its deadline, signed offYes

The last one can happen when a checklist is filled in on more than one phone or tablet, or offline, and an answer reaches Brikly after the sign-off. Where each shows:

  • on the web, the checklist, its card and the template's page use these words. On the checklist itself, Signed off late adds "after its 09:00 deadline", and Answered after its deadline, signed off adds "The last answer came after its 09:00 deadline." under an amber banner;
  • the Team App and the kiosk show a Late pill on a late checklist;
  • the diary pill uses the same words with the sign-off time, for example "Signed off late 09:12";
  • the 4-weekly review and the EHO Report Pack count every signed-off checklist that is late (both late rows above) as Signed off late. The pack prints each one's status in these words, with the time it was signed off, and shades late rows amber.

In the safety score, a late checklist counts half, signed off or not, and an on-time one counts in full, whenever it was signed off. A Team App or kiosk sign-off made in time but sent later (because the phone or tablet was offline) keeps the time it was really done.

Closed days​

A site is closed on a day when its opening hours say so, when a closed date covers it, or when someone marks it Closed today. Opening hours and closed dates are set in Settings > Locations: see Opening hours and closed dates.

  • Nothing is made for a site on a day it is closed.
  • Checklists for that day that nobody had started become Closed: neither done nor missed. They are left out of the safety score, the 4-weekly review's counts and the Missed checklists, and the diary needs no signature that day.
  • Nothing is overdue at a site that is closed today, including a checklist someone started before the site was marked closed.
  • A weekly or monthly checklist is only Closed if the site was closed for its whole week or month. Otherwise it can be done on any open day, and it is Missed if nobody does it.
  • A deadline never falls on a closed day. The Due by time moves to the first day in its period the site is open: a weekly due on a Monday, at a site closed on Mondays, is due on the Tuesday at the same time, and isn't late for being done then. A one-off whose date falls on a closed day is due on the site's next open day.
  • Start still works on a closed day. A checklist someone opens on a day that is already closed is theirs to fill in. If it isn't signed off and the site was closed for its whole day, week or month, it is recorded as Closed, not Missed.

See Closed days for Mark closed today.

One-off checklists​

A one-off is a single task for a date, such as a deep clean before a visit, or checking a new fridge on the day it is delivered.

  • Date and Due by. Pick the date (it starts on today, and can't be a day already gone: "That date has passed. Choose today or a later date for this one-off checklist."). Due by is optional and is the time on that date.
  • It is made when you save. Staff see it on the web, the Team App and the kiosk from its date until it is done. For All sites in a business with several sites, each site gets its own copy. A one-off for today whose Due by time has already passed has no deadline: it is never shown as Overdue.
  • It is never Missed. After its Due by time it shows as Overdue until someone signs it off.
  • Changing its date, deadline or site moves the copies nobody has started. Copies already started or signed off stay as they are.
  • The templates list and the detail page show it as, for example, "One-off on Thu 8 Oct". Start checklist opens the copy made when it was saved and never makes a second one.

Cancelling a one-off. Owners and admins see Cancel checklist on a one-off's detail page. The confirmation reads: "Staff who haven't started (checklist name) will no longer see it. If someone has already started it, they can still finish it (with no deadline), and anything already recorded stays in your records." Copies nobody had started disappear. A copy someone had started stays open to finish and is never shown as overdue again. The detail page then says "This one-off checklist was cancelled. Staff no longer see it, unless someone had already started it."

Permissions​

RoleCan completeCan create templatesCan edit templatesCan turn off templates
ViewerNoNoNoNo
MemberYesYesYesNo
AdminYesYesYesYes
OwnerYesYesYesYes

In practice: anyone past viewer can build templates, but only owners and admins can turn them off. Checklists aren't deleted, so a checklist's history always stays in your records.

A few more actions are for owners and admins only:

  • Turning a checklist off or back on. A member who tries gets "Only an owner or admin can turn a checklist off or back on. Ask one of them to do this."
  • Cancelling a one-off checklist.
  • Mark closed today, and its Undo, and changing opening hours and closed dates in Settings > Locations.

Turning a checklist off​

Owners and admins can turn off a daily, weekly or monthly checklist that is no longer needed, with Turn off on its page. The confirmation says what happens, for example for a weekly: "No new checklists are made. This week's checklist goes if nobody has started it and it isn't overdue yet. One that is overdue, or that someone has started, stays and can still be finished; if it isn't finished by the end of the week, it's recorded as Missed. Everything already recorded stays in your records. You can turn it back on at any time."

Once it is off, staff stop seeing it, except a checklist that was already started or overdue. The page shows a Turned off badge and "This checklist is turned off. No new checklists are made, and staff only see one that was already started or overdue." On the Checklists list it is hidden until you tick Show turned-off checklists (N), which anyone can tick, viewers included.

Turn back on brings it back. Staff see it again straight away, and the current day's, week's or month's checklist is made at once, unless one is still there from before. A new one whose due time has already passed has no deadline this time, and can be done until the end of its period. One still there from before keeps its deadline, so one that was already overdue stays overdue.

Both are in the audit log, as Checklist turned off and Checklist turned back on. A member who tries is told "Only an owner or admin can turn a checklist off or back on. Ask one of them to do this." A one-off is cancelled rather than turned off: see One-off checklists.

Turning every checklist off doesn't switch off the rest of SafetyBrik: the safety score's daily history is still kept, and safe method, risk assessment and 4-weekly review reminders keep coming.

Saving and going live​

Click Create checklist (or Save changes when editing). The template appears on the list immediately, and the checklist for the current day, week or month is made straight away, with no deadline this time if its due time has already passed. Your team sees it on Today, the Team App and the kiosk at its site. A weekly or monthly checklist created part-way through its week or month appears for the current one, and Start checklist on the web opens it.

A one-off is made as soon as you save it. Nothing is made for a site on a day it is closed.

What's next​