A guest asks for extra coat hangers near the end of a shift. A colleague checks availability, leaves a note and moves on. The next team can see the request, but cannot tell whether anyone accepted it, what the guest was told or who should act next. The note has travelled; responsibility has not.
A useful hotel shift handover makes the next decision possible. It gives the incoming team enough context to continue the work without reconstructing the previous shift. That means being clear about what remains open, what has actually happened and which colleague owns the next action.
These seven hotel shift handover steps offer a starting framework for routine guest-service work. Adapt the roles and records to the property’s own service procedures, then try them with a colleague before using them across shifts.
1. Define the work a hotel shift handover must carry
Begin with unfinished work that requires a decision, action or guest update. A long account of everything that happened can make those items difficult to find. Separate background information from something that the next team must pick up.
For each open item, ask: what remains to be done, what would happen if nobody acted, and who needs to know? A routine request for an additional room item might need a delivery check. A question about an amenity might need an answer from another department. Neither should be described simply as “guest request”.
Keep the hotel shift handover focused on continuation. Completed work belongs in the appropriate record; bring it into the briefing when it explains an outstanding issue or changes what the next colleague should do. This keeps the boundary between an update and an assignment visible.
2. Follow the work across departments
For a hotel shift handover, take one routine request and trace its route. Who receives it? Who can decide whether it can be fulfilled? Who carries it out? Who tells the guest what happened? Those roles may sit in different departments, or one person may cover several of them.
ASQ’s flowchart guidance recommends defining a process’s boundaries and reviewing its sequence with the people involved. Applied here, that means checking the handover with the colleagues who actually receive and deliver the work, rather than designing the record solely from a manager’s view.
Use the conversation to find gaps, not to create a larger form. If reception says a task goes to housekeeping, ask which role receives it and what happens when that person is unavailable. Our overview of hotel staff responsibilities provides background on the different teams; the local map must name the property’s own arrangements.
Consider a property where departments change shifts at different times. The person leaving reception may be unable to brief the colleague who will eventually deliver a request. Name a receiving role and fallback in the process itself. Until that responsibility is clear, the outgoing team still has an open handoff to resolve.
3. Separate a request from a confirmed commitment
A request has been received. A colleague has checked whether it can be met. An authorised person has agreed an action. The action has been completed. These are different positions, even when a team uses one short word, such as “pending”, for all of them.
Define the states that matter for your service. Explain what evidence moves an item between them: an acknowledgement, an availability check, an authorised decision or confirmation that the work has been carried out. Avoid treating a sent message as proof of completion.
A hotel shift handover also needs the guest’s side of the story. Digital NSW’s service-blueprint resource distinguishes the customer’s experience from the processes supporting it. That is a useful prompt: an internal task can be complete while the guest is still waiting for an answer. Record both positions where they differ.
4. Write a record someone else can use
The record should help a colleague act without guessing. Use concrete descriptions, the latest confirmed position and an explicit next step. “Follow up” needs an object: check availability with whom, answer which question, or confirm what action?
This small hotel shift handover record is a starting point, not a required software format. It can sit in an approved system or an existing operational log. Keep guest information within the property’s established arrangements; the example fields below require no real guest details.
A small hotel shift handover record
- Open item: The specific request or question still requiring work.
- Current position: What has been checked, decided or completed, and what remains unknown.
- Next action and owner: The next task, its responsible role and an agreed fallback contact.
- Guest update: What the guest has been told and who will provide the next update.
- Review point: When or after which event the team will check the item again.
A review point is not automatically a delivery promise. It might be the moment another department confirms availability. Make that distinction in the record and in the conversation with the guest.
Before adding another hotel shift handover log, identify where the team already records the work. If a notebook and a message channel are both involved, agree which record holds the current position. Other notes should point colleagues towards it. Otherwise, an apparently detailed briefing can leave two people working from different versions of the same request.
5. Make the handover a two-way conversation
Written hotel shift handover notes give the incoming team something to refer to. A conversation lets them challenge an unclear instruction before the outgoing colleague leaves. Use both for the items that need explanation, rather than reading every line of the log aloud.
The CIPD’s public overview of employee communication highlights line managers, multi-directional dialogue and the planning and tailoring of communications. The practical implication for this framework is simple: leave room for the receiving colleague to ask questions.
During the hotel shift handover, ask that colleague to explain the next action in their own words. They may understand the request but lack authority, access to the relevant information or a contact in another team. Resolve that gap or record who will resolve it. Acknowledging an item should mean accepting a clear responsibility, rather than merely confirming that a note was seen.
Plan for interruptions too. If a guest arrives during the briefing, identify which item was being discussed and who is holding it while the conversation pauses. Resume from that point. Being present at the desk should not silently transfer responsibility for an item that was never explained.
6. Close the task and the guest update deliberately
Decide what completion means for the particular item. An enquiry passed to another department is at a different stage from an answer returned to reception. An item prepared for delivery is at a different stage from confirmation that the agreed action happened.
In a hotel shift handover, the next owner should be able to identify the remaining gap. If the action is complete but the guest has not been updated, keep that communication visible. If the request cannot be fulfilled, the team needs an authorised response, rather than an entry quietly disappearing from the list.
A service record cannot establish that a guest is satisfied simply because a colleague marked it closed. Record the action and communication that actually occurred. Broader questions about the working environment belong alongside this process; THD’s guide to managing hospitality teams offers that wider context.
7. Review the pattern without turning the log into a verdict
Use a short review to ask why items are carried forward. Was a decision missing? Did a message reach the wrong role? Was the current version difficult to find? Choose a specific weakness to address instead of treating every unfinished request as a failure by an individual.
The hotel shift handover record shows what the team captured; it is not a complete measure of service quality. A rise in recorded items could reflect better recording, a busier period or a different mix of requests. Establish what the entries mean before drawing conclusions.
After changing a hotel shift handover field or responsibility, walk through a routine example again. Check whether the next colleague can identify the current position, owner and update point. Keep the change small enough to explain, and give subsequent shifts the same version.
A worked example: the unfinished coat-hanger request
Consider this hypothetical example. A guest requests extra coat hangers shortly before the morning team hands over. Reception has asked the relevant colleague about availability but has not received an answer.
A weak hotel shift handover entry would say only “extra hangers requested”. The incoming colleague would still need to discover whether the guest received a promise, whether anyone accepted the task and what should happen next.
Using the proposed record, the outgoing colleague states that availability is unconfirmed, identifies the role expected to answer and records what the guest has actually been told. The incoming colleague accepts responsibility for checking the reply and providing an update. The property’s own arrangements determine who may approve the response if the item is unavailable.
When the answer arrives, the record changes to reflect that answer. If the request can be fulfilled, the team still needs confirmation of the agreed action. If it cannot, the authorised response and guest update remain the next work.
The point of a hotel shift handover is visible here: the next person inherits a defined piece of work, together with its uncertainty. Start with one routine request, test whether another colleague can continue it, and revise the record where they still need to guess.
Sources and further reading
This hotel shift handover guide applies general process-mapping and communication methods to routine guest-service work. The linked resources provide further background.
- ASQ: Flowchart — process boundaries, sequence and review with the people doing the work.
- Digital NSW: Service blueprint — the relationship between a service user’s experience and supporting work.
- CIPD: Employee communication — the role of managers and two-way dialogue in employee communication.
