Operational checklists, duties & handover
Use versioned standards with separate performers, reviewers, corrective actions and auditable handover.
On this page · Jump to a section
Before you begin
Named owners for opening, closing, preparation, equipment checks and branch review.
Where to go
Operations → Templates / My Work / Handover
Visible menus may vary with language, permissions, app version and shop configuration.Follow these steps
- Build templates from actual shop procedures with accepted results, evidence and branch scope, then publish. Later edits create a new version.
- Assign schedules/duties and have staff check My Work before service. In-app notices are not proof of LINE/email delivery.
- Record observed PASS/FAIL and attach only shop-owned evidence. A FAIL needs a corrective action and owner; never rewrite the old result as PASS.
- Use a separate reviewer where required. Acknowledgement is not approval, and handover does not close POS bills or transfer financial ownership.
- Close the cycle with a manager-confirmed summary, pending owners and remediation dates. Use reports for overdue follow-up, not as a certification score.
How to verify success
Every task has version, performer, reviewer, evidence and remediation owner; pending work reaches the next shift without changing financial state.
Limits & things to check
Shop-configured limits and checklist approval are operational evidence, not food-safety or legal certification.
Ready to try it in your shop
Lessons are free to read. Actual operations require sign-in and the appropriate permission. Use test data for training.