Template preview · Hospitality
Hotel front office handover
Transfer front-office priorities between shifts with an actionable guest-service record.
A shift handover for a fictional hotel.
Sample purpose
Transfer front-office priorities between shifts with an actionable guest-service record.
Audience: Front office manager, Guest services agent- Structure
- 4 sections
- Criteria
- 12
- Sources
- 5
- Watches
- 3
- Default approach
- Review first
Set the purpose first. Then change every section, criterion, and agent setting before anything runs.
Fictional sample
Structure and criteria
Sample content shows the shape of a useful document. Copying it is optional.
01 Review firstShift and occupancy snapshot
For this hotel front office handover, states occupancy, rooms out of order, and shift timestamp.
Criteria
- Occupancy count and percentage stamped within 15 minutes of handover.
- Each out-of-order room has a reason and expected return time.
- Records outgoing agent and handover time.
Sources
- Seabird occupancy API (fictional) api.seabird-hotel.exampleFictional live occupancy and out-of-order rooms.
- Hotel shift checklist example receptionhub.britanniahotels.comReal example of snapshot items.
Sample content
- Occupancy
- 42 / 49 rooms (86%)
- Arrivals due
- 11 total; 3 after 22:00
- Rooms awaiting inspection
- 2
02 Review firstArrivals and room readiness
For this hotel front office handover, lists due arrivals and room-readiness exceptions.
Criteria
- Every arrival has an ETA, room and readiness status with a target time.
- A room is Ready only after housekeeping confirms inspection.
- Arrivals after 22:00 include key procedure and escalation contact.
Sources
- Seabird room status API (fictional) api.seabird-hotel.exampleFictional housekeeping status per room.
Watches
- Follows Shift and occupancy snapshot
Sample content
Room Arrival Readiness Owner 214 19:30 Ready Theo 307 22:40 Awaiting inspection Nia 115 23:10 Late arrival noted Night agent 03 ManualGuest incidents and follow-up
For this hotel front office handover, records incident status, owner, and promised next update.
Criteria
- Each incident has room, status, named owner and next-update time.
- Distinguishes handled from needs follow-up.
- Refers to guests by room number only, with no names, payment details or health information.
Sources
- Seabird incident log (fictional) api.seabird-hotel.exampleFictional incidents with owner and next action.
Watches
- Follows Arrivals and room readiness
Sample content
Incident Status Next update Lead Room 214 noise report Security checked hallway; no further report 21:30 guest call Theo Room 307 inspection delay Housekeeping notified at 18:20 18:50 readiness check Nia 04 Review firstHandover acceptance
For this hotel front office handover, names incoming agent and confirms open items accepted.
Criteria
- Incoming agent names each owner and action accepted.
- Records date, time and both agents.
- Rooms with housekeeping risk are flagged do not assign.
Sources
- Seabird handover log (fictional) api.seabird-hotel.exampleFictional acceptance audit trail.
Watches
- Follows Guest incidents and follow-up
Sample content
- ☐ Theo gives incoming agent the 21:30 guest follow-up
- ☐ Nia confirms Room 307 inspection or places arrival on hold
- ☐ Incoming agent signs handover and names open-item owners