What's an effective AI prompt for writing a shift-handoff production summary

The Prompt

Summarize this shift's production data into a handoff for the incoming shift.

Raw data: [output numbers vs. target, any downtime/incidents, quality issues, open work orders]
Format as: (1) output vs. target, (2) downtime/incidents and current status, (3) what the incoming shift needs to watch or continue.
Keep it scannable — the incoming shift lead needs this in under a minute.

Why This Prompt Works

A shift lead starting their shift needs to know three things fast — did we hit target, is anything currently broken, and what’s still open — and a summary organized around exactly those three questions gets read and acted on, where a raw data dump or a purely narrative handoff often doesn’t.

How to Customize It

Flag the current status of any open incident explicitly (resolved / monitoring / still down) — an ambiguous incident status is what most often causes duplicate or missed follow-up across a shift change. If output is trending below target for a specific, identifiable reason, name it rather than just reporting the shortfall, so the incoming shift knows whether to expect it to continue.

Common Mistakes to Avoid

Don’t bury an active incident in the middle of routine output numbers — it should be impossible to miss in a fast scan. Also avoid carrying forward stale watch-items shift after shift without updating their status; a list that never shrinks stops getting read closely.

Bottom Line

A shift-handoff summary built around output-vs-target, incident status, and open watch-items — in that order, scannable in under a minute — is what actually transfers information across a shift change.