Friday, 11:47 PM. A pipe bursts in room 812 and water is coming through the ceiling of 712. In 615 the lock has died, and a guest is stuck in the corridor with their luggage. In the conference room the lights just went out, fifteen minutes before a VIP's morning run-through. Three problems, one shift, one technician.
That's hotel corrective maintenance: the unglamorous work of handling whatever breaks, whenever it breaks. The difference between a strong engineering team and a struggling one isn't how much breaks. It's whether the response is a system or just endless firefighting.
In a well-run hotel, about 70% of maintenance work is planned, and only 30% is corrective. That ratio isn't arbitrary. It reflects decades of industry practice, and it's a fair signal of how mature a hotel's engineering department really is.
How to interpret the balance:
| PM/CM Ratio | What It Says | What to Do |
|---|---|---|
| 80/20 | Excellent proactive service | Maintain the level, analyze for potential complacency |
| 70/30 | Healthy balance | Target state for most hotels |
| 60/40 | Room for improvement | Strengthen PM, analyze recurring failures |
| 50/50 | Firefighting mode | Urgent PM program revision needed |
| 40/60 | Crisis | Immediate management intervention required |
One important nuance: that 30% shouldn't be read as "failure." Some share of breakdowns is statistically inevitable. Equipment ages, guests use things in ways nobody predicted, and outside factors intervene. The goal isn't zero corrective work — it's the right balance.
There's a common misconception that hotel corrective maintenance is unpredictable, so there's no point preparing for it. In reality, most emergency work is predictable. It just hasn't been analyzed yet.
If you systematically collect information about breakdowns, patterns emerge:
Once you know the patterns, you can get ahead of them: add a technician on Monday mornings, inspect the AC units in May, swap aging mini-bars before the summer failure wave hits. That's the shift from reacting to chaos to managing it.
Not all breakdowns are equal. The priority cascade decides what gets fixed first when the queue is longer than the team can handle.
| Priority | Criteria | Response Time | Resolution Time | Examples |
|---|---|---|---|---|
| P1 — Critical | Safety threat or total loss of functionality | Immediate | <1 hour | Fire system failure, flooding, elevator stuck with people |
| P2 — High | Significant guest impact in occupied room | <15 min | <4 hours | No AC in 90°F heat, lock won't open, no hot water |
| P3 — Medium | Inconvenience or problem in vacant room | <1 hour | <24 hours | TV doesn't work, slow drain, squeaky door |
| P4 — Low | Cosmetic issues, back-of-house areas | <4 hours | <72 hours | Scuff on wall, worn carpet, staff area repairs |
Priority can be raised based on context:
But watch the balance: if everything is P1, nothing is. The chief engineer has to watch for priority inflation and tighten the criteria when it starts creeping.
An incomplete work order is how mistakes happen. Every corrective request should carry seven things:
| # | Element | Why It's Important | Example |
|---|---|---|---|
| 1 | Location | Where to go | Room 412, bathroom |
| 2 | Problem | What to fix | Faucet drips continuously |
| 3 | Source | Who discovered | Guest complaint at 14:23 |
| 4 | Priority | Urgency | P2 — occupied room |
| 5 | Assignee | Who's responsible | Mike, plumber |
| 6 | ETA | When to expect resolution | Today by 16:00 |
| 7 | Status | Current state | In progress / Waiting for parts |
Once the job's done, three more get added: actual time spent, parts used, and root cause. That data is what later powers your corrective-maintenance analysis and feeds straight back into preventive maintenance.
Corrective maintenance carries hidden costs that rarely make it onto a spreadsheet:
The math for deciding is simple. If prevention costs X and the corrective version costs 3-5X plus the reputational hit, the early investment wins every time.
Without data, there's nothing to optimize. Every work order needs time stamps, a root cause, and how it was resolved. CELLYPSO CMMS handles that collection automatically: technicians update status from their phones, the system logs the time, and everything lives in one place.
Monthly review of CM data to find:
Analysis reveals what breaks most often. Stock those parts:
Optimal inventory: 2-week supply of high-turnover items. More = tied-up capital. Less = emergency orders.
The best way to optimize hotel corrective maintenance is to need less of it. For anything that keeps failing, ask one question: could a scheduled inspection have caught this? The answer is usually yes. When it is, add that inspection to the maintenance checklist.