
Following up without a spreadsheet means giving every decision four attributes the moment it is made: a named owner, a due date, a planned reminder and the proof you expect once it is done. Spreadsheets fail because they depend on someone keeping them current, and they never chase anyone. AI helps with one specific job: turning a sentence said in a meeting into a prepared task the manager confirms, then flagging what is overdue without turning it into a trial.
Tuesday, 11:20 a.m., by the walk-in
Prep is nearly done. Élodie, the kitchen manager, walks past the walk-in fridge and runs her hand along the door seal. It is still torn at the bottom corner. She remembers it well: item 7 on the internal audit three weeks ago. It came up at the following Monday's meeting, where the team agreed seven actions.
Nicolas, her sous-chef, set up a shared spreadsheet called "Action tracker". Week one: all seven rows filled in, color-coded. Week two: two rows updated. Week three: nobody opened it. The refrigeration engineer was never called back. The storeroom labels were redone, but nobody recorded it. And Sabrina's closing training "will happen when things calm down".
Élodie does not conclude that her team is careless. She reaches a fairer conclusion: "We said it. We just never wrote it anywhere that comes back on its own."
The scene is fictional. Plenty of kitchens will recognize it.
Why agreed actions get lost
A spoken decision has no owner
"We should get that seal replaced." That "we" is nobody. Everyone agrees, and that is the problem: agreement feels like the matter is settled. After the meeting, everyone goes back to their station and the action stays in the room.
A spreadsheet needs a keeper
A tracking sheet chases no one. It waits to be opened. It lives on the office computer, not on the kitchen tablet. It survives as long as its keeper remembers it. The day that person goes on holiday, moves to another site or simply has a heavy weekend, the sheet stops, and nobody notices.
The deadline stays vague
"Next week", "before summer", "as soon as we can": none of these trigger anything. Without a date, the action is never late, and nobody chases it.
"It's done" is not proof
Actions are often closed with a remark made in passing. The box gets ticked. Nobody looks. At the next audit, the same issue comes back with a slightly different score. That is the pattern described in restaurant audits: moving from a score to an action plan: an issue that is never checked at closure always returns.
Chasing that feels like blame
When the only follow-up happens at the pre-shift briefing, chasing happens in front of everyone. "Sabrina, the fridge engineer, still nothing?" Nobody likes being caught out in front of colleagues. Next time, "it's done" will come a little faster. The follow-up then produces green ticks, not finished actions.
The four-attribute rule
An action only leaves the meeting if it has all four attributes. Otherwise it is still an idea.
- One owner, one person. Not "the kitchen", not "the evening team". The owner can get help, but one person answers for the action.
- A due date, an actual day. Specific and realistic. If you cannot set one, the action is too big: split it.
- A reminder, planned from the start. The day before the deadline for a short action, halfway through for a longer one. The reminder goes to the owner, not the whole team.
- Proof that it is done. Agreed at the same time as the action: a photo, a reading, a quote received, a checklist item, a validated skill, or a second person checking.
A fifth element makes the rest worthwhile: the source. An action that knows it came from audit item 7, or from the incident on November 3, lets you close the original item once it is done. Without that link, you have tasks on one side, audits on the other, and nobody knows whether the issue was really dealt with. It is also what stops incidents from repeating, as we explained in why restaurant incidents keep repeating despite reports.
What AI adds, and what it does not do
The rule stays the same with AI. What changes is the data entry, the part that eventually makes people give up on the spreadsheet.
From a sentence to a task
Walking out of the meeting, Élodie says: "Sabrina replaces the walk-in door seal by Friday, with a photo." The assistant prepares a task: the action, Sabrina as owner, Friday as the due date, a photo as the expected proof. It sums up what it is about to create. Élodie reads it, corrects it if needed, and confirms. Nothing is created without that "yes".
If the sentence is vague ("someone should call the fridge engineer"), a good assistant does not pick a person on the manager's behalf. It asks: "Who's taking it, and by when?"
Reminding at the right moment
A useful reminder arrives once, at the right time, to the right person. Not every hour, not to the whole team. The day before the deadline, Sabrina sees the task. If she needs help reaching the supplier, there is still time to say so.
Flagging what is overdue without putting anyone on trial
Wording matters. "Walk-in door seal: due Friday, no photo yet." The task is late, not Sabrina. The next line offers a way forward: move the date, reassign it, or ask for help. Often the delay has a mundane reason: a part has not arrived, or the schedule left no time.
Linking the action to where it came from
When a task comes from an audit or an incident, that link should be visible. At the next audit, you can see that item 7 was dealt with, when, by whom and with what proof. Or that it was not.
What it does not do
It does not decide who does what and creates nothing on its own. A lateness rate never becomes, in its hands, a score for a person. Tsuno brings the facts together. People decide.
The table: what a well-written action looks like
| Action | Owner | Due date | Reminder | Proof |
|---|---|---|---|---|
| Replace the walk-in door seal | Sabrina | Friday | Thursday morning | Photo of the new seal, invoice attached |
| Call the fridge engineer back for a quote | Élodie | Wednesday | Tuesday after service | Quote received, attached to the task |
| Relabel the storeroom tubs | Nicolas | Monday | Saturday | Photo of the storeroom, checked by Élodie |
| Train Sabrina on closing | Élodie | In two weeks | Halfway through | Skill validated and dated |
| Check the walk-in door every night this week | Closing lead for the night | Every night until Sunday | At closing | Item on the closing checklist |
| The version that dies: "We should look at the fridge" | We | Soon | None | None |
The last row is the one teams write most often. It looks like an action. It has none of the attributes of one.
Common mistakes
- A shared owner. "The morning team" will never open the task. Name one person, even if they delegate afterwards.
- Too many actions at once. Fifteen actions after an audit means fifteen half-done actions. Better to hold five, then move on to the next ones.
- Reminding everyone. A notification sent to ten people is read by none. The reminder goes to whoever has to act.
- Closing without proof. An action closed without proof is an action you hope is done.
- Running two systems. The spreadsheet kept "for now" beside the tool: after a month, neither is up to date.
- Turning lateness into a people metric. Once follow-up is used to blame, boxes get ticked too early. We cover this in compliance theater.
What to measure
- The share of actions that have all four attributes when they are created. Out of ten agreed actions, how many have an owner, a date, a reminder and a planned proof?
- The number of actions more than seven days overdue, counted weekly, along with what was decided about them.
- Issues that come back from one audit to the next. If the walk-in seal shows up again, the loop was never closed.
Where Tsuno fits in
In Tsuno, actions are tasks: assigned to a person, with a due date, organized in projects and sections, recurring if needed, with comments. Everyone finds them on their Today page, the day's action feed sorted by due date: overdue, today, tomorrow, later. A temperature alert on a sensor-equipped cold room only closes once the corrective action is recorded, and the manager can create a task for the closing team straight away. Audits come with their grids and history, and the site's weekly report picks up the week's highlights. The details are on the Features page.
Tsuno's assistant, used from Tsuno or from the AI you already use, can prepare a task from a plain-language sentence: it sums up, you confirm, and it is logged. Tsuno San, the smart voice assistant for frontline teams, is connected to the same tasks; San Voice, the voice interaction, is available as a demo, and San acts within the rights of the person speaking to it. A reminder sent the day before the deadline, and a task linked back to its original audit item, describe what a good tool should do: check in a demo what is in place today. See the Tsuno San page.
If your team agrees three actions a month, a whiteboard in the office with a name and a date on every line will do the job well. A tool earns its place when actions multiply, come from different sources (audits, incidents, meetings) and need to survive the holidays of whoever tracks them.
Further reading
The overall framework is in AI for frontline managers: analyse, advise, reassure. To turn an audit into actions, read restaurant audits: moving from a score to an action plan, and to close the loop after an incident, why restaurant incidents keep repeating despite reports. For the assistant itself, the pillar page Tsuno San, the work companion for frontline teams gives the full picture.
Key takeaways
An action only exists if it has an owner, a due date, a reminder and a proof; without one of the four, it is an intention. AI makes those four attributes easy to write and makes chasing feel less like blame, but the manager decides and confirms.
Frequently asked questions
How do you follow up on actions agreed in a restaurant team meeting?
Every action should leave the meeting with four things: one named owner, a due date, a planned reminder and the proof that will show it is done. If any of the four is missing, the action is likely to be forgotten.
Why do action-tracking spreadsheets get abandoned?
Because they depend on one person keeping them up to date, and they never chase anyone. They sit beside the work: someone has to remember to open them. After a few weeks, nobody does.
What counts as proof that an action is done?
Something you can check: a photo, a reading, a quote or invoice, a ticked checklist item, a validated skill, or a second person verifying it. Saying it's done in passing is not proof.
Can AI create tasks from a meeting?
It can prepare a task from a sentence, spoken or written, with an owner and a date, and ask who is taking it on if that is unclear. The manager reviews and confirms: nothing should be created without that yes.
How do you chase an overdue action without putting people on the defensive?
Talk about the task, not the person: what was planned, the date, what is missing. Then offer a concrete next step: move the date, reassign it or ask for help. Calling someone out in front of the team just pushes them to tick the box too early next time.