Pipeline draft · Operations
DRAFTWriting a Shift Handover
This lesson left the pipeline and nobody published it. It passed the structure and concept-ordering gates; the rubric gate result below is read from the verdict files beside it. This version was revised by hand after it left the pipeline; the status file lists every change, and the original is kept beside it. Rubric gate: passed with three independent models, means 4.25–5.00, largest disagreement on any one criterion 2 points. LLM rubric scores, not human QA. Panel decision: goes to a human, because the models differ by more than a point on bilingual quality. A split is a signal, not something to average away.
- OPS-01Given the end of a shift with work still open, write a handover that the next person can act on without having to contact you
What is a shift handover?
A shift handover is the moment work changes hands at the end of a shift, with all relevant context recorded so the next person can continue without asking you. The simple test of a successful handover is: **Can the next person act on it without contacting you?**
Length is not the measure; a page of narrative that buries the one urgent item is worse than three precise lines.
The moment work changes hands at the end of a shift, with all relevant details recorded.
A ticket, order, or task that is not yet resolved when the shift ends.
An open item that requires action before the next shift ends, usually marked with a deadline.
Separate verified statements (facts) from assumptions (guesses).
A promise to complete a specific action for a customer, colleague, or manager by a certain time.
The central system (ticket, log, channel) where the handover is written so anyone covering the shift can find it.
- What is it?One line that precisely identifies the item (ticket, order, customer).
- What is the status?Current state as a fact, not a feeling.
- What has been done?What has already been tried and failed, so the next person does not repeat it.
- What happens next and by when?Specific next action with a clear deadline.
Key takeaways
- Write the handover in a shared record, not on a personal scrap.
- Order items by urgency, then answer the four questions for each item, in order.
- Separate facts from guesses; label guesses clearly.
Put it to work
- Define next action and deadline
- Log what has been done
- State the status
- Identify the item
Ticket #4523 concerns a customer payment failure. Two retry attempts have already been made without success. The customer asked for a response before the end of the day. Write the appropriate handover.
You are ending your shift with two open items: a ticket from customer "Ali" about a login issue, who was promised a reply before 14:00 today; and an order waiting for the supplier to confirm a delivery date, with no deadline today. The order arrived first. Which line opens your handover?
Choose a card, then choose the group it belongs to.
Knowledge check — not scored
Your handover has three open items. In what order do you write them?
Select one answer.
Knowledge check — not scored
A colleague's handover reads: "Ticket 77: the customer's card is expired. Ask for a new card." You open the record: the payment failed twice, and nobody has confirmed why. What is wrong with the line?
Select one answer.
Files in the repository: lesson.json · items.json · STATUS.md