How a hotel tracks maintenance issues, from staff report to fixed room

A hotel runs the same loop a residential building does. Someone finds a problem, someone fixes it, someone signs off that it is actually fixed. The difference is the clock. A resident might live with a flickering hallway light for a week. A guest in room 214 calls the front desk about the AC within ten minutes, then again in twenty.

Kvaro was built to run that loop for building managers, and the issue-tracking flow moves onto a hotel with almost nothing lost. The building becomes the hotel. The apartment becomes the room. The residents become your staff. Managers, fixers, and owners keep the roles they already have.

Here is that flow for a hotel: who reports, who fixes, who confirms, and what the software does in between.

Who does what

Four roles, the same four the building version uses.

• Staff report issues and confirm the fix. Housekeeping finds a cracked shower door, the front desk hears the elevator is slow, a porter spots a dead bulb in the corridor. Whoever notices it files it.
• The manager owns the queue. Every new issue lands with the duty manager, who either handles it or sends it to the right person.
• Fixers resolve issues. Your in-house engineer, the on-call electrician, the AC contractor. Each one sees only what is assigned to them.
• The owner watches the whole operation across every property without touching a single ticket.

Every room has a number, so every issue is anchored to a place the moment it is filed: “AC not cooling, room 214” leaves nothing to guess. Common areas work the same way. The lobby, the pool, the kitchen line get tagged to the area instead of a room.

The flow

Staff files the issue, it gets routed, a fixer marks it ready, staff confirms. In status terms it is a short state machine:

1. A staff member files it in seconds. Title, a line of description, the room or area, an optional photo. The photo earns its place in a hotel more than almost anywhere: “the faucet in 214 is loose” and a picture of the faucet hanging off the wall are two different work orders.
2. The issue routes to a handler. Three ways to run this, covered below.
3. The fixer works it and marks it Awaiting Confirmation rather than Closed. The fixer cannot close it: the person who reported it confirms the fix (a manager can resolve it directly if needed), so a half-done job cannot quietly disappear off the board.
4. Staff confirms the room is guest-ready, or reopens with a reason. A confirmed issue closes and leaves the queue. A reopened one goes back to New with the reason attached, so the fixer sees it again with full context.

Routing: three ways to run it

The routing step is where a hotel decides how much the manager stays in the loop. Kvaro supports all three, and most properties end up mixing them.

• Auto-route by category. Set a rule once (“AC to the HVAC contractor”, “plumbing to the on-site engineer”) and every matching issue skips the manager’s inbox and lands straight with the fixer.
• The manager handles it. Small property, one handyman, no need for fixers at all. The manager works the list directly. The fixer role is optional.
• The manager assigns each one by hand. The manager reads every issue and picks who takes it. Useful when the same problem could go to two people depending on the shift or who is on site.

A typical hotel auto-routes the predictable categories and hand-assigns the odd ones, so the front desk never becomes the bottleneck between a broken thing and the person who fixes it.

What this replaces

Hotels already track maintenance. The tracking lives in places that lose things:

• The maintenance logbook at the desk that only the desk can read.
• The radio call that gets the AC fixed but leaves no record it was ever broken.
• The staff WhatsApp group where the message scrolls past the night engineer before the shift even starts.

None of these can answer the one question that runs a hotel’s maintenance: what is open right now, and who is on it. A ticket queue answers it on one screen. The reasoning behind that, and why a structured record beats a chat message, is the same argument we made for buildings in what a structured ticket system looks like.

A shift, start to finish

At 9:14 a.m. a housekeeper files “AC not cooling, room 214” with a photo of the thermostat reading 81°F. The rule sends it to the HVAC contractor automatically. The contractor sees it on their phone, marks it In Progress, arrives at 11:00 a.m., recharges the unit, and marks it Awaiting Confirmation with a photo of the thermostat back at 70°F. Housekeeping checks the room before the 3 p.m. check-in and confirms. The ticket closes.

The guest walks into a cold room and never knows anything was wrong. The manager never touched it. And at year end the owner can see that room 214’s AC has now been recharged three times, which is the moment “replace the unit” stops being a hunch and becomes a decision backed by a record. That accumulating history is the same lifecycle we break down step by step in the tenant complaint workflow, applied to a guest room instead of an apartment.

Getting started

The flow is the same whether you run one boutique hotel or a group of them. Staff report, the queue routes, fixers resolve, staff confirm. Set up your hotel, add your rooms, invite your staff and your fixers, and the loop starts the first time someone files an issue instead of walking it down to the desk.