Acknowledging a recipe

How a cook confirms they have read the current spec, and when a manager's PIN is required instead.

Publishing tells you a recipe left. An acknowledgment tells you it arrived. It is the difference between “we updated the spec” and “the line has read the spec”, and it is what every coverage number on your dashboard is counted from.

The ordinary case

At the bottom of a recipe, a cook confirms they have read it. Once done, the recipe shows ✓ “Signed off on the current version.”

Current is the important word. Publishing a new revision clears it and asks again — an acknowledgment is against the version that was read, not the recipe forever. That is what makes the number mean anything after a change.

When a manager’s PIN is required

If the recipe carries a critical control point, “I’ve read this” is not enough. Instead a keypad appears, and a manager PIN is required.

The resulting record says two things at once: the device showed it, and a named manager authorised it. In your records the acknowledgment is attributed to that manager by name — “Dana Reyes · device” — rather than to an anonymous tablet.

That distinction is the point. Anyone can tap a button; a food-safety attestation should have a name against it.

A location with no manager PINs cannot sign off a control-point recipe at all, so add at least one before publishing anything with a CCP.

Reading it back

  • Your dashboard shows On current spec overall and Seen / Signed off / On spec per location. See Your dashboard.
  • A recipe’s own page in the authoring app lists who acknowledged the current revision.

Making the number mean something

A few things are worth telling your managers, because coverage is only as honest as the habit behind it:

  • Sign off after reading, not at the start of shift. A tap that happens before anyone has read the change records the opposite of what you want to know.
  • Expect it to drop after every publish. A dip to 50% right after a menu change is the system working. A dip that stays down for days is a location that has not looked.
  • Chase the location, not the number. Coverage tells you which store has not read the new spec — that is a conversation, not a metric to manage.

Last checked against the product on August 18, 2026.