Cleaning gets done when it is somebody's named job at a named time, and skipped when it is everybody's job whenever there is a gap. This is how to split the work into daily, weekly and monthly, and how to write the schedule so the deep-clean tasks stop quietly vanishing.
Last updated
Most cleaning schedules are organised by room, and that is why they fail. A room-based list makes every task look equally urgent, so the ones that only matter monthly get done never and the ones that matter daily get done twice.
Sort by how often the task has to happen, then by area inside each frequency. Now the daily list is short enough to finish in a shift, and the monthly list is a separate conversation that gets scheduled rather than squeezed.
| Frequency | Typical tasks | Who usually does it |
|---|---|---|
| Every shift | Surfaces, front of house, bins, spot-mop, restock | Whoever is on, as part of close |
| Daily | Full floor, toilets, equipment wipe-down, fridge fronts | Closing shift, one named person |
| Weekly | Behind and under equipment, shelving, glass, outdoor area | Rostered as a task, not assumed |
| Monthly | Extraction filters, deep-clean of cold storage, high dusting, drains | Scheduled with time allowed for it |
A cleaning schedule with a task and a tick box records that something happened. It does not record who, or when, which is exactly what you need to know when it turns out it did not happen.
Four columns is the whole schedule: the task, how often, who is responsible on that run, and the time or trigger. "Mop the floor" is a wish. "Mop the floor — closing shift, after the last table leaves" is an instruction.
The gap between two staff members' idea of "clean the coffee machine" is where the argument lives. The fix is not supervision, it is one more clause on the line.
Name the method and the product where it matters, and the standard where it is measurable. Where a task exists for food-safety reasons, say so on the line — people skip tasks they think are cosmetic, and rarely skip ones they know are not.
These are the ones that are never on the daily list, are always somebody's next-week problem, and are the ones an inspection or a breakdown finds first.
Cleaning and sanitising requirements for food businesses are set by your state or territory food authority under the Food Standards Code, and what you must record varies by the kind of business you run. We are not going to print a rule here and have you rely on it — check your local food authority and write the requirement into your own schedule as a note.
What is true everywhere: a completed record is worth more than a laminated plan. If a temperature check or a sanitising step is part of your food-safety program, the cleaning schedule is the natural place for it to be signed off, because it is the list somebody is already holding.
A printed schedule by the sink is read carefully for a fortnight and becomes furniture after that. It cannot tell you whether anything was done, so nobody is ever asked, and the weekly tasks are the first to go.
The moment to change something is not a headcount — it is when you find yourself asking whether the weekly clean happened and there is no way to answer. A list that records who ticked what, and when, turns that into a question with an answer.
Send the cleaning list as a link and staff tick items off on their own phones — no account, nothing to install. You can see what was done and what was not, and finished runs are kept. Free on every plan.