Shift-Change Log to Structured Handover Prompt

Start here

Paste your raw shift log where the prompt says [paste raw shift log here], then optionally add shift, site, next shift start time and who you hand over to. Paste the whole prompt into any ordinary AI chat that accepts text. No terminal or account setup is needed.

Check the draft yourself: every log line should appear as an item or an Open Question, each item should carry a short quoted fragment from your log, and any mention of injury, damage, near-miss, rule breach or hazard should appear under SAFETY / HOLD. If your log has no such mention, the draft should say "No safety items identified".

What this prompt does

It reads only the text you paste and produces a draft handover, not a sent message. Items are sorted into SAFETY / HOLD, PENDING, DONE and FYI, with conflicts shown side by side and gaps listed as Open Questions. It never invents owners, times, locations or causes.

Inputs you need

• The raw log text, pasted as-is. Shorthand, typos and out-of-order notes are fine.
• Optional context: shift and site, when the next shift starts, and names or roles receiving the handover.
• If a field is unknown, say so; the prompt asks the assistant to mark it rather than guess.

Permissions and limits

The assistant cannot reach your systems, records or messaging tools and sends nothing. It works on pasted text only, so it cannot verify counts, close tickets or confirm that a safety issue was escalated. A human must review, correct and actually send the handover. Output quality depends on how much of the log you paste.

Checking the output

The worked example inside the prompt is explicitly fictional and is only a shape reference, not a test result.

FAQ

Can it retrieve my actual shift records? No. It only uses what you paste; nothing is fetched, and it cannot send the handover. What if my log is very short or missing details? Items stay as written and missing owner, time or location appear as Open Questions instead of guesses.

Verification note

source reviewed; runtime not tested.

Complete reusable prompt

You are helping me turn a messy shift-change log into a clean, reviewable handover for the next person or team. You do not have access to my systems, records or messaging tools. You only work from what I paste below, and you prepare a draft for a human to review and send.

INPUT I WILL PROVIDE I will paste a raw shift log. It may be shorthand, out of order, contain typos, or mix facts with opinions. If a field is missing, say so rather than guessing. Log: [paste raw shift log here]

Also tell me, if I know them:

• Shift and site: [e.g. Night shift, Warehouse B]
• Next shift starts: [time or unknown]
• People to hand over to: [names or roles, or unknown]

TASK

1. Read the log and extract every distinct item as a separate entry. Do not merge or drop items, even minor ones.
2. Classify each item into exactly one group:
   • SAFETY / HOLD: anything that could injure someone, damage equipment or product, breach a rule, or that a next-shift person must not ignore.
   • PENDING: work started but not finished, or promised but not yet done.
   • DONE: completed, needing no handover action beyond awareness.
   • FYI: context with no action required.
3. For each item, quote the original log words (short verbatim fragment) so the reader can trace it back. If the item is inferred rather than stated, mark it [inferred] and keep the inference minimal.
4. Flag conflicts: if two entries disagree (times, counts, status), list both side by side and mark [conflict]. Do not silently pick one.
5. Flag gaps: if the next shift would clearly need information the log never provides (owner, location, time, next step), list it under Open Questions.

OUTPUT FORMAT Handover draft - [shift] - [site] - [date if given]

1. SAFETY / HOLD - do not proceed without checking

   • Item: ... | Source: "..." | Status: ... | Owner (if stated): ...

2. PENDING - carry over

   • Item: ... | Source: "..." | What remains: ... | Owner (if stated): ... | Blocker: ...

3. DONE - awareness only

   • Item: ... | Source: "..."

4. FYI

   • Item: ... | Source: "..."

5. CONFLICTS

   • A: ... / B: ... | Which is which: ... | Needs human decision: yes

6. OPEN QUESTIONS for the next shift or the log author

   • ...

7. ONE-LINE SUMMARY

   • The single most important thing the next shift must know: ...

RULES

• Never invent an owner, time, location, cause or outcome that is not in the log.
• Never soften a safety item. If the log hints at risk, put it in SAFETY / HOLD and let a human downgrade it.
• Keep each item to one or two lines. No advice, no blame, no speculation about people.
• Do not tell me to contact anyone and do not claim you sent anything. You produce a draft only.

CHECK BEFORE YOU FINISH

• Did every log line map to at least one item or Open Question?
• Does every item have a short verbatim source fragment, or an [inferred] tag?
• Is at least one item in SAFETY / HOLD if the log mentions any injury, damage, near-miss, rule breach or hazard? If none, say 'No safety items identified' explicitly.
• Are all conflicts shown side by side with no silent resolution?

WORKED EXAMPLE (fictional) Input log: '2300 forklift 3 steering loose told Sam. aisle 7 pallet leaning. 0130 finished cycle count zone A 148/150 - two missing, think miscounted. 0200 break. told night supe about forklift, he said note it. restocked gloves. drowsy around 0300.'

Expected output shape:

1. SAFETY / HOLD

• Forklift 3 steering loose | Source: 'forklift 3 steering loose' | Owner: reported to Sam, night supe asked to note it | Status: unresolved, do not operate until checked.
• Leaning pallet in aisle 7 | Source: 'aisle 7 pallet leaning' | Owner: not stated | Status: unresolved.

2. PENDING

• Cycle count zone A | Source: '148/150 - two missing, think miscounted' | What remains: confirm two missing items | Blocker: possible miscount.

3. DONE

• Gloves restocked. 4. FYI: fatigue noted around 0300.

5. CONFLICTS: none stated, but 'think miscounted' is unverified - flag as [inferred].
6. OPEN QUESTIONS: Was the foreskinned loose steering escalated to a maintenance ticket? Who verifies the two missing items?
7. ONE-LINE SUMMARY: Do not operate forklift 3 until steering is checked.

Now wait for my log and produce the handover draft.

References and reuse

• ChatGPT release notes · Reviewed 2026-10-04

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.