CSV headers can fill rooms, rate, channel mix, F&B, labor, housekeeping, maintenance, actuals, and people-support fields when names match the template.
Single-property decision control
One property. One accountable operating decision.
Connect demand, profitability, labor, facilities, guest impact, approval, actuals, and reviewed memory without forcing every department through the same screen.
Station 1 · Intake
Define the property decision before the departments start solving different problems.
Hotels need the same decision spine as ChefQuote, but the inputs are different: date pattern, segment, room inventory, owner promise, and the department load behind the sell.
Station 2 · Imports and source state
Bring in hotel sources, but keep assumptions visible.
PMS/CRS/RMS, POS, labor, housekeeping boards, maintenance, guest feedback, and finance rarely tell the same story at the same time. Source state is part of the decision, not a footnote.
PDFs are treated as supporting evidence. They do not silently change numbers until a person maps the values into visible fields.
Every upload updates the source ledger as imported, reviewed, manual, stale, or unavailable so the decision record shows what is trusted.
Station 3 · Rooms and revenue
Model the revenue decision with inventory reality attached.
Rooms revenue cannot stand alone. Occupancy, ADR, RevPAR, TRevPAR, comp-set strength, channel cost, pickup, and cancellation risk have to be read before the operating handoff.
Commercial + owner economics
Translate rooms demand into profit, cash exposure, and group value.
RevPAR alone cannot approve the decision. This layer adds net room revenue, GOPPAR, budget variance, flow-through, and a transparent group displacement comparison.
Forecast, budget, and profit conversion
Compare total group value with displaced transient demand
Station 4 · Labor and readiness
Do not sell a stay the departments cannot deliver.
Housekeeping turns, front desk arrival pressure, engineering tickets, out-of-order inventory, supplies, and overtime become operating gates before the decision is released.
Station 5 · People support + protections
Turn operating pressure into a named support plan.
Schedule evidence and qualifying aggregate feedback are kept separate, then brought together for support routing. This station can change coverage, training, tools, recovery time, and manager support. It cannot create individual scores or inform discipline, termination, compensation, promotion, health, loyalty, intent, or protected-class inference.
Schedule and workload evidence
Qualifying aggregate feedback
Compare the same support conditions
Assign the corrective operating plan
Schedule and hotel workload before release.
Ready for evidenceRecovery, tools, clarity, and manager availability after the event.
Select to evaluatePersistent voice, fairness, recognition, recovery, and stability.
Select to evaluateCompare manager estimate to qualifying team aggregate.
Select to evaluateStage 7 · F&B and events
Plan food and beverage by service model.
Set revenue, covers, labor, direct cost, and capacity for each active outlet.
Revenue mix
Enter revenue by outlet.
Service load + capacity
Match forecast covers to service capacity.
Cost + labor
Set direct costs and labor.
Legacy blended labor inputs
Facilities + operating risk
Keep sellable inventory, life safety, utilities, and capital exposure in the decision.
A room can be physically available and still be operationally unsafe or economically poor. This station connects preventive maintenance, critical assets, energy and water cost, safety readiness, and deferred capital work.
Station 7 · Decision guard
Turn hotel signals into a human-owned operating choice.
The guard reads the commercial upside, the operating constraint, the guest promise, the people boundary, and the owner priority together. It explains the suggested move without publishing protected scoring mechanics or silently overriding the GM, owner, revenue leader, or department heads.
Build the decision to see how the hotel operating layer connects source evidence, demand, capacity, guest promise, people protection, finance, and owner judgment.
Station 8 · Role packets
Generate the operating document each role must execute.
Every packet starts from the same decision record, then applies a strict role boundary. Each one includes the call, role-specific measures, evidence, blocker/warning/lever matrix, action owners, approve and hold conditions, source gaps, next handoff, and actuals rule.
Approval + governance
Record who can approve, what conditions remain, and why an override is justified.
Server-verified roles control who can review, operate, edit, and approve. Every committed approval is written to the encrypted property record and its audit trail.
Station 9 · Actuals and variance
Close the loop after the stay, event, or date pattern actually happens.
The product value is not only the forecast. It is the return path: actual rooms, rate, labor, issues, OOO inventory, outcome, and variance reason.
Station 10 · Feedback routing
Route feedback to the accountable hotel owner.
Guest comments, front desk pressure, housekeeping misses, revenue exceptions, BEO issues, finance variance, and engineering blockers need different routes.
Station 11 · Governed memory
Do not let one strange night silently rewrite the next decision.
Hotel memory must be comparable: segment, date pattern, room availability, source state, staffing, event load, and guest context need to match before reuse.
Packet library + audit
Eight bounded documents. One saved operating record.
Download a print-ready HTML from current values or open the included sample PDF. Every export preserves its role boundary, source caveats, release conditions, handoff, and closeout obligation. Working records and audit events are stored through the authenticated Hotel Operations service.