Operations

A daily handover that closes the loop

Give the next shift a clear account of what changed, what needs a decision and who owns the next action. Use one record per issue to track verified outcomes, protect access details and follow through on guest commitments.

Sixto team22 min read

Two people review a sheet on a clipboard while one holds a set of keys.

A handover works when the next shift can act

Reception, housekeeping leads, managers and owners covering their own shifts all need the same result: the next person can pick up the work without calling whoever just left.

Make what changed, what needs a decision and who owns the next action clear. A reservation export cannot do that on its own. Neither can a meeting transcript or a detailed account of your shift.

Example: give “early arrival” a next step

Consider this illustrative note: “Unit 4A: guest requests early arrival. Readiness unconfirmed. Laura, housekeeping lead, will verify the unit’s status. Mateo at reception will check the result at 11:00 before replying. Early access has not been promised.”

“Early arrival” alone leaves the next shift guessing. This version identifies the uncertainty and gives named people something to do.

Keep the basic test short:

  • The change and outstanding decision are clear.
  • Someone owns the next action.

Tip: Hand over a way forward, not just an account of what happened.

Acceptance is not completion. An accepted handover means the incoming person understands how to carry the work forward, not that the outstanding work is finished.

Start with exceptions, not a reservation dump

Compare today’s arrivals and departures with actual unit readiness. The reservation schedule tells you what should happen. The handover identifies where reality no longer matches that plan. Include differences that require action, a decision or verification. Leave the full reservation list in its source record.

1. Compare the schedule with confirmed conditions

Check recorded departures, expected arrivals and the latest housekeeping or maintenance update. A scheduled departure does not prove the guest has left. Cleaning in progress does not mean the unit is ready for the next arrival. Look for changed commitments as well as unfinished work.

2. Check the source and timestamp

For each status, establish who confirmed it and when. If reception says “ready” but a newer housekeeping update lists unfinished work, flag the conflict and request verification. Do not pick whichever version makes the schedule easier. Write awaiting verification when evidence is missing.

3. Separate promises from estimates

Record what the guest has actually been promised separately from the team’s working estimate. An early-arrival request is not an approved early check-in. “Housekeeping estimates completion at 13:00” does not mean “You can enter at 13:00.”

Tip: Keep the source and timestamp attached to an estimate. Copying it into a handover must not turn it into a guest commitment.

Worked example: three exceptions worth handing over

These situations, times and role assignments are illustrative. The source timestamp shows when the fact was confirmed, not when the note was copied. The next review is an internal checkpoint, not a guest promise.

Unit Confirmed fact Verification source and time Guest commitment Internal estimate Next action and owner Next review Decision-maker
4A Guest requested early arrival Guest message, 12:00 Early entry has not been confirmed Not confirmed Incoming receptionist checks actual availability 12:30 Duty manager approves early arrival
402 Cleaning remains unfinished Housekeeping lead’s report, 12:15 Entry at 15:00 Completion at 13:00, from housekeeping lead’s 12:15 report Housekeeping lead confirms completion and inspection 13:15 Duty manager decides on an alternative if the commitment is at risk
305 Lock is faulty Maintenance report, 12:20 Guest update at 14:00 No resolution estimate Maintenance verifies technical condition; incoming receptionist coordinates an alternative and the guest update 13:30 Duty manager authorizes a change of accommodation

4. Decide what needs attention first

  1. Urgent blocker: Does it prevent arrival or threaten an existing commitment? Put it ahead of routine follow-up.
  2. Decision needed: Does someone need to approve an alternative or change a commitment? Name the person with that authority. Verifying a repair does not authorize a change of accommodation.
  3. Routine follow-up: Is this a progress check with no known conflict? Record the specific verification needed and the next review, not the entire history.

Give each open item an owner and a next-action time

Give every open action one accountable owner, even when several people help. That person tracks progress and confirms the outcome. Name supporting staff, a backup for absences and the decision-maker for anything outside the owner’s authority. A group chat cannot own a task.

