Lesson objective

Run an assisted plant task through seven fixed steps, from naming the output and its signer to recording the approval, so every draft is built from released documents at a stated revision and checked before anyone acts on it.

Plain-language explanation

Why this matters now

Triage decides whether a task may use AI and on what terms. This lesson is what happens next: the same seven steps, in the same order, every time, so two people doing the same task produce work a signer can check the same way.

The steps are fixed because manufacturing errors are quiet on paper. A diameter of 12.70 mm reads as smoothly as 12.07 mm. Revision C looks just like revision D. A sentence that turns "the lot is on hold pending review" into "the lot has been reviewed and released" reads as a small edit and is really a release nobody authorised.

A question to sit with

Two process engineers each produce a setup sheet with an assistant. One supplies the print at revision D, the router and the material specification, and spends fifteen minutes checking every value. The other asks the assistant to "write a setup sheet for the 4471 bracket" and edits the wording. Three weeks later a lot is scrapped for a wrong datum. Which engineer can show what the sheet was built from?

What goes wrong

Starting with the question instead of the documents. "Write a setup sheet for the 4471 bracket" asks the model to supply dimensions, tolerances and a material it was never given. It will supply them.

Using the wrong revision. The print in the engineer's downloads folder is revision C; document control released revision D last week.

Letting the draft become the source. After two rounds of edits nobody has looked back at the print.

Checking the easy items only. The part number and the customer name get checked; the torque value that appeared from nowhere does not.

Accepting instead of challenging. Checking asks whether the draft matches the documents. Challenging asks what it left out, what it smoothed over and what an operator would read into it.

Drifting into a decision. A draft that says "parts may be released" or "acceptable as is" has made a disposition on paper, whether or not anyone meant it to.

Skipping the screen because the task is familiar. The export and trade-secret check happens before the prompt every time, not only for new customers.

The practical answer

Seven steps. They are this programme's recommendation.

Step What you do Must be true before moving on
1. Name the output and signer One sentence: what will exist, and who signs or approves it A named person, not a job title
2. Assemble the released set Print, router, specification, customer requirement, each at its stated revision Every revision confirmed against document control
3. Screen before the prompt Data class, export status and trade-secret handling for every file Every file cleared for this system; nothing undetermined
4. Write the instruction and generate Task, audience, format, constraints, in the approved system "Use only the supplied documents" is in it
5. Check and challenge Every value against its source, then what is missing or implied Every checkable item checked, not sampled
6. Signer's decision The signer approves, returns or rejects, and names who acts No disposition, release or conformance statement was drafted by AI
7. Record Log the task, documents, screen, checks, corrections and approval Written now, not reconstructed

Step 2: the released set is the point. Whatever the model did not receive, it may invent. Whatever it did receive, you can check against. Identify each item precisely: "Print 4471-B, revision D, released 3 September; router R-4471 revision 6; material specification MS-12 revision B; customer quality clauses dated 14 July." Level 2 never asks a model to recall a standard, a print or a customer requirement from memory.

Step 3: the screen comes before the prompt, not after. Three checks for each file.

Check Question If the answer is unclear
Data class Is this system approved for this class of material? Do not upload; ask the owner of the approved-tools list
Export status Has the person the company named for export questions decided what this file is? Undetermined stops the work
Trade secret Is this our process knowledge or a customer's confidential information, and does the approved system's handling fit the controls we apply to it? Use a reduced extract or no AI

Law / rule (United States, federal; 15 CFR 734.13): an export includes a transmission out of the United States and the release of technology or source code to a foreign person in the United States. Whether a particular file needs a licence depends on its classification and destination, which only the company's export authority decides. Law / rule (United States, federal; 18 U.S.C. 1839): trade-secret protection requires that the owner "has taken reasonable measures to keep such information secret"; step 3 is one of those measures, and the record of it is how the plant later shows what it did.

Step 4: four constraints travel with every instruction.

  1. Use only the supplied documents; where they are silent, write "not stated" rather than filling the gap.
  2. Tie every value to a document, revision and location.
  3. Draft no disposition, release, signature block or conformance statement; if the material raises one, write "decision for the quality authority."
  4. Convert no unit and round no value unless the instruction says how; flag every conversion for a person to recompute.

Module 02 builds these into a full prompt architecture.

Step 5: check, then challenge. Checking is a list.

Item Checked against
Dimensions, tolerances, datums The print at the stated revision, read by a person
Material, heat treatment, finish The material specification and the print notes
Operation sequence, work centres The router at its revision
Torque, speed, feed or other process values The released process document, never the draft
Customer-specific clauses The customer's document at its date
Unit conversions and arithmetic Recomputed by a person

An AI output is never proof. A dimension, a part number, a revision or a standard reference produced by a model is checked against its source before anyone relies on it.

