6 ways to automate the semi-annual bar cleaning checklist

#1 - Simple checklist

Who it's for: Single-site bars where the manager runs the twice-yearly deep clean themselves and wants the paper checklist on a phone.

What it is: A semi-annual bar cleaning checklist is the set of occasional, heavy tasks done twice a year. This version is the tick-list of 12 twice-yearly tasks, plus a notes field. It covers full strip-downs, cellar and cooling maintenance, and the areas a routine clean never reaches.

In practice: A single-site pub schedules the deep clean for a quiet week twice a year. The team strips equipment fully, services the cellar cooling, ticks each task, notes the cellar cooler is overdue a professional service, and the clean is on record with a clear date stamp for the next one.

Why it works: The list lives on the canvas, so a job done only twice a year, easy to forget entirely, actually happens and is dated. The notes field flags anything needing a contractor.

Steps included:

• 1 checklist (12 twice-yearly tasks: full strip-downs, cellar and cooling maintenance, unreachable areas)
• 1 notes field

#2 - With guidance

Who it's for: Bars where the twice-yearly clean is delegated to staff who rarely do it.

What it is: The simple checklist with a guidance note: strip equipment down following the maker's instructions, service or arrange servicing of cellar cooling, and reach the areas only touched twice a year, flagging anything that needs a specialist.

What it adds to the simple checklist:

1. The occasional, heavy jobs are spelled out and done safely
2. Staff know what to attempt and what to book a specialist for
3. The clean is consistent however rarely it runs

Why it works: The guidance sits with the list, so staff doing a job they see twice a year have the method in front of them.

Steps included:

• 1 guidance note (strip-downs and maintenance, done safely)
• 1 checklist (12 twice-yearly tasks)
• 1 notes field

#3 - With a signature

Who it's for: Bars where the deep clean needs a name against it, so you know who signed it off.

What it is: The simple checklist plus a signature captured at sign-off. The 12 tasks and the notes field stay the same; the signature confirms who did the clean and when they signed it.

In practice: A pub with a rotating team does the semi-annual strip-down, ticks each task, notes any issues, and signs. The next time the manager plans the deep clean, they know exactly who to ask about the note, not just that someone left one.

What it adds to the simple checklist:

1. A signature naming who did the clean, captured at sign-off
2. A record of when the clean was signed, next to what was ticked
3. Accountability without needing a photo

Why it works: The name goes on the record at the moment the work finishes, not from memory later. When something is found needing attention the next deep clean, the conversation starts with who signed it off, which is specific instead of general.

Steps included:

• 1 checklist (12 twice-yearly tasks)
• 1 notes field
• 1 signature (sign-off)

#4 - With photo evidence

Who it's for: Teams that want proof the work was done to standard, not just a ticked list.

What it is: The simple checklist plus a photo of the ice machine interior after cleaning, taken on completion as a record alongside the ticks. One specific, telling spot rather than a vague wide shot.

What it adds to the simple checklist:

1. A photo of the ice machine interior, captured at the time
2. Proof that holds up to an inspector, not just a ticked box
3. A visual record kept alongside the checklist

Why it works: A photo taken on completion is far stronger than a tick. It shows the state things were actually left in, not just that someone said the work was done. A single named spot like the ice machine interior is easy to shoot and easy to check.

Steps included:

• 1 checklist (12 twice-yearly tasks)
• 1 notes field
• 1 photo of the ice machine interior

#5 - With Poppi checking the photo

Who it's for: Bars where the photo gets taken but nobody reviews it. Multi-site groups where head office can't review every site's photos every deep-clean cycle.

What it is: A photo-checked clean is the simple checklist plus a photo of the ice machine interior that Poppi (AI) reviews the moment it's saved. Poppi answers one question about that photo, set by you: is the ice machine interior properly cleaned, with no scale, mould or residue? A single named spot is something an AI can actually judge, where a wide shot of the whole bar is not. If the answer is no, Poppi posts what it spotted to the team chat, so the problem gets fixed before everyone leaves.

In practice: A three-site bar group closes down and photographs the ice machine interior as always. Poppi reads the photo: clear, no buildup, no mould. Verdict yes, and nothing changes. On a rush day the photo shows mineral scale and some green growth inside. Poppi answers no and posts the reason to the team chat ("The photo shows scale and mould in the ice machine interior"). The team member sorts it and retakes the photo while still on shift.