Keep three times distinct:

  • Action due time: when that work should finish, not necessarily when the unit will be handed over.
  • Next review time: when you will check progress if completion cannot yet be confirmed.
  • Guest commitment: what you promised the guest and when. An internal estimate does not replace it.

1. Assign the action and get acceptance

  1. Write a specific next action and the evidence needed to verify it. “Check the unit” needs a clear inspection scope.
  2. Name the proposed owner, supporting staff and a backup. Identify who can make decisions beyond the owner’s remit.
  3. Ask the recipient to confirm the action and its due or review time. Sending an assignment does not establish acceptance.
  4. If the recipient does not respond, mark it awaiting acceptance. Record who will monitor it, when they will check and who will contact the backup.

Example: reception to housekeeping and maintenance

In this illustrative example, reception asks the housekeeping lead to verify the inspection of Unit 402. The lead accepts a 13:00 review. That is a progress check, not a promise that the unit will be ready for the guest.

If the inspection reveals a leak, create a linked action for the maintenance technician. The technician accepts responsibility for assessing the leak; the housekeeping lead retains the inspection action. Name the manager as decision-maker if spending approval is needed.

Use these operational labels:

  • Awaiting acceptance: assignment sent but not accepted, with a named monitoring owner and next review time.
  • In progress: work has started.
  • Blocked: an identified dependency prevents progress.
  • Awaiting verification: completion reported but not checked.
  • Closed: outcome verified.

Tip: An action nobody has accepted still needs coverage. It is not a completed transfer.

Before you leave the assignment, check:

  • Can the owner act, or do they know who must decide?
  • What evidence will confirm the outcome?
  • Who will check next, and when?
  • Who covers an absence?

If you operate alone, schedule your own next review. If reception will be unattended, explicitly name the person monitoring the open item.

Use a handover record you can copy

Keep one record per open item, not a new record for each shift. Retain its ID through closure and reference it in related messages. This keeps reception and maintenance from maintaining competing versions of the same issue.

Blank record template

Copy this table for each item. Brackets mark fields to complete, not facts to assume.

