Ops Builder — the shift checklist itself: stages, tasks, standards, deadlines. Numbers Builder — sales figures and other numbers managers log each shift. Comms — one-off announcements to the team, separate from the checklist. Ops and Numbers can each be switched on or off independently ("ops on/off" next to the tabs) — turning one off hides it from managers entirely without deleting anything.
A stage is a time-blocked section of the shift — Opening, Midday Peak, Closing, whatever fits your business. Click + Stage to add one, give it a name and a short purpose line. Everything a manager needs to do in that window goes inside it as blocks. If you've reshaped the default stages and want them back, ↺ Restore defaults replaces your current stages with the originals — this goes live immediately, same as any other change, so use it deliberately.
Click into a stage, then add blocks — each one is a different kind of thing a manager can be asked to do:
Deadline sets when a task is due — miss it and it shows as late, or missed entirely if never completed. Points is how much a task is worth toward the shift score. Pillar is which of the four scoring categories it feeds — Compliance, Speed, Standards, Sales — this is what shows up broken out in Perception, so a task's pillar should match what it's actually testing.
Any task can be restricted to specific days instead of showing every shift — useful for weekly deep-cleans or monthly checks that don't need doing daily. Options: Every day (default), Weekly (pick a day), Monthly (pick a date), or a Custom cycle — fortnightly, every 3–4 weeks, or once a year on a specific financial week. A task hidden by its own schedule doesn't count toward or against the score that day — it simply isn't part of that shift.
Separate from the checklist — this is for figures a manager logs each shift: a Metric (a number with a target, e.g. daily sales), a Target (a number that should stay within a range, e.g. till variance), or a Snapshot (a photo or note, not a number — e.g. best sellers). Each has a "direction" — higher is better, lower is better, or simply completed — which decides how it affects the score.
There's no separate "draft" mode — changes go live on their own, about 4 seconds after you stop editing. The button in the top-right shows "Unsaved changes…" while you're actively working, then flips to "Saved ✓" once it's live for managers. Clicking Save & Go Live yourself just forces that to happen immediately instead of waiting. Worth knowing before you start reshaping something mid-shift — managers see it the moment it lands, not after you explicitly publish.