Operations · Closing
The last hour builds tomorrow morning.
Closing is often treated as cleanup after the real work. In practice, it is the final custody transfer of the day: every remaining vehicle, key, payment, incident, and promise must land with a named owner before the closing lead disappears.
The close
Finish the open set; do not merely turn off the stand.
A useful close leaves the next crew a known starting state. Anything unresolved becomes a documented exception with ownership, secure custody, and a next action. Unclaimed vehicles are governed by contract and state or local rules; follow the operation's approved process rather than general advice.
The last-hour sequence
Reconcile while the facts are still nearby
Close in dependency order
→Vehicle and key custody come before sweeping and stocking. Appearance cannot certify control.
Require a specific zero-state
Custody
Every remaining car is named
Session, location, key, expected guest action, and overnight owner agree.
Money
Every tender has a disposition
Digital totals, cash, validations, refunds, and unresolved charges are reconciled or assigned.
Incidents
No report is ownerless
Evidence is preserved, communication status is recorded, and the next contact has a named role.
Stand
Opening can begin cleanly
Devices charge, supplies return, signage resets, and exceptions are visible before intake begins.
Make the closing lead sign the state, not a list of chores. Checkboxes such as “keys counted” and “cash done” are useful only if a mismatch cannot be checked away. The close should preserve both the count and the exceptions that explain it.
Track close defects as opening defects too. If the morning crew repeatedly searches for a charger, deciphers an overnight vehicle, or learns about a guest promise from the guest, the last hour has become hidden setup labor for the next shift. Put that work back where the context exists.
Keep the close short by collapsing completed complexity. A resolved incident, returned key, or reconciled payment should leave the open set. The final report should emphasize what remains, not replay everything the shift successfully completed.
Where a shift report helps
Close against one operating record.
Active sessions, notes, payment status, and unresolved work are easier to reconcile when they share a current record instead of separate paper, texts, and memory.
The takeaway: a good close is not an empty curb. It is a complete explanation of everything that is not empty.
