Skip to content
Log in

Shift Handover Protocol

Structures the handover, because failures cluster at the boundary where responsibility transfers.

0

Share this prompt

Free — no card needed

Create a free account

to open Shift Handover Protocol — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryOperationsForOperatorsTested onClaudeChatGPT

Running it, start to finish

  1. Use a fixed format covering current state, in-flight work and the watch list.
  2. Have the incoming person acknowledge and question before the outgoing leaves.
  3. Retain the log — it is the most useful artefact in any incident review.

What you get back

The output this produces, every time.

  • Includes the watch list of things not yet a problem, which nothing else carries forward.
  • Requires both a written record and a verbal exchange, since each catches what the other misses.
  • Makes the handover complete on acknowledgement rather than on delivery.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Record what was tried and failed. Without it the incoming shift repeats the diagnosis, which is the most common wasted hour in shift operations.
  • Give the watch list its own section. Things not yet a problem have no ticket and no owner, so they are simply not mentioned unless the format demands it.
  • Design the busy-shift version. A long format gets abbreviated exactly when the shift was eventful, which is when the handover matters most.

More Operations prompts

All Operations

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.