Shift Handover Template: Let AI Turn Operator Notes Into a Report

AI can turn operator notes into a shift handover report if you give it a fixed template, the raw notes and one hard rule: it may only rearrange what operators said, never add to it. Keep safety in its own top section, and have the outgoing supervisor read and approve the draft before the next shift sees it.

The value is not elegant writing. It is that every handover answers the same questions in the same order: what is unsafe, what ran, what stopped, what is on hold, what is short, what needs maintenance. A template makes the gaps visible, and AI makes filling it less painful than a handwritten log at ten to six.

Follow me on Instagram@sagnikteaches

Why handovers go wrong in a plant

Handover failures are rarely dramatic. A press operator leaves a note saying "die running warm". The day shift reads it as a comment, not a warning, and the die is not checked until a part sticks. A pallet on quality hold is not recorded and the forklift driver ships it. A guard was bypassed for a trial run and nobody says it should be put back.

Connect on LinkedInSagnik Bhattacharya

The cause is usually one of three habits. Notes are written for the writer, not the reader. Everything is the same size on the page, so the urgent line sits between a note about a missing label roll and a reminder about overtime. And information lives in three places at once: the whiteboard, a paper log, and someone's memory. A template tackles the first two. Treating the report as the single record tackles the third.

Subscribe on YouTube@sagnikteaches

The template: sections in the order a supervisor needs them

Use one page per line or area. Here are the fields, with the reason each earns its place.

1. Header. Date, shift, line or area, outgoing supervisor, incoming supervisor. Without it a report cannot be found later.
2. Safety and environment. Injuries, near misses, guards or interlocks bypassed, spills, equipment locked out, anything an incoming operator must know before touching the line. If there is nothing, the field says "None reported", never a blank.
3. Output against plan. Planned units, actual units, scrap or rework count, and the reason for any gap in a few words.
4. Stoppages. Each one: machine, start, duration, cause as the operator understood it, whether it is fixed or temporarily fixed.
5. Quality holds and checks. Batches or pallets on hold, why, who owns the decision. Checks that failed and were rerun.
6. Materials and supplies. What is running short, what has arrived, what changes at the next run.
7. Maintenance requests. Raised, still open, urgent. Include the request number if you have a system.
8. People and cover. Absences, training in progress, anyone working a new station, anything the incoming supervisor must plan around.
9. First jobs for the next shift. Three lines at most, in priority order.

Name each section the same way every time so the AI can find it, and so people stop hunting. A column or two of tick boxes beside the stoppage and hold sections speeds up the writing, and removes ambiguity: "fixed" or "monitor" is easier than a sentence.

A filled-in handover (illustrative)

Here is an invented but realistic report for a packaging line at a food manufacturer, night shift to day shift.

HANDOVER: Line 3 (filling and capping), Night to Day, outgoing: [supervisor], incoming: [supervisor]

SAFETY
- Near miss 03:40: pallet jack caught the edge of the guard on the left of the capper. No injury. Guard bent, door still closes. Reported to [supervisor]. Check before restart.
- None else.

OUTPUT
- Plan 14,400 bottles; actual 12,950 (90%). Gap: stoppages below.
- Scrap: 85 bottles (misaligned caps). Rework: 0.

STOPPAGES
- Filler head 4, 01:10-01:55 (45 min): dripping nozzle. Replaced seal. Fixed, monitor.
- Capper, 04:20-04:50 (30 min): cap chute jam. Cleared by hand. Temporary: chute is bent, see maintenance.

QUALITY
- Pallet 118 on HOLD: three bottles with short fill found at 02:30. QA to decide. Do not ship.

MATERIALS
- Cap stock for next run is low: about 6,000 left. Next batch needs 9,600.

MAINTENANCE
- Raised: capper cap chute (urgent), filler head 4 seal (routine)

PEOPLE
- One operator on a new station (labeller), needs a second check on first 50 labels.

FIRST JOBS
1. Check capper guard and chute before restart.
2. QA decision on pallet 118.
3. Order or move caps for 9,600 bottles.

That report is under 200 words and takes about two minutes to read. It is also the standard to aim for: a person reading it cold knows what is dangerous, what is held, and what to do first.

Operator notes as they really arrive

Nobody writes the report above on their own at the end of a shift. What you get is closer to this, typed or dictated in a rush:

