Energy management and room controls in hotels: what to check before investing
Judge room control offers on their mechanisms, not promises. Learn to verify savings with your own meters and ensure PMS links prevent guest complaints.
Contents
Key takeaways
- A room control system saves money only in the hours it actually switches something off, so the quality of the emptiness signal matters more than the control unit itself.
- Without a link to the PMS, a system cannot tell a sold room from an empty one, and the guest who arrives at a set-back room pays for the saving with a complaint.
- The complaints are predictable: a warm room on arrival, lights that go out while a guest sits still, and sockets that die when the key card leaves the slot.
- Savings are proved by your own meter readings over a comparable period, adjusted for occupancy and outdoor temperature, not by a figure in a proposal.
- Sensors and valves fail quietly, so the system needs an owner, a monthly review and alarms for rooms that report occupied for weeks.
A hotel energy management system switches heating, cooling and lighting according to whether a room is occupied, and records what it did. Before investing, check three things: how reliably a room detects that it is empty, whether the system reads the PMS so sold rooms are ready on arrival, and whether you can measure results on your own meters.
The proposal says the system pays for itself in two years. Nobody at the hotel has a meter on that floor, so no one can check the claim. The first real test arrives on a July afternoon, when a guest walks into a room that was cooled to nothing and calls the front desk. After reading this, you will be able to judge a room control offer on its mechanisms rather than its promises, and set up a measurement that proves or disproves the payback figure on your own property.
What does a hotel energy management system actually control?
It controls the three things that use most of a room's energy: heating, cooling and lighting, switched by whether the room is occupied. Everything else in the offer is either a sensor, a report or a promise.
The in-room control unit sits between the thermostat, the fan coil or valve, and the lighting circuits. It decides what happens when the room is empty and what happens when a guest returns. Typical actions are a set-back or switch-off of cooling and heating, shutting the fan coil, cutting selected lighting circuits and sometimes the bathroom extractor. Some systems also control curtains or a water heater.
The three layers: room, riser, software
The room layer is the control unit and its sensors. The riser layer is the cabling and the connection back to a central system. The software layer is where signals become actions and records. Vendors bundle these differently, so ask which parts you are buying and which parts are assumed to exist already.
Most of the saving comes from hours, not from devices. A room that is empty for six hours a day and set back for those hours is where the money is. The control unit only decides how quickly the room returns to comfort when someone comes back.
The system also produces a record: which rooms were empty, when, at what temperature, and who overrode what. That record is the part most hotels never read, and it is the part that tells you whether the system works. It is also useful context for how the core hotel systems fit together, since the room control system is one more data source among several.
What a room system cannot do
It is not a building management system. The plant, the chillers, the boiler house and the common areas are a separate discussion. A room system will not fix an oversized chiller or a building with no insulation. Ask early whether the offer covers one room type, one floor or the whole building, and whether common areas, back of house and the laundry are in or out of scope.
How does a room know it is empty?
Through one or more signals: a key card in a holder, a door contact, a presence sensor, or the room status in the PMS. Each proves something different, and each fails in its own way.
| Signal | What it proves | What it misses | Upkeep |
|---|---|---|---|
| Key card holder | A card is in the slot | A second card or a card left in the slot defeats it | Contact wear, guest tape |
| Door contact | The door opened or closed | Cannot tell whether someone is inside | Alignment, battery |
| Motion sensor | Movement in the room | A sleeping or still guest reads as empty | Lens cleaning, placement |
| Radar presence sensor | Small movement including breathing | Higher cost, more configuration | Firmware, false positives through thin walls |
| PMS room status | Sold, arriving, in-house, departed | Says nothing about who is inside | Depends on front desk discipline |
| Thermostat setpoint alone | The guest's last setting | Nothing about presence | None |
Combining signals without annoying the guest
Good systems combine signals and wait. A short delay before switching off, a longer delay before a deep set-back, and a return to comfort the moment the door opens. The key card holder is the cheapest and most common signal, but it is also the easiest to defeat, because a guest can leave a second card in the slot all day. A door contact cannot tell you whether someone is inside, but combined with a card holder it separates a room that was left from a room that is being used.
Motion sensors read movement, so a guest sleeping or sitting still under a blanket can read as empty. Radar-based presence sensors pick up smaller movement, cost more and need more careful configuration. The PMS room status is the only signal that knows the room is sold and a guest is arriving at a given time. It says nothing about who is physically inside, and it is only as good as front desk discipline around room status codes such as VC, VD and OOO.
What happens when a sensor fails
Ask what happens when a sensor is covered, unplugged or out of battery. The safe default is comfort, not saving, and the fault should raise an alarm rather than quietly switch the room to economy. A system that fails toward saving is a system that fails at your guests' expense.
Why does the PMS link decide whether guests notice the system?
Because a sold room is not an empty room. Without the PMS, the system treats a room that is booked for this afternoon exactly like one nobody wants, and the guest walks into a set-back room.
Cooling a room from a deep set-back to a comfortable temperature takes time, and that time is the difference between a guest who notices nothing and a guest who writes a review about the heat. The useful events are arrival date and time, departure, room move, early check-in, late check-out and day use. Ask which of these the system reads and how often.
The events that matter
Housekeeping needs the room in a workable state too. A cleaner needs light and a reasonable temperature, and a room marked as being cleaned should not be treated as empty in the same way as a departed room. Room moves and connecting rooms are where links break in practice: the guest is in 412, the PMS says 414, and the system cools the wrong room. The same discipline applies to key cards, encoders and the link to the PMS, where a wrong room status causes the same class of problem.
What should happen when the link fails
Ask whether the link is one-way or two-way, and what the system does when it is down. The correct behavior is to fall back to comfort and tell someone, not to keep saving quietly. This is the same integration question as any other PMS connection, and it deserves the same scrutiny: which events, which direction, what happens on failure, and who is called when it stops.
Watch outSpecify the fail-safe in writing
If the PMS link drops and the system keeps running on its last known state, sold rooms stay at set-back and guests arrive to a warm room. Specify the fail-safe behavior in writing before signing, and make the failure visible on a screen someone actually looks at.
Which guest complaints should you expect, and how do you prevent them?
They cluster in three places: arrival, the quiet hour when a guest sits still, and the bathroom. All three are predictable, and all three are cheaper to prevent than to answer.
Arrival complaints come from the room being warm or cold because nothing told the system a guest was coming. The fix is the PMS link and a preparation window before the stated arrival time. Stillness complaints come from a guest reading or watching television without moving, who can lose the lights. The fix is a presence signal that does not depend on movement, or a lighting circuit that stays on while the room is occupied.
Sockets are a policy question. Guests charge phones and laptops overnight and expect the socket to work with the card out. Decide the socket policy deliberately and tell guests at check-in. Bathroom extractor fans and bathroom lighting are often overridden by hand, and an override is a signal that the design is wrong for the room.
What to tell guests at check-in
One sentence, the same in every room, about the card and the sockets. Night-time set-back that is too aggressive shows up as a morning complaint about cold, not as an energy report. Keep the empty-room set-back small enough that a returning guest does not notice it. Give the front desk a documented override with a reason code and a log, so the same room is not overridden every week without anyone asking why.
Reading overrides as design feedback
ChecklistPre-launch comfort checks
- Walk into a set-back room in summer and time how long it takes to reach the setpoint.
- Sit still in a room for ten minutes and confirm the lights stay on.
- Confirm which sockets stay live with the card out.
- Confirm the bathroom light and extractor behavior.
- Confirm the night-time set-back and test it in a room overnight.
- Confirm the front desk override and who is allowed to use it.
- Write the check-in sentence staff will say about the card and the room.
Who maintains it, and who reads the data?
The system needs one named owner, a monthly review and alarms that fire when something stops working. Without those three, sensors and valves fail quietly and the savings disappear without a complaint.
Sensors get covered, lenses get dirty, batteries die and valves stick. None of these produces a guest complaint immediately, and all of them reduce the saving. The three alarms worth setting are: a room that reports occupied for an implausible stretch, a room that reports empty while the PMS says in-house, and a link that has been down longer than a day. Both of the first two catch the common failures.
Decide who owns the dashboard: the technical manager for the equipment, the front office for the overrides, the owner for the monthly number. One report with three readers is better than three reports nobody opens. A monthly review of twenty minutes, with the override list and the fault list on one page, is worth more than any additional sensor.
Access, spares and the end of the warranty
Ask about spare parts, controller access and what happens at the end of the warranty. A system you cannot service without the original installer is a system you cannot negotiate with later.
NotePresence data is personal data
Presence patterns in a guest room say something about a guest. Keep retention short, restrict access, and treat the room-level history as guest data, not as building data. Do not let an energy report become a record of when individual guests were in their rooms.
How do you measure savings from your own meters?
Read your own meters, on the same rooms, over comparable periods, and adjust for occupancy and outdoor temperature. A figure in a proposal is not a measurement.
Sub-meter the floor or a sample of rooms before the system goes in. Without a baseline taken before the work, there is nothing to compare against afterwards. Choose a baseline period in the same season and long enough to cover a normal week, and record the occupancy of the measured rooms alongside the reading.
Baseline, control group, weather adjustment
Adjust for the weather: a cooler month will lower consumption with or without the system, so record daily outdoor temperatures and compare periods with similar ones. Keep a control group: rooms on a similar floor, without the system, measured over the same weeks. If the control rooms fall by the same amount, the system did not do it.
| What to record | Why it matters | Example entry |
|---|---|---|
| Meter reading and date | The raw evidence | For example, 14,320 kWh on 3 July |
| Occupancy of measured rooms | Separates saving from a quiet week | For example, 78 of 100 room-nights |
| Daily outdoor high and low | Weather explains most variation | For example, 34°C high, 24°C low |
| Control rooms without the system | Shows what would have happened anyway | For example, same floor, other wing |
| Other changes in the period | The usual false explanation | For example, new lamps in the corridor |
| Complaints and overrides | The cost side of the saving | For example, four override requests |
What else changed: the list to keep
Write down everything else that changed in the period: new lamps, a tariff change, a rate change, a renovation, a different breakfast service. These are the usual explanations for a good-looking result. Read monthly and keep the raw readings. An annual comparison hides the month where the system was off for maintenance.
What should be in the contract before you sign?
The measurable parts: which rooms, which signals, which PMS events, what happens on failure, who services it, and how the result will be judged. Everything else is a conversation.
Scope belongs in the contract in rooms and in functions: which room types, which circuits, which areas of the building, and what is explicitly excluded. The emptiness logic belongs there too, in writing: which signals are used, how long the delays are, and what the set-back values are in summer and in winter.
The clauses that decide the outcome
The PMS events the system reads, the direction of the link, the failure behavior, and the response time when the link breaks. The measurement method agreed before installation: which meters, which baseline period, which control rooms, and who signs off the result. Service terms: response time, spare parts, access to the controller, warranty length, and what the hotel keeps if it changes supplier.
ChecklistContract checklist
- Rooms and circuits in scope, and exclusions.
- Signals used and the delay and set-back values.
- PMS events read, direction of the link, failure behavior.
- Agreed measurement method, meters and baseline period.
- Service response time, spares and controller access.
- Warranty length and what the hotel keeps at the end.
- A staged rollout with a review point after the first floor.
Why one floor first
A staged start, one floor first, measured for a season, then the rest. It costs less to be wrong on one floor.
What to do next
Pick one floor or a sample of rooms, read the meters for four weeks before anyone signs, and put that baseline and the measurement method into the contract. The parts of this article fit together in that order: the emptiness signal decides whether the system can act, the PMS link decides whether guests notice, comfort and maintenance decide whether it lasts, and your own meters decide whether it was worth it.
Frequently asked questions
Does a key card energy saver really save money?
It saves only in the hours it actually switches something off, so the answer depends on guest behavior and on whether the holder can be defeated with a second card. A holder alone is the weakest signal; combined with a door contact and a PMS link it becomes useful. The only way to know the saving at your hotel is to read your own meters before and after.
Can room controls work without a PMS connection?
Yes. The system then reacts only to what happens inside the room, so a sold room stays at set-back until the guest opens the door. That is exactly the arrival complaint. A standalone system can still save energy; it just cannot prepare a room before arrival.
Do presence sensors work in hotel rooms?
Motion sensors miss a guest who is sleeping or sitting still, which is why they are often combined with a door contact and a card holder. Radar-based presence sensors pick up smaller movement and cost more. None of them should be the only signal, and all of them need a delay before switching anything off.
Should we retrofit or wait for the next renovation?
Retrofitting is possible, especially where the control unit talks to the thermostat and the lighting circuit without new cabling. Waiting for a renovation gives cleaner wiring and better placement of sensors. The deciding factor is usually disruption in occupied rooms and whether the ceiling and riser are accessible.
What about guests who leave a phone charging with the card out?
Decide the socket policy deliberately: which sockets stay live when the card leaves the slot, and which do not. Guests expect to charge overnight and often leave a device charging while they are out. Tell them at check-in, and keep the policy the same in every room.