Handover Notes: Brain Dump vs Runbook Format (Prompts)
Fourteen recurring duties, 22 staff, three freezer chambers at minus 18 degrees, and one supervisor about to disappear for six weeks. Northport Cold Storage had all of it written down in a 2,300-word document labelled “notes for cover”, and the person stepping in still called on day one to ask what time the carrier cutoff was.
The site holds 4,200 pallet positions, and the annual cold-chain audit falls in week four of the leave. That call is the whole problem: a handover can be complete on paper and still leave the reader unable to act at the moment it matters.
Fourteen Duties in One Word Document
A handover fails quietly. Nothing looks wrong on the first day, because the stand-in is competent and the building is running. The failures show up in week two: a log signed late, a booking missed by twenty minutes, a defrost that nobody started because the note said “as needed”.
The brain dump is not lazy writing. It is what a knowledgeable person produces when asked to explain their job: context first, exceptions next, and the routine compressed into a sentence, because the routine feels obvious to the person who does it every day.
- Time is relative: “first thing” and “end of shift” mean different hours on different shifts.
- Ownership is implied: the note says what happens, never who signs for it.
- Cutoffs are missing: the deadline that actually matters is the carrier’s, not ours.
- Exceptions are buried: the one page that matters in a failure sits in paragraph nine.
A model summarising that document will faithfully preserve its shape. Summaries shorten prose; they do not add the fields the prose never had. That is why the first prompt made the handover worse: it produced a tidier version of the same gaps.
The Summary That Buried the Cutoffs
The prompt below was written on a Friday afternoon, with the leave starting on Monday.
Summarize these handover notes into a clear document for the person
covering my leave. Make it easy to read and keep it under two pages.
Here are my notes: [2,300 words pasted]What came back: 760 words of clean prose in five sections, grouped by theme: daily operations, weekly tasks, supplier contact, equipment, and “other”. The temperature log appeared as “monitor chamber temperatures throughout the day and record as required”. The carrier booking appeared once, in a sentence about paperwork, with no time attached. Nothing named a person. Nothing said what to do when a reading went out of range.
The formatting was better than the original. The document was still unusable in the first hour of a failure, because “as required” is not an instruction, and “supplier contact” is not an escalation path.
The prompt asked for readability, and readability is a property of prose. A runbook is not more readable prose; it is a different object, with fields and thresholds, designed to be executed under pressure by someone who did not write it.
The Runbook That Names the Trigger
The second prompt does not ask for a summary. It asks for a conversion, specifies the unit of output, and gives the model permission to leave gaps visible instead of smoothing them over.
You are converting a supervisor's notes into a runbook for a cold-storage
warehouse. The reader is an experienced shift lead who has never run this
site. They will use the document while wearing gloves, standing up.
Input: the notes below. Duties mentioned: 14.
Produce one block per duty, in this order of fields, each field on its
own line and labelled:
Trigger - the event or clock time that starts the task
Cadence - how often, stated as a number and a unit
Owner - the role, never a person's name
Cutoff - the latest acceptable completion time, with the consequence of
missing it in the same line
Steps - no more than four, each starting with a verb
Escalation - role to call, and after how many minutes
Proof - what is left behind that shows it was done
Rules: maximum 70 words per block. Order the blocks by consequence of
failure, worst first, not by time of day. Use exact times in 24-hour
format. Where the notes are vague, do not invent a rule: write
"QUESTION: " and the exact question to ask before the leave starts.
Flag any duty that only one person on site can perform with the tag
SINGLE POINT.
After the blocks, add two lists: first-day checks, and do-not-touch items
that must wait for the supervisor's return.
Return the runbook only.What came back: 14 blocks, worst-consequence first, starting with the ammonia alarm response and the out-of-range temperature procedure. Each block had seven labelled lines. The carrier booking block read “Cutoff 15:30 for next-day collection; a missed cutoff costs one day and a rebooking fee”. Four duties carried the SINGLE POINT tag. The model also produced nine QUESTION lines, including “what is the acceptable range for chamber two during a defrost” and “who signs the pallet reconciliation when the shift lead is alone”.
Those nine questions were the most valuable output. They were the gaps the supervisor could no longer see, written down while there was still a week to answer them.
Five Fields a Stand-In Cannot Guess
The model can write steps from almost any notes. It cannot invent the five fields below, and those are exactly the fields that decide whether a handover works.
| Field | Weak version | Version that survives a bad night |
|---|---|---|
| Trigger | Regular checks | At 06:00, 14:00 and 22:00, or when a chamber alarm sounds |
| Owner | The team | Shift lead on duty, counter-signed by the loader |
| Cutoff | Before collection | 15:30, or the load rolls to the next day |
| Escalation | Contact maintenance | Call the refrigeration contractor after 15 minutes, site manager after 30 |
| Proof | Record it | Signed log line plus a photo in the shift channel |
Cutoff is the field people omit most often, because the deadline usually belongs to someone else. The carrier sets 15:30, not the warehouse. A stand-in who does not know that will plan the afternoon around the wrong constraint and discover the error at 15:45.
Escalation needs a number of minutes as well as a role. “Contact maintenance” leaves the reader to decide when persistence becomes appropriate, and a new person will always wait too long, because calling someone out at 03:00 feels like an overreaction until the chamber hits minus 12.
Converting Your Notes This Afternoon
The skeleton works for any role with recurring duties. The important part is the ordering rule and the permission to leave questions open.
You are converting [role] notes into a runbook for [reader], who has
[experience level] and has never run this site.
Input: [notes]. Duties mentioned: [n].
One block per duty, fields in this order, each labelled:
Trigger / Cadence / Owner / Cutoff / Steps (max [n], verb first) /
Escalation (role plus minutes) / Proof.
Rules: max [n] words per block. Order by consequence of failure, worst
first. Exact times, 24-hour. Where the notes are vague, write
"QUESTION: " and the question, do not invent a rule. Tag duties that
only one person can perform as SINGLE POINT.
Then: first-day checks, and do-not-touch items.Two edits make it fit a real site. Put the reader’s physical conditions in the prompt, because “gloves and standing up” changes the answer toward short lines and numbers. And set the word cap low, around 70 words per duty: the cap forces the model to drop the context that a stand-in does not need.
Then walk the runbook on site before the leave starts. Stand at the chamber door with the document and try to complete two duties from it, including one with a cutoff. The gaps you find in ten minutes are the ones a new supervisor would have found at 03:00 in week two.
Northport’s supervisor used the last week to answer the nine questions and to train a second person on the four SINGLE POINT duties. The audit in week four passed with two minor findings, both paperwork, neither caused by the handover. The document itself is now reviewed each quarter, which is the only way a runbook stays true after the person who wrote it comes back.
If you are building this into a wider operations library rather than a one-off leave document, the structure in our SOP workflow guide covers versioning and review cycles, and the first-week framing in our onboarding workflow is a useful cross-check for anything a new reader must be able to act on alone.
Sources & Notes
The seven-field block, the consequence-first ordering rule, and the SINGLE POINT tag are our own framing, reviewed on 2026-10-24. Northport Cold Storage, the 4,200 pallet positions, the three chambers, the 22 staff, and the 14 duties are illustrative examples. Cold-storage procedures are regulated differently by jurisdiction and by product category, and temperature limits, logging intervals, and refrigerant handling rules must come from your own safety and compliance documentation rather than from a generated draft. Treat any generated runbook as a first draft for a qualified reviewer, and never as the controlled procedure itself.
