Field proof
Work Orders, Rebuilt for the Floor
WO-003 · Work order lifecycle · Defense Manufacturing (AS9100D)- Situation
- A defense manufacturer — engineering and rapid prototyping, an AS9100D quality environment, defense cybersecurity requirements — running its entire work order process on paper.
- What they tried
- In an AS9100D shop, the quality process lived on clipboards. Now the software enforces it — every checkpoint, every inspection, every job, structurally. A work order was a paper document. It described the operations, traveled the floor with the job, and collected handwritten sign-offs as it went. Quality checkpoints were flagged by hand on the form — which meant enforcing them depended on someone remembering to look. When the job finished, the paper was scanned and filed in SharePoint, and that scan became the permanent quality record. The costs were the quiet kind. No one could see the status of a job without physically finding it. Nothing routed itself — every handoff was a person remembering to tell another person. There was no consolidated view of the floor, no way to catch a missed inspection before it became a finding, and the audit trail was whatever made it onto the paper. In an AS9100D environment, where the process is the product's credibility, the process lived on clipboards. They looked at buying their way out — evaluated every off-the-shelf work order and manufacturing execution option on the market. None fit how their floor actually runs. So the workaround calcified, the way workarounds do.
- What we built
- A complete work order lifecycle system, shaped to their floor's real sequence of work — where the quality process isn't documented next to the software. It is the software. From customer document to work order: a work order starts life as whatever the customer sent — a PDF, a photo, a spreadsheet. Upload it, and AI extracts the details, the operations, and the equipment into a drafted work order that a human reviews and applies. Then the PM builds it out: operations from a managed catalog, each with its stage and its inspection checkpoint, numbered automatically, drawings attached. Approval that moves at the speed of whoever's fastest: submitting a work order notifies the whole approval pool — any qualified approver can take it, and the first to act owns the review. No single-person bottleneck, no order waiting on someone's vacation. The shop floor as a first-class user: every work order carries a QR code on its traveler. An operator scans it and gets a phone-sized screen with big buttons — start, ready for review, accept. Starting the first operation automatically moves the order into In Progress, no clerical step, no one back at a desk updating a status. Photos of the work attach straight from the phone. And the system controls the sequence structurally: a stage of operations opens only when every earlier stage is fully accepted, so work physically can't get ahead of its inspections. Quality the software enforces, not requests: who may sign off an inspection is computed from the job's delivery level and the person's role, and at the levels that demand it, the system enforces two-person integrity — the inspector cannot be the person who did the work. Not as policy. As a rule the server will not let you break. The final inspection on critical work routes to leadership automatically. When something fails, the process tightens instead of scattering: any rejection — a whole order at approval, or a single operation at inspection — automatically logs a non-conformance record and freezes the job for Material Review Board disposition. Leadership picks from the five real MRB outcomes, and the system acts on the choice — a rework disposition automatically appends the rework operation with a forced inspection gate behind it. The failure path, which on paper depended entirely on discipline, is now the most controlled path in the building. A permanent record, kept by the architecture: every change to every work order — every field, every status, every sign-off, who and when — is captured automatically, by construction. Completion is blocked until every operation is accepted, then permanently stamped with the approver's name and title. The quality record isn't a scan of a form anymore. It's the system's memory of everything that happened. And the visibility that never existed: one queue showing each person exactly what's waiting on them, a live board of the whole floor by customer, phase, and operation, where blocked work is dimmed with the reason why, and a dashboard leadership reads in real time instead of walking the floor to compile. All of it running inside the manufacturer's own secure environment, meeting the cybersecurity requirements their defense work demands — their data never leaves their walls. And the process itself — workflow steps, the operation catalog, checkpoint defaults, notification templates — is configuration their admins own, not code they have to pay to change.
- How fast
- First release delivered on the compressed timeline the customer's own statement of work demanded.
- What changed
- Paper is gone from the floor. Every quality rule that used to depend on vigilance — checkpoint sign-offs, inspection authority, two-person integrity, MRB discipline — is enforced by the software itself, every job, structurally. Leadership sees the whole floor in real time. And the audit trail that used to be handwriting on a scanned form is complete, automatic, and permanent.
- What's next
- The work order system was the first module. They're now scoping a full custom ERP on the same foundation — the process that started on paper is becoming the operating system of the company.
What's the workflow nothing fits?
The form your team fights with. The process living in a spreadsheet. The tool you pay for and route around. Tell us about it — that's where we start.
Tell us about your workflowLive in 30 days or it's free. Cancel anytime. Keep everything you own.