Skip to main content

Cleaning schedule

The cleaning schedule is your SFBB Section 10 record - what gets cleaned, how often, with which chemical, and the PPE the person doing it should wear. It is the page an Environmental Health Officer turns to when they want to see that you are not just cleaning when something looks dirty, but running a documented cleaning programme that covers the equipment, surfaces, and high-touch areas in your kitchen.

You will find it at /safety/cleaning-schedule.

Why this is in your EHO pack​

The Safer Food Better Business pack expects every caterer to keep a cleaning schedule. The reason is straightforward - cleaning is one of the four Cs (cross-contamination, cleaning, chilling, cooking) the FSA judges your food safety on, and "we just clean as we go" is not enough on a visit. The schedule is the structured list that shows you have thought through every surface and every piece of equipment, decided how often each needs cleaning, and matched the right chemical and PPE to the job.

The Cleaning Schedule has its own section in your EHO Report Pack, grouped by frequency, with the chemical name and PPE printed alongside each item.

What you can record​

Each cleaning task has:

  • Item - what gets cleaned (for example, Coffee machine grouphead, Walk-in fridge handles, Pass shelf).
  • Frequency - how often, from the SFBB list below, or Other, which asks how often it repeats (every N days, weeks or months) with an optional name such as Quarterly.
  • Applies to - either All sites or pinned to a specific site.
  • Chemical - the COSHH chemical used for the job, picked from your COSHH register. Optional - some jobs only need water and a clean cloth.
  • PPE - which of the curated PPE codes (gloves, apron, goggles, mask) plus an Other escape hatch with a custom label.
  • Method steps - up to twenty short steps describing how to do the job. Optional, but helpful for staff who are new to a piece of equipment.
  • Notes - free text for anything that does not fit the structured fields.

The frequency options​

The form offers six frequencies, which group consistently in the EHO PDF:

  1. After use - cleaned every time the item has been used (probes, blenders, prep boards). It is a log, never Due.
  2. Every shift - signed off once each trading day, for example front-of-house tables wiped through service. The trading day starts at 4am, in the site's local time, and the form says so under the button.
  3. Daily - cleaned at least once a day (floors, bins, hand-wash sinks).
  4. Weekly - cleaned weekly, Monday to Sunday (extractor filters, walk-in shelving, oven interiors).
  5. Monthly - cleaned monthly (under heavy equipment, behind fridges, light fittings).
  6. Other - any cadence outside the standard list, such as quarterly or every 6 weeks.

The first five cover the cadences SFBB itself uses. Other asks Repeats every: a whole number of days, weeks or months, at most once a year (365 days, 52 weeks or 12 months). It can have a name too, which is optional. It shows as, for example, "Every 3 months (Quarterly)" or "Every 6 weeks", and is Due once that long has passed since it was last done. Saving an Other task without an interval says "Choose how often this task repeats.", and a number outside that range says "Enter how often it repeats as a whole number: at most 365 days, 52 weeks or 12 months."

An Other task saved before Other had an interval keeps the daily rule and reads "Other: Quarterly" until you edit it and give it one.

Linking a chemical from your COSHH register​

When you add a cleaning task, you can pin it to a chemical from your COSHH register. This does two things:

  • The chemical name prints alongside the item in your EHO report, so the auditor can see which sanitiser, degreaser, or disinfectant is being used for which job.
  • SafetyBrik suggests PPE based on what the chemical's data sheet recommends. If your sanitiser's COSHH record says gloves and goggles required, ticking the chemical pre-ticks gloves and goggles on the cleaning task. You can adjust the suggestion before saving - the toast that fires when auto-fill happens lists exactly which codes were added.

A cleaning task without a linked chemical (water-only jobs, brushing, dry wiping) is fine - leave the chemical field empty.

Why PPE is suggested, not enforced

