Digital Shift Handover Log

The problem this kills

Shift change is the most dangerous five minutes in the plant. The outgoing supervisor scribbles a few lines in the pass-down notebook — line 3 was running rough, the QA hold on lot 882 is still open, the new operator on the packer needs watching — and walks out the door. The incoming supervisor reads what they can make out, fills in the rest from a hallway conversation, and hopes nothing was missed.

Then something falls through the cracks. The quality hold never gets actioned because it lived on a page nobody flipped back to. The machine that was "acting up" goes down hard at 2am because the warning was a smear in a notebook. The safety near-miss never gets logged. And when a customer or an auditor asks "what happened on the night shift three weeks ago," the answer is a shrug.

This is exactly the kind of structured, must-not-be-skipped handoff that a small internal tool does far better than a notebook — and you do not need to be a developer to build it.

What you'll build

A simple internal web tool for shift change. The outgoing supervisor opens a new handover for their line or area, date, and shift, and fills it in by section — what ran and the numbers, open issues, machine and equipment status, quality holds, safety notes, and the specific items the next shift must act on. When it's complete they sign it. The incoming supervisor opens it, reads it, and acknowledges receipt — and only then is the handover finalized.

The clever part is the carry-forward. Any open item that isn't closed automatically appears on the next shift's handover, and the one after that, until someone marks it done — so nothing quietly disappears at shift change. The finished handover is emailed to the incoming supervisor via Resend, and you can export the full handover history and a live list of everything still open.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent. It opens by interviewing you about your plant — your lines and areas, your shift pattern, the exact sections and fields on your current handover template, how you name machines and lots, your typical and peak volumes, and your messy edge cases — and then tailors the data model, the handover form, and every later step to your answers. This is a build shaped around how your plant runs a shift change, not a generic template.

From there it walks the agent through the database schema, the section-by-section handover form built from your template, the sign-and-acknowledge gate, the automatic carry-forward of open items, the Resend email to the incoming supervisor, and the history and open-items exports. Every step ends with a ready-to-copy prompt. Because the whole thing runs on CSV in (import your template) and CSV out, you can build and use it this afternoon even with no connection to your MES or ERP.

The governance it includes (this is the point)

A handover is a record people rely on, so it's built like it matters: login so only your supervisors and line leaders can use it, row-level security so each plant or area only sees its own handovers, and a complete audit trail of who created, signed, acknowledged, and closed each item — and when. Nothing is "done" automatically: a handover is a draft until the outgoing supervisor signs and the incoming supervisor acknowledges — that two-person sign-and-acknowledge step is the hard human-in-the-loop gate. And a duplicate guard on line/area + shift + date means you can't accidentally open two handovers for the same shift.

Who it's for

Shift supervisors and line leaders who run the pass-down at every shift change and are tired of trusting a notebook with the things that keep the plant safe and running. If you can describe what goes on your handover sheet today, you can build this.

You've got this — open the plan, paste the first prompt, and let it interview you about your shift change.