Write a shift handover note so nothing falls through the cracks
A structured handover from one shift to the next covering open issues, safety, status, and what the next shift must do first.
The prompt
Write a shift handover note from my rough notes.
Operation and shift: [e.g. "warehouse, day shift to night shift", "call center, morning to evening"]
My rough notes from this shift: [PASTE NOTES, CHAT MESSAGES, OR BULLETS]
Key numbers: [output vs. plan, backlog, staffing, downtime - whatever we track]
Who is taking over: [ROLE - e.g. "night supervisor"]
Organize the handover in this order:
1. Safety and urgent: injuries, near misses, hazards, anything unsafe or out of service. Put these first, even if minor.
2. Status vs. plan: a short table - metric | plan | actual | note.
3. Open issues: each with what happened, what's been done, current owner, and the next action expected from the incoming shift.
4. Equipment and systems: what's down, degraded, or under maintenance, with expected return time if known.
5. People: absences, cover arrangements, anyone new or in training (no personal or medical details).
6. First three things the next shift should do.
7. Waiting on others: pending replies from other teams, vendors, or customers.
Rules:
- Use only facts from my notes. Where something important is unclear (owner, time, status), mark it [CONFIRM] rather than guessing.
- Write in short, scannable lines - it will be read standing up.
- Flag anything that looks like it has been carried over from previous shifts without progress.
Then list any questions I should answer before I leave.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- PASTE NOTES, CHAT MESSAGES, OR BULLETS
- ROLE - e.g. "night supervisor"
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Write an after-action report and improvement planAn after-action report that rates performance against each objective, finds root causes, and produces a tracked improvement plan.
- Write a control plan for a production processA control plan that turns my product and process characteristics into what to check, how, how often, and what to do when it fails.
- Prepare a PPAP submission package for my customerA checklist of every PPAP element at my submission level, the status of each, and a plan to close gaps before the due date.