Restaurant audit: from score to action plan, step by step

An audit is only worth what it triggers. The score tells you where to look; the action plan tells you what changes. Each finding becomes an action with an owner, a due date, expected proof and a closing check. Without that, the next audit will find the same findings with a barely different score.

The report received on Tuesday, forgotten by Thursday

An outside firm audits the first site of a group. The report arrives by email: an overall score, several pages of findings, red and orange boxes. The owner skims it and forwards it to the manager with "let's look at this." The manager reads it in turn, deals with the easy findings, forgets several, and does not know who to give the rest to. At the next audit, the score has barely moved. Several identical findings come back.

Nobody failed: the report describes, it does not delegate. Between the finding and the action, a link was missing.

Why audits stay without effect

• The report is a document, not a task list. It stays in the inbox or the shared folder.
• All findings are handled on the same level. A food safety breach and a missing poster do not have the same urgency, but both sit in the same column.
• The score grabs the attention. People discuss the number and how it compares with the previous audit, not what has to change.
• Nobody is named. "The team" or "the site" are not owners.
• Closure is assumed. An action is considered done because someone said it would be.

From finding to action: the sheet template

An action sheet fits on one line. It is created the same day as the finding, not a week later.

Field	Fictional example
Finding	Opened products not dated in the walk-in
Severity	Food safety: handle immediately
Probable cause	Dating rule not posted at the station
Action	Post the rule, add the task to the prep routine
Owner	Site chef
Due date	End of the week
Expected proof	Photo of the station + task signed over one week
Verified by	Manager from another station
Status	Open, in progress, closed

The steps of an action plan that holds

1. Classify the findings on audit day. Critical or safety first, then improvements. The auditor's grid should allow this.
2. Look for the cause before the action. "Not dated" can mean unknown rule, forgotten step, missing labels. The action differs.
3. Create one action per finding, with a name. A person, not a department.
4. Set a realistic due date. Better two actions kept than ten postponed.
5. Plan the proof at creation. Photo, log, updated document: whatever will show it is done.
6. Have someone else verify. Closure is observed, not declared.
7. Review in a weekly check-in. Ten minutes with the manager: open, overdue, closed. Escalate to the owner whatever is blocked.

Preparing the audit so that it produces actions

The action plan is prepared before the visit. Ask the auditor in what format they hand over their findings, and prepare an action table ready to receive each one. Make sure a manager attends the verbal debrief, with the means to note down owners. Set the date of the first follow-up check-in at the outset, before even reading the report. When all of this is ready, the report no longer falls into a void: it arrives in a circuit that is already in place, with people and deadlines.

Mistakes that cancel the effect of an audit

• Aiming for the score rather than the finding. You erase the visible symptom and the root stays.
• Multiplying actions. Dozens of simultaneous actions will be followed by nobody.
• Closing without proof. An action marked "done" with no trace will reappear at the next audit.
• Using the score to rank sites or managers. Teams learn to disguise rather than correct.
• Forgetting to link the finding to the process. If training or scheduling is the cause, the action must address it.

Auditing internally, without waiting for the firm

The same circuit works for a monthly check round done by a manager at another manager's site. A short grid, ten points chosen from your past findings, a finding recorded with a photo or a reading, and actions created on the spot. The outside perspective prevents habit from setting in, and the exchange between managers spreads good practice from one site to another.

Three indicators to follow

• The number of actions from the last audit still open, with their age.
• The share of findings that reappear from one audit to the next.
• The delay between the finding and the first recorded action for food safety findings.

Where Tsuno comes in

Tsuno keeps standards, incidents and tasks with their history: an audit finding can become a task assigned to a station, followed until closure, with the date and the person who signed it. Checklists, training and scheduling rely on the same standards, which lets you fix the cause rather than the symptom. You can ask in plain language: "What have my managers not dealt with?" Tsuno does not score sites or people and does not replace the auditor: it keeps the record. See the solution page.

To continue

The full logic is in digital HACCP: what software should actually remove. Also read compliance theater, why restaurant incidents keep repeating despite reports and the closing checklist.

Key takeaway

An audit has value only through the actions it creates. One line per finding, a name, a due date, proof, a check by someone else. The score comes last.