← Back to blog

Restaurant Operations Checklist for Managers: Ready-to-Use Templates

August 6, 2026
Restaurant Operations Checklist for Managers: Ready-to-Use Templates

Every U.S. restaurant needs multiple checklists to run a compliant, consistent shift, covering front-of-house and back-of-house openings, mid-shift handovers, closings, supervisory oversight, food safety temperature monitoring, waste management, equipment checks, delivery receiving, and emergency and alcohol compliance procedures. The FDA Food Code sets the federal baseline for temperature, allergen, and sanitation standards; your state health department adds the local inspection criteria on top. Wits' End Solutions provides templates, training, and operational support to help you put all of it into practice.

Your core checklist set:

  • FOH opening checklist (lead server or host)
  • BOH opening checklist (opening cook or sous chef)
  • Mid-shift/swing handover checklist (swing MOD)
  • Closing checklist (closing cook + closing manager)
  • Manager-on-Duty (MOD) supervisory checklist
  • Food-safety temperature log (with corrective-action fields)
  • Waste log (with corrective-action fields)
  • Equipment daily/weekly check
  • Delivery and receiving log
  • Emergency response checklist
  • Alcohol service compliance log

Copy the list above into a shared drive, convert each item to a Google Form or a printed sheet, and assign an owner before tonight's shift. The templates in Section 3 give you the exact fields to start with.


Table of Contents

What types of checklists does a restaurant actually need?

Think of your checklist library as a taxonomy, not a single document. Each type has a defined owner, a cadence, and a scope. Conflating them creates bloat; leaving gaps creates liability.

Restaurant manager reviewing checklist at desk

FOH opening checklist

Hands holding restaurant checklist tablet

Owner: Lead server or host. Cadence: Every opening shift.

The FOH opening checklist wins the shift before the first guest arrives. Items to copy into yours:

  • Confirm table layout matches the reservation floor plan.
  • Test POS terminals, receipt printers, and card readers.
  • Verify restrooms are stocked and clean.
  • Check ambient music, lighting levels, and Wi-Fi.
  • Confirm host stand has menus, reservation list, and a printed 86 list.

BOH opening checklist

Owner: Opening cook or sous chef. Cadence: Every opening shift.

  • Verify walk-in and reach-in temperatures (coolers ≤41°F, freezers ≤0°F per FDA Food Code).
  • Confirm equipment warm-up: fryers, flat-top, ovens, steam wells.
  • Check mise en place against the prep sheet.
  • Inspect sanitizer solution concentration (chlorine: 50–100 ppm; quaternary ammonium: per label).
  • Review the prep list and flag any shortages before service.

Mid-shift/swing handover checklist

Neglecting the swing transition is one of the most common failure points in restaurant operations. A formal mid-shift checklist treats each service change like an opening and prevents inventory and prep erosion between meal periods. The swing MOD owns this.

  • Verify par levels on all high-volume items; replenish before the next service.
  • Update the 86 list and communicate it to FOH and BOH.
  • Record cooler temperatures and log any corrective actions.
  • Confirm sanitizer buckets are refreshed.
  • Brief the incoming crew on any VIP reservations, pacing issues, or maintenance flags.

Closing checklist

Closing is where most food-cost leaks and safety risks crystallize. The closing cook handles BOH; the closing manager handles FOH and cash.

  • Break down stations; cool and label all food with item name, date, and time.
  • Record final cooler and freezer temperatures.
  • Reconcile cash drawer and complete tip-out.
  • Shut down and secure all equipment per manufacturer specs.
  • Lock all exterior doors; confirm alarm is set.

Manager-on-Duty (MOD) checklist

The MOD checklist is a supervisory tool, not a manual-labor list. The MOD acts as the keel of the ship: proactive pacing, VIP management, and problem spotting before guests feel the impact. Full MOD detail is in Section 6.

Food-safety temperature log

Owner: Assigned cook or shift lead. Cadence: Every shift, minimum twice per service.

Required fields for U.S. health inspections: timestamp, item name, temperature in °F, corrective action taken, and staff initials. The FDA Food Code requires hot-hold foods at ≥140°F and cold-hold foods at ≤41°F.

Equipment daily/weekly check

Daily checks catch wear and tear; weekly and monthly items protect assets and align with life-safety inspection requirements, as detailed in the complete guide to commercial dishwashers for catering kitchens. This checklist is frequently overlooked until a fryer fails mid-service or a fire suppression system fails an inspection.

Delivery and receiving log

Owner: Receiving manager or opening cook. Cadence: Every delivery.

  • Verify invoice against purchase order.
  • Check temperatures of refrigerated and frozen items on arrival.
  • Inspect packaging for damage or pest evidence.
  • Sign and date the delivery receipt; retain for 90 days.

