Hotel maintenance software: setting up the asset list, work orders and schedules

Hotel maintenance software, or a CMMS (computerized maintenance management system), holds three things: the assets a building owns, the work orders raised against them, and the calendar of jobs that repeat. Set up the asset list first, give every item a code staff can read, then open every fault through one route.

The chiller stops at two in the morning. The night manager calls a technician, the technician fixes it, and by breakfast nobody can say which part failed, when the unit was last serviced, or whether the same thing happened in March. That is not yet a software problem. It is a record problem. After reading this guide you will be able to build the asset list, code and label equipment so staff can find it, route every fault through one door, put recurring inspections on a calendar, and read the three reports that tell you whether any of it is working.

What is a maintenance management system for a hotel?#

It is the record of three things: what the building owns, what has been done to it, and what is due next. Maintenance software, usually called a CMMS, keeps those three in one place so they survive staff changes.

The asset is a physical thing with a location, a make and a history: a boiler, an air-handling unit, a room's door lock. The work order is one job with one owner and one close: who reported it, what was found, what was done, which part was used. The schedule is a job that repeats without anyone having to remember it: a monthly plant-room round, a quarterly service, an annual inspection.

It is not a chat group or a photo album of broken things. Those record that something happened; they do not record what was done or what is due. Paper can run the process but not the memory. A paper job card closes one repair; the value appears when the third failure of the same asset is visible on one page.

The minimum setup is small: an asset list with location codes, a single intake route, a close-out note and a calendar. Software adds search, history and alerts on top of that. Four people read it for four reasons: the technician needs what and where, the chief engineer needs repeat faults and backlog, the general manager needs rooms out of sale and spend, and the owner needs the capital replacement case.

Should hotel maintenance live in the PMS or in separate software?#

Choose by the links, not by the feature list. If a repair can take a room out of sale or put a cost on a guest's bill, the maintenance record must be able to reach the front desk and the billing system.

Two links decide the question. Room status, because a repair can block a room. Money, because labor, spare parts or a charge can land on a department or a guest. Everything else is preference.

Separate maintenance software is usually deeper on asset hierarchies, spare-parts stock, meter readings, warranty and service contracts. A module inside a hotel operating system is usually shallower but already knows the room and the bill. The cost hides in the join: a nightly export that nobody reads is not an integration. Ask what happens in the minute after a technician marks a room out of order.

A workable middle is one system of record for assets and jobs, a written rule for which system owns room status, and a daily reconciliation of rooms blocked in one and not the other. Watch the second and third asset list too: the finance fixed-asset register, the maintenance list and the insurance schedule drift apart within a year, so reconcile them once a year against one list. Switching later is expensive mainly because of history, so insist on a full export of assets and job history in a readable format before you sign anything.

For the department-by-department map of what hotel software covers, see the linked guide.

Which assets belong on the list, and how deep should you go?#

List an asset when you would repair or replace it as a whole and want its history. Go deep enough to separate items with their own warranty, service contract or failure pattern, and no deeper.

In rooms, treat the room as a location, and list inside it the items with their own service life: the air-conditioning unit, minibar, television, door lock, safe and bathroom fittings. The towel rail does not need a record. In plant, list the boiler and burner, chiller, cooling tower, air-handling units, circulation pumps, generator, transformer and switchgear, water treatment, fire pump, lift as a contracted asset, and pool plant. In kitchen and laundry: walk-in cold rooms, extraction hood, dishwashers, laundry machines and the grease trap. Outside the building shell: pool dosing and filtration, irrigation, shuttle vehicles, network cabinets, CCTV and access control.

The depth rule: two identical units that fail independently and are serviced separately are two assets. Units that always fail and are serviced together can be one asset with a note. Fields per asset: a readable code, location, make and model, serial number, install date, warranty end, service provider and contract, criticality, and the spare parts you hold. Criticality is the field most often skipped and the one that sets priority: what happens to guests and to revenue if this stops tonight.

A coding rule staff can read#

Use one short code a person can read out loud on the phone, built from location first and equipment type second. Keep the length and the positions fixed so codes sort and search cleanly, and avoid meanings that will change, such as a manager's initials or a supplier's name.

