On Tuesday morning, housekeeping notices water dripping from the AC unit in Room 214. She mentions it to the floor supervisor. The supervisor tells front desk. Front desk writes it on a sticky note. By Thursday, the note is gone, engineering never received a formal request, and a family checks in for a two-night stay.
By Friday evening, there is a damp patch on the carpet, a one-star review mentioning "poor maintenance," and a comp night the GM approves to settle the guest down. The repair itself would have taken an hour. The complaint cost far more — in revenue, reputation, and staff time.
This is not a staffing problem. It is a workflow problem. The issue was seen early. It was reported informally. It was never tracked, assigned, or closed with proof. That gap is where guest complaints are born.
The Complaint That Should Never Have Happened
Most maintenance-related guest complaints follow the same pattern: someone on staff already knew about the fault days before the guest arrived. The failure is not detection — it is the handoff between detection and repair.
Resorts and hotels that run on verbal reports, WhatsApp groups, and handwritten notes depend on memory and goodwill. On a busy weekend, with full occupancy and short-staffed engineering, those informal channels break down. Issues sit in limbo. Rooms get released before they are genuinely ready. Small faults become review-worthy problems.
The fix is not more meetings or a bigger maintenance team. It is a simple rule: every issue becomes a work order — numbered, assigned, time-bound, and traceable from report to verified closure.
Why Informal Reporting Fails at Resorts and Hotels
Hospitality operations move fast. That speed is exactly why informal reporting fails.
Messages get lost, not maliciously — just inevitably
- WhatsApp and verbal handoffs have no owner. A message in a group chat is not a task. Nobody is accountable until someone else complains.
- No due date means everything is "when you get a chance." Urgent and low-priority items look the same in a notebook.
- Room-ready pressure pushes supervisors to release rooms before faults are confirmed fixed — especially when the front desk is waiting.
- Repeat failures go unnoticed without a history. The same shower mixer fails three times in six months, but each fix is treated as a one-off because there is no linked record.
Engineering hears about issues only after guests complain. Staff say "I thought someone had already fixed it." The same room generates maintenance callbacks within weeks. Overdue work orders exist only in someone's head. Supervisors cannot answer "who reported this and when?" without making phone calls.
What a Proper Issue-Handling Workflow Looks Like
A disciplined maintenance workflow treats every fault the same way, whether it is a leaking tap in a villa, a broken sun lounger by the pool, or a flickering light in the lobby.
Staff report the issue in under a minute. The system creates a work order with a unique number (for example, WO-2026-00147), records who reported it, routes it to the right technician or maintenance manager, sets response and resolution deadlines, and logs every status change on a timeline. When the fix is done, a supervisor verifies and closes the order — for room issues and critical assets, this step is mandatory.
The result is not a conversation. It is a record. And that record is what keeps properties maintained to the standard guests expect.
Three Ways Staff Report an Issue
Good systems meet staff where they already work — during room cleaning, at an asset location, or during a scheduled audit. There are three entry points in a structured PMS workflow.
Any authorised staff member opens Report Issue, selects the Area (Lobby, Pool, Garden, or a custom location), enters the Room number, chooses Priority (Low, Normal, or Urgent), picks a Category (Electrical, Plumbing, HVAC, Carpentry, Civil, IT, Housekeeping-Repair, or Other), and types a Problem statement. On submit, the work order number appears immediately along with the assignee — or "Pending assignment" if routing is still in progress.
When housekeeping or engineering scans a QR tag on a TV, minibar, or piece of furniture, the asset record opens with its tag, name, and current location pre-filled. Report Issue links the work order to that asset, so the fix appears in Service History — useful when the same item fails repeatedly or when auditors need a maintenance trail.
During a location audit, staff verify assets and grade condition as Good, Fair, Poor, or Damaged. For Poor or Damaged items, they can raise a work order directly from the audit report. Damaged assets get Urgent priority; Poor items get Normal. This catches deterioration before a guest encounters it.
Housekeeping is servicing Room 312 and finds the shower mixer leaking. She opens Report Issue on her phone, selects Plumbing, sets priority to Normal, and types "Shower mixer dripping — steady leak when turned off." The system creates WO-2026-00147, assigns it to the plumbing maintenance manager, and starts the SLA clock. She returns to cleaning. No call to engineering. No note at the front desk. The issue is in the queue before she leaves the room.
| Entry Point | Who Uses It | What Gets Created |
|---|---|---|
| Work Orders → Report Issue | Housekeeping, front office, F&B, pool staff, any authorised user | Work order with area, room, category, priority, and problem statement |
| Asset detail / QR scan | Housekeeping, engineering during walkthroughs | Work order linked to asset tag and service history |
| Quick Audit → Raise Work Order | Audit team, department heads | Work order from Poor or Damaged condition finding |
From Open to Closed: The Work Order Lifecycle
Once created, every work order moves through a defined lifecycle. Each transition is logged on an activity timeline — who did what, and when.
| Status | What It Means |
|---|---|
| Open | Issue logged. Awaiting assignment or already assigned to a technician. |
| In Progress | Technician has started work. The response SLA is met once this status is set. |
| On Hold | Work paused — waiting for parts, access, or a vendor. A reason is required. The item stays visible in the maintenance queue; it does not disappear. |
| Done | Technician has completed the fix. Resolution notes can document what was done. If verification is required, the order waits for supervisor sign-off. |
| Closed | Supervisor has verified the fix and closed the order. Asset service history is updated. |
Why Verify & Close matters
For room-linked issues, staff-reported issues, and critical assets, a technician cannot silently close their own work. A supervisor with verify permission must confirm the fix before the order is closed.
This is the accountability layer that protects property standards. Without it, "done" often means "I tried" — and the room goes back into inventory before the guest would agree the problem is fixed. Verify & Close is what separates a maintenance log from a trustworthy maintenance process.
"A work order that anyone can mark complete without inspection is just a to-do list with extra steps. Verification is what makes it a quality system."
SLA Targets That Keep Small Problems From Becoming Big Ones
Without deadlines, maintenance queues grow until something urgent forces attention — usually a guest complaint. Service Level Agreements (SLAs) give every work order two clocks:
- Response SLA: How quickly someone must start work (move the order to In Progress)
- Resolution SLA: How quickly the fix must be marked Done
Typical default targets by priority:
| Priority | Response Target | Resolution Target |
|---|---|---|
| Urgent | 2 hours | 8 hours |
| Normal | 8 hours | 24 hours |
| Low | 24 hours | 72 hours |
Properties can adjust these in settings to match their staffing and seasonality. The point is not the exact hours — it is that overdue items are visible. The work order list highlights past-due dates. The WO SLA Report gives managers a dashboard: pending issues, overdue counts, response and resolution breach rates, assignee workload charts, and CSV export for weekly ops meetings.
When a pool pump noise complaint is still open after 48 hours, the GM should not need to walk the property to find out. The report should already show it.
How This Reduces Guest Complaints
This workflow does not replace guest feedback channels. It reduces the need for them — by fixing faults before the next guest walks in.
- Issues caught during cleaning, not at check-in. Housekeeping is in every room, every day. Report Issue turns that visibility into action without breaking their rhythm.
- Room issues cannot close without verification. A room with an open or unverified plumbing work order should not be sold as ready. The system enforces the standard the brand promises.
- Overdue work is visible, not buried. Dashboards and SLA reports surface what is slipping — while there is still time to fix it before arrival.
- Resolution notes build institutional memory. "Replaced washer on mixer valve" on the third callback tells engineering it is time for a full replacement, not another patch.
- Audit-driven work orders catch decline early. A chair graded Poor during a quarterly audit becomes a work order before a guest sits on a wobbly leg.
For more on the inspection side, see our guide to hotel housekeeping management — particularly quality control and room inspection practices that feed directly into this workflow.
Roles and Accountability
A work order is only as good as the clarity around who owns each step.
Reported by
Every work order records who logged the issue. This is not about blame — it is about traceability. When a manager asks "who knew about the AC in 214 on Tuesday?", the answer is in the system, not in someone's memory.
Maintenance Manager per department
Properties configure a maintenance manager for each trade — electrical, plumbing, HVAC, and so on. New complaint and audit work orders auto-route to the right manager based on category. No one has to decide who gets the ticket.
Technician (assignee)
The person doing the work sees their tasks under My Tasks, Today, and Overdue tabs. They start, pause with a reason, resume, and mark done — each action timestamped on the timeline.
Supervisor (verify)
Users with verify permission perform Verify & Close after Done. They can also reopen an order if the fix was inadequate — sending it back to Open with a full audit trail.
Permissions that match real operations
- Technicians see and execute their own assigned work
- Supervisors and managers see all open orders, assign technicians, and verify closures
- Cancel requires a reason — nothing vanishes without a record
Keeping the Property Up to Standard
A five-star promise is not one grand gesture. It is hundreds of small things working correctly — the shower pressure, the TV remote, the pool deck chair, the lobby light. Guests notice when those details slip, even if they cannot name what is wrong.
Property standards are maintained when:
- Faults are reported at the point of discovery, not after escalation
- Every fix has an owner and a deadline
- Closures are verified, not assumed
- Asset service history shows what was done, when, and by whom
- Audits convert Poor and Damaged findings into tracked work — not verbal reminders
This is the operational backbone behind the guest experience. Revenue managers optimise rates; housekeeping delivers cleanliness; maintenance workflow ensures the physical product matches what you are selling. For the broader asset register, tagging, and audit framework, see our hotel asset management guide.
How Resortree Handles Issue Reporting and Work Orders
Resortree builds issue reporting and work order management into the same PMS your team already uses for reservations, housekeeping, and billing — so maintenance is not a separate system that falls out of sync.
Staff log faults from the Work Orders page, an asset detail screen, or a QR scan — area, room, category, priority, and problem statement. The work order number and assignee appear on submit.
Work orders route to the right department head based on category — electrical to electrical, plumbing to plumbing. No manual triage on busy shifts.
The WO SLA Report shows pending issues, breach rates, and assignee workload. Overdue items stand out in the queue. Export to CSV for weekly ops reviews.
Room-linked and critical-asset work orders require supervisor sign-off before closure. Resolution notes feed service history for future audits and repeat-failure analysis.
Issue reporting and work orders are part of the Resortree PMS — integrated with assets, housekeeping, and property operations. Talk to the team to see how it works for your property.
Frequently Asked Questions
What is the difference between Report Issue and a guest complaint?
Report Issue is a staff action inside the PMS that creates a maintenance work order — typically when housekeeping, front office, or engineering spots a fault during their shift. A guest complaint is feedback from a paying guest, usually after the problem has already affected their stay. A solid reporting workflow catches faults at the staff level before they become guest complaints.
Who should report maintenance issues at a hotel?
Anyone who finds a fault during normal work: housekeeping during room cleaning, front desk when a guest mentions something at check-in, F&B in restaurant areas, pool attendants, engineering on walkthroughs. Reporting should take under a minute and not require calling engineering directly.
What happens if a work order misses its SLA?
Overdue work orders are highlighted in the maintenance queue and on the WO SLA Report. Managers see which items breached response or resolution targets, who they are assigned to, and how workload is distributed. That visibility turns a missed deadline into a management action instead of a hidden backlog.
Why require Verify & Close instead of just marking done?
For room issues, staff-reported issues, and critical assets, a supervisor must verify the fix before closure. This stops technicians from marking work complete when it is not — a common cause of repeat guest complaints and rooms released before they are genuinely ready.
Can housekeeping report issues without calling engineering?
Yes. Housekeeping opens Report Issue, enters area and room, selects category and priority, and types the problem statement. The system creates a numbered work order, assigns it to the maintenance manager, and starts the SLA clock — no phone call or group message required.