Emergency response checklist

Post this near the manager station. It covers fire (call 911, evacuate, pull suppression), injury (first aid, incident report, contact ownership), and foodborne illness outbreak (isolate implicated food, contact local health department, document everything).

Alcohol service compliance checklist

Owner: Bar manager or MOD. Cadence: Every shift.

  • Verify all servers hold current TIPS or equivalent state certification.
  • Check IDs for all guests who appear under 30.
  • Log any refusals of service with time, description, and reason.
  • Confirm no minors are seated at the bar.

Waste disposal and environmental compliance

Owner: Closing cook. Cadence: Daily.

  • Separate food waste, recyclables, and grease for proper disposal.
  • Confirm grease trap is not overflowing; log last service date.
  • Verify dumpster lids are closed to prevent pest access.

A note on scope: A checklist is a repeatable verification tool for standards and compliance. Dynamic, ad-hoc work (a broken walk-in, a vendor dispute, a staffing gap) belongs in a task management system, not a checklist. Conflating the two creates bloat on one side and accountability gaps on the other.


Ready-to-use checklist templates and sample logs

The snippets below are copy-ready. Paste them into a Google Form, a spreadsheet, or a printed PDF. Each template is intentionally short; add items only when a compliance or operational gap demands it.

FOH opening template

FOH OPENING CHECKLIST
Date: _______ Shift: _______ Owner: _______

□ Table layout matches reservation floor plan
□ POS terminals and printers tested
□ Menus clean and complete
□ Host stand stocked (reservation list, 86 list, pens)
□ Restrooms stocked and inspected
□ Music, lighting, and Wi-Fi confirmed
□ Pre-shift briefing completed with staff
Staff initials: _______ Time completed: _______

BOH opening template

BOH OPENING CHECKLIST
Date: _______ Shift: _______ Owner: _______

□ Walk-in temp logged: ___°F (must be ≤41°F)
□ Freezer temp logged: ___°F (must be ≤0°F)
□ Equipment warm-up complete (fryers, ovens, flat-top)
□ Sanitizer concentration verified: ___ ppm
□ Prep sheet reviewed; shortages flagged to MOD
□ Mise en place complete for all stations
Staff initials: _______ Time completed: _______

Mid-shift/swing handover template

MID-SHIFT HANDOVER CHECKLIST
Date: _______ Handover time: _______ Outgoing MOD: _______ Incoming MOD: _______

□ Par levels checked; replenishment ordered/completed
□ 86 list updated and communicated to FOH and BOH
□ Cooler temps logged: ___°F Corrective action (if any): _______
□ Sanitizer buckets refreshed
□ VIP/reservation notes transferred
□ Open maintenance issues documented
Outgoing MOD signature: _______ Incoming MOD signature: _______

Closing template

CLOSING CHECKLIST
Date: _______ Shift: _______ Owner: _______

□ All food cooled, labeled (item/date/time), and stored
□ Final cooler temp: ___°F Final freezer temp: ___°F
□ Stations broken down and sanitized
□ Cash drawer reconciled; discrepancies noted: _______
□ All equipment shut down per spec
□ Grease traps checked; waste disposed
□ Exterior doors locked; alarm set
Staff initials: _______ Time completed: _______

MOD checklist template

MANAGER-ON-DUTY CHECKLIST
Date: _______ Shift: _______ MOD: _______

□ Pre-shift huddle completed
□ Pacing plan confirmed with kitchen
□ VIP/large party reservations briefed
□ Mid-shift FOH walkthrough completed
□ Mid-shift BOH walkthrough completed
□ Labor vs. sales checked at ___:___ (time)
□ One coaching moment documented: _______
□ Incident log updated (if applicable)
MOD signature: _______ End-of-shift time: _______

Temperature and waste log sample

TimestampItemTemp (°F)Acceptable RangeCorrective ActionStaff Initials
Walk-in cooler41°F≤41°FNone requiredJ.R.
Steam well (soup)140°F≥140°FNone requiredJ.R.
2:15 PMWalk-in cooler45°F≤41°FAdjusted thermostat; re-checked later within safe rangeM.T.
2:15 PMWaste (soup, 2 qt.)N/AN/ADiscarded; prep order placedM.T.
6 PMReach-in cooler41°F≤41°FNone requiredK.L.

Minimum fields for a defensible audit trail: timestamp, item name, temperature in °F, acceptable range, corrective action taken (or "none required"), and staff initials. For critical failures (a cooler above 45°F, a hot-hold below 135°F), add a photo and a supervisor signature.

Pro Tip: Convert your temperature log to a Google Form with required fields. Set a conditional alert: if a submitted temperature falls outside the safe range, the form auto-emails the MOD. This closes the corrective-action loop without adding a manual step.