Challenge is three questions: what do the documents say that the draft does not, what does the draft say that the documents do not, and what would an operator or a customer take as an instruction or a promise?

Step 6: the signer decides. The signer approves, returns with corrections, or rejects, and names who issues the document and at which version. Where the output is a controlled document, it goes through document control like any other change.

Remember this

  • Supply the released documents at stated revisions; never ask a model to recall a print, a specification or a customer requirement.
  • Screen every file for data class, export status and trade-secret handling before the prompt; undetermined stops the work.
  • Four constraints: supplied documents only, tie each value to a source, no disposition or release language, no unflagged conversion.
  • Check every item, then challenge for what is missing or implied.
  • The signer decides and names who issues it; record it now.

Manufacturing example

Hollow Creek Stamping is a fictional metal stamping plant. The process engineer, Lorenzo Batiste, is asked for a first-draft setup sheet for a fictional bracket, part 7730, for a new press line. Step 1: the output is a draft setup sheet; the signer is the engineering manager, Hana Okafor, and it will go through document control. Step 2: he pulls print 7730 from document control and finds revision E, released on 2 September; the copy on his desktop was revision D, so he discards it. He adds router R-7730 revision 3 and material specification MS-40 revision A. Step 3: the print carries no export notice and the plant's export contact has already recorded it as not controlled; the die clearance table is plant process knowledge, and the approved system is cleared for that class, so he supplies only the rows for this part. Step 4: his instruction carries all four constraints. Step 5: checking finds three problems. The draft gives the flange height as 18.5 mm; revision E says 15.8 mm. It lists a lubricant the specification never names. It ends "parts produced to this sheet are acceptable for shipment." Challenge finds that the draft dropped the print note requiring a burr-side direction. Lorenzo corrects the height, removes the lubricant and the shipment sentence, and restores the burr note. Step 6: Hana returns it once for a missing operation number, then approves and assigns document control to issue it. Step 7: he records the documents and revisions, the screen, four corrections and the approval. Checking took 18 of 30 minutes.

Responsible-use warning

Do not let the draft replace the released documents. After the first round of edits it is easy to work only from the text on screen, and from then on nothing is being checked. Checking means returning to the print, the router and the specification at their released revisions for every value. A fluent sentence that says parts "are acceptable" or "may be released" is a disposition nobody made, and a value that appeared from nowhere is how a wrong number reaches a machine under the plant's name.

Human-review requirement

The named signer decides before the output is used: the engineering manager or the engineer of record for setup sheets and instructions, the account owner for customer messages, and the designated quality authority for anything touching conformance. The signer confirms every document was at its released revision, the export and trade-secret screen was completed before the prompt, the checking list covered every value rather than a sample, the challenge questions were asked, and no disposition, release or conformance language survived. The signer names who issues the output and confirms the record entry exists.

Practical exercise

Use a fictional plant, part and customer only.

  1. Choose one recurring written task from your role and describe it in one sentence.
  2. Write step 1: the output and its named signer.
  3. List the step 2 released documents, each with a fictional revision and release date, and note how you confirmed each is current.
  4. Complete the step 3 screen for each document: data class, export status and trade-secret handling. Mark any item you would have to escalate.
  5. Write the step 4 instruction with all four constraints in your own words.
  6. Write a fictional draft yourself containing one transposed dimension, one value the documents never gave, one unit conversion and one sentence that sounds like a release.
  7. Build the step 5 checking list: every checkable item and its source.
  8. Recompute the unit conversion by hand and record the arithmetic.
  9. Write the three challenge questions and answer them for your draft.
  10. Write the signer's decision note, including who issues the document and at which version.
  11. Write the step 7 record entry.
  12. Swap drafts with a colleague, repeat steps 7 to 11 on theirs, and list what each of you caught that the other did not. Record everything in your workbook.

Knowledge check

  1. Why does step 3 of the workflow come before the prompt rather than after the draft?

    Answer guidance: Once a file is inside a tool, any export release or loss of control has already happened. The data class, export status and trade-secret handling must be settled before any file is supplied.

  2. Name the four constraints that travel with every instruction in this workflow.

    Answer guidance: Use only the supplied documents and write "not stated" where they are silent; tie every value to a document and revision; draft no disposition, release, signature or conformance statement; flag every conversion or rounding for a person to recompute.

  3. How does challenging a draft differ from checking it?

    Answer guidance: Checking compares each value with its source. Challenging asks what the documents say that the draft omits, what the draft adds, and what an operator or customer would read as an instruction or promise.

  4. What does NIST AI 600-1 say about the logical steps a model shows?

    Answer guidance: That models sometimes provide logical steps for how they reached an answer even when the answer itself is incorrect, so shown working is not evidence the output is right.

Sources and further reading