What it adds to the simple checklist:

1. A photo of the ice machine interior that gets checked the moment it's saved, not just stored
2. A team chat message with Poppi's reason the moment a photo fails the check
3. The manager stops being the only person who ever looks at the photos

Why it works: The check happens in the seconds between the photo being taken and the cleaner leaving. That's the only moment the problem is still cheap to fix. A manager reviewing photos days later can only record that the clean was poor; Poppi (AI) catching it immediately gets it fixed while the team is still on site.

Steps included:

• 1 checklist (12 twice-yearly tasks)
• 1 notes field
• 1 photo of the ice machine interior
• 1 Poppi decision (judges the photo against your question)
• 1 Poppi action (posts to the team chat if the photo fails the check)

#6 - With a team alert if the clean is overdue

Who it's for: Bars with a scheduled cleaning deadline that sometimes gets postponed or forgotten, especially where the next deep clean falls during a busy season.

What it is: An overdue-clean alert is the simple checklist plus a Poppi (AI) action set to the workflow's scheduled completion date. If the cleaning checks aren't finished by when the clean was supposed to be done, Poppi posts a message in the Pilla team chat so the team knows it's overdue and needs to be rescheduled or completed. It watches the deadline, so it catches the clean that quietly got pushed back, not just the one that never started.

In practice: A mid-size cocktail bar schedules the semi-annual deep clean for the first Monday of June and December, with a goal to finish by end of business that day. When staffing is tight or a problem emerges, the clean gets moved to Tuesday, then Thursday, then just forgotten. With this version, if the clean isn't finished by end of Monday, the team chat gets a message flagging that the deadline has passed, so the manager knows it's overdue and can reschedule explicitly or add staff to finish it that week.

What it adds to the simple checklist:

1. A message in the team chat if the clean isn't finished by its scheduled date
2. A catch for the clean that got quietly postponed, not just the one that was skipped
3. A record of when the clean was supposed to be done, against when it actually was
4. The manager finds out that week, not months later when the next deep clean is due

Why it works: The alert is tied to the scheduled date, so an overdue clean raises its own hand. Nobody has to notice it's missing; the deadline does.

Steps included:

• 1 checklist (12 twice-yearly tasks)
• 1 notes field
• 1 Poppi action (posts to the team chat if the clean isn't finished by its scheduled date)

How to pick the right version

You don't need to know our product to choose. Every version here is the simple checklist plus one addition, so pick the additions your bar actually needs.

Do other people run this clean?

If you do it yourself and know the occasional jobs, the plain list is enough. #1. The moment rota staff do it, they need the method on the screen. #2.

Does the clean need a name against it?

If knowing it was done is enough, skip this. If you want who signed it off on the record, #3 adds a signature.

Do you need photo proof?

A ticked checklist says the work was done; a photo shows it. If you want visual proof of the ice machine interior specifically, #4 adds a photo of that one telling spot.

Does anyone actually look at the photos?

If a manager genuinely reviews every photo, #4's record is enough. If photos get taken and filed unseen, #5 has Poppi (AI) check each one as it's saved, and tell the team chat when something is wrong.

Does the clean have a scheduled deadline, and does it sometimes get postponed?

If your clean has a set calendar date and sometimes gets moved to "next week" and then forgotten, #6 posts a message to the team chat if the clean isn't finished by its deadline. If the clean always happens on schedule, #1 to #5 are enough.

Need more than one addition? Open the version with the addition that matters most in the playground and add the others as steps. That's how the product works anyway: every option here is one step added to the same list.

Related workflows

• Monthly bar cleaning checklist - the monthly clean this twice-yearly one extends
• Weekly bar cleaning checklist - the weekly clean underneath
• Daily bar cleaning checklist - the everyday clean at the base

Conclusion

The twice-yearly clean is the easiest to let slip, and the most expensive to skip. A recorded checklist with proof turns it into something scheduled and verifiable. Every version above is the same simple list plus one addition: guidance, a signature, a photo, an AI check on the photo, or a deadline alert. Pick the ones your bar needs and combine them in the playground.

→ Build your own semi-annual bar cleaning checklist on Pilla.