REGISTER REGISTER TO LEARN

Gather -> Summarize -> Carry Forward -> Draft -> Sign

Shift Handover Draft Generator

At the end of each shift the agent pulls every open batch, held item, and overnight alarm and writes a structured handover draft. It carries forward anything the last shift left unresolved so nothing drops between crews. The outgoing shift lead edits the draft and signs it before the next crew reads it.

The Problem

Shift change at 7 a.m. The logbook is half-filled and two alarms never made it into the notes.

The night shift is packing up. One reactor is mid-batch, a drum of intermediate is on hold pending a QC result, and the DCS logged three high-temperature alarms around 2 a.m. that got acknowledged but never written down. The handover is a rushed paragraph in a logbook, and the day shift starts the morning reconstructing what happened. The held drum sits another shift because no one flagged it.

What Changes

Every open batch, held item, and overnight alarm in the handover before the crew leaves.

The agent reads the shift logbook, the batch status list, and the DCS alarm log, then drafts a structured handover with open batches, held items, and the overnight alarm summary in one place. Unresolved items from the prior shift carry forward automatically so nothing quietly disappears. The outgoing lead edits and signs, and the next crew starts with a full picture.

Humans stay in control: the agent drafts and carries items forward, and the outgoing shift lead edits, adds context, and signs the handover before it goes to the next crew.

HOW THE AGENT WORKS

TRIGGERLLMAPIDECISIONACTIONWAIT
TRIGGERShift-end time reachedFires shortly before turnover or on a shift-end signal.
APIPull logbook and batch statusesReads shift logbook entries and open and held batch items.
APIPull DCS alarm logReads overnight alarms and events from the historian.
LLMSummarize overnight alarmsGroups alarms by unit with severity, counts, and active state.
DECISIONUnresolved items from prior shift?
LLMAssemble handover draftWrites the structured handover with carry-forward items included.
ACTIONPost draft for lead to signSends the draft to the outgoing lead to edit and sign.
The agent does not hand over the shift or close any item. Your outgoing shift lead does. The agent removes the rushed reconstruction and the alarms that never reach the logbook.

HOW TO BUILD IT

Three levels of depth. Pick the one that matches where you are.

For the ops person who needs to understand what's involved and brief their team.

Shift DataLogbook, batch status, and alarm log
The AgentWorkflow engine + LLM
Shift LeadEdits and signs the handover draft

WHAT YOUR TEAM PROVIDES ONCE

  • Open batch list - every batch still running or waiting with its current step
  • Held items - drums or lots on hold with the reason and who to chase
  • Alarm summary - overnight DCS alarms and events grouped by unit
  • Carry-forward - unresolved items from the last shift kept visible
  • Handover draft - a structured document the outgoing lead edits and signs
What happens day-to-day: near end of shift the agent gathers the logbook entries, batch statuses, and the alarm log. It writes a structured handover draft and carries unresolved items forward. The outgoing lead reviews it on screen, adds any context, signs, and the next crew reads it at turnover.

For the IT person or technical lead who needs to scope the integration.

INQUIRY SOURCES

Shift logbook entries
Batch status list
DCS alarm and event log

WORKFLOW ENGINE (N8N)

Shift-end time reached
Pull statuses and logbook
Pull DCS alarm log
Summarize overnight alarms
Items to carry forward?
Assemble handover draft
Post draft for signature

CONNECTS TO

MES / batch system (Werum PAS-X / Emerson Syncade / AVEVA MES)Read: batch status, held items. Write: none
Historian / DCS (Emerson DeltaV / Honeywell / OSIsoft PI)Read: alarm and event log. Write: none
Logbook / eLog (Electronic logbook / SharePoint / shared drive)Read: shift entries. Write: signed handover
Notification (Email / Slack / Teams)Read: none. Write: handover draft to shift lead
WITHOUT PMS API

Without API access, the lead exports the batch list and alarm log or copies the logbook into the agent. It returns the same structured draft to edit and sign. Gathering the inputs stays a manual step.

WITH PMS API

With API access to the batch system and historian, the agent pulls statuses and the alarm log at shift end and posts a ready draft to the lead's screen. The lead edits and signs in a couple of minutes. Best experience.

For the person who wants to build this agent step by step. Each node below maps to an n8n workflow node.

