Daily Operations
A useful opening or closing checklist is not a long list of obvious chores. It is a shift-control tool: it confirms that critical work was completed, exceptions were handed over and the next team starts with fewer surprises.
Start with outcomes, not tasks
Before writing “clean counter” or “check fridge,” define what ready means. For example, a station may be considered ready when required equipment is working, essential stock is at par, prep is labeled and the station has no unresolved safety issue.
What belongs on an opening checklist
- Access, lighting and security checks
- Equipment startup and exception reporting
- Required food-safety and temperature checks
- Prep readiness and stock exceptions
- POS, cash float or payment-terminal readiness
- Dining-room, restroom and guest-area readiness
- Staff attendance and role coverage
- Reservations, events, large orders or expected demand
What belongs on a closing checklist
- Cash-up and payment reconciliation
- Waste, void and comp review
- Storage and labeling of usable food
- Cleaning and sanitation tasks
- Equipment shutdown where appropriate
- Inventory shortages for the next shift
- Security and access checks
- Manager handover notes
For the finance side of close, use Restaurant Cash Control and End-of-Day Reconciliation.
Assign ownership
Every line should have a clear owner. “Kitchen” is often too vague. Use roles such as closing manager, line cook, cashier or shift supervisor. The manager should verify critical controls, not redo every task personally.
Use exception-based handover
A checkbox only proves that someone marked a task. Add a short exception field for items that are broken, missing, late or below standard. The next manager should be able to understand unresolved issues in less than a minute.
Keep the checklist short enough to use
If a checklist becomes a complete operations manual, staff will rush through it. Put detailed SOP instructions elsewhere and keep the daily checklist focused on actions and verification points.
Review the checklist when operations change
Update the checklist after a new piece of equipment, service channel, menu change, recurring incident or audit finding. Remove items that no longer add control. A checklist should evolve with the operation.
A simple implementation method
- Observe one complete opening and closing shift.
- List the controls that would cause real problems if missed.
- Assign each item to a role.
- Separate opening, shift-handover and closing items.
- Test the list for one week.
- Remove vague or duplicated tasks.
- Review exceptions in the manager meeting.
Manager takeaway
The best checklist is not the longest one. It is the one the team actually uses to prevent predictable failures.