From WhatsApp groups to corrective actions

Every multi-branch operation has the group. "Chiller 2 is at 9 degrees again." Three thumbs-up, a voice note, somebody says they will call the technician. Two weeks later the same message, from a different shift, and nobody can say whether the technician came.

The group is not the problem — people should talk. The problem is that a message has no owner, no due date and no ending. Here is what changes when a fail becomes a corrective action instead.

A fail gets a number

The moment a critical check fails, a case opens: CAPA-0012, walk-in chiller at 9 °C, Downtown / Kitchen, raised by the person who saw it, with the photo they took. It has a status — new, investigating, action planned, verified, closed — and it appears on one board for the whole company. Nothing about it depends on who is in which chat.

A root cause gets written down

"Chiller broken" is a symptom. "Door gasket split, condenser coil blocked, no maintenance since March" is a root cause, and it changes what the fix is. Asking for the root cause in a field, before a plan can be saved, is the single habit that stops the same failure returning under a new case number.

A plan gets an owner and a date

Somebody's name, a date, and the steps. If the plan needs a technician, the case links to a maintenance ticket with an SLA — four hours for a critical asset — a provider, and an escalation path when the SLA is about to be breached. If the fix means the line must not restart until a chef and a safety officer sign, that is a hold point, and it blocks the restart until both have.

Closing means proving

A case is not closed because someone typed "done". It is closed when the check that failed passes again — with the photo — and the owner marks it verified. The evidence sits on the case, next to the original fail, for the next inspection.

What the owner sees

Open cases by branch. The oldest open case and how many days it has waited. Which assets keep failing — three tickets in fourteen days is a pattern, not bad luck. This is the view that the group chat could never produce, and it is the view that decides where the next maintenance budget goes.

In ServWay a failing critical check opens the CAPA case for you, equipment tickets carry the SLA, provider and escalation, hold points block the work that needs a signature, and the CAPA board shows every open case across every branch — in the language each person works in.