TRIGGERNode 1
Trigger - shift end approaches
Schedule the run 15 minutes before turnover, or fire on a shift-end signal.
Output: { shift_id, unit_area, shift_end_at, prior_open_items[] }
APINode 2
API - pull batch status and alarms
Query the batch system for open and held items and the historian for alarms since shift start.
Output: { open_batches[], held_items[], alarms[] }
LLMNode 3
LLM - summarize overnight alarms
Send the raw alarm log. The model groups by unit, counts repeats, and flags still-active alarms.
Output: { by_unit[]: { unit, top_severity, count, active, note } }
You are summarizing overnight process alarms for a shift handover. Raw alarm and event log: {alarms}. Group them by process unit, note the highest severity per unit, count repeats, and flag any that are still active. Respond ONLY with valid JSON. No explanation.
INPUT
{"alarms":[{"unit":"R-101","tag":"TIC-101","desc":"high temp","severity":"high","time":"02:14","state":"cleared"},{"unit":"R-101","tag":"TIC-101","desc":"high temp","severity":"high","time":"02:31","state":"cleared"},{"unit":"D-201","tag":"PIC-201","desc":"low vacuum","severity":"medium","time":"04:05","state":"active"}]}
OUTPUT
{"by_unit":[{"unit":"R-101","top_severity":"high","count":2,"active":false,"note":"two high temperature alarms around 02:14 to 02:31, both cleared"},{"unit":"D-201","top_severity":"medium","count":1,"active":true,"note":"low vacuum on dryer still active at handover"}]}
LLMNode 4
LLM - assemble the handover draft
Send open batches, held items, alarm summary, and carry-forward items. The model writes actionable section lines.
Output: { handover: { open_batches[], held_items[], alarms[], carry_forward[] } }
You are drafting a shift handover for a chemical plant unit. Open batches: {open_batches}. Held items: {held_items}. Alarm summary: {alarm_summary}. Items carried from the prior shift: {carry_forward}. Write a structured handover with sections for open batches, held items, overnight alarms, and carry-forward, each item a short line an operator can act on. Respond ONLY with valid JSON. No explanation.
INPUT
{"open_batches":[{"batch":"B-5521","product":"CMP-204","step":"crystallization","eta":"09:30"}],"held_items":[{"lot":"L-8842","reason":"awaiting QC assay","owner":"QC"}],"alarm_summary":[{"unit":"D-201","note":"low vacuum still active"}],"carry_forward":[]}
OUTPUT
{"handover":{"open_batches":["B-5521 CMP-204 in crystallization, ETA 09:30"],"held_items":["Lot L-8842 on hold awaiting QC assay, owner QC"],"alarms":["D-201 low vacuum still active, check dryer"],"carry_forward":[]}}
DECISIONNode 5
Decision - unresolved items to carry?
If prior_open_items are still not closed, include them in a carry-forward section of the draft.
Output: { carry_forward[]: item_ids }
ACTIONNode 6
Action - post the draft for signature
Send the structured draft to the shift lead's queue or channel for edit and sign, with an unsigned signature block.
Output: Draft document with sections and an unsigned signature block
MVP vs Advanced — Where To Start
MVP — START HERE
  • Run 15 minutes before turnover
  • Pull open and held batches
  • Summarize overnight alarms by unit
  • Draft a structured handover
  • Lead edits and signs on screen
  • Next crew reads at turnover
ADVANCED — ADD LATER
  • =+ Carry-forward tracking across shifts
  • =+ Auto-pull alarms from the historian
  • =+ Held-item aging and owner reminders
  • =+ Link each batch line to its record
  • =+ Trend recurring alarms by unit and shift
  • =+ Searchable archive of signed handovers

Full Video Walkthrough Coming Soon

Watch the agent assemble a shift handover draft from the logbook, batch list, and alarm log.

Register to be notified

Everything on this page is free to learn.

When you're ready to build — do it yourself or bring us in.

Register FOR WALKTHROUGHS
Book a call to scope this

OTHER AGENTS IN LEASING & MARKETING

Yield and Mass-Balance Explainer

Reconciles charge versus output, flags abnormal loss, and shortlists likely causes

Reactor Changeover and Cleaning-Level Advisor

Recommends the minimum reactor clean between two products, with the residue check.

Solvent Recovery Reuse Advisor

Matches recovered solvent to upcoming batches, recommends reuse, top up, or discard.

Batch Record Right-First-Time Checker

Flags blanks, unsigned steps, and math errors before the record reaches QA

Frequently asked questions

Shift Handover Draft Generator is an AI agent that drafts the end-of-shift handover with open batches, held items, and overnight alarms.
Shift change at 7 a.m. The logbook is half-filled and two alarms never made it into the notes. The Shift Handover Draft Generator addresses this: drafts the end-of-shift handover with open batches, held items, and overnight alarms.
No. Your team stays in control. The agent does not hand over the shift or close any item. Your outgoing shift lead does. The agent removes the rushed reconstruction and the alarms that never reach the logbook.

This is 3 of 5 agents in Production & Batch Manufacturing. → · Explore all 15 departments →