Hotel maintenance log: template and how to run it

What a maintenance log is for

A hotel maintenance log is the single record of every fault and maintenance job in the property: what broke, where, who fixed it, how long it took and what was done. It is not paperwork for its own sake. It is how a chief engineer knows what is open right now, how a front-office manager knows whether a blocked room is coming back tonight, and how an owner knows whether to replace the chiller or keep repairing it.

Most hotels have some kind of log. The common problems are that it lives in three places (a notebook in the engineering office, a chat group and a spreadsheet), that entries are written at the end of the shift from memory, and that nobody reads it until something goes wrong. The template below fixes the first two. The routine further down fixes the third.

The template, field by field

Every entry should carry the same fields. If you use paper, print these as columns. If you use a spreadsheet, make them headers and lock the drop-down values. If you use software, check it captures each one.

That is nineteen fields, which sounds like a lot. In practice the reporter fills four (time, reporter, location, description), the supervisor fills three (category, priority, assignee), and the engineer fills the rest on the phone or the sheet in under a minute. The rules for what goes where matter more than the number of columns.

Rules that keep the data usable

• Location exactly as the PMS writes it. If the PMS says 412, the log says 412, not “4th floor corner room”.
• Assign to a person. A job assigned to “maintenance” is a job nobody owns.
• Fixed lists for category, priority and room impact. Free text in these fields makes reporting impossible.
• Times recorded when they happen. A completion time written at 15:00 for every job of the shift is worthless.
• Never delete entries. Cancel them with a reason. Deleted entries are where disputes start.

Priority and room impact

Priority and room impact are different fields on purpose. A broken lobby light is low impact on inventory but may be high priority before an evening event. A dripping tap in an occupied room is not urgent technically but disturbs a guest. Keep a short written guide so supervisors pick consistently.

• Urgent: safety risk, water leak, no power, guest locked out, lift fault. Drop everything.
• High: affects an occupied room or an arriving guest: no hot water, AC not cooling, TV dead.
• Normal: affects a vacant room or a public area without guest impact today.
• Low: cosmetic, can wait for a planned visit.

Set target response and resolution times for each level. If you have not done that yet, the SLA and escalation guide includes an example matrix to adapt.

The daily routine

A log only works if people read it. This routine takes around fifteen minutes a day across roles.

• Start of each shift: duty engineer reads every open entry and confirms the assignee is on shift. Reassign anything owned by someone who has gone home.
• Mid-morning: front-office supervisor compares out-of-order rooms in the PMS against open entries with room impact “out of order”. Any mismatch gets resolved on the spot.
• Before afternoon arrivals: chief engineer reviews all high and urgent entries still open, and tells the front office which rooms will not be ready.
• End of each shift: handover lists open entries by ID, not by memory. “MNT-0412 waiting for part” beats “the AC thing”.
• Weekly: pull repeat locations and repeat assets. Three entries on the same fan coil in a month is a replacement conversation, not three repairs.
• Monthly: look at average time from report to completion by category, and the share of reactive versus planned work.

What the log tells you after a month

Once the log has a few weeks of honest data, it starts answering questions that used to be opinions.

• Repeat faults. Sort by asset or location. The same shower mixer failing every few weeks points to a bad batch, a water pressure issue or a poor previous repair.
• Waiting versus working time. The gap between reported and started is a dispatch problem. The gap between started and completed is a skills, parts or access problem. They need different fixes.
• Rooms blocked too long. Entries with room impact “out of order” and a long completion time are lost revenue. Often the repair was quick and the delay was the handoff back to the front office.
• Trade load. If most entries are plumbing, your rota and your spare parts should reflect it.
• Where reports come from. If most faults are reported by guests rather than housekeeping, room checks are missing things guests then find.

Common mistakes

• Logging only what guests complain about. Housekeeping and engineers spot far more than guests do. Make it easy for them to log in seconds.
• Closing without verifying. A technician marking a job done is not the same as the room being right. Verify anything that affected a guest room.
• Letting the log split across channels. If a job is reported in a chat group, it still has to land in the log. Better still, stop taking reports in chat groups at all; see why WhatsApp groups fail as a work tool.
• Keeping planned work somewhere else. You will never see the real workload if preventive jobs live in a separate binder.

Where TaskLoop fits

If you would rather not maintain a spreadsheet, TaskLoop covers both sides of this template as tasks: reactive repairs, and planned jobs that preventive-maintenance schedules generate automatically. Requests come in from guests via room QR codes or are registered at the reception dashboard, supervisors assign them with priority, deadline and instructions, engineers accept and complete them on the staff mobile app with optional photo proof and completion timestamps, and overdue tasks escalate to supervisors. Reports show response and completion times by department and by person. See work orders for details.