Shift Leader Daily Coaching & Priorities Checklist

Interactive shift checklist to help shift leaders prioritize guest experience, keep service and quality on standard, capture coaching moments, and close the shift with clear actions. Saves a concise record for later review and trend spotting.

{ "Title": "Shift Leader Daily Coaching & Priorities Checklist", "IntroductionHtml": "

Use this short guided checklist each shift to keep the team focused on guest experience, throughput, and staff development. This form captures a concise, searchable record you can review later to spot trends, follow up on actions, and coach consistently across shifts. Aim for quick entries: most fields can be completed in 2–4 minutes while you walk the floor.

Why this matters: Regular, short coaching moments and clear handoffs keep standards steady between shifts, reduce guest problems, and help people learn on the job. This checklist helps you notice, act, and follow-up.

Quick coaching script (use as a 60–90 second conversation)

Observe: "I noticed you (specific behavior)."

Impact: "That affected (guest experience/flow/quality/team)."

Ask & Align: "What do you think we should do differently next time?"

Agree on next step: "Let's try (specific action) on the next ticket. I’ll check in after two orders."

Keep it short, factual, and next-step focused. Use praise the same way: "I noticed you . That made the guest's experience better because . Keep it up."

Tip: If you check a problem more than once, add it as an action item so it doesn't slip between shifts.

", "SubmitLabel": "Save shift checklist", "SuccessMessage": "Shift checklist saved — thank you. You can revisit these notes later to track improvements and follow up on actions.", "DataType": "ShiftLeaderChecklist", "SchemaVersion": "1.1", "Fields": [ { "Key": "shift_id", "FieldType": "text", "Label": "Shift date and name (e.g., 2026-09-12, Dinner)", "HelpText": "Enter the shift date and whether it's breakfast/lunch/dinner/closing or a location-specific identifier.", "Required": true }, { "Key": "location", "FieldType": "text", "Label": "Location / station (optional)", "HelpText": "If you manage multiple sites or stations, note which one this entry refers to.", "Required": false }, { "Key": "lead_name", "FieldType": "text", "Label": "Your name / initials", "HelpText": "Who completed this checklist?", "Required": true }, { "Key": "morning_priorities", "FieldType": "checkbox", "Label": "Pre-shift priorities confirmed", "HelpText": "Check the items you confirmed before service began.", "Options": [ { "Value": "staffing_confirmed", "Label": "Staffing confirmed and roles assigned" }, { "Value": "prep_par_levels", "Label": "Prep completed & par levels checked" }, { "Value": "mise_en_place_ok", "Label": "Mise en place and station readiness" }, { "Value": "reservations_reviewed", "Label": "Reservations / expected covers reviewed" }, { "Value": "systems_ready", "Label": "Service tools ready (POS, printers, tickets)" } ] }, { "Key": "morning_notes", "FieldType": "textarea", "Label": "Morning notes / staffing issues to watch", "HelpText": "Capture anything the incoming shift should know or follow up on (e.g., late staff, low prep)." }, { "Key": "midshift_checks", "FieldType": "checkbox", "Label": "Mid-shift quality & throughput checks", "HelpText": "Quick checks to do while service is underway.", "Options": [ { "Value": "ticket_time_ok", "Label": "Ticket times within target" }, { "Value": "presentation_consistent", "Label": "Plate presentation consistent" }, { "Value": "temp_checks_done", "Label": "Temperature checks performed" }, { "Value": "handoffs_ok", "Label": "Handoffs between expo and servers smooth" }, { "Value": "hygiene_observed", "Label": "Handwashing & hygiene observed" } ] }, { "Key": "midshift_quality_score", "FieldType": "scale", "Label": "Mid-shift quality score", "HelpText": "Rate overall quality and flow right now (1 = serious problems, 5 = running very well).", "ScaleMin": 1, "ScaleMax": 5 }, { "Key": "guest_recovery_count", "FieldType": "number", "Label": "Number of guest recoveries (complaints resolved) this shift", "HelpText": "Count of times you or the team recovered a guest's bad experience (refunds, re-makes, manager interventions).", "Required": false }, { "Key": "guest_recovery_notes", "FieldType": "textarea", "Label": "Brief guest recovery notes (what happened, how resolved)", "HelpText": "Capture one-line context for later review and pattern spotting." }, { "Key": "coaching_occurred", "FieldType": "yesno", "Label": "Did you coach any team member during this shift?", "HelpText": "Coaching includes short corrective or positive conversations using the script above." }, { "Key": "coaching_count", "FieldType": "number", "Label": "Number of coaching moments captured", "HelpText": "Estimate of coaching conversations during the shift (optional).", "Required": false }, { "Key": "coaching_details", "FieldType": "textarea", "Label": "If yes, who and what (one-line per coaching moment)", "HelpText": "Example: 'Maria — portion consistency — agreed to tweak plating order.'" }, { "Key": "safety_incident", "FieldType": "yesno", "Label": "Any safety incident or near miss?", "HelpText": "If yes, provide details below so it can be escalated and recorded." }, { "Key": "safety_details", "FieldType": "textarea", "Label": "Safety incident / near miss details", "HelpText": "Short description, location, who was involved, and immediate actions taken." }, { "Key": "equipment_issue", "FieldType": "yesno", "Label": "Any equipment or facility issues observed?", "HelpText": "Examples: oven not reaching temp, broken refrigerator door, POS problems." }, { "Key": "equipment_details", "FieldType": "textarea", "Label": "Equipment / facility issue details", "HelpText": "Describe the issue and any temporary workarounds." }, { "Key": "end_shift_well", "FieldType": "textarea", "Label": "End-of-shift: What went well?", "HelpText": "Capture concrete examples you want the team to repeat." }, { "Key": "end_shift_improve", "FieldType": "textarea", "Label": "End-of-shift: What needs improvement?", "HelpText": "Be specific so improvements can be assigned and measured." }, { "Key": "action_items", "FieldType": "textarea", "Label": "Action items (who, what, when)", "HelpText": "List actions, the person responsible, and a due date or next-check time. Example: 'Tom — reorder tomatoes — by next morning'. Use one line per item." }, { "Key": "action_item_priority", "FieldType": "select", "Label": "Overall action priority for next shift", "HelpText": "Choose the priority level to help the incoming leader triage follow-up.", "Options": [ { "Value": "low", "Label": "Low" }, { "Value": "medium", "Label": "Medium" }, { "Value": "high", "Label": "High" } ] }, { "Key": "handoff_complete", "FieldType": "yesno", "Label": "Handoff completed to next manager/supervisor?", "HelpText": "Confirm next leader received key notes and actions." }, { "Key": "handoff_notes", "FieldType": "textarea", "Label": "Handoff notes (who received it / any follow-up required)", "HelpText": "Short note about the handoff." }, { "Key": "escalation_required", "FieldType": "yesno", "Label": "Is escalation required (e.g., corporate, maintenance, food safety)?", "HelpText": "If yes, provide details so the appropriate team can be notified." }, { "Key": "escalation_details", "FieldType": "textarea", "Label": "Escalation details (who should be notified / why)", "HelpText": "Provide suggested contacts or next steps for escalation." }, { "Key": "final_comments", "FieldType": "textarea", "Label": "Any other notes or risks to escalate", "HelpText": "Use this for supplier issues, equipment problems, safety concerns, or persistent quality problems." } ] }

Discussion

Comments and conversation will live here.