During a management handover, a duty log can preserve operational context that does not fit in a formal report. It should help the incoming team see what happened, what remains open and who owns the next step, while protecting guest information and avoiding assumptions presented as facts. For related ownership and operational context, see the hotel-owner perspective, hotel operations, and Feathers Hospitality’s management approach.
The handover should follow the property’s authority, privacy and safety procedures. For ownership and operating context, see the hotel-owner perspective, hotel operations and Feathers Hospitality’s management approach.
At a glance
- Record events, status, owner, deadline and source.
- Separate confirmed facts from hypotheses and recommendations.
- Restrict access and confirm unresolved items with the incoming team.
Set the purpose and coverage of the log
Define which shifts and operational topics the handover covers: safety notices, room status, supplier visits, unresolved guest matters, system issues and decisions due. Do not use the log as a general diary or a substitute for financial or incident records.
Identify the period and time zone where relevant. A dated entry without time or status can be misunderstood during a transition. Link to approved records instead of copying details unnecessarily.
Capture facts and their source
State what occurred, when, who reported it and what evidence is available. Mark an observation, a confirmed fact and an interpretation separately. The incoming manager needs to know what is known before deciding whether to act.
Avoid subjective labels about staff or guests. Record the operational impact and any immediate control. If information is unverified, name who will confirm it and by when.
Assign every open action
For each unresolved item, name an owner, deadline, next step and escalation route. “Follow up with supplier” is incomplete if no one knows which contact or expected response. A handover log should make pending work transferable.
Confirm acceptance with the person taking over. Mark actions that were completed during the outgoing shift and close them with evidence. Do not assume that writing an entry transfers accountability.
Include decisions and temporary instructions
Record who authorized a change, its scope, start time and expiry or review date. Temporary service changes can remain in place after the reason disappears unless the log says when to revisit them.
Link to the approved procedure or contract where appropriate. Identify decisions that require owner approval and do not imply authority that the outgoing manager did not have.
Protect guest and staff information
Use minimum detail needed to continue the task. Keep personal data, payment details and sensitive complaints in authorized systems with appropriate access, not a broad shared log. Follow retention and access rules during the management transition.
Check who can view, export and retain the log. Remove temporary access when roles change. If an incident involves personal data or safety, use the formal reporting path in addition to the handover.
Verify the handover in both directions
The incoming manager should review high-risk items and ask questions before the outgoing person leaves. Confirm priorities, contacts, room blocks and supplier commitments against their source. A signature can acknowledge receipt without confirming every detail is accurate.
Use a short checklist for unresolved actions and escalation. Record items that need further evidence and who will provide it. Review the log after the first operating period and correct recurring gaps in the transition procedure. During the first days after transfer, compare the log with live supplier contacts, room status and scheduled work. Record discrepancies and correct the source record, rather than maintaining two competing versions. Confirm that the incoming manager knows which items require owner approval and which can be handled within the operating mandate.
Frequently asked questions
Should a duty log include every guest interaction?
No. Include operationally relevant events and link to authorized systems for detail. Avoid collecting personal data without a clear need.
Does a signed handover transfer all accountability?
No. Confirm specific actions, authority and ongoing responsibility. Use the contract and governance process to determine formal accountability.