A menu can display one drink name while the counter operates with several recipes. One shift follows a printed card, another remembers a recent tasting, and a third uses a photograph saved on a phone. Each person may believe they are following the latest instruction. The problem starts when a recipe change has no clear release process.

A small shop does not need complicated software to prevent this. It needs a reliable place for approved recipes, a way to distinguish current instructions from drafts, and a person responsible for confirming that a change has reached the counter. Start with one drink and make the routine easy to repeat.

Give each recipe an identity

Use a stable recipe code alongside the customer-facing name. Include cup size, recipe version and approval date. If the same drink has different sizes, describe the formula for each size instead of relying on informal scaling. A staff member should be able to identify the correct card without asking which photograph is newest.

Record ingredient identifiers as well as familiar names. “Peach syrup” may refer to more than one item in storage. A recipe can remain understandable to staff while still identifying the exact approved product. Keep purchasing codes in a separate column if they make the working instructions harder to read.

Separate a tasting draft from a service instruction

Mark experimental recipes as drafts and keep them away from the active station cards. A tasting note is evidence for a decision, not permission to change service. Record the proposed adjustment and its reason: perhaps a portioning method is unclear, or a new cup size requires a separate assembly sequence.

During the trial, change one decision at a time where practical. Note the preparation method and who reviewed the drink. Avoid writing “everyone preferred it” unless that accurately describes a documented review. Specific observations let the next person understand why the revision was accepted and what still needs checking.

Release the whole instruction together

An approved change should include all affected steps. If a topping portion changes, check the fill instruction, assembly order and related training notes. If a product is substituted, confirm its suitability through the shop’s normal review process before updating the recipe. A handwritten replacement name alone may leave important differences unexplained.

Choose a clear start point for the revision, such as the next scheduled shift briefing. Replace the printed card, update the shared file and remove old copies from the working folder. Tell staff what changed and what stayed the same. Ask them to find the current version themselves; that reveals whether the filing system is actually usable.

Keep a short change log

The log only needs the recipe code, previous version, new version, reason, approver and release date. Retain old versions in an archive labelled as inactive. This helps investigate a later complaint without putting obsolete instructions back on the counter. Do not rely on file modification dates as the only record of approval.

For multiple locations, ask each manager to acknowledge the revision. Follow up on missing acknowledgements rather than assuming a sent message was read. A short demonstration may be more useful than a long announcement when the change concerns scooping, stirring or cup assembly.

Check the handover at the next shift

Watch a staff member prepare the revised drink from the card. Ask where they would find the instruction if the printed copy were damaged. Record confusing steps and correct the document through the same revision routine. Consistency improves when staff can point to one trustworthy instruction instead of reconstructing a conversation.

  • Assign a recipe code, version and release date.
  • Keep drafts out of the service folder.
  • List every instruction affected by the change.
  • Replace old station cards and acknowledge the handover.
  • Archive the previous version with a short explanation.
  • Observe the next shift using the updated card.