End-of-Shift Digest Email
Build an internal tool that auto-drafts a clean end-of-shift digest - output vs target, downtime, scrap, open issues, and safety notes - then lets the supervisor review, edit, and send it to managers with one click. No more chasing each line for a verbal handoff.
A logged-in tool where a supervisor gathers shift numbers, gets an auto-drafted digest, edits and approves it, and sends a consistent end-of-shift snapshot to managers - with every sent digest archived and exportable.
Before you start
- A free Supabase account
- A free Resend account (or any email-sending account you can get an API key for)
- A free Vercel account for deploy
- Your shift's summary numbers (output, downtime, scrap, issues) - typed in or pasted from a spreadsheet
- A recipient list of managers (CSV or Google Sheet)
The problem this kills
Every shift change, the same scramble happens. A manager pings the supervisor: "How'd the line run? What was down? Any scrap problems? Anything I need to know before tomorrow?" The supervisor digs through a clipboard, a whiteboard, two spreadsheets, and their memory, then types a slightly different summary than they typed yesterday - or forgets to send one at all.
The result is that managers get an inconsistent, incomplete picture of what happened on the floor. Output-vs-target gets buried, a recurring downtime cause goes unnoticed for a week, and a safety note never makes it past the supervisor's head. The handoff between shifts is the riskiest moment in production, and it's running on memory and goodwill.
What you'll build
A small, private web tool your supervisors log into at the end of every shift. They punch in (or paste) the shift's numbers, and the tool auto-drafts a clean, consistent digest - output vs target, downtime highlights, scrap, open issues, and safety notes - in the exact format your managers want. The supervisor reads it over, fixes anything, approves it, and sends it to the manager recipient list with one click via email.
Nothing goes out automatically. A human always reviews and presses send. Every digest that ships is archived so you have a searchable record of every shift, and you can export the whole log to a spreadsheet any time.
What's inside the Implementation Plan
The plan is a complete, paste-and-go runbook for an AI coding agent (Claude Code) - written so a non-developer can follow it.
It opens by interviewing you about your plant - your lines and areas, your shift names and times, how you measure output and target, the downtime and scrap categories you actually use, your issue and safety conventions, and your typical and peak volumes. It then tailors the digest template, the data fields, and every later build step to your operation, so you get a tool shaped like your floor - not a generic template you have to bend to fit.
From there it walks you step by step: set up the database and login, build the "enter the shift numbers" screen, generate the auto-draft, add the review-edit-approve gate, wire up sending through Resend, archive every sent digest, and add a one-click spreadsheet export. Each step ends with a ready-to-paste prompt.
The governance it includes (this is the point)
- Login so only your team can open the tool.
- Row-level security so each plant or team only ever sees its own shifts and digests.
- A full audit trail - who drafted, who approved, who sent, and exactly when.
- A hard human-in-the-loop send gate - the tool drafts, a supervisor reviews and approves, and only then does the email go out. No silent auto-send, ever.
- A duplicate guard keyed on line/area + shift + date, so you can't accidentally fire off two digests for the same shift.
Who it's for
Shift supervisors who send the handoff, and production or plant managers who receive it. If you run a floor on shifts and you're tired of chasing a consistent end-of-shift snapshot, this is for you. You don't need to know how to code - you need to know how your shifts actually run.
You've got this - paste the first prompt and let the agent interview you.