What do U.S. health and fire authorities expect from your logs?

The short answer: time-stamped, signed, and complete records with a corrective-action field that closes every exception. An inspector who finds a 45°F cooler reading with no corrective action noted will cite you; the same reading with a documented corrective action and a follow-up temperature is a managed event, not a violation.

Digital checklists, when properly configured, require photo evidence, time-stamping, and integrated corrective-action tracking to create defensible audit trails. Paper logs can satisfy inspectors, but they are vulnerable to pencil-whipping — staff filling in readings without actually taking them. Requiring a photo of the thermometer display for any out-of-range reading eliminates that risk without slowing service.

Essential log fields by category:

  • Temperature logs: timestamp, item/unit, reading in °F, acceptable range, corrective action, staff initials, supervisor sign-off for critical failures.
  • Waste logs: timestamp, item discarded, quantity, reason (spoilage, contamination, over-production), staff initials.
  • Sanitizer logs: timestamp, solution type, concentration in ppm, corrective action if out of range, staff initials.
  • Pest sighting log: date, location, description, action taken, pest control contact notified (yes/no).
  • Fire-safety checks: date, suppression system visual inspection, hood cleaning date (last/next), extinguisher inspection date, staff initials.

Retention guidance: Most state health departments require food-safety logs to be retained for a minimum of 90 days; some require up to one year for HACCP-based operations. Fire-safety inspection records typically follow local fire marshal requirements, often one to three years. Keep digital backups in a read-only export format so records cannot be altered after the fact.

Pro Tip: Set a monthly calendar reminder to export all logs to a read-only PDF or cloud folder. Auditors and attorneys both want records that cannot be edited retroactively. A time-stamped, unalterable export is your best protection.


How to roll out checklists so your team actually uses them

The biggest implementation mistake is launching all checklists simultaneously. Start with the closing checklist first: it has the largest immediate ROI (food cost, safety, cash security) and the smallest crew to manage. Pilot it for two weeks with senior staff, track time-to-complete and missed-item rates, then iterate before adding opening and swing lists.

Assign ownership before you print anything

Every checklist needs a named role, not a named person. "Closing cook owns the BOH closing checklist" survives turnover; "Maria owns it" does not. Map each checklist to a position, post the ownership matrix in the manager office, and update it when roles change.

Organize by time block, not by department

Organizing daily checklists by time block (morning, service blocks, pre-close) improves completion rates and reduces confusion about when items are due. A single long list invites cherry-picking; a block structure makes sequencing obvious.

Training and adoption

Structured checklists reduce performance variance between veteran staff and new hires and shorten training cycles when frontline staff help design them. Involve your lead cook and lead server in the first draft. Their buy-in becomes peer pressure on the rest of the team. Pair new hires with a checklist champion for the first two weeks and use the checklist during coaching conversations, not as a punitive scorecard.

Wits' End Solutions's restaurant staff training programs are built to reinforce exactly this kind of standards-based adoption, connecting daily checklist habits to measurable service outcomes.

Digital vs. paper: a practical decision guide

Paper is acceptable for single-location operations with stable, experienced teams and no multi-site reporting requirements. Go digital when you need multi-site visibility, integrated corrective-action escalation, or analyzable trend data. Digital checklists create timestamps, accountability, and trend data showing which shifts generate the most defects — information paper logs cannot surface.

Minimum features to require from any digital checklist tool: mandatory timestamp on submission, photo-upload field for critical items, corrective-action field that triggers a notification, and a read-only export for audits. Google Forms covers the basics at no cost; purpose-built inspection apps (iAuditor by SafetyCulture, Jolt, or similar) add escalation routing and analytics.

Pro Tip: Keep each role's active checklist to 12 items or fewer. Anything beyond that gets skipped under pressure. Move low-risk admin items (ordering office supplies, updating the specials board) to a weekly task list, not the shift checklist.


How the MOD checklist and shift handover work together

The MOD checklist is not a task list. It is a supervisory tool focused on pacing, guest flow, and proactive problem spotting, and the MOD should be moving through the dining room and kitchen, not behind a prep table. The shift handover is the formal moment where one MOD transfers accountability to the next.

MOD checklist: step by step

  1. Pre-shift huddle (15 min before doors): Brief FOH and BOH on reservations, VIPs, 86 items, and one service standard to focus on during the shift.
  2. Pacing plan confirmation: Align with the kitchen on ticket time targets and cover pacing for the first two hours.
  3. Reservation and VIP check: Confirm large parties are prepped, VIP preferences are communicated to the floor, and any special accommodations are in place.
  4. Vendor and delivery oversight: Verify any scheduled deliveries are received, invoiced, and stored correctly before service.
  5. Mid-shift FOH walkthrough: Check table turns, guest satisfaction signals, server pacing, and host queue management.
  6. Mid-shift BOH walkthrough: Verify ticket times, station cleanliness, temperature log completion, and prep levels.
  7. Labor vs. sales check: Pull a mid-shift labor report and compare against projected sales. Flag any variance above your threshold to ownership.
  8. Coaching moment: Document one specific coaching interaction (staff member, standard addressed, outcome). This is the MOD's most underused tool.
  9. Incident log update: Record any guest complaints, injuries, refusals of service, or equipment failures with timestamps.

