Your dashboard, and what it is telling you

Signing in takes you here. The dashboard is built around one question — is every location actually cooking the current spec? — and everything on it is derived from live data, so there is nothing to refresh or keep up to date.

The time-range buttons (7d / 30d / 90d) change the engagement section only. The counts above it are current state, not a window.

On the pass

The dark board at the top is the day at a glance. Every tile is a link to the screen it summarises.

• On current spec — the headline. The share of your live recipes that have been signed off at each location, against what is published right now. Below 100% means at least one store has not acknowledged the current version.
• Menu ready — whether the items on your active menus are actually publishable.
• Awaiting review — recipes sitting in the approvals queue. See Getting a recipe onto the line.
• Live recipes — published, reaching the line.
• Active menus — menus with a live version.

On current spec and Menu ready answer different questions, and it is worth knowing which one is complaining. Menu ready is about your content — is the menu complete and publishable. On current spec is about receipt — did the kitchens read it. A menu can be 100% ready while coverage sits at 50%, which simply means the spec is correct and someone on the line has not signed off yet.

On the current spec

Under the board, the same coverage number broken out per location:

• Seen — how many live recipes that store has opened.
• Signed off — how many it has acknowledged.
• On spec — signed off as a share of what is published.

The footnote tells you the shape of the calculation, e.g. “of 1 stores × 2 live recipes”. That matters: coverage is per store and per recipe, so adding a location or publishing a recipe will move the percentage down until the line catches up. That is the number working, not breaking.

This section is visible to brand admins, and appears only once you have at least one active store and one published recipe — before that there is nothing to measure.

Menu readiness and what is scheduled

Menu readiness lists each active menu with its live version and how many of its items are ready. Scheduled to activate shows menu versions with a future start date, and reads “Nothing scheduled ahead” when there are none.

Recipe pipeline

A count of every recipe by status — draft, in review, published, archived. Drafts are not a backlog to feel bad about; a recipe stays a draft until someone chooses to submit it.

Engagement

How much the line is actually reading, over the selected window: total recipe views and the change against the previous period, a trend, the most-viewed recipes, and a breakdown by store and by station. A new brand sees “Not enough history for a trend yet” until there is a second period to compare.

Three things to know before you read anything into these numbers:

• Only the recipe viewer counts. A view is recorded when a recipe is opened on the line. Reading the same recipe in the authoring app does not count.
• Your own browsing counts too. Opening the line view yourself is recorded the same way a store’s iPad is, so a quiet brand’s early numbers are often partly your own checking.
• Cooks are not identified individually. The recipe viewer is the store’s screen, not a personal login. Read these as “how much this location leaned on Tavorly”, never as one person’s activity.

Recipes with no station show under Unassigned in the station breakdown. That is a prompt to set default stations, not an error.

Recent activity

The last few things that happened in your brand, newest first, with how long ago.

View as

View as… lets a brand admin see Copper Fork the way a lower-privilege user does — pick Viewer, Creator or Approver, and optionally a specific store. It is view-only: you cannot make changes while emulating. Exit view in the header returns you to your own role.

The sidebar respects the role you picked: viewing as a Creator, Approvals and your brand-management screens disappear, exactly as they would for a real Creator.

“Start viewing” lands you where that role actually works. Viewing as a Viewer takes you to the line view; Creator and Approver land on the dashboard, in their own workspace.

What you see is what they see. Screens no longer offer controls your emulated role could not use — viewing as a Creator, the recipe editor shows “Submit for review”, not the approver’s publish-direct button. Unpublished drafts stay hidden from an emulated Viewer, exactly as they are from a real one, so you can use this to answer “is my draft reaching the line?” and trust the answer.

A Viewer with no store selected sees nothing, and that is correct. Menus are assigned to stores, so somebody not tied to a location has no menus to open. Pick a store in the picker to preview a real line.

Anything you try to change while emulating is refused, so the preview cannot alter your brand. Exit view is in the strip at the top of every screen, including the line view and any permission error you land on.