At 2:55 p.m., the receptionist knows that a guest is waiting for an update. At 3:10 p.m., a new colleague is at the desk, and the guest has to explain everything again. The problem is often a handover that records the request without making the next action clear.
A useful handover answers five questions: What is happening? What has been checked? What must happen next? Who owns that action? When is the next update due? This HCA practice framework should be adapted to your hotel's approved system, procedures and authority limits.
Start with the next expected outcome
“Maintenance informed” describes something that happened. It does not explain what the guest is still waiting for. Write the request, the verified position and the next commitment.
Separate facts from assumptions: “Engineering acknowledged the request” is different from “Engineering fixed the problem.” Do not promise a completion time that the responsible team has not confirmed. You can still agree when you will update the guest.
The handover checklist
- Reference: use the approved reservation or case reference so your colleague can find the correct record.
- Issue: explain the request or problem in one clear sentence.
- Verified action: record what actually happened and the latest relevant time.
- Next step: state the specific action still required.
- Owner: identify the colleague or department responsible for that action.
- Update time: say when the guest should hear from the team, even if work remains unfinished.
- Escalation: note the agreed supervisor contact or escalation route when needed.
- Status: distinguish open, awaiting confirmation and completed work using approved labels.
Read urgent or time-sensitive items aloud with the incoming colleague. Ask them to explain the next action back in their own words. A silent signature does not show that both people understand the same commitment.
Worked example: an unfinished request
The following case is fictional and contains no real guest information.
Weak handover: “A/C problem. Engineering told.”
Useful handover: “Training case FO-014. Guest reports that the room feels too warm. Engineering acknowledged the request at 14:40; completion is unconfirmed. Incoming front-desk colleague to contact engineering, then update the guest at 15:10 as agreed. If unresolved, give an honest update and follow the duty manager's escalation procedure. Status: open; guest update required.”
Notice that the note distinguishes an acknowledged request from completed work. The incoming colleague should not mark the case complete merely because responsibility changed at the end of the shift.
If your hotel uses OPERA traces
Oracle describes traces as actionable instructions for a selected department and a specific date and time. Its Today's Traces guidance covers reviewing traces, updating fields and changing their status after action. Use your configured workflow and permissions; a general note may not replace a required trace.
A five-minute practice exercise
Create three fictional cases: a pending guest request, an arrival needing coordination and a billing question awaiting an authorized colleague. Write a handover for each. Have a partner identify the owner, next action and update time without asking for clarification. Revise any missing detail.
Develop your skills through HCA Academy, describe relevant experience accurately in the CV Builder, and explore hotel jobs.
The checklist and scenario are original HCA training suggestions. The reused header image is an AI-generated illustration with fictional people, as recorded in the existing HCA asset metadata.
