Most independent hoteliers can tell you their monthly electricity bill to the nearest thousand rupees and have no idea what it's made of. It's treated as weather — something that happens to the business rather than something the business decides.
Quick answer (for the impatient)
Cooling and water heating dominate in most Indian hotels — usually the majority of consumption between them.
The biggest single waste is conditioning empty rooms, and it's largely free to fix.
Check your tariff structure before buying equipment. Demand charges and power factor penalties are frequently the cheapest wins available.
Where it actually goes
The rough shape at a typical Indian property, in descending order: air conditioning, then hot water, then kitchen and laundry, then lighting, then lifts and pumps. Lighting gets disproportionate attention because it's visible and easy to act on — but if cooling is the majority of your bill, a full LED retrofit is a rounding error next to fixing how your AC is operated.
Start by finding out your actual split rather than assuming. Even rough sub-metering of the main loads — cooling, water heating, kitchen — changes the conversation from opinion to fact.
The empty room problem
At 60% occupancy, four rooms in ten are empty on any given night, and in a lot of hotels a meaningful share of them are being cooled anyway. Housekeeping leaves the AC on after cleaning. A guest checks out and the room runs until someone notices. Nobody is being careless; there's simply no mechanism.
The interventions, in order of cost:
Make AC-off part of the housekeeping SOP's exit sequence, and inspect for it. Free.
Key-card or occupancy-linked power for rooms, which removes the human step entirely.
Set sensible default and limit temperatures. Each degree costs real money, and a room set to 18°C is not cooling faster — it's just running longer.
Service filters on schedule. A dirty filter raises consumption for the same cooling; this is where preventive maintenance pays back directly.
Read your tariff before you buy anything
Commercial tariffs in India are not a single per-unit rate. Depending on your state and connection, your bill may include demand charges based on peak load, power factor penalties or incentives, and time-of-day differentials. Each of these can be addressed without reducing consumption at all.
Sanctioned load — many hotels pay demand charges on a sanctioned load well above what they ever draw, having sized it years ago for equipment that no longer exists.
Power factor — poor power factor attracts penalties and is usually fixable with capacitor correction that pays back quickly.
Time-of-day rates — where they apply, shifting laundry and pumping out of peak windows costs nothing but scheduling.
Getting an energy audit of the bill itself, before any capital spend, is the highest-return hour most hoteliers can spend on this topic.
Hot water, quietly expensive
Electric geysers in every bathroom, running continuously, are a large and invisible load. Solar water heating has strong economics across most of India, particularly for properties with consistent occupancy, and heat pump systems are worth evaluating for larger operations. Both are capital decisions — but they're the capital decisions with the clearest payback in this list.
What to do first
Read twelve months of bills and identify every charge component.
Check sanctioned load against actual peak demand.
Fix power factor if it's being penalised.
Put AC-off into the housekeeping SOP and inspect for compliance.
Service AC units properly and on schedule.
Only then consider capital projects — solar water heating first for most properties.
Steps one to five cost almost nothing. Most hotels start at step six.
A realistic hotel example: what the team sees during a working shift
Picture Lakeview Residency, an independent property where the same manager may answer a booking query, approve a rate, settle a guest account and help a new employee before lunch. The question behind Electricity Is Your Second-Biggest Cost. Most Hotels Have Never Looked at It Properly. does not arrive as a neat software task. It arrives while somebody is waiting, another department needs an answer and the record must still make sense at the end of the day.
The first useful observation is this: Cooling and water heating dominate in most Indian hotels — usually the majority of consumption between them. The manager should translate that statement into a visible hand-off. Who starts the action? Which record do they open? What information must already be present? Who checks the result? If any answer depends on one experienced employee remembering an exception, the process is not yet reliable.
The second observation is equally practical: The biggest single waste is conditioning empty rooms , and it's largely free to fix. At Lakeview Residency, the team would test this with one ordinary case and one awkward case. The ordinary case confirms the expected path. The awkward case exposes missing permissions, incomplete data, unclear ownership or a decision that still happens in a private message. Both tests matter because hotel operations rarely fail on the clean example shown in a demonstration.
The third observation is about the downstream record: Check your tariff structure before buying equipment. Demand charges and power factor penalties are frequently the cheapest wins available. A completed action should leave enough context for the next person to understand what happened without reconstructing the story from calls and chat messages. That does not mean collecting every possible field. It means keeping the few facts that change the decision, the status, the responsible role and the next action together.
Rollout checklist: move from a good idea to a repeatable process
Use this checklist before the team treats the workflow as normal operating procedure. It deliberately separates product reachability from management discipline: software can make a record available, but the property still decides who owns it and how exceptions are handled.
Name the owner. Choose the role responsible for starting and completing the process. "The office" or "the front desk" is too vague when several people share a shift.
Confirm access. Test with the real role and tenant configuration, not an unrestricted demonstration account. Check enabled modules, feature permissions and the property or outlet context.
Define the minimum input. Agree which guest, room, date, amount, document or operational detail must be present before somebody can act.
Run the normal case. Complete one realistic example from beginning to end and ask the next team member to explain the result using only the saved record.
Run the exception. Try a correction, cancellation, missing value, late change or disputed instruction that genuinely occurs at the property. Record the fallback if the product path does not cover it.
Check the hand-off. Make sure the relevant people in front desk, reservations, housekeeping and accounts can see the status they need without receiving unnecessary access to unrelated records.
Write the fallback. If the system is unavailable or the case sits outside the verified path, state who records the temporary decision and who reconciles it later.
Review after live use. Ask staff where they paused, duplicated work or returned to a spreadsheet. Fix the process before adding more fields or automation.
Decision table: evidence to collect before you approve the workflow
A manager does not need a large transformation project to evaluate this topic. A short evidence review is enough to distinguish a reachable workflow from an attractive claim. Use the table during a property review and write the answer in plain language.
Review point What to verify Evidence to keep Decision if it fails
Reachability The responsible role can open and complete the path in the correct tenant and property context. A completed test record and the role used. Do not announce the workflow; check provisioning and permissions.
Data quality The minimum information needed for the decision is present, understandable and current. The input checklist and one reviewed example. Fix the collection step before adding automation.
Ownership One role owns the next action and another can review where separation is appropriate. The operating owner and escalation path. Assign responsibility before rollout.
Exception handling A correction, cancellation or disputed case has a documented path. The tested exception and fallback note. Keep the process in controlled trial use.
Downstream hand-off The next department sees the status it needs without manual re-entry or excessive access. A hand-off check by the receiving role. Use a documented interim hand-off and reconcile it.
The honest AXOIX limit and what to review after the first live cycle
The first review should focus on behaviour, not vanity metrics. Ask the people who performed the work where they hesitated, what they entered twice and which decision still escaped into a phone call or personal message. Compare the saved record with what actually happened. If they differ, find the earliest point where context was lost.
Then separate a training problem from a product boundary. A training problem means the verified path exists but the team did not understand the trigger, required input or next action. A configuration problem means the module, property context or permission is not available to that role. A product boundary means the audited path does not support the case. Those three diagnoses require different responses; calling all of them "user error" guarantees a repeat.
Keep the limitation visible while reviewing this article: Verify the workflow and its applicability before relying on it. That boundary is part of the buying and rollout decision, not a footnote to remove from the sales conversation. Where the workflow is usable, test it honestly. Where it is partial, keep the manual control explicit. Where applicability depends on law, policy or professional judgement, confirm it with the appropriate adviser.
FAQ
Is solar worth it for a small hotel?
Solar water heating usually has better economics than solar PV for hotels, because hot water demand is constant and large. Evaluate both, but don't assume PV is the obvious one.
Will key-card power annoy guests?
It's standard enough internationally that most guests don't notice. The complaint arises when it also kills the fridge — wire that separately.
How much can a property realistically save?
Enough that the audit pays for itself, but the honest answer depends on how badly the current setup is running. Measure first.
How should a hotel test this before rolling it out?
Use the real tenant, property context and staff role. Complete one ordinary case and one exception from start to finish, then ask the receiving role to verify the saved result without relying on a private message.
What should the team do if the verified product path does not cover its case?
Keep a documented manual control, name the person responsible for reconciliation and avoid describing the unsupported step as automated. Recheck module provisioning and permissions before concluding that a capability is absent.
The bottom line
Energy is the largest controllable cost most independent hotels have never actually examined. The first wins aren't equipment — they're a tariff nobody read and rooms being cooled for nobody.
See how maintenance protects efficiency, how housekeeping SOPs make it habitual, or pricing.
Control the costs you can. Start free →
Comments