A shift handoff should let the incoming engineer act without repeating the outgoing shift's diagnosis. The record needs to answer five questions: what is urgent, what changed, what remains open, what is blocked, and who owns the next action.
Use the checklist below as a standard for every handoff. Keep the durable details with the work order or maintenance queue; use the verbal handoff to focus attention on risk and decisions.
Before the outgoing shift ends
1. Review safety and guest-impact items first
Call out life-safety concerns, electrical or water hazards, rooms out of order, active leaks, refrigeration failures, public-area issues, event impacts, and repeat guest complaints. For each item, record the current control, affected location, escalation owner, and next review time.
Do not bury a safety or guest-impact item in an alphabetical ticket list. Priority should be visible before the incoming shift starts routine work.
2. Confirm the location and asset
Every open work order should include the room number or public-area location, building or zone, equipment name, and asset tag or model when relevant. Add access restrictions, key requirements, vendor escort needs, and whether the room is occupied.
“Air conditioner broken” is not a handoff. “Room 214 PTAC, compressor trips after three minutes, room held out of service” gives the next engineer a safe starting point.
3. Separate completed, active, waiting, and monitoring work
Use fixed status labels so the next shift can scan the queue:
- Completed: repair finished and the required test or inspection passed.
- Active: work is underway and the next physical or diagnostic step is known.
- Waiting: work is blocked by a part, vendor, access, approval, or scope decision.
- Monitoring: a temporary fix is in place and a defined check is required.
Do not mark a temporary workaround as complete unless the property has an explicit monitoring plan and risk owner.
4. Record the next action, owner, and timing
Each open item should state the next action, person or role responsible, expected time, and what evidence will close it. If the timing is unknown, record the dependency that prevents a reliable ETA.
5. Attach the evidence the next shift needs
Include photos, readings, test results, parts information, vendor notes, access details, and any guest or department communication. Evidence prevents the next person from repeating the same inspection just to reconstruct context.
Incoming-shift review
The incoming engineer should acknowledge the handoff, not merely receive it. Review the following in order:
- safety, life-safety, and occupied-room risks;
- events, arrivals, public spaces, and other time-sensitive impacts;
- active work with a next action due during the shift;
- parts, vendor, access, and approval blockers;
- rooms or assets under temporary control or monitoring;
- the oldest open items and any overdue preventive maintenance;
- items that require a manager, security, housekeeping, front desk, or event-services update.
If an item is unclear, resolve the ambiguity before the outgoing engineer leaves or assign a named follow-up. An unassigned question becomes a repeat visit.
Copyable shift handoff form
Date / shift:
Outgoing engineer:
Incoming engineer:
Manager on duty:
SAFETY / GUEST IMPACT
- Location / asset:
- Risk or guest impact:
- Temporary control:
- Escalation owner and next review:
ACTIVE WORK
- Ticket / location / asset:
- Status:
- Finding and work completed:
- Next action:
- Owner and ETA:
- Evidence attached:
WAITING ON PART / VENDOR / ACCESS / APPROVAL
- Ticket / dependency:
- Contact or order reference:
- Expected update:
- Contingency if delayed:
MONITORING / TEMPORARY REPAIR
- Location / asset:
- What to check:
- Check time and success condition:
- Escalate if:
EVENT / ARRIVAL / PUBLIC-AREA IMPACTS
- Function or area:
- Required completion time:
- Coordination owner:
PREVENTIVE MAINTENANCE / OLDEST OPEN ITEMS
- Item and reason still open:
- Next decision:
- Owner:
HANDOFF ACCEPTED BY:
Notes / unresolved questions:
Handoff quality checks
Once a week, sample open work orders from each shift and check whether another engineer could act from the record alone. Track reopened work, repeat incidents, age at handoff, overdue high-priority work, blocked hours, and missing evidence.
The goal is not to rank technicians. It is to find where the operating system loses information: a missing asset ID, an unclear status, a vendor dependency with no owner, or a temporary repair with no inspection time.
Standardize this form inside Maintenance, then connect it to the hotel maintenance SLA playbook and digital maintenance requests guide.