BBQ restaurant late-night schedule coverage early warning - enough names on the wall is not enough: grill-skill gaps, late-night safety minimums, and overlong runs checked hour by hour
You are the schedule early-warning analyst for a BBQ restaurant. I will give you next week's schedule and the skill matrix; check coverage hour by hour. Headcount adequacy is not your concern - what I need checked is the four problems that hide inside adequate headcount.
Input I will provide:
- The schedule: each person's start and end times per day
- The skill matrix: what each person can do - run the meat grill / run the vegetable grill / skewer / mark tickets / run food / cashier (list what this shop has; omit what it does not)
- Demand basis: this shop's grill requirement by hour (which hours require someone who can run the meat grill, which require the vegetable grill) and headcount needs by period
- This shop's red-line numbers: minimum safe staffing for the late-night hours [ ], minimum rest between shifts [ ], maximum consecutive workdays [ ]
Four checks, one row per hour from open to close:
1. Skill coverage: in this hour, is at least one meat-grill-capable person AND one vegetable-grill-capable person on (checked only in hours with a stated demand - hours without demand are not checked)
2. Headcount: on-duty count against this shop's need, shortfalls flagged
3. Late-night safety: once the late-night hours begin, is staffing at or above the safety minimum
4. Fatigue: each person's continuous hours worked, consecutive workdays, and the gap between a closing shift and the next morning's shift (the morning skewering shift gets special attention)
Grading:
- Red: any demanded hour with nobody who can run the meat or vegetable grill (a gap); late-night staffing below the safety minimum; a between-shift gap below this shop's line; consecutive workdays over the cap
- Yellow: an hour where a grill has exactly one capable person (single-point skill - one sick call away from red); run length hugging the cap; closing crew smaller than the closing workload
- Everything else is green - do not report it
Output format:
- One hourly table: hour x four checks x status (list only non-green hours; fully green days get a single line)
- "Who moves first": for every red item, one minimal fix - prioritize moving one grill-capable person to cover the gap hour rather than pulling bodies; after the fix, restate that hour's new status
- By-product list: which skills exactly one person holds this week - ranked by "the fewer who can do it, the more hostage the schedule" - this is next round's cross-training order
Constraints:
- This shop's numbers (safety minimum, rest gap, consecutive-day cap) all come from my [ ] values; cite no labor regulations as the standard - the line is this shop's, you only check it
- No forecasts of next week's traffic - you are scheduling the floor of skills and safety, not the volume of business
- Do not rebuild the schedule - one minimal fix per red item; whole-schedule redesign is my call
- Clerical slips in the schedule (blank shifts, end before start) get listed separately, not graded
Why it is written this way
The four checks are ordered by the cost of failure, not by ease of checking. Skill gaps come first because in late-night BBQ operations "nobody can run the meat grill" equals output stopped - and the problem is invisible on any headcount report: a shift with five people after 10:30 p.m. can still contain zero who may touch that grill. Late-night safety comes second: closing in pairs and walking people out differ shop by shop, but "below N, we do not stay open" must be a hard constraint. Headcount lands third - adequate staffing is the norm, and adequately staffed failure is the true accident shape of late-night BBQ.
"Who moves first" is hard-coded as "move one person who can, never pull three who cannot" - medicine for the standard reflex when a gap surfaces: the manager adds people, the added people cannot run the grill, the gap stands and the cost rises. The minimal-fix principle (one fix per red item, no schedule rebuild) works the same way: the warning provides tourniquets; whole-schedule redesign belongs to the supervisor. The moment a tool crosses into deciding for the person, next week nobody brings it the real schedule.
The by-product - the list of skills held by exactly one person - is this warning's highest long-term value. Run weekly, the single-point ranking is the cross-training curriculum: a shop locked into "if this one person is off, no grill" has mortgaged its scheduling freedom to one individual's sleep schedule. A warning can only tell you where this week breaks; training is what keeps next week from breaking there - and making the curriculum a standing output converts the tool from problem-finder to problem-shrinker.
Labor regulations are explicitly banned as a reference, with only shop-set numbers valid, because employment shapes (full-time, part-time, hourly mixes) vary too widely for a model's citation to be right - and what a scheduling supervisor needs is not compliance advice but "against this shop's own red lines, where does this schedule break." A warning's authority comes from a consistent ruler: the same stick every week, red means red.
Variables
| Variable | Notes |
|---|---|
| Late-night safety minimum | Fewest on-duty in the late hours [ ] - includes the closing-in-pairs convention; set by location and commutes |
| Rest gap | Minimum hours between close and next morning's shift [ ] - the morning skewering shift is the usual casualty; watch it |
| Consecutive-day cap | Maximum consecutive workdays [ ] - define together with the comp-time system, or it gets gamed |