Checklists that count.
Run the opening check, count what is on the shelf, and see what failed before the owner calls.
Who is working today?
Pick a seat. This is a working sandbox for a pretend ice cream franchise, and nothing you do leaves your browser.
- Sam SlingerSlinger. Runs the checks on Cart 7.Open as SamOpen as Sam
- Maya ManagerTerritory manager. Manages the Atlanta territory.Open as MayaOpen as Maya
- Ray RegionalRegional manager. Southeast region. Can approve runs.Open as RayOpen as Ray
- Cora CorporateCorporate. Every location in the franchise. Can approve runs.Open as CoraOpen as Cora
- Owen OwnerFranchise owner. Owns the Texas region.Open as OwenOpen as Owen
- Fran FranchisorFranchisor. The whole brand, all locations.Open as FranOpen as Fran
What you can look at today
- Checklist templates, with the version each run started on
- Every run and how it ended
- Schedules, with due times in each location's timezone
- Follow-ups that a failed answer created
- The approval queue, which changes with your role
- A location tree where carts are locations too
- Stock levels against par, and live tally sessions
Still being built
- The checklist builder, with logic and scoring
- Running a checklist from the phone, offline
- Shared-tablet login with a PIN
- Assets with types, QR tags and repair history
- Multi-stage jobs: prep, live tally, closeout
- Reports and PDFs
One bad freezer, followed through
- Sam, on the cart
- Records the freezer at -9 C on the Cart 7 opening check. The allowed range is -25 to -15, so the answer is flagged on the spot.
- When Sam submits
- The run goes in as a permanent record. A follow-up called “Freezer out of range on Cart 7” is suggested and marked critical.
- Maya, at her desk
- Sees the suggestion waiting for her and confirms it. The original answer stays on the run.
This is the seeded sample data in the sandbox. Open it as Sam to see the same cart.