ok so quiet start. filler 4 dripping again around 1am replaced the seal 45min lost ish.
about 4 capper jammed cap chute cleared by hand its bent again needs fixing properly.
oh and near miss at 340 the pallet jack clipped the guard on the capper, nobody hurt, guard bent but shuts.
pallet 118 3 bottles short fill, left on hold, QA to look. didnt ship.
caps are low, enough for about 6000. new guy on labeller was fine but check first fifty.
we did 12950 i think, scrap 85.

Everything is there, but the near miss is in the middle and the output figure is at the end. The AI's job is to move each fact to its section, keep the figures as stated, and flag anything it was unsure of.

The prompt that does the conversion

You are preparing a shift handover report for a factory supervisor to review.

Use ONLY the operator notes below. Do not add, estimate or infer any figure,
cause, time or action that is not in the notes. If a field has no information,
write "Not reported". If something is ambiguous, list it under
"Questions for the outgoing supervisor" at the end.

Sections, in this order: Safety and environment; Output against plan;
Stoppages (machine, time, duration, cause, status); Quality holds;
Materials; Maintenance requests; People and cover; First jobs for the next shift.

Safety rule: anything that mentions injury, near miss, guard, interlock, spill,
lockout, fire, fume, chemical, forklift or "unsafe" goes in Safety and
environment, even if the operator mentioned it casually. Never summarise a
safety item more softly than the operator said it.

Plan for the shift: 14,400 bottles (I have supplied this; use it for the percentage).

Operator notes:
[paste notes here]

Illustrative output for the notes above: the same sections as the filled-in report, but with gaps wherever the notes were silent. The capper stop reads "about 04:00, duration not reported", the near miss has no exact position on the guard, the scrap line has no cause, and Materials says "about 6,000 caps left; next batch requirement not reported". Then comes a short list such as "Questions for the outgoing supervisor: 1. Capper stoppage at about 4:00: what time did it start and end? 2. Operator said '12950 i think': confirm the figure before the report is filed. 3. Which operator is new on the labeller? 4. How many caps does the next batch need?" The filled-in report earlier is what the draft becomes once the supervisor answers those questions. That list is the most useful part. It shows exactly where the AI refused to guess, which is the behaviour you want.

Look at what you must fix every time. A common slip: the assistant writes the capper stoppage as "approximately 30 minutes" when the operator never gave a duration, or fills in the cap requirement for the next batch from nowhere. Another: it moves "check first fifty" under Quality rather than People, which is harmless. A serious one: it rounds the near miss into "minor incident". The safety rule in the prompt tells it not to, but the supervisor's read is what makes the report safe.

Voice notes: from a recording to the report

Operators with greasy hands and a ten-minute changeover do not want to type. A voice memo is faster, and it is how many plants start. The pipeline is simple: record on a phone or a shared tablet at the line, transcribe, then run the prompt above. Several phone apps already turn a recording into text (Apple's Notes app and Google's Recorder app on Pixel phones both describe transcription in their help pages), so you need no new equipment to try it.

Watch four things:

• Noise. A loud floor garbles transcripts. Record in the supervisor's office or at the edge of the floor, and keep to short sentences.
• Numbers and part codes. Transcription mangles "twelve nine fifty" and codes with letters. Ask operators to say numbers digit by digit for lot or pallet numbers, and check every figure in the report against a source such as the counter.
• Accents and mixed languages. If the crew speaks several languages, test the transcript with each speaker for a week before relying on it. If a voice memo is in a language the supervisor does not read, the supervisor should not sign off a translated version without a bilingual check.
• Privacy. Voice notes can pick up names and conversations. Check what your chosen tool stores, and keep recordings only as long as your policy says. Never send a recording to a service your company has not approved.

A realistic first-week stumble: operators speak a line and then end with "and that's it", which the assistant faithfully writes into the report as a note. A tidy fix is a line in the prompt, "ignore filler such as 'that's it' or 'um'", and a template on a card by the recorder reminding people which headings to speak to: safety, output, stops, holds, materials, maintenance, people.

Safety flags: rules that stay with the human

This section matters more than any other. A report that buries a near miss is worse than no report, because it looks reliable. Build four rules into your routine.

