1) Confirm setup and access first
Make sure account, people, location access, integrations, and billing readiness are in place before teams depend on audits, incidents, and corrective-action workflows.
This guide works like an operator manual: setup first, then run the daily playbook and screen-by-screen routines in service order. It also shows that Ops Tool supports real daily manager workflows, not just a feature list.
Keep the first decision on audit discipline, incident control, and manager follow-through before continuing to the app overview, pricing, or contact.
Make sure account, people, location access, integrations, and billing readiness are in place before teams depend on audits, incidents, and corrective-action workflows.
Run planner, audit center, live audits, incident control, coaching, and daily review in service order so nothing important gets captured out of sequence.
Continue to Ops Tool, Pricing, or Contact after workflow fit is clear and the conversation turns to launch timing, pricing scope, or rollout support.
The guide keeps setup, daily operating flow, and move-on decisions separate so teams can understand the work before pricing, launch, or implementation review begins.
Access, location state, billing, and integrations lead because every audit, incident, and coaching workflow depends on that foundation being correct first.
Planner, audits, incidents, coaching, and review stay together in the middle so managers can follow the real shift rhythm instead of reading disconnected feature blurbs.
Support details sit last so the guide stays useful as an operator manual first, while still giving owners a clear path to rollout, licensing, or technical review when they need it.
This quick launch map helps an operator or new manager understand where the Ops Tool day actually begins.
Start in the planner and audit center so priorities, audits, and shift launch all line up before service.
Move into the audit workflows, incidents, and coaching screens once the live shift is running and proof needs to be captured in the moment.
Use daily review, exports, billing, integrations, and multi-location controls to verify the day closes with usable visibility instead of scattered notes.
Set this up once, then managers can run the full operating workflow without gaps or guessing which screen opens first.
Follow this sequence every operating day so audits, incidents, coaching, daily review, and reporting stay connected.
| Phase | Screen | What To Do | Done When |
|---|---|---|---|
| Open Prep | Command Center | Review Strategy, Resolutions, Pulse; confirm weather/zip and top priority items. | Managers know top 3 priorities before service. |
| Shift Launch | Audit Center | Use Audit Center: confirm team roster, select floor/culinary/ring-it tasks for active shift. | Audit workflow and assigned staff are ready. |
| During Service | Floor audit, Culinary audit, Ring-It audit | Complete audits with scores, notes, and optional photo AI checks; save continuously. | All required audits submitted with actionable notes. |
| Incident Control | Incident management | Create/report incidents, update statuses, use AI recommendation button for resolution suggestions. | Open incidents have responsible party and resolution path. |
| Coaching & Documentation | Performance alerts, Warning documentation | Convert low-score patterns into documented coaching/warnings with follow-up dates. | Corrective actions are documented and signable. |
| End Of Day | Daily review | Run archive date review, verify floor/culinary/ring/incidents, export PDF dossier. | Daily report is archived and downloadable. |
Practical usage instructions for the main Ops Tool screens.
Audit Center
All, Floor, Kitchen, Ring It).Floor audit
Culinary audit
Prep & Quality, Line Performance, HACCP Safety).Ring-It audit
Low, Medium, High).Incident management and report flow
Performance alerts to Warning documentation
Command Center and Goals board
todo, done, stuck).Integrations, Sales, and Owner locations
Keep these routines on calendar so the platform keeps driving outcomes.
Keep this guide focused on setup, daily order, and manager follow-through. Continue after those steps are clear and the next decision is obvious.
Open the Operations login after the audit-and-follow-through sequence makes sense and you want to inspect the working screens directly.
Open the integrated platform guide once the operations routine makes sense and the buyer wants to see how this work connects with Scheduling, POS closeout, Label, and cross-app follow-through.
Go back to the Ops Tool product page when you want the shorter product overview instead of the full operating manual.
Keep this manual focused on audit order, incident control, coaching, and manager follow-through. Continue when the team needs a different level of detail.
Go back to the Ops Tool product page when you want the shorter public overview instead of the full manual.
Open the integrated platform guide when the need shifts from operations discipline to how Operations connects with Scheduling, POS, Label, floor service, and closeout across the stack.
Open the Resources hub for platform planning order, front-door explainers, manager playbooks, and food-safety structure when the next step is educational rather than this Ops manual.
Open Reader or Training when the next need is leadership reading, standards support, onboarding, or manager reinforcement instead of screen-by-screen Ops use.
Open engineering when the conversation turns to architecture, rollout constraints, or implementation detail. Keep pricing and launch timing for after workflow fit is already clear.
The operator guide above stays focused on how managers use Ops Tool. For deeper architecture, rollout, or integration questions, use Engineering or direct implementation follow-up without making the operator manual harder to read.
Ask for technical review when the question becomes permissions, integrations, rollout constraints, data flow, or multi-location deployment details.