ADR, occupancy, RevPAR, TRevPAR, MPI, ARI, RGI, total revenue, comp-set language, and fair-share concepts are used as recognizable hotel vocabulary.
Public evidence reference
What users can inspect and what remains protected.
| Evidence area | Buyer-safe explanation | Protected boundary |
|---|---|---|
| Rooms economics | Occupancy, ADR, RevPAR, TRevPAR, MPI, ARI, RGI, pickup, cancellation/no-show risk, direct/OTA mix, and channel cost frame the commercial choice. | Private scoring, thresholds, weighting, rate-move rules, and channel-risk logic. |
| Rooms readiness | Housekeeping turns, stayovers, front desk waves, OOO rooms, supplies, overtime, leadership readiness, and room-type promise frame whether the stay is executable. | Readiness bands, pressure weighting, exception ranking, and room-release logic. |
| F&B / events | Outlet revenue, breakfast capture, banquet covers, BEO confidence, shared service load, and event labor show total property pressure. | Event-risk weighting, cannibalization logic, protected BEO confidence rules, and proprietary acceptance bands. |
| Owner economics and displacement | GOP, GOPPAR, net RevPAR, material flow-through, budget variance, reserve exposure, and group value versus displaced transient demand translate top-line performance into an owner decision. | Private cost allocations, forecast assumptions, commercial thresholds, and group acceptance rules. |
| Facilities and capital | Preventive maintenance, critical assets, life-safety readiness, utility variance, sustainability measures, vendor coverage, and capex at risk remain visible beside sellable inventory. | Asset-priority rules, risk severity, engineering release logic, and owner capital-policy thresholds. |
| Decision guard | The system shows owner priority, commercial lever, weakest constraint, decision confidence, displacement exposure, brand promise risk, and human approval boundary. | Exact gate math, conflict-resolution order, coefficients, and protected prioritization mechanics. |
| Approval and audit | Status, authority, actor, due time, release conditions, override reason, and evidence reference are attached to the same decision record. | Production permission enforcement, separation-of-duties policy, append-only server audit implementation, and export controls. |
| Actuals and memory | Forecasts are compared to real rooms, ADR, F&B, labor, OOO, guest issues, outcome, feedback route, and written variance reason. | Memory eligibility, matching, source-conflict resolution, comparable-date logic, and return conditions. |
| People protections | Shift pressure, short turns, consecutive days, training readiness, manager support, role clarity, and qualifying aggregate feedback support coverage and recovery routing. | No individual scoring, discipline, termination, health inference, loyalty inference, protected-class inference, or hidden employment selection logic. Response-threshold, suppression, and prioritization mechanics remain private. |
Transferable ChefQuote logic
The domain changes. The closed-loop operating spine remains.
| ChefQuote layer | Hotel translation | What the user sees | Protected boundary |
|---|---|---|---|
| Operating intake | Property, segment, date pattern, stay promise, stakeholder, and decision window. | A guided hotel record that starts with the decision being made, not with a generic report. | Decision-routing rules and private prompt/source orchestration. |
| Source state | PMS, CRS/RMS, POS, labor, housekeeping board, maintenance, finance, guest feedback, CSV, and PDF evidence. | Imported, reviewed, manual, stale, and unavailable states remain visible beside the working inputs. | Source hierarchy, conflict logic, validation order, and confidence math. |
| Role calculators | Rooms/revenue, labor/readiness, people protection, F&B/events, guest recovery, finance/owner, and actuals. | Each station answers one operating question while returning to the same record. | Station scoring, weightings, edge-case rules, and source-specific quality adjustments. |
| Decision packet | GM, revenue, rooms, engineering, F&B, people, and owner packets. | Different roles see different explanations from one shared decision record. | Permission rules, role-level suppression, and export-visibility controls. |
| Actuals and return | Actual revenue, labor, guest issues, OOO rooms, variance reason, feedback route, and approved memory. | The system learns only when a human accepts, adjusts, or rejects a lesson. | Memory matching, versioning, and future-return eligibility. |
Hotel industry input used
The operating method is grounded in established hotel practice.
Demand, strategic, revenue, and operational forecast thinking informs the handoff from market signal to pricing, staffing, purchasing, cash-flow, and execution choices.
Rooms, F&B, other operated departments, labor/FTE reporting, owner/operator costs, and sustainability/utility reporting inform the public financial boundaries.
Demand resilience, cost pressure, labor/wage pressure, taxes, and profitability compression are treated as operating context, not decoration.
ENERGY STAR benchmarking and NIST hotel property-management guidance inform utility evidence, integration boundaries, and the production security roadmap.
NIST, DOL, and EEOC sources support a product stance that keeps people protections visible and blocks employment-selection use of pressure signals.
Most tools show departmental facts. This layer links facts to a governed decision, role packet, feedback route, actuals closeout, and reviewed memory.
Decision layer public explanation
How a hotel decision moves through the product.
Show what is imported, reviewed, manual, stale, or unavailable before trusting the result.
Read occupancy, ADR, RevPAR, TRevPAR, comp-set indices, pickup, and cancellation/no-show risk.
Choose whether to push rate, hold mix, clarify rate fences, shift channel mix, condition group/event demand, or stimulate demand.
Translate forecast into housekeeping turns, desk load, engineering release, F&B load, recovery coverage, and supplies.
Protect the team and the guest promise before the system recommends releasing more work.
Separate top-line revenue from labor, acquisition cost, flow-through quality, displacement, and owner cash lens.
The GM, owner, asset manager, or responsible leader approves, conditions, or holds the recommendation with a written reason.
Only reviewed actuals and variance reasons can return to future comparable decisions.
References and attribution
References define the measures, safeguards, and decision context.
- CoStar / STR Benchmark Glossary — hotel KPI vocabulary including ADR, occupancy, RevPAR, TRevPAR, MPI, ARI, and RGI.
- HSMAI Different Forecasts for Different Objectives — demand, strategic, revenue, and operational forecast framing.
- HSMAI Commercial Resource Hub — commercial strategy, forecasting, segmentation, rate fences, and total revenue concepts.
- HSMAI Sales Acumen Glossary — group displacement and total-value decision vocabulary.
- AHLA 2026 State of the Industry report page — hotel demand, cost, labor, wage, tax, and profitability context.
- AHLA/HFTP USALI announcement — lodging accounting/reporting standard context and 12th edition adoption timing.
- NIST AI Risk Management Framework — AI risk management posture for impacts to people, organizations, and society.
- NIST Securing Property Management Systems — hotel PMS security and integration risk context.
- ENERGY STAR Portfolio Manager benchmarking — energy, water, waste, and emissions benchmarking categories.
- U.S. Department of Labor AI worker principles release — worker well-being, transparency, worker engagement, rights protection, and enhancing work.
- EEOC Employment Tests and Selection Procedures guidance — caution against discriminatory employment use and adverse-impact risk.
This page publishes the decision categories, evidence expectations, role boundaries, and human controls. ChefQuote Hotel OS calculations, weights, coefficients, source-control mechanics, role-suppression rules, and memory-matching logic remain protected. A production deployment should place authentication, authorization, calculation, and storage behind server-side services.