1. AI may promote, never demote. It can move an item into Safety because of a keyword. It must never move an item out, shorten it, or change its wording.
2. The supervisor reads Safety first, from the operator's original note. Not just the AI summary. If the two differ, the original wins.
3. "None reported" is a claim. The outgoing supervisor confirms it before it is filed. If operators did not mention safety at all, the report says so, and the supervisor asks.
4. Escalate through the usual route. A handover report is not an incident report. Injuries and near misses go through your normal reporting process, and the handover mentions the report number.

For wider ideas about a safety checklist on the floor, see building a 5S audit checklist for the shop floor, which uses the same prompt-then-check routine.

Supervisor review: two minutes that make the report trustworthy

The supervisor is the last gate. Give them a checklist so the review is quick and consistent:

• Read Safety against the operator's own words. Does anything feel softer than what you were told?
• Check three numbers: output, scrap and the longest stoppage, against the counter or log.
• Read the questions the AI raised and answer or delete each one.
• Add anything that was said at the walk-round and is not in the notes.
• Sign, with initials and time, then file or send.

A review that takes more than five minutes usually means the notes were poor, not the AI. Fix it at the source, with a card of prompts at the line and a simple rule: if you did not note it, it did not happen.

A morning handover in a small plastics shop (a second example)

Here is an illustration from a different kind of plant: a six-machine injection moulding shop with two shifts. Before the template, handover was a whiteboard, wiped each morning, and a conversation at the door. In the first week of the new routine the outgoing supervisor spoke a two-minute voice memo into a phone, ran the prompt, corrected two items, and pasted the report into a shared document titled with the date.

The day supervisor found that the report listed "Machine 5: running warm, die temperature alarm at 02:10, reset, cause unknown" under Stoppages. In the old routine that line would have been shouted across the floor and forgotten. On paper, under a heading, it prompted a check of cooling lines before the next start. Nothing dramatic happened. The gain was that the same question, "what was wrong with machine 5 overnight?", was now answered in the morning without anyone chasing it.

When two notes disagree, and other awkward cases

Real notes contradict each other. One operator writes "filler 4 fixed", another writes "filler 4 still dripping at 5". If you let the assistant resolve it, it will pick one and sound confident. Tell it to do the opposite: list both under the stoppage and move the conflict to the questions list. The incoming supervisor then walks to filler 4 first thing, which is what you want.

Three more cases to prepare for:

• An empty shift. Machines were down for a planned changeover and nothing ran. The report should say so in one line ("Planned changeover, no production 22:00 to 04:00") rather than show a row of zeros that look like a failure. Add "Planned downtime" as a tick box to the Stoppages section so the data stays honest.
• A handover across several lines. A supervisor covering three lines should produce three short reports, not one long one. Paste each line's notes with its own header, and ask the assistant to produce a one-paragraph plant summary after the three, listing only safety items, holds and urgent maintenance. Keep the three line reports attached, because the summary leaves detail out.
• A contractor or agency operator. People who do not know your abbreviations write notes that look complete but use words the AI cannot interpret ("the usual fix"). Add a glossary of your machine names and codes to the prompt, and ask the assistant to ask rather than guess.

A quick before and after

Before: "cap chute jammed again, bent, sort it." After, as it should appear in the report: "Capper, 04:20 to 04:50 (30 min): cap chute jam, cleared by hand. Chute is bent. Maintenance request raised, urgent. Status: temporary fix." The second version names the machine, the time lost, the cause, the status and the follow-up. Train operators to give those five items for every stoppage and the report writes itself.

A simple sum shows why it is worth the effort. If each stoppage that lacks a clear cause costs the next shift ten minutes of asking around, and the line has four such stops a week, that is about 40 minutes of supervisor time weekly on one line, before counting the repeat breakdowns that nobody linked together. At five lines the figure passes three hours. These are illustrative numbers, so replace them with your own from a week of tallying, but the habit of counting is what persuades a plant manager.

Where the report goes after it is written

A report that lives in one inbox is half a handover. Decide where each one is filed and who reads it. A shared folder by date and line works for a small plant; a sheet with one row per shift suits a plant that wants to count stoppages. Over a month the filed reports become data: how often cap chute jams recur, which line loses most time to changeovers, which materials run short. Feeding a month of reports to an assistant and asking "list repeat stoppages by machine and likely cause as stated by the operators" is the starting point described in reading downtime logs to find repeat stops, and the daily rollup in the daily production report tutorial pulls the shift figures into a single page for the plant manager.

