Work Order Generator from Demand

The problem this kills

Right now, turning demand into work orders is a copy-paste marathon. A planner reads a demand list, opens the right BOM, hand-keys the materials, looks up the routing, eyeballs the lot size, back-counts the due date from the need-by, and pastes it all into the ERP - line by line, job by job. It is slow, it is mind-numbing, and it is exactly the kind of work where a missed line or a fat-fingered quantity becomes a shortage on the floor two weeks later.

The errors are quiet until they are loud. A BOM that was never attached. A quantity that ignored the minimum lot size. A due date that left no time for the longest operation. A demand line that got entered twice because two people imported the same sheet. None of these show up until material is short or a job is late.

This tool removes the keying and the guesswork. You bring the demand, the BOMs, and the routings. The tool matches each demand line to its BOM and routing, rounds the quantity to your lot rules, back-schedules the due date, flags anything missing a BOM or routing, and drafts the whole batch for a human to check.

What you'll build

A private web app, just for your team, that:

• Imports a demand list (item, quantity, need-by date) from a CSV or Google Sheet.
• Matches every line to the right BOM and routing template.
• Rounds quantities to your minimum and multiple lot sizes.
• Back-schedules the due date from the need-by using routing lead times.
• Flags any line missing a BOM or routing so nothing silent slips through.
• Shows the planner the full batch of draft work orders to review and edit.
• Holds everything behind a hard approval gate - nothing is "released" until a person says go.
• Exports WO and WO-line CSVs in the exact column layout your ERP imports.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent (Claude Code). It builds the whole tool with you, step by step, and every step ends with a ready-to-copy prompt.

The best part: the plan opens by interviewing you about your business. Before it writes a single line of code, it asks how your demand arrives, how your BOMs and routings are named, what your lot-size and scheduling rules really are, and where the messy exceptions live. It reads back a short tailored spec, you give a thumbs-up, and only then does it build - so you get a tool shaped to your shop, not a generic template you have to fight.

Inside you'll find: the discovery interview, a tailored data model, the import + matching engine, the lot-size and back-scheduling logic, the planner review screen, the approval gate, the ERP-ready CSV export, and a full "how to know it works" checklist.

The governance it includes (this is the point)

This is not a toy. The plan builds in the controls a real production system needs:

• Login so only your team can open the tool.
• Row-level security so each organization only ever sees its own demand, BOMs, and work orders.
• A complete audit trail - who imported, who edited, who approved, and exactly when.
• A human-in-the-loop approval gate - the tool drafts, a planner reviews and approves, and only an approved batch can be exported for release. Nothing reaches your system of record without a person.
• Duplicate guards - the dedupe key is demand source ID + item, so re-importing the same sheet can never double-create work orders.

Who it's for

Production planners and schedulers who release jobs. If you are the person who turns "we need this many by this date" into actual work orders, this is built for you. You do not need to be a developer - if you can fill in an interview and copy-paste a prompt, you can build this.

You've got this - paste the first prompt and let the agent interview you.