Work Order Status Board
A live board that shows every open work order, the operation it's at, how far along it is, and whether it's on time or late - so nobody has to walk the floor or trust a stale whiteboard.
Import work orders and their routing, let operators update operation status, watch a live board show current operation, percent complete, and on-time vs late - with supervisor approval before completions or late flags hit your reporting.
Before you start
- A list of open work orders with their routing operations (a spreadsheet is fine)
- A way operators or supervisors report operation progress today (verbal, paper traveler, or a shop-floor CSV)
- Free Vercel, Supabase, and Resend accounts
The problem this kills
Right now, finding out where a job actually is means walking the floor and asking, squinting at a whiteboard somebody forgot to update, or pinging three people on the radio. Meanwhile a customer-service rep is on hold trying to answer "where's my order?" and a planner is guessing at what'll ship this week.
The information exists - it's just trapped in people's heads, on travelers, and in scattered messages. This tool pulls it into one live board everybody trusts.
What you'll build
A web app, just for your team, that shows a live status board of every open work order:
- Which operation each job is at right now (cut, weld, paint, inspect - whatever your routing says).
- How far along it is - percent complete, based on the operations finished versus the ones remaining.
- On-time, at-risk, or late - computed from the due date against the standard time still left to run, and color-coded so a glance tells the story.
- Operator updates - the people doing the work mark operations started and finished, right from a phone or tablet.
- A supervisor approval gate - status changes that touch commitments (marking a job complete, flagging it late) wait for a supervisor's thumbs-up before they show up in reports or exports.
- A status snapshot export - one clean CSV of where everything stands, in the columns your other systems expect.
What's inside the Implementation Plan
A step-by-step runbook you paste into an AI coding agent (Claude Code). It does the building - you steer.
It opens by interviewing you about your shop. Before a single line of code, the plan has the agent ask how your work orders and routings are shaped, what your operations and standard times look like, how progress gets reported today, your real volumes, and your messy exceptions (split jobs, reworks, rush orders). It reflects a short tailored spec back to you, you give a thumbs-up, and only then does it build - so you get a board tuned to your shop, not a generic demo.
Inside you'll find: the discovery interview, a clear definition of done, an accounts checklist, the exact data model, the import flow, the operator update screens, the on-time math, the supervisor approval gate, the audit trail, email alerts, and a verification checklist.
The governance it includes (this is the point)
This isn't a toy. The plan builds in the controls a real shop needs:
- Login so only your team can see or touch the board.
- Row-level security so you only ever see your own organization's work orders.
- A complete audit trail - every status change recorded with who, what, and when.
- A human-in-the-loop approval gate - the tool drafts a completion or a late flag; a supervisor reviews and approves before it commits to reporting or exports.
- Duplicate guards so the same operation update can't be processed twice (the dedupe key is work order plus operation number).
Who it's for
Shop supervisors, production planners, and customer-service reps who field "where's my order?" calls. If you can fill in a spreadsheet, you can build and run this.
You've got this - paste the first prompt and let the agent interview you.