The chemical's COSHH data sheet is the authoritative source on what PPE is needed to handle that chemical. But the PPE for a cleaning task sometimes differs - you might wear goggles when decanting a strong concentrate but skip them for a diluted spray. SafetyBrik suggests so you do not have to retype the obvious, and lets you adjust because the cleaning task knows best.

Pinning to a location​

Most cleaning tasks apply to every site you run. Leave Applies to as All sites in those cases.

Pin a cleaning task to a specific site when:

  • The equipment only exists at one site (a deck oven at the bakery, a juicer at one cafe).
  • The cleaning regime differs by site (different sanitisers, different frequencies because of usage volume).
  • A site has a specific local issue (drains that need extra attention, an extractor that runs longer hours).

Each site's tab lists that site's tasks and the All sites ones. The All sites tab lists every task, and is read only: open a task there to see it, then choose a site above to see its sign-offs and mark it done. It says "Showing every site's cleaning tasks. Choose a site above to see what's due and mark tasks done." A business with one open site opens on that site's tab.

Two active tasks at the same site (or two for All sites) can't share a name: "There's already a cleaning task called Floors here. Choose another name."

Method steps​

You can record up to twenty short method steps per cleaning task. Each step is up to 500 characters - enough for a sentence or two, not a full page. Steps render numbered in the EHO PDF, and double as a quick how-to for new staff.

Method steps are optional. If the item is obvious (Wipe table with sanitiser spray) you can leave them blank. They are most useful for equipment that has a specific routine - the [Coffee machine grouphead] backflush sequence, the [Slicer] strip-down for weekly clean, the [Combi oven] descaling cycle.

Where the data comes from​

Tasks reach the schedule, and change, in these ways:

  • Setup import - a cleaning schedule imported with the setup wizard adds each task at its site with the How often you confirmed on the review (an Other task with its interval). A task already on the schedule under that name at that site isn't added again, and confirming the same import twice never adds anything twice. An import archives the default tasks nobody has used or edited only for the cadence it gives a site a checklist for: a daily checklist replaces the after-use, every-shift and daily defaults there, and a weekly checklist the weekly ones. A default with the same name as an imported task also gives way where that task is. An All sites default replaced at some sites is kept, as a copy, at your other open sites. In first-time setup, every default task the import doesn't replace still comes, for All sites or set to each site it isn't replaced at.
  • Manual add - the Add cleaning task button on /safety/cleaning-schedule opens the form. Use this when a new piece of kit arrives or you decide to formalise an "as-needed" job.
  • Editing in place - clicking a row opens the task (how to do it, its recent sign-offs and Mark done); the pencil at the end of the row opens the form to edit it. Frequency changes, PPE updates, and notes go through the same form.
  • Default tasks - a business with no cleaning tasks yet gets a starting set of common ones. They are added once, the first time the schedule is opened at an open site, on the web or the Team App, or by a first setup import, which adds the ones it doesn't replace (see Setup import above). Once you have deleted a task they are never added again, so deleting the defaults you don't want never brings them back.

What an EHO sees​

When you download an EHO Report Pack, the Cleaning Schedule section prints as a table for each frequency. It shows the schedule as it is on file on the day you make the pack. The columns are:

  • Item - what gets cleaned.
  • Site - only in a pack for all sites: the site name, or All sites for an item that applies to every site.
  • Frequency - only for Other tasks: how often it repeats, for example "Every 3 months (Quarterly)" or "Every 6 weeks" (an older Other task without an interval prints "Other: Quarterly").
  • PPE - the PPE labels, comma-separated.
  • Chemical - the linked COSHH chemical name, or "-".
  • Method - the numbered steps, then "Notes: ..." with your notes. Every step and note is printed in full.

