Employee Shift Scheduling App Starter · Industry version
Occupancy-driven rosters across housekeeping, front desk, F&B, and events — scheduling code your property owns.
A hotel never closes, so its schedule never resolves — it just rolls: night audit hands to morning desk, housekeeping loads by last night's occupancy, and Saturday's wedding needs a banquet crew that doesn't exist on Tuesday. This starter generates scheduling for a property that runs in departments but staffs as one building.
01 · The problem
Hotel demand is written in the PMS, not on the calendar: tonight's occupancy decides tomorrow's housekeeping load, arrivals and departures shape the desk's peak hours, and a full house on Friday means a different building than the same Friday at 40 percent. A scheduler that can't take occupancy as an input staffs every week like an average week — which is exactly wrong in both directions.
The property is also five businesses sharing one roof. Housekeeping is piecework-paced room coverage, the front desk is a 24/7 continuity chain where an unfilled 11 p.m. shift means a manager sleeping in the office, F&B flexes to breakfast counts, engineering runs on-call, and banquets staff to an events calendar. One flat employee list with start times models none of them — and cross-trained staff who bridge departments become scheduling orphans.
And the night is a first-class problem. Night audit is a specific, certified role that must be filled every single date; overnight coverage carries its own differentials and rest math; and handoffs between shifts are operational moments, not just boundaries on a grid. Tools built for daytime businesses treat 3 a.m. as an edge case; a hotel treats it as Tuesday.
02 · Data model
Everything in the base Employee Shift Scheduling starter —
employeeslocationsshiftsshift_swapstime_entriesavailability— plus the entities this industry actually runs on:
| table | what it holds |
|---|---|
departments | Housekeeping, front desk, F&B, engineering, banquets — each with its own roles, rules, and staffing logic under one property. |
occupancy_forecasts | Expected rooms, arrivals, and departures by date — the demand signal that sizes housekeeping and desk coverage. |
event_bookings | Banquets, conferences, and functions with dates, headcounts, and the crew requirements they inject into the schedule. |
03 · Screens
Housekeeping staffing computes from forecast rooms at your credits-per-attendant rate; desk coverage shapes around arrival and departure peaks. When the forecast moves — a group cancels, a city event sells the house out — the affected days flag for restaffing.
Front desk and night audit render as an unbroken chain across dates, where any gap is an alarm, not a blank cell. The night-audit slot enforces its certification requirement, and handoff overlaps are scheduled minutes, not accidents of rounding.
A banquet booking carries its crew needs — servers, bartenders, setup — and injects those shifts into the schedule weeks out. Cross-trained staff from other departments appear as eligible picks with their rest and hour math intact, so the wedding staffs without breaking Sunday breakfast.
04 · In practice
The occupancy forecast jumps for the weekend. Housekeeping's Saturday requirement recalculates to fourteen attendants, the gap shows against the current roster of ten, and offers go out to part-timers and cross-trained staff — days ahead, instead of a panicked morning call-around.
Sales confirms a 180-guest wedding for the 21st. The event's crew template drops twelve shifts into banquets for that date; eligible staff claim them, gaps escalate to the F&B manager, and the labor cost lands on the event's P&L line, not lost in the department average.
The continuity board shows audit coverage six weeks forward. When the regular auditor books leave, the gap flags immediately, the two certified backups are offered the dates, and the differential is applied automatically — the one shift a hotel can never miss, never missed.
Yes — occupancy, arrivals, and departures per date drive computed requirements: housekeeping from rooms at your credit rate, desk coverage from arrival and departure peaks. Forecast changes reflag the affected days, so restaffing happens ahead of the rush rather than during it.
Departments are first-class, each with its own roles, rules, and staffing drivers — piecework-paced housekeeping, continuity-chained front desk, event-driven banquets. Cross-trained employees hold eligibility in several departments with one profile and one set of hour and rest math.
Overnight roles carry their own pay differentials, certification requirements, and rest rules, and night audit is modeled as a must-fill chain with no permissible gap. The labor cost view prices differentials in, so the true cost of the night is visible, not discovered at payroll.
Yes — event bookings carry crew templates that inject dated shifts into the schedule automatically, with claims, gap escalation, and per-event labor costing. The banquet manager staffs the wedding from a list of eligible, rested, cross-trained people instead of a phone tree.
Dual7 App Starters
Occupancy-driven rosters across housekeeping, front desk, F&B, and events — scheduling code your property owns. Describe your version to start — the output is a project you own.