The same structure works outside a factory floor. The pattern in hotel shift handover notes is a good reference for how a different workplace splits urgent items from routine, if you want to borrow ideas for a warehouse or maintenance team.

Checking that the new routine works after a month

Do not judge it by how nice the reports read. Judge it by these measures, taken over four weeks:

• Completion. How many shifts produced a report? Aim for every shift; investigate gaps.
• Edits. How many facts did the supervisor have to correct? A falling number means notes are improving. A rising number means the template or the prompt needs work.
• Surprises. How often did the incoming shift find something that was not in the report? Keep a tally on a clipboard; each tick is a field the template is missing.
• Safety misses. Zero tolerated. Any case where a safety item was demoted or omitted means the rule is rewritten that day.
• Time. Minutes from end of shift to report filed. A realistic target is under ten.

Review the template every month and drop fields nobody reads. A shorter template that is filled in beats a thorough one that is skipped. If you find the report is mostly "Not reported", that is a sign that either the line is calm or the operators have stopped writing notes, and a walk round on the next shift will tell you which.

Keeping the template alive: a monthly twenty-minute review

Templates decay. Fields stop being used, a new product line needs a new check, and the safety section gets shorter as people get bored. Book twenty minutes a month with two supervisors and one operator. Bring five reports picked at random and ask four questions of each: did the next shift act on it, was anything missing, was anything never read, and did the wording of safety items match what happened? Change one thing each month and write the change on the template's header so everyone knows which version they are using. Update the prompt in the same sitting, because a prompt that lists fields the template no longer has produces confusing reports.

Rolling it out without a revolt

Start with one line and one willing supervisor. Run the old method and the template side by side for a week. Ask operators what they would change in the template, and change at least one thing visibly. Tell the crew in plain words what the AI does and does not do: it tidies their notes, it does not judge their work, and the supervisor's name is on every report. People who fear that the tool will be used to rank them will stop writing honest notes, so say in writing that handover reports are for the next shift, not for performance reviews. Keep to that promise.

Handover questions from supervisors

How long should a handover report be?

One page, readable in two minutes. Safety first, then output against plan, stoppages, quality holds, material and maintenance. If the incoming supervisor needs more, the report should say where to find it rather than reproduce it.

Should operators still talk to each other at the changeover?

Yes. A written report records the facts, but a five-minute walk and talk at the machine catches things nobody wrote down. Use the report as the agenda for that conversation, not as a replacement for it.

Can AI be trusted with safety items?

Not to decide them. AI can copy a safety note into the right section and flag the word it spotted, but a person must classify and sign off every safety item. Set the rule that AI may promote an item to Safety, never remove one.

What if operators will not dictate or type notes?

Make it easier than the alternative. A one-tap voice memo at the end of the shift takes less time than a handwritten log. Start with one line, and fix the template if the same field is always empty.

Where should the reports be stored?

Somewhere the next shift, the supervisor and maintenance can all find them by date and line, such as a shared folder or a sheet. Keep operator names out of any text you paste into a public AI tool unless your company policy allows it.

Further reads

• Small Factory CMMS With AI: Does the AI Layer Earn Its Cost? — Decide whether maintenance requests need their own system.
• Factory Training Videos With AI: Safety Clips in Several Languages — Teach the handover routine to a multilingual crew.
• Forklift Safety Checklist: AI-Built Daily Inspection Forms — A daily inspection form built with the same method.
• MRO Inventory Management: AI-Set Minimums for Maintenance Spares — Stop 'short on spares' appearing in every handover.
• How Can AI Help Project Delivery? Status Reports, Risks, Handovers — Status reports and handovers for longer projects.
• AI for Small Manufacturing Companies: Build a Weekly Production Schedule — A spreadsheet-based production schedule with worked capacity maths, changeover checks and a daily review routine.
• Six AI Applications in Manufacturing That Need No New Machines — Six office-side AI jobs for a small factory, each with a worked example, a starting step and the check that keeps it honest.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: general shift-handover practice in manufacturing; Apple Notes and Google Recorder help pages for phone transcription. Machine names, counts, times and sample outputs in the examples are illustrative.