Pass it on without repeating

A procedure buried in WhatsApp is not a procedure

An instruction posted in a group chat gets lost in the stream. Here is what turns a message into a procedure, plus a one-page template you can copy.

Published on

A cook glances at a message thread on a phone propped on a shelf

A procedure is a text you can find without asking, with a date, an owner and a moment of use. A message in a group has none of that: it sinks under the messages that follow, nobody knows whether it still applies, and the new hire was not in the group that day. WhatsApp is excellent for talking about today. It is poor at keeping what must stay true.

Tuesday, 11:12 p.m., the chef's message

The chef at the first site posts in the group: "Reminder: raw fish, we switch board and knife, thanks all." Fifteen thumbs up. The next day, everyone has seen it.

Six weeks later, an extra shows up for Saturday. He did not read the message: he was not in the group, or he was in the group but the message is far back. The chef is busy at the pass. The extra uses the board that is lying around. Nobody disobeyed an instruction: the instruction no longer existed anywhere the extra could run into it.

What separates a message from a procedure

CriterionMessage in a groupProcedure
Findable without askingNo, you have to scroll or searchYes, a single location
Validity dateSend date onlyLast-review date
OwnerWhoever wrote it, sometimes goneA designated role that keeps it current
VersionSeveral, in no clear orderOnly one in force
Read by the new hireOnly if they were thereYes, on arrival and at the station
Proof of applicationA thumbs upA signed box, a photo if needed

Why procedures end up in messages

  • It is the only channel everyone opens. The team looks at their phone more than at any binder. The message is the path of least effort.
  • Writing a sheet takes a step nobody planned for. A message takes ten seconds; a sheet takes ten minutes and a place to file it.
  • Nobody owns "what stays true." The chef corrects, the manager reminds, but nobody updates a source.
  • Departures cut the memory. When a manager leaves the group, they take their version of the instructions with them.

Five steps to get an instruction out of the stream

  1. Take inventory of one month of messages. The manager rereads the group and highlights only what was meant to stay true: techniques, service temperatures, guest-greeting rules, hygiene instructions.
  2. Keep what is still valid. An instruction contradicted by a more recent message needs a ruling, not a copy.
  3. Rewrite it as a short sheet. Use the template below, one sheet per task.
  4. Give it an owner and a review date. The owner is a role (the sous chef, the floor manager), not a single person.
  5. Answer with the sheet. When someone asks the question again in the group, reply with the link or the location, never with a new explanation.

A sheet template to copy

Title: Raw fish, board separation
Role concerned: cold station, prep
When: before any raw fish is cut
Action: dedicated board and knife (assigned color), clean before switching to another product
Critical error: reusing another product's board without cleaning
Proof: signed box at prep, photo in case of a deviation
Owner: sous chef
Last review: (date)

Eight lines. The new hire reads it in a minute, and the chef updates it once for everyone.

Common mistakes

  • Pinning a message in the group and calling it done. The pin keeps one version alive, with no owner and no date.
  • Copying the procedure into a document and still sending corrections by message. The two sources diverge within two weeks.
  • Writing the sheet in the name of the manager who left. It must belong to a role.
  • Writing everything at once. Start with the three or four tasks that matter for hygiene and guest welcome.

If you do not know where to start, the method in how many times to repeat an instruction before changing the system gives a sorting into three instructions. If the group holds the instructions of a manager who just left, also read what leaves with your best manager. And for the sheet to actually serve a new hire, see the real problem with onboarding manuals.

What to measure

  • The number of instructions that still exist only in a message. It should drop over the weeks.
  • The time a team member takes to find a given instruction. Ask them, in a live situation, to show you where it is.
  • The number of times the same question comes back in the group. Every return is a missing or misplaced sheet.

Where Tsuno comes in

Tsuno writes the instruction once, assigns it to a role, then delivers it through checklists, training and onboarding. You keep your group chat for the daily flow. When an instruction changes, the version in force is the one in Tsuno, dated and viewable; you can ask in plain language what the instruction said at a given time. Tsuno does not monitor conversations and does not replace your messaging app. It handles what must stay true. The details are on the features page.

Key takeaways

A message is made to pass, a procedure to last. Sort out what must endure, write it in eight lines with an owner and a date, and point to the sheet every time the question comes back.

Frequently asked questions

Can we keep the team's WhatsApp group?

Yes, for day-to-day exchanges: someone running late, a shift swap, a photo of a delivery. What needs to come out of it are the instructions that must stay true over time. Those move into a sheet with an owner and a review date.

How do you find an instruction given three months ago in a group chat?

In practice, you do not: a keyword search returns dozens of messages, some of which have since been contradicted. That is exactly the sign it should have been written somewhere else, once, with a date.

Does a procedure have to be digital?

No. A laminated sheet at the station beats a file nobody opens. What matters is a single location, an owner and a last-review date, whatever the medium.

What should we do with old messages that contain instructions?

Sort them once: spot the instructions that still hold, rewrite them as short sheets, and keep in the group only a message pointing to the sheet. Old messages do not need to be deleted, just no longer treated as a source.

How do we stop every manager from creating their own instruction group?

Give them one official, simple place for the sheets, and answer systematically with it whenever someone asks the question in a group: "It's in the sheet, here's where." Within a few weeks, the habit of looking in the right place takes hold.