Operations · Shift Handoffs

Nothing important should cross a shift by memory.

A night crew can appear to create a problem that actually began hours earlier: an open ticket with no key location, a damage note nobody passed along, or a guest promise that existed only in conversation. The failure belongs to the handoff, not the people who inherited it.

The operating truth

A handoff is a transfer of unfinished work.

A schedule tells you who is leaving and who is arriving. It does not tell the arriving crew what remains unresolved. A useful handoff names every car, key, exception, promise, and constraint that can still change the next shift.

The standard is simple: the incoming lead should be able to orient the stand without reconstructing the afternoon from parked cars and half-finished conversations.

The open set

Transfer what can still surprise someone

01

Build the handoff around exceptions, not a diary

A long shift recap buries the few facts the next crew must act on. Start with what is still open.

Sessions

Cars still in custody

Guest identity, vehicle, space or staging area, request status, and anything unusual about return.

Keys

Every nonstandard location

Keys in a pocket, lockbox, office, vehicle, or with a manager are exceptions until acknowledged.

Condition

Damage and incidents

Record what was observed, when it was observed, what evidence exists, and who owns the next communication.

Promises

What the guest was told

A waived charge, a retrieval time, a manager callback, or special access must survive the speaker leaving.

If it can cause the incoming crew to say “nobody told me,” it belongs in the open set.

02

Use a closed-loop exchange

Posting a note is not a handoff. The receiving crew must confirm that the operating picture matches the curb.

1Outgoing lead updates the open set before relief arrives
2Both leads walk keys, spaces, and exceptions together
3Incoming lead acknowledges each unresolved item
4Ownership changes; completed items collapse out of view

The overlap can be brief. What matters is that responsibility changes explicitly.

Do not make “no issues” the default shorthand. A quiet shift can still leave an unclaimed vehicle, a key outside its normal place, or a guest expected after midnight. A useful zero-state is specific: all active sessions accounted for, all keys in their recorded locations, no unresolved incidents, and no guest commitments outstanding.

Review recurring handoff misses monthly. If the same kind of exception keeps appearing, the fix is probably a standard field, a clearer owner, or an earlier cutoff rather than another reminder to “communicate better.”

Where a live record helps

Make the open set visible before the crew changes.

A shared session board and shift report can preserve the status, notes, and unresolved work that spoken handoffs lose. Visibility does not prevent every miss, but it gives both crews one operating picture to reconcile.

The takeaway: a handoff is complete only when the incoming crew can name what remains open and owns the next move.

Keep reading.

OperationsTeam

Closing Procedures: What a Good Last Hour Looks Like

The close reconciles vehicles, keys, money, incidents, and tomorrow's setup while someone still owns every exception. It should produce a clean opening state.

Feb 25, 2026 · 6 min readRead
OperationsTeam

The Car That Will Not Start

A no-start is a classification problem before it is a repair problem. Protect the vehicle, preserve the curb, involve the guest, and escalate without improvising electrical work.

Feb 15, 2026 · 6 min readRead
OperationsTeam

Key Control: The Discipline Nobody Writes Down

Boards, pockets, and lockboxes each create a different failure mode. Good key control makes custody visible, exceptions explicit, and every transfer accountable.

Jan 28, 2026 · 6 min readRead

When reading is not enough

See it on your drive.

Twenty minutes on your own property, with your own volumes. We would rather show you the parts an article can only describe.

or keep reading the journal