The section is always in the pack. When there is nothing to list it says why: "Cleaning schedule not set up." for a business with no cleaning schedule, or "No items on the cleaning schedule for this site." for a site with no items of its own or for all sites. Making a pack never creates a schedule for you: the default tasks are only added when the schedule is opened at an open site, or by a first setup import (the ones it doesn't replace).

Signing off cleaning​

Staff sign off cleaning tasks as they do them: on the web from a site's tab, and on the Team App from Cleaning schedule on the Safety screen. A sign-off can have an optional note or photo.

On the web​

Choose a site's tab to see what's due there. Each task shows:

  • Due when it hasn't been done in its current window (its day, trading day, week or month, or its interval for an Other task), or Done once it has.
  • Closed, in grey, when the site is closed for the task's whole window: a daily or every-shift task on a day the site is closed, or a weekly or monthly task whose whole week or month is closed. A Closed task isn't counted as Due, but it can still be marked done. The tab says, for example, "Station Road is closed today (Christmas Day). Tasks marked Closed aren't due, but you can still mark them done." Opening hours and closed dates are set in Settings > Locations: see Opening hours and closed dates.
  • Log use for an after-use task, which is never Due. Once it has been used it reads, for example, "3× today": today's count at that site.

Above the list, the chips count what is still due: Today (daily and every-shift tasks, for example "Today: 1 of 2 still due"), This week and This month. Click a chip to list only those tasks, or tick Show only due. When nothing is left to show, the list says "Nothing is due here right now." or "No tasks match these filters." with Clear filters.

Click a task to open it: how to do it (its PPE, method steps and notes), its recent sign-offs and Mark done (Log use for an after-use task). In a business with several sites, Mark done names the site it records at, for example "At Burford". If a sign-off can't be saved, the reason shows under Mark done and your note and photo are kept. Cancel clears the note and photo.

The All sites tab shows no sign-offs and has no Mark done. A task opened there says "Choose a site above to see this task's sign-offs and mark it done."

A site that has been switched off or removed keeps a read-only tab, for example "Station Road (closed)", while it has records: "Station Road is closed. Its records can be read and printed but not changed." Its tasks open with their sign-offs, but nothing there can be signed off, undone or voided, and its tasks can't be added, edited, archived, restored or deleted. Tasks for All sites carry on at the open sites.

If the schedule can't be loaded, the page says "The cleaning schedule couldn't be loaded." with Try again.

Undo, void and where a task can be signed off​

A task's sign-off history on the web names the person and, for a sign-off made on a kiosk, the tablet, for example "Sam Taylor on Burford tablet".

Someone can undo their own sign-off within 30 minutes of when it was done; older sign-offs need a manager. Undo is a change to the record, so a viewer can't undo a sign-off, not even one they made before they became a viewer. Undoing a sign-off also deletes the photo taken for it. Owners and admins can void a sign-off made in error, with a reason: a voided sign-off stays on record and keeps its photo. If an undo or a void is refused, the reason shows in the task, and a refused void keeps its box open with your reason in it.

A task that applies to one site can only be signed off at that site. A task for all sites can be signed off at any of them. An archived task takes no new sign-offs: "This cleaning task has been archived, so it can't take new sign-offs. An owner or admin can restore it."

On the Team App​

Team App staff sign off cleaning at the same sites as their checklists: their primary location, the site they are clocked in at, or the only site of a business with one site. Staff with Owner or Manager Team App access can sign off at every active site. See Which sites staff can do checks at.

The Cleaning screen lists the site's tasks under a summary such as "Today: 1 of 4 daily · This week: 2 of 3 weekly · This month: 0 of 1". Each task says who did it last and when, for example "Last by Sam · 09:12" today, or "Last by Sam · Tue 15 Sep, 09:12" for an earlier day. An Other task shows how often it repeats under its name. An after-use task reads Log use, then, for example, "3× today". On a day the site is closed, the screen says Closed today (or, for example, "Closed today: Christmas Day"), and a task the site is closed for, as on the web, reads Closed rather than Due.

Tapping a task opens it: how often it is cleaned, the PPE in words, the method steps and notes, and the Last sign-off with its photo. Tap the photo to see it full size. Undo is offered on your own sign-off for 30 minutes. If a sign-off is refused while the phone is online (at a site that has been switched off, say, or for a task archived since), the app says Couldn't record sign-off with the reason and keeps the note and photo, and trying again doesn't upload the photo a second time.

Offline sign-offs​

A sign-off sent while the phone is online is recorded when it reaches Brikly. One made without a connection is saved on the phone with the time it was done, and sent when the phone reconnects. It counts at the time it was done if it reaches Brikly within 48 hours of the end of that task's day, week or month:

  • A daily, every-shift or after-use task, or an Other task that repeats every few days: its trading day, which ends at 4am the next morning.
  • A weekly task, or an Other task that repeats every few weeks: its week, which ends at midnight on Sunday.
  • A monthly task, or an Other task that repeats every few months: its month.

So a weekly clean done on Monday and sent on Saturday counts on Monday, and a daily clean signed off at 22:40 on Sunday counts on Sunday if it reaches Brikly by 4am on Wednesday. A later one is refused, and stays under Saved records with "This sign-off reached Brikly more than 48 hours after its day, week or month ended, so it can't be recorded now. Show it to your manager."

A sign-off done during a shift at a site still counts after clocking out there, if it reaches Brikly in time. A sign-off done before its task was archived still counts. Undo works for 30 minutes from when the clean was done, so a sign-off that arrived later than that is voided by an owner or admin if it was made in error.

These are refused when they arrive too, and stay under Saved records with the reason:

  • A sign-off for a task that was archived before it was done: "This cleaning task has been archived, so it can't take new sign-offs. An owner or admin can restore it."
  • A sign-off at a site that has since been switched off: "This site is closed, so its records can be read and printed but not changed."
  • A sign-off at a site that has since been removed: "This site has been removed, so it can't take new sign-offs. Refresh the list and try again."
  • A sign-off for a task that has since been moved to another site: "This cleaning task belongs to another site. Reload the page to see this site's tasks."
  • A sign-off for a task that is no longer on the schedule: "This cleaning task isn't on this site's schedule. Refresh the list and try again." This is rare, as a task with sign-offs can only be archived.

Sending again a sign-off Brikly already has is always confirmed.

If SafetyBrik is switched off, or the business account isn't active, sign-offs saved on the phone are kept, and sent once SafetyBrik is back on or the account is active again. Brikly then judges each one by the time it was done, by the 48-hour rule above. See Saved records and offline working.

Keep the Team App up to date

Offline sign-offs that keep the time they were done, photos on the phone, Closed on closed days and the reasons under Saved records need the latest Team App. An older version sends no time with an offline sign-off, so it is recorded when it arrives.

In the safety score​

In the safety score, the Cleaning schedule part is the share of each task's due days, shifts, weeks and months signed off in the last 28 days, at each site it applies to, so one sign-off a day doesn't cover several daily tasks. Each window counts once, however many sign-offs it has.

  • After-use tasks are never due.
  • An Other task with an interval is due once its interval has passed since it was last done (or since it was added). If nothing is signed off by then, it counts as missed from its due day. A due day that falls on a day the site is closed moves to the next open day.
  • An Other task without an interval counts as daily.
  • A task is owed nothing for its first 24 hours after it is added, restored, moved to another site, or given a new frequency or interval, and the window still running counts once it's done.
  • A change keeps the task's earlier record. Its earlier schedule still counts for the windows that ended before a change of frequency, interval or site, at the site it was at then: a daily task made weekly and back keeps its earlier misses, and a task moved to another site keeps its misses at the first site. The window running at the change counts neither way, unless an Other task with an interval was already overdue then: that stays a miss, unless it is signed off later that day. A restored task starts afresh, and so do the copies of the default tasks an import keeps at your other sites.
  • Days a site was closed are left out: a week, a month or an Other task's interval only when the site was closed for all of it.

A site with no cleaning tasks counts 0, and the all-sites figure is the average of the open sites.

Photos on sign-offs​

Cleaning photos are private to your business. On the web, a sign-off's photo shows as a thumbnail in the task's Recent sign-offs and in Records > Cleaning sign-offs, and a voided sign-off keeps its photo, greyed out. Click a thumbnail to open the photo full size in a new tab. On the Team App it shows under Last sign-off: tap it to see it full size. Photo links last an hour and are refreshed while the page is open; if one won't load, the web says "This photo couldn't be loaded. Refresh the page to try again."

On the web, a sign-off photo is turned the right way up and made smaller before it uploads, so a large phone photo is fine. A photo can be JPEG, PNG or WebP, up to 5 MB once made smaller; a HEIC photo is refused with "This photo is in HEIC format. Save it as a JPEG and try again." 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."

Cleaning sign-off records​

Records > Cleaning sign-offs lists every sign-off, newest first, with the task, how often it is cleaned, who signed it off, when, and its photo. A sign-off made on a kiosk names the tablet beside the person, for example "Sam Taylor on Burford tablet"; a renamed tablet shows its current name. Use Start date and End date to choose the days, and the site tabs if you run more than one site: All sites, each open site, and a "Station Road (closed)" tab for a site that has been switched off or removed, whose sign-offs keep its name.

  • The dates start as the last 30 days, on the site's clock (each sign-off's own site's day with All sites selected). Until you pick End date, the dates move on with the day, so a page left open overnight shows today's sign-offs.
  • Sign-offs load 200 at a time, newest first. While there are more, the count reads "Latest 200 sign-offs" with Load more under the list, and at the end it reads, for example, "312 sign-offs in range". If Load more fails, it says "We couldn't load more sign-offs. Try again." and keeps the list. If a refresh fails, the list stays with "We couldn't refresh the list. Reload the page to see the latest."
  • If the list can't be loaded at all, it says "We couldn't load cleaning sign-offs" and "Your records are safe." with Try again, rather than showing an empty list.

The EHO Report Pack includes a Cleaning Sign-off Log covering the same period and site as the pack, with a Site column when the pack covers all sites. Each sign-off shows when it was logged, in the site's local time, and who signed it off by name ("Former team member" if they are no longer on file), with "on" and the tablet's name for one made on a kiosk. A sign-off with a photo reads "Photo on file in Brikly" in the Note column: the pack never prints the photo or a link to it. A voided sign-off stays in the log, greyed out with its note struck through, followed by who voided it and why. A period with no sign-offs says "No cleaning sign-offs were recorded in this period."

Audit trail​

Every cleaning task added, updated, archived, restored or deleted writes an entry in the Audit log (Cleaning task added, Cleaning task updated, Cleaning task archived, Cleaning task restored and Cleaning task deleted). If a regular task suddenly disappears from the schedule, the audit log shows who archived it and when.

Archive, restore and delete​

  • Archive (owners and admins) takes a task off the schedule. Its sign-offs and their photos stay on record. The confirmation asks, for example, "Archive Floors? It comes off the schedule and its sign-offs stay on record."
  • Show archived (N) can be ticked by anyone, viewers included. Archived tasks are listed greyed out under an Archived heading. Open one from a site's tab to read its sign-offs: "This task is archived, so it can't take new sign-offs. Its sign-offs stay on record."
  • Restore (owners and admins) puts an archived task back on the schedule. Open the task with its pencil and click Restore. A restore is refused if the task's site has been switched off or removed, or if another active task there now has its name. A restored task is owed nothing for its first 24 hours.
  • Delete (owners and admins) is only offered for a task that has never been signed off (voided sign-offs count as sign-offs), such as one added by mistake: "Delete Floors? This can't be undone." A task with sign-offs is archived instead, and Brikly says so if asked to delete one: "This cleaning task has sign-offs, so it can't be deleted. Archive it instead: it comes off the schedule and its sign-offs stay on record."

Members can add and edit tasks, but can't archive, restore or delete them. If an archive, restore or delete is refused, the reason shows in its box, which stays open.