An allergy query mid-service, a fridge that died overnight, a delivery that turned up warm. Log it in forty seconds from the phone, give it an owner, close it with a paper trail — the difference between "an incident" and "a finding" at your next inspection.
Staff report from the phone, mid-service: what happened, where, photo if it helps. No form-hunting — incident types are presets (customer complaint, allergy query, equipment failure, delivery issue), so the report takes seconds, not a shift-end memory exercise.
Every incident has a status and a person responsible. Open incidents sit on the manager's dashboard — and on the estate view, so a complaint at one site is visible to the group the moment it's logged, not at the monthly meeting.
"What do you do when something goes wrong?" is a standard EHO question — and the follow-up is "show me." Every incident keeps its timeline: reported by whom and when, what was done, when it closed. It exports with the rest of your records in the report pack.
A customer allergy query is not "feedback" — it's the highest-stakes incident in hospitality. Blueroll links the complaint to the dish and its allergen matrix entry, so the answer to "what's in it?" is one tap, and the record shows you checked.
Incidents are included in the £24.99/month plan — like everything else. Unlimited reports, unlimited team.
Serious incidents (food poisoning allegations, allergen reactions) may need reporting to your local authority — but every incident, big or small, should be in your own records. Inspectors judge the system, not the absence of bad days.
Yes — role-based access means kitchen staff can report an incident without access to reports, settings or other sites.
They're timestamped, named and exportable — exactly the evidence you want on your side of the table.
Ten minutes to set up. Built-in UK checklists, fridge temps, allergens and sign-offs — live before tomorrow's opening checks.