Hotel operators facing ESG and utility-reporting requirements usually ask the AV question last: not "what does the guest see," but "what does the energy report show at the end of the month, and can we prove it?" That question sits upstream of the guest experience entirely — it lives in how the guest-room system talks to the property management system on check-in and check-out, and how that data eventually reaches a building management system.
How occupancy state actually triggers a setback
A guest-room automation platform does not independently decide a room is vacant. It is told. Crestron's guest-room management documentation describes the sequence directly: when a guest enters a room, presence sensors trigger a welcome scene and simultaneously report occupancy back to the Guest Room Management System (GRMS); on departure, the door lock event triggers "a smooth, energy-saving exit automation process: lights turn off, shades and drapes close, HVAC adjusts to eco mode, audio mutes or powers off, and the TV shuts off," with occupancy sensors updating the GRMS again (Hospitality Guest Rooms, Crestron Electronics). In practice this means the setback logic is a chain of inputs working together — door lock state, occupancy sensor, and PMS check-in/check-out status — rather than any single sensor acting alone. A property evaluating a guest-room platform should ask its integrator which of those inputs fires the setback, and what should happen if one of them disagrees with the others — a housekeeping cart left in a doorway, for instance, or a guest who unlocks the door but doesn't enter.
Crestron's broader hospitality materials frame this as part of the business case rather than a side effect: vacancy sensors, smart thermostats, and lighting/shading control "combine to deliver a powerful solution for reducing energy costs and increasing efficiency, while meeting your local green building standards" when integrated with BMS software (Hospitality Solutions, Crestron Electronics). That framing matters for a property comparing vendors: the setback behavior and the reporting behavior are meant to be designed together, not bolted on afterward.
What the dashboard actually reports, and where it goes
The GRMS dashboard itself is the reporting layer a property manager actually looks at. Crestron's documentation describes "a dashboard view for efficient monitoring and management of rooms and devices" fed by the PMS/GRMS integration, with the standard, luxury-suite, and penthouse room tiers all listed as compatible with PMS, BMS, and GRMS reporting (Hospitality Guest Rooms, Crestron Electronics). Whether that view aggregates to the floor level or stays per-room is a configuration decision that should be specified during design, not assumed — ask your integrator what granularity the reporting dashboard will actually expose before you commit to it as an ESG data source.
The technical path from a guest room to a building-wide energy report runs through BACnet. Crestron's enterprise control platform documentation confirms native BACnet network/IP support, describing it as providing "a direct interface to third‑party building management systems over Ethernet, simplifying integration with HVAC, security, and other systems" — with object-count limits that scale by license tier, up to 10,000 BACnet objects on a server dedicated to BACnet use (VC-4 Features, Crestron docs). A similar native BACnet interface is documented on Crestron's residential-grade PC4-R processor, supporting up to 2,000 objects out of the box with no additional licensing (PC4-R Manual, Crestron docs). The practical implication for a hotel project: the number of BACnet objects a property needs to expose — one per room sensor or setpoint, multiplied by room count — should be sized against the license tier before construction, not discovered after a BMS integrator asks for a point list that the room controller can't deliver.
Questions worth resolving before rollout
None of this reporting chain is automatic by default — it has to be specified. Properties evaluating this for ESG reporting should resolve, during design rather than after go-live: which PMS field (check-out, housekeeping status, or door event) is the authoritative trigger for the setback; whether the dashboard reports energy data per room or only aggregated by floor; and how many BACnet objects the server license needs to support across the full room count plus common-area systems. Ask your integrator to confirm these answers in writing before construction, since changing them after commissioning tends to mean a second project rather than a configuration change.
Cave Group designs custom guest-room automation on Crestron, and packaged guest-room systems on Lutron myRoom, as part of its hospitality practice, integrating that control layer with the PMS platforms a property already runs. For properties scoping a renovation or new build where energy reporting is part of the brief, that integration work is worth specifying alongside the guest-facing scenes, not after them.