Think of a plant where every changeover has a written procedure, a nonconformity record exists the afternoon a problem is found, and everyone reviewing an engineering change knows which assemblies, stock and orders it reaches before they sit down. The documents behind that plant are familiar: standard operating procedures, the exceptions they leave out, nonconformity records and engineering change records.
AI workflows draft each one from what your people know and the records you keep. Approval stays where your document control procedure puts it. The procedure owner signs the SOP, the quality owner decides every call on a nonconformity, and engineering, sourcing and operations decide what a change means for their part of the business. AI prepares; it never approves, releases or closes a record.
What you bring, what comes back and who approves.
| Document | What you bring | What comes back | Who approves |
|---|---|---|---|
| SOP | An operator’s walkthrough of one real case, and anything already written. | A draft procedure in ten fixed sections, with open questions. | The procedure owner. |
| SOP exceptions | The procedure, three to five recent cases and thirty minutes with the operator. | An exception register: missing decisions, stop conditions and whom to ask, step by step. | The procedure owner. |
| Nonconformity record | Observation notes, the requirement with its revision, the work register and the evidence list. | A draft record with affected lots counted, containment options and the decisions as questions. | The quality owner. |
| Engineering change | The change request and exports of the bill of materials, drawing index, stock and open orders. | An index of the assemblies, revisions, stock and orders it reaches, with questions for each owner. | Engineering for the design; sourcing and operations for orders and stock. |
| Quality review brief | Measures, complaints and defects, audit results, the action register and owners’ notes. | One brief ending in the decisions still open. | Senior leaders. |
| Batch trace | The batch record, movements, repacking records and dispatch lines. | A map from the batch to every recorded shipment, with each gap as a question. | The quality lead confirms the scope. |
An SOP starts from a walkthrough of the work.
A supervisor records the operator’s walkthrough of one real case, adds any old procedure or checklist, and names the procedure, its owner and any limits already set.
The Write an SOP from how the work is done workflow prepares a draft in ten fixed sections, including steps, exceptions, stop conditions and records. Every step names one role and its sign of done, and every gap becomes a question instead of a guess. The procedure owner settles the questions and approves the procedure before anyone relies on it. An SOP written this way is also the source a work instruction for the station is drawn from.
The exceptions are where an SOP earns its place on the floor.
A procedure that covers only the trouble-free shift fails a new operator on the first awkward one. Your most experienced people already know what to do, and Your SOP describes the happy path. Where are the exceptions? sets out how to ask them.
The SOP exception capture workflow turns the procedure, a few recent cases and thirty minutes with the operator into an exception register, with the case behind every rule. Where two colleagues handle a case differently, it leaves the question open for the procedure owner, who settles it and approves the register.
A nonconformity record is drafted while the notes are fresh.
Something looks wrong at inspection. The supervisor supplies the notes in the observer’s own words, the requirement quoted with its revision, the work register and the evidence list.
The nonconformity record draft workflow keeps what was observed apart from what is suspected, counts the lots that may be affected, flags anything already shipped, lists your containment options and ends with the quality owner’s decisions as questions: whether this is a nonconformity, how serious it is on your scale, what to contain and who outside the company needs to know. The quality owner decides each one and assigns the record number. The workflow classifies nothing and accepts or rejects no work.
An engineering change shows where it lands before the review starts.
When a change request enters review, the document controller supplies it with that day’s exports of the bill of materials, drawing index, stock list and open purchase orders.
The engineering change affected records index workflow lists every assembly that uses each changed part, the revision it points to, the stock held at each revision and the orders still open, quoting the export values behind every line. Anything the records cannot answer, such as two assemblies pointing to different revisions, becomes a question for a named owner. Engineering decides the design change; sourcing and operations decide their orders and stock. The index releases no revision and changes no record.
Two more documents follow the same pattern.
Before each periodic quality review, the quality management review pack gives the quality lead one brief for senior leaders, ending in the decisions still open; it states no conformity with any standard. When a concern points at one production batch, the batch distribution trace maps it to every recorded shipment and turns each gap into a question. The quality lead confirms the scope, and operations verifies the matches before anyone acts.
Here is one walkthrough becoming a draft SOP.
Illustrative example with invented data. Kestrel Lane Fabrication, an invented 70-person plant that makes powder-coated steel enclosures for electrical equipment.
Only two of Kestrel Lane’s operators change powder colour the same way every time. The second-shift supervisor records one of them changing from grey to black: stop the conveyor, purge the guns, blow down the booth from the top, swap the hopper, spray three test panels, check coating thickness on the first and note the change on the line sheet. The operator adds that grey specks on a test panel mean a second blow-down.
In the draft, each step names its role and its sign of done, such as “test panel shows no specks of the previous colour”. The specks become a written exception, and the line sheet is listed under records. Two questions come back, because the walkthrough did not answer them.
- What coating thickness passes, and who decides when a panel falls outside it?The operator checks thickness but named no range, and the workflow never guesses a limit.
- Who may restart the line when the shift lead is off the floor?The shift lead was there during the walkthrough, so it never came up.
The production manager, who owns the procedure, answers both. The quality lead reviews the draft as the document control procedure requires, the production manager signs it, and the SOP goes into the plant’s quality system.
Your people keep control of every document.
Each workflow runs in the AI your plant already uses, whether that is ChatGPT, Claude, Copilot or Gemini, from files and exports your team already has. What changes is the starting point: every owner opens a complete draft with its gaps already named. That is how you 10X the ROI of your existing AI on the documents that keep a plant running.
Every workflow template is free to read with a free account, and AI workflows for manufacturing gathers every manufacturing example in one place.
Start with the procedure that lives in one person’s head.