Shift handover: 4 items to pass on

In the previous lesson we built the daily close: four checks before shutting the branch, each leaving unfinished items with a named owner and a time. But most branches do not run one shift. Between morning and evening there is a handover, where the till, the live orders and the customer promises pass from one employee to another. The close protects the end of the day; the handover protects its middle.

In most businesses that handover is verbal: a sentence at the door, or a voice note in a group. The result is a second shift that does not know what a colleague promised an hour earlier. This lesson covers the four items that must pass in writing.

Why the verbal handover fails

• It leaves no trace: when a customer calls in the evening about a morning promise, the incoming employee has nothing but a departed colleague's memory.
• It never fixes when responsibility moves: an order delayed in the first shift and noticed in the second becomes a mistake with no owner.
• It reports the good and skips the bad: people hand over what they finished, rarely what got stuck — and the second is what the incoming shift needs.
• It shrinks under pressure: on the busy day, when it matters most, it collapses into one word.

The four items that pass in writing

1. Custody: cash, keys and devices

The first thing to pass is whatever can be counted: the till balance, anything already banked, and the devices held by the shift. The point is not suspicion, it is that any later difference belongs to a defined window instead of a whole day — which turns an investigation from hours into minutes.

2. Live orders and their real status

Passing the list of open orders is not enough — it already exists in the system. What the handover carries is the gap between the status on screen and the status on the ground: an order marked ready but waiting for a driver, one delayed at the customer's request, one blocked on a missing part. That gap is the whole value of the handover.

3. Promises made to customers

Every verbal promise given during the shift must leave it in writing: customer name, what was promised, and when. A promise only one employee knows about is not a commitment by the business, it is a risk to it. When the customer calls later and finds someone who already knows, the handover has paid for itself.

4. Faults and open exceptions

The printer that stopped, the card reader that lags, the item logged as an exception. These repeat forever precisely because they pass verbally and never escalate. Make any fault appearing in two consecutive handovers escalate automatically to whoever owns maintenance, like the other steps in running the system from WhatsApp.

The handover as two messages

A good handover needs no meeting and no paper form. The outgoing employee writes one word:

Morning shift: handover

System: Morning shift handover, Yasmin branch, 3:00 PM. Till: SAR 4,200. Live orders: 4, including order 518 waiting for a driver. Customer promises today: 1. Open faults: none. Anything I did not record?

Morning shift: I promised Abu Mohammed a call before 7 PM on order 518, and the second card reader is slow

System: Logged the promise to Abu Mohammed on order 518, due 7:00 PM, and the card reader fault. That fault is now in two handovers, so I escalated it to maintenance. Summary sent to the evening employee.

Evening shift: received

System: Responsibility transferred at 3:04 PM. Reminder: call Abu Mohammed before 7:00 PM.

Notice three things: the system starts from what it already knows, the incoming confirmation is what moves responsibility, and the repeated fault escalates unasked.

Checklist before you turn handovers on

Item	Decide in advance
Handover time	Fixed per shift, not the moment someone walks out
Who hands over, who receives	Two names per shift, plus a stand-in
When responsibility moves	On the receiver's confirmation, not the sender's message
Verbal promises	Written with customer name and due time before closing
Repeated faults	Two consecutive handovers means automatic escalation

A common mistake: a handover with no receipt

The design that fails most often stops at the message the outgoing employee sends. Responsibility does not move on sending, it moves on receiving: without a confirmation you have proof that someone wrote, and none that anyone read. Close every handover with a word from the receiver, and alert the supervisor if it never arrives. More in the system on an employee's phone.