Field Value to enter
Item ID [Stable ID]
Unit or reservation [Reference]
Shift and update timestamp [Shift, date and time]
Exception [What changed or needs attention]
Operational status [Blocked, in progress, awaiting verification or closed]
Priority [Priority and reason]
Verified fact and source [Fact, source, date and time]
Guest commitment [Promised outcome, date and time, or explicit status]
Next action [Specific action]
Owner [Name]
Acceptance [Who accepted, date and time, or pending]
Deadline [Date and time, awaiting confirmation or not applicable]
Next review [Date and time]
Backup [Name and confirmed availability]
Decision-maker [Name for decisions beyond the owner's authority]
Blocker [What prevents progress, or none identified]
Protected-record reference [Reference, awaiting confirmation or not applicable]
Closure evidence [Outcome, source, date and time, or pending]

Worked examples: Units 402 and 4A

All names, dates and references below are illustrative inventions. Availability and acceptance are recorded before making a commitment. A shift label alone proves neither.

Field Unit 402 Unit 4A
ID P-021 P-022
Shift and update Morning, 15 October 2026, 11:00 Morning, 15 October 2026, 11:05
Exception Guest reports a leaking tap Early arrival requested
Status and priority Blocked; inspection needs arranging Awaiting verification; readiness needs checking
Fact and source Guest conversation received on 15 October 2026 at 10:50; leak unverified Reception confirmed departure on 15 October 2026 at 10:30; readiness unverified
Guest commitment Update on 15 October 2026 at 12:00 No confirmed entry-time promise
Action and owner Arrange a maintenance check; Laura Pérez, reception Ask housekeeping lead for status; Diego Ruiz, reception
Acceptance and availability Laura accepted on 15 October 2026 at 10:55 and confirmed coverage through the 12:00 update before it was promised Diego accepted on 15 October 2026 at 11:00 and confirmed availability for the 11:30 review
Deadline 15 October 2026, 12:00, for guest update Awaiting confirmation; no entry time promised
Next review 15 October 2026, 11:30 15 October 2026, 11:30
Backup Ana López; coverage confirmed for the 12:00 update Ana López; coverage confirmed for the 11:30 review
Decision-maker Ana López, manager Ana López, manager
Blocker Entry permission awaiting confirmation Readiness awaiting confirmation
Protected-record reference R-402 R-4A
Closure evidence Pending Pending

1. Complete and update the record without guessing

  1. Search for the existing ID before opening another item. Add new information to that record and preserve its history.
  2. Separate a report from a verified condition. Record the source and date of each check.
  3. Avoid unexplained blanks. Enter awaiting confirmation when a fact is unknown, not applicable when the field does not apply, and no confirmed promise when you have checked that no commitment exists.
  4. Keep the deadline, internal review and guest commitment separate. Include dates and times so an inherited item does not look as though yesterday's deadline belongs to today.
  5. Confirm acceptance and coverage. An unanswered assignment remains pending acceptance; it does not establish availability.
  6. Add closure evidence when it exists. Until then, leave the evidence field marked “pending”.

Tip: Keep the ID when ownership changes. A new shift should not restart the record.

Internal handover message

Share references rather than protected content:

Subject: Handover [shift] | [date and time]
Main record: [location]
Priority items: [ID, action, owner and deadline date/time]
Next review: [ID, date and time]
Coverage: [owner who accepted and confirmed backup]
Decision needed: [ID and decision-maker]
Confirm receipt and the action you accept: [ID and action].

Receiving the message is not the same as accepting the action. Accepting it is not evidence that the work is finished.

Separate a conversation from an action

A guest message can create three different outcomes: a reply, a repair and a follow-up. Track them separately and connect them to the same reservation and issue. Read is not resolved. A helpful reply does not prove that maintenance has fixed anything.

1. Turn the message into verifiable actions

  1. Acknowledge the report. Explain what you understand and what happens next. Do not announce a visit before it has been arranged.
  2. Create the operational task. Describe the specific fault, name its owner and agree a due time or next review time. Link the conversation rather than copying the entire exchange.
  3. Arrange the visit. Confirm timing and the relevant entry permission with the guest, following your property's procedure. Record the blocker while that confirmation is outstanding.
  4. Require evidence of the result. Ask the person doing the work to record what they did, when and how they checked the repair. “Done” is not a test result.
  5. Track follow-up separately. Tell the guest what has been verified. If you still need confirmation that a reported inconvenience has stopped, keep that follow-up open with an owner and next review time.

Tip: Hand over the outstanding outcome, not another copy of the message. Each action needs its own evidence before you close it.

Worked example: a leaking tap in Unit 402

In this illustrative example, a guest reports a dripping bathroom tap. Reception acknowledges the message and assigns an inspection to the maintenance lead. The conversation is now answered, but the repair remains open.

Reception asks about a suitable visit time and permission to enter. Maintenance accepts the task but waits for that arrangement before entering. After access is authorized, the technician completes the repair and records the check: running and closing the tap, then observing that the drip has stopped. That supports technical closure. Reception shares the verified result and keeps any outstanding guest follow-up separate.

If the guest cannot be reached to arrange entry, do not assume permission. Record the actual position: report received, visit unconfirmed, repair not performed. Reception owns the next contact attempt and review time. If the guest is unreachable after an authorized, verified repair, record that without claiming they are satisfied.

Mistakes that hide unfinished work

Do not close an issue because someone read it, mistake “technician notified” for an accepted task, or treat a scheduled repair as completed. Avoid spreading copies across chats. Keep one operational record linking the reply, the repair and the follow-up.

Handle an early arrival without overpromising

Worked example: Unit 4A is still pending at shift change

In this illustrative example, Unit 4A has a scheduled 10:30 checkout. The next guest requests an arrival before the agreed check-in time. Reception changes shifts while cleaning is underway. Scheduled checkout does not confirm actual departure, and a housekeeping estimate is not a promise of entry.

1. Establish the facts before handing over

  1. Verify departure. In the example, at 10:40 the outgoing receptionist personally checks that the guest has left and the unit is vacant. Record that source and verification time separately from the scheduled 10:30 checkout.
  2. Check with the housekeeping lead. At 10:45, the lead confirms cleaning is underway and inspection remains outstanding. Keep any completion estimate separate, labelled as an internal estimate rather than a guest commitment.
  3. Assign the next check. The incoming receptionist accepts responsibility for checking progress and updating the guest at 11:00. This is a follow-up time, not an entry time. Before offering entry, they must still verify inspection, access readiness and the relevant authorisation.

Tip: Promise an update you can deliver, not entry that still depends on unverified conditions.

2. Follow the branch supported by the evidence

  • Readiness confirmed: can you authorise early entry under the reservation terms? If so, confirm it and send instructions through the approved guest channel.
  • Cleaning delayed: keep entry unconfirmed. Arrange another check and send the promised update even if there is no change.
  • New maintenance blocker: record what prevents release. Assign someone to consult the authorised decision-maker about the next step. Do not replace one estimate with another unsupported promise.

Copyable handover notes and guest update

These notes continue the example. Adapt the owners and times to your operation.

Outgoing note: 4A. Scheduled checkout: 10:30. Outgoing receptionist personally verified departure and vacancy at 10:40. Housekeeping lead confirmed cleaning underway at 10:45. Inspection and access verification outstanding. No early-entry promise. [Incoming owner] to check progress and update guest at 11:00.

Incoming note: Accepted. I own the progress check and guest update at 11:00. Entry remains unconfirmed.

Keep the guest message separate from the internal record:

Subject: Your arrival at [property]
Hi [name], we cannot confirm early entry yet. We will update you at [time], even if availability is still unconfirmed.

Keep access details out of the general handover

Record whether access is ready, blocked or awaiting verification, not the credentials needed to enter. Keep reusable master codes, identity documents and payment details out of general shift notes. Give the next person only what they need to take the next action.

1. Record status without exposing credentials

Include the unit, verified status, source and next check. Illustrative example: “Unit 402: access awaiting verification. Reception to check the protected record before sending arrival instructions.” Do not add the code or a screenshot that reveals it.

2. Point to the protected record

Use an internal record reference and check that the incoming person has access appropriate to their role. A reference should not make the contents available to everyone. If an authorised colleague cannot open it, assign the permissions issue to the responsible person. Do not bypass the restriction by copying the contents into a group chat.

3. Check the recipient before sending

Confirm the reservation, the recipient and the arrival checks relevant to your operation. Then send access instructions through the approved guest channel. A request from a new number or a forwarded message is not, by itself, proof of the sender’s identity.

Tip: The handover tells the next shift that access is ready. The protected channel holds the information that lets someone enter.

4. Review permissions and retention

When a team member leaves or changes roles, review their access, including shared documents. Define where records belong and how you review their retention and deletion. Check current Superintendencia de Industria y Comercio guidance for the personal-data obligations and retention practices applicable to your operation. Do not assume one retention period fits every record.

Internal access-readiness tracking does not replace guest registration. Check current requirements with Migración Colombia and MinCIT when reviewing that process.

Before handing over:

  • The note contains only necessary information.
  • Protected records have role-appropriate permissions.
  • The recipient is verified before instructions are sent.
  • Screenshots, attachments and general chats contain no credentials.

Avoid two common mistakes: treating “access ready” as permission to send credentials, and duplicating sensitive information because it is convenient.

Choose between paper, spreadsheets and software

Choose the system you can keep current during a shift, not the one with the longest feature list. Name one authoritative record where everyone checks the current status and updates open items. Chat can alert the team to a change. It should not force the next shift to reconstruct the situation from messages.

Option Best for Strengths Watch-outs
Paper Small operations with in-person handovers Works offline and keeps open items available at the desk Physical custody, legibility, manual searching and backup against loss. Avoid multiple active copies.
Shared spreadsheet Teams that need to view and filter a common record Lets you organise items by unit, owner or status Check permissions, concurrent edits, change history, backups and offline availability in your chosen tool.
Task software Multiple shifts or departments coordinating work Can bring assignments, comments and supporting evidence together Verify access controls, search, history, exports, backups and offline behaviour. Features vary by product.

Test it against your actual workflow

For a small rental operation, ask: can you find the open item without calling someone? Who updates it when you are away? Do you need remote access, or would a securely stored folder work?

For a multi-shift aparthotel, test what happens when reception and the housekeeping lead edit at the same time. Does either change disappear? Can you see who changed the record? Can each role access only what it needs? How would you recover the record if it became unavailable?

Use an illustrative case, such as an outstanding repair in Unit 402. Find the item, change its owner and check that the incoming shift sees the current version. If every update must be repeated on paper, in chat and in a spreadsheet, you are adding duplicate work and opportunities for conflicting instructions.

Tip: Use chat to flag an item and point to its authoritative record. Do not maintain a second version of its status there.

What to do when the handover breaks down

Missing information or an absent recipient means the item is not yet handed over. Keep its existing identifier. Record what is verified, what remains uncertain and who must remove the blocker.

1. Recover control of the open item

  1. If the incoming owner is absent: contact the named backup. If they are unavailable too, escalate to the person coordinating operations. State who will monitor the item until someone accepts it. Posting in a group chat does not establish coverage.
  2. If records conflict: compare sources, timestamps and supporting evidence. Do not automatically trust the newest note. Ask someone able to check the actual condition, and leave the disputed status unverified until they respond.
  3. If a commitment was missed: preserve both the promise and what actually happened. Contact the guest through the approved channel, acknowledge the missed commitment and explain the next verifiable step. Do not turn another estimate into a replacement guarantee.
  4. If the system is unavailable: use a securely held fallback sheet with the item identifier, timestamp, status, next action, owner and next review. Exclude credentials. Once service returns, reconcile those updates into the main record, identify their source and remove duplicate tracking without losing the sequence of events.
  5. If the issue survives several shifts: retain one authoritative item, summarize previous attempts and escalate the blocker to someone with decision-making authority. Copying yesterday’s note is not progress.

Worked example: night reception cannot confirm access

In this illustrative case, the Unit 402 handover says “access ready,” but the protected source does not confirm verification. The night receptionist keeps the status awaiting verification. They do not improvise a code or share alternative credentials.

They assign escalation to the shift coordinator and record the next check. The guest receives a separate update: “I’m checking access to your accommodation. I’ll let you know through this channel when it is confirmed.” Internal disagreements and staff blame stay out of that message.

Tip: When records disagree, pass on verified facts, not the most convenient version.

For suspected credential exposure or an immediate safety concern, follow the property’s incident protocol and involve the designated responder. For personal-data handling, check current guidance from Colombia’s Superintendencia de Industria y Comercio rather than inventing reporting duties or deadlines.

Finish with a short reconciliation

Before signing off, compare completed tasks with unresolved guest conversations. You do not need a fixed meeting length. You need to account for every open action.

1. Check tasks against conversations and promises

  1. Review completed tasks alongside unanswered or unresolved guest messages. Did the work deliver the promised outcome, or only part of it?
  2. Check the evidence: who verified the result, when and what they observed. A “done” message alone does not establish that the outcome is true.
  3. Review blockers and overdue actions. State what is preventing progress, who can remove the obstacle and whether a guest commitment remains outstanding.
  4. Give every open action one owner and a next check time. Update changed facts rather than carrying yesterday’s note forward unchecked.
  5. Ask the incoming person to explain the next action and confirm responsibility for following it through. Assignment is not acceptance. If they have not responded, identify who will monitor the item until receipt is confirmed.

Worked example: reported repaired, not yet verified

In this illustrative example, maintenance reports that the leaking tap in Unit 402 has been repaired. Nobody has checked whether the drip has stopped. Keep the repair awaiting verification, with an owner and a next check. If you also promised the guest an update, keep that follow-up open separately.

Close the repair when a recorded check confirms the result. Close the guest follow-up when the promised communication has been delivered. If a later check finds the tap still dripping, reopen the same item, record the finding and assign the next action.

Tip: Close an item because the outcome is verified, not because the shift ended or someone read the message.

Copyable outgoing and incoming checklist

Before you leave

  • I compared completed tasks with open guest conversations.
  • I recorded closure evidence and updated blockers and overdue actions.
  • Every open action has an owner and a next check time.

When you take over

  • I can explain the next actions without calling the previous shift.
  • I confirmed which items I own and which guest promises remain open.
  • I recorded questions or conflicting information before accepting the handover.

Measure progress, not messages sent

Count distinct items, not messages or copies of yesterday’s note. An issue carried across several shifts keeps its identifier. Three people receiving it does not make it three cases.

1. Set the reporting window

  1. Choose a review week and record its start and end.
  2. For open-item measures, take a snapshot at the end of that window. Include unresolved items inherited from earlier weeks.
  3. For reopened items and recurring causes, review events within the week. Count each item ID once per measure, even if it generated several messages or was reopened more than once.

Keep the definitions consistent so comparisons mean something:

Metric Definition or formula Source Review question
Open items missing an owner or next check Open items lacking either or both fields, counted once End-of-period record Who will pick this up, and when?
Overdue open actions Open items whose action due time falls before the reporting cutoff Due time and current status What prevented progress?
Reopened items Distinct IDs moved from closed back to open during the week Change history Was the outcome verified before closure?
Repeat exceptions by cause Distinct items with the same recorded cause during the week Item record and verified cause Which part of the process needs changing?

2. Read the numbers in context

Illustrative example: you have 12 open items at the cutoff. Of those, 3 lack an owner or next check. The calculation is 3 ÷ 12 × 100 = 25%. An item missing both fields still counts only once.

An overdue internal action is not automatically a broken guest promise. Compare the internal due time with the commitment actually recorded for the guest. Keep suspected causes separate from verified ones rather than forcing every delay into a convenient category.

3. Fix the recurring obstacle

Review readiness delays weekly with reception and the housekeeping lead. Look for documented patterns: an unconfirmed departure, a missing inspection or another repeated blocker. Assign one specific process change and check its effect at the next weekly review. Do not solve a recurring delay by making the handover longer.

Tip: Avoid staff rankings based on closure totals. They can reward closing work before anyone verifies it. Look for evidence of progress, not items disappearing from the list.

Test the handover at your next shift change

1. Choose one working record

Pick the record you will keep current: paper, a shared spreadsheet or a task board. Adapt the earlier template to your operation. Remove fields that do not help anyone decide, but keep the evidence, next action, owner and review time. Name a backup for anything that cannot wait until you return.

2. Test it on real open items

At the next shift change, ask the incoming person to explain what they will do first, what needs verification and when they will check again. If they cannot explain it, improve the record, rather than scheduling another meeting.

For example, when handing reception to your night colleague, check that they can find readiness evidence without seeing access codes in the general note. If you work alone, write for your next working session. Set the next review and identify who will handle developments while you are unavailable.

Tip: Judge the handover by what the next person can do, not by what you remember explaining.

3. Decide what needs changing

Before you finish the trial, check:

  • Can you locate evidence for each recorded status?
  • Are access details kept outside the general record?
  • Does every unresolved guest promise have an owner and next check?
  • Is someone covering for an unavailable owner?
  • Can the incoming person explain the next action without calling you?

Review recurring exceptions weekly. When the same blocker returns, change the process causing it instead of making the handover longer.

If a task board would help, test whether it lets you assign owners and keep comments and supporting evidence with each item. You can also run this method in the record you already use.

Practical operations guidance, not legal or tax advice.

ShareWhatsAppLinkedInX