What gets recorded

Tavorly’s value in an awkward conversation — an inspection, an incident, a supplier dispute — is that it can say who did what, and when. This is what it keeps.

Actions are attributed to people

Every meaningful action is recorded against the person who took it, not just the fact that it happened. For a recipe, the chain reads:

recipe.created    Sam Ortiz
recipe.submitted  Sam Ortiz
recipe.published  Priya Nair

This is why “who approved this?” has an answer even though the approvals queue holds no assigned approver. The queue is a shared pool by design; the record of who actually decided is kept separately, against the action. See The approvals queue.

Device and store actions are recorded too — issuing an enrollment code, adding or removing a manager PIN, changing a location’s settings.

Acknowledgments are the record that matters most

An acknowledgment ties a person or a named manager to a specific revision of a recipe at a specific location. That is a stronger claim than “we sent out the update”, and it is the one worth understanding:

• an ordinary acknowledgment records that the location’s screen confirmed the current revision
• a control-point recipe records the named manager who PIN-signed it — “Dana Reyes · device” — because the device acted and the manager authorised
• revoking that manager’s PIN later does not remove their past sign-offs. The name travels with the acknowledgment, so the record survives the person leaving

See Acknowledging a recipe.

Revisions keep their own history

Separately from the audit trail, every published revision is kept with the note it shipped under — so “what changed, and why” is answerable a year later without anyone having to remember. See Revisions and history.

What you can see yourself

In your own brand you can see:

• who acknowledged the current revision of a recipe, per location
• coverage per location on your dashboard
• revision history with notes, on each recipe

⚠ There is no brand-facing audit log screen today. The underlying trail is recorded and Tavorly can retrieve it, but it is not a page you can browse. If you need an extract — for an inspection, an incident review, or a dispute — ask us and we will pull it.

We would rather tell you that plainly than have you assume a screen exists and go looking for it during the one week you actually need it.

What Tavorly does not record

• Cooks are not identified individually. A recipe viewer is the location’s screen, not a personal login, so views and ordinary acknowledgments are attributed to the device and its location. Manager PINs are the deliberate exception, for the one case that needs a name.
• View counts are not a productivity metric. They are recorded per device session and include your own browsing of the line view. Read them as “how much this location leaned on Tavorly”. See Your dashboard.

That split is deliberate. Proving a spec was received does not require surveilling the people who received it.