Mid-shift handover protocol

The swing transition is the highest-risk moment in a restaurant's day. A formal handover takes ten minutes and prevents hours of recovery.

The outgoing MOD verifies and documents: current par levels and any shortages, all temperature log entries since opening, the updated 86 list, any open maintenance issues, and any incidents or corrective actions from the shift. The incoming MOD signs the handover checklist, acknowledging receipt of all open items. Any corrective action that has not been closed (a cooler still running warm, a vendor dispute unresolved) escalates immediately to the incoming MOD's action list.

Items requiring proof: temperature photos for any out-of-range reading, delivery invoices signed by the receiving manager, and incident notes with timestamps and staff signatures. The MOD closes corrective actions; ownership does not transfer until the incoming MOD signs.

Pro Tip: Use the MOD checklist as an archival record, not a surveillance tool. When a health inspector asks what happened on a specific date, a completed MOD log with incident notes and corrective actions is your best evidence. Managers who understand this treat the checklist as professional documentation, not a report card.


Key Takeaways

A complete restaurant operations checklist system, built around role ownership and time-stamped records, is the most direct path to consistent shifts and defensible compliance.

PointDetails
Start with closingPilot the closing checklist first for two weeks; it delivers the fastest ROI on food cost, safety, and cash security.
Require timestamps and photosTime-stamped, photo-backed temperature logs are the difference between a managed event and a health code citation.
MOD is supervisory, not manualThe MOD checklist should drive pacing, coaching, and quality assurance, not manual prep or cleaning tasks.
Keep lists shortCap each role's shift checklist at 12 items; move low-risk admin tasks to a weekly list to prevent skip-under-pressure.
Wits' End Solutions as your partnerWits' End Solutions provides checklist templates, training programs, and taskforce support to implement these systems across single or multi-location operations.

Why checklists fail in practice, and what actually fixes it

Most operators I work with already know they need checklists. The gap is almost never awareness; it is accountability structure. A checklist without a named role owner and a completion review mechanism is just a suggestion posted on a wall.

The pattern that works: assign ownership by position, not by person; build the review into the MOD's end-of-shift routine; and treat a missed checklist item the same way you treat a missed temperature log entry. Both are operational failures. Both have consequences. When managers frame checklists as professional documentation rather than busywork, adoption follows naturally. Staff who understand that a completed temperature log protects them as much as it protects the restaurant take it seriously.

The other thing I see consistently: operators who try to build a perfect checklist before launching any checklist. Start imperfect. A closing checklist with eight items that gets completed every night beats a 30-item masterpiece that nobody finishes. Iterate quarterly, involve the team, and let the data from your digital tool tell you where the gaps are.


How Wits' End Solutions helps you build this system

Running a compliant, consistent operation across one location is hard. Across multiple sites, it requires a system, not just good intentions. Wits' End Solutions works with restaurant and hotel operators across the United States to design and implement checklist systems that actually stick: role-mapped ownership, digital or paper formats calibrated to your team, and analytics reporting that turns completed checklists into trend data your leadership team can act on.

For operators who need faster results, our taskforce services place experienced operators on-site to pilot checklist systems, train managers on MOD protocols, and hand off a running operation within weeks. No long-term contract required to get started. Contact Wits' End Solutions to request a template set or schedule a brief operational assessment.


Useful sources for compliance and further reading

  • FDA Food Code (2022): The federal baseline for temperature, allergen, and sanitation standards in U.S. food service operations.
  • CDC Foodborne Illness Response Guidance: Protocols for responding to suspected outbreaks, including isolation of implicated food and health department notification.
  • Your State Health Department: Inspection scoring criteria, local temperature variance rules, and log retention requirements vary by state. Check your state's environmental health division for the applicable standards.
  • Clover Blog — Restaurant Checklists for Daily Operations: Practical FOH and BOH checklist examples organized by operational area.
  • Wits' End Solutions — Daily Restaurant Operations Guide: Operational workflow guidance for managers building shift-based systems.
  • Wits' End Solutions — Restaurant Launch Checklist: Pre-opening and launch-phase checklist guidance for new venues.
  • Wits' End Solutions — Training Programs: Manager and staff training that reinforces checklist adoption and service standards.