One code per physical thing. When a unit is replaced, either retire the code and issue a new one, or keep the code and log the swap as a history entry. Pick one rule and write it into the procedure.

Labels that survive a plant room#

Label in three places: on the equipment, on the panel or schematic, and on the floor plan. A label on a machine nobody can find in a drawing is half a label. Materials matter: plant rooms are hot and damp and kitchens are greasy, so use printed labels that survive cleaning rather than tape and marker pen. Barcodes and QR codes speed up scanning, but the plain code comes first, because a technician with gloves on must be able to type it. Keep codes out of guest sight: a label on a corridor ceiling hatch is fine; a label on the minibar door is not.

How does a fault become a work order?#

Through one door. Anyone may report a fault, but every report must land in the same queue with a location code, a symptom and a name attached, or it becomes a phone call that nobody owns.

The ways in are many: reception, housekeeping on the floor, the night shift, a guest message, the planned calendar, an alarm or meter reading, and the manager's morning walk. Whatever the route, the report must carry who reported it and when, the asset or location code, what the guest or staff member actually sees or hears, a photo where useful, and whether the room is occupied.

Triage once, at intake: safety first, then guest-visible faults in an occupied room, then revenue-affecting faults such as a closed outlet or a dead point-of-sale terminal, then everything else. Priority is set by the person on duty, not renegotiated by whoever is loudest. One owner per job: a job with two owners has none.

Close-out must distinguish states: fixed, made safe until the part arrives, and deferred with a date. Recording all three as closed erases the difference that matters at the next failure. The failure mode to watch is the job closed by the person who reported it, with no note. That removes exactly the history the system exists to keep.

When the fault takes a room out of sale#

The work order must be able to change room status, the desk must see the block before it sells the room, and the room must pass a check before it returns to sale. For the full life of a work order, from guest complaint to closed job, see the linked guide, and for out-of-order rooms and when to repair, wait or close, the decision guide.

How do periodic inspections become recurring jobs?#

They become jobs the calendar creates, not jobs someone remembers. Each one carries a period, an owner, a written scope and a record of what was actually found.

Keep three kinds of recurring job apart: the manufacturer's or contractor's service interval, the legally required periodic check, and your own rounds such as the weekly plant-room walk. Every recurring job needs a scope: what is checked, what counts as a pass, and what to do when it fails. A line reading "boiler check" is not a scope.

The record is the product: who did it, when, what was measured, what was found and what was done. A tick with no reading tells the next inspector nothing. Missed jobs need an escalation rule: a job past its due date should appear on someone's list the next morning, not at the annual audit. Legal periodic checks belong on one compliance calendar with its own evidence file, kept apart from routine rounds so neither hides the other.

For the practical layout of boilers, lifts, electrics and fire systems on one inspection calendar, see the linked guide.

The first month: which three reports should you read?#

Read three: open jobs by age, jobs by asset and location, and planned versus reactive work. They tell you whether the system is being used, where the building is failing, and whether you are still firefighting.

Open jobs by age is a decision list, not a scoreboard. Anything older than a week needs a decision: fix it, defer it with a date, or close it as will not fix. Jobs by asset and location separates two cases: the same asset three times is a replacement case, not a repair case; the same room three times is a room to inspect properly rather than patch again. Planned versus reactive work shows whether the calendar is real, because a calendar full of jobs that are always closed late is decoration.

Glance at two smaller lists: jobs with no close-out note, and jobs reopened within days of closing. Both point at the intake and close rules, not at the technicians. Read the three reports in the same meeting as the rooms-out-of-sale list, so maintenance and the front desk see the same picture of the building. And publish them where the team can see them: a report that only the chief engineer opens changes nothing.

What to do next#

The next step is not a purchase. Walk one guest floor and the plant room this week with a clipboard, write down every item you would repair or replace as a whole, give each one a location code, and only then decide whether maintenance lives in your hotel operating system or in separate software. The order matters: assets, then codes, then one intake route, then the calendar, then the link to room status, and finally the three reports that show whether any of it is being used.