Revisions and history

A recipe is not a document you overwrite. Every published version is kept as a numbered revision, and the note you wrote when submitting or publishing it is kept with it.

Revision history

A recipe’s Revision history lists each revision, newest first, with the note it shipped under:

rev 2 — Switched to the new lemon supplier - ratio unchanged
rev 1

That is the whole argument for the note field. “rev 2 — swapped to the new supplier’s cut” answers “why is this different?” a year later. “rev 2 — update” does not, and by then nobody remembers.

The header shows which revision you are looking at, e.g. PRODUCTION · REV 2, along with its status. A revision awaiting a decision shows IN REVIEW.

Reviewing what changed

From the approvals queue, Review changes opens the submitted revision against the published one. On a recipe’s first revision there is nothing to compare against, and it says so — “New recipe — no earlier published version to compare against.” See The approvals queue.

A Print button is available here, for reviewing a spec away from a screen.

⚠ A new revision resets acknowledgment

This is the consequence worth internalising. Acknowledgment is recorded against the revision that was read, not against the recipe — so publishing a new revision clears it and asks the line again.

That means:

• your dashboard’s On current spec will drop right after you publish, at every location. That is the number working, not breaking.
• a location that has not read the change is visible immediately, by name
• a trivial edit costs your line a real acknowledgment. Fixing a typo in a description re-prompts every store, and if you do that three times in a shift, people start tapping through without reading.

So batch cosmetic edits and publish them together. The acknowledgment is only worth something while your team still reads before tapping, and that is a budget you can spend.

Rolling back

There is no one-click rollback. To return to an earlier spec, edit the recipe back and publish it as a new revision — which is honest: the line has already read the version you are undoing, and quietly reverting would leave them out of step with a change they had acknowledged.

Say so in the note. “rev 4 — reverting rev 3, the new supplier’s cut was inconsistent” is exactly the history you want in six months.

What is recorded elsewhere

Beyond revisions, the actions themselves are audited — created, submitted, published, each attributed to the person who did it. So “who approved this?” has an answer even though the approvals queue holds no assigned approver. See Roles, and what each one can do.