In most hotels, faults are reported by radio, by a note on the maintenance office door or by a word in the corridor. Some get fixed the same hour; others are forgotten until a guest complains. This article explains how to set up a maintenance process where every fault is recorded, assigned and tracked, and how planned checks fit alongside reactive jobs.
Why informal reporting fails
Radio calls and sticky notes feel fast, and for urgent problems they are. The trouble starts with everything that is not urgent:
- Nothing is written down. A dripping tap reported on Monday is easy to forget by Wednesday.
- Nobody knows the status. Reception cannot tell a guest whether the air conditioning in their room will be fixed today.
- The same fault is reported three times by three people, or not at all because everyone assumes someone else has.
- Repeat problems stay hidden. If the same room has a heating fault every month, nobody can see the pattern.
- Priorities are set by whoever shouts loudest, not by the impact on guests and safety.
A small maintenance team in a busy hotel cannot hold all of this in their heads. The fix is not more meetings; it is a single place where every job lives.

Step 1: make reporting easy from any phone
If reporting a fault takes longer than walking to the maintenance office, people will keep walking. The report form should open on any phone and ask only for what the engineer needs:
- Where: room number or area, such as "Terrace bar" or "Kitchen walk-in".
- What: a short title and, if needed, a description.
- How urgent: low, normal, high or urgent.
- A photo: often clearer than any description, especially for damage and leaks.
Housekeeping, front of house, kitchen and the duty manager should all be able to report. Guests can report too, if the hotel offers a simple way to do it from the room, which avoids a call to reception for a problem that only maintenance can fix.
Step 2: assign every job to one person
A job that belongs to "maintenance" belongs to nobody. Each job should have a named owner, even in a team of two. The head of maintenance or the duty manager assigns new jobs at the start of each shift and whenever an urgent one comes in. The owner can then update the status, add notes and photos, and close the job when it is done.
Agree a short list of statuses that everyone understands, for example:
| Status | Meaning |
|---|---|
| New | Reported, not yet looked at |
| In progress | Someone is working on it |
| Waiting for parts | Diagnosed, but parts or a contractor are needed |
| Done | Fixed and ready for the person who reported it to check |
| Closed | Confirmed and finished |
"Waiting for parts" is worth having on its own. It separates jobs that are stuck for a known reason from jobs that are being ignored.
Step 3: set target times and track overdue jobs
Not every job needs to be done today, but every job needs a target. A simple rule set is usually enough: urgent jobs within a few hours, high priority the same day, normal within a few days. What matters is that the target is written down and that overdue jobs are visible to the person who can act on them.
A board view helps here. When jobs are shown as cards in columns by status, a column full of old cards is hard to miss. Review overdue jobs at the daily operations meeting, and ask one question for each: what is needed to close it?
Step 4: keep the history
Every comment, status change and photo should stay with the job. This history is useful in three ways:
- It shows guests and managers what was done and when.
- It helps spot rooms or pieces of equipment that fail again and again, which supports a case for replacement.
- It gives evidence when a contractor's work or a warranty claim is in question.
Step 5: separate planned checks from reactive jobs
Reactive jobs are faults that someone reports. Planned checks are routines that happen whether or not anything is wrong: weekly fire alarm tests, monthly emergency lighting tests, flushing little-used water outlets, checking pool and spa readings. They need a different tool. A planned check has a schedule, a set of questions or readings, and a record that it was done on time.
The link between the two is important. When a planned check fails, for example a hot-water outlet below its target temperature, it should create a maintenance job with the reading attached, so the fault is fixed and not only recorded.
Reactive jobs answer "what is broken?". Planned checks answer "how do we know it is working?". A hotel needs both, and a failed check should become a job.
Summary checklist
- One place for every fault, reachable from any phone.
- Location, priority and a photo on every report.
- One named owner per job.
- A short, shared list of statuses, including "waiting for parts".
- Target times per priority or status, with overdue jobs clearly marked.
- Full history of comments, changes and photos on each job.
- Planned checks on a schedule, with failures turned into jobs.
How Staybase handles this
The Staybase Maintenance module replaces radio calls and notes with tickets. Staff create a ticket on a computer or in the Staybase app on their phone, with a title, location, priority from low to urgent, a description and attachments, and can add photos straight from the phone camera in comments. Where a hotel uses in-room tablets, guests can report a problem from a "Report an issue" tile, and a ticket is created for that room.
Each ticket is assigned to one person. Teams switch between a table view and a Kanban board, and managers can drag cards between columns with an optional comment. Each hotel defines its own statuses with colours and a target time in hours, and tickets that pass it are marked as overdue. Every comment and status change appears in the ticket timeline. Notifications go by email, to Microsoft Teams and as push notifications to managers' phones. Managers with several hotels can view one hotel or all of them, and tickets export to PDF and CSV.
Planned checks run in the Staybase Compliance module on daily, weekly or monthly schedules. If the same piece of equipment fails its check several times in a row, Staybase opens a high-priority maintenance ticket with the recent readings. To see it with your own team's jobs, book a demo at staybase.co.uk.