Lesson objective

Record each AI-assisted plant task as it happens, with the triage route, the export and data screen, the documents and revisions, the checks, corrections and the signer's decision, so the plant can later show what was done rather than reconstruct it.

Plain-language explanation

Why this matters now

Every lesson in this module has ended with "record it." This lesson is about the record itself: what goes in it, when it is written, and why a record written at the time is worth far more than one pieced together after a customer complaint or an audit question.

Plant paperwork raises questions long after it is issued. A customer asks why a setup sheet cited revision D when revision E had been released. An auditor asks who approved a work instruction and what it was checked against. The plant manager wants to know whether the new assistant is saving engineering time or creating rework. The task AI use record is how the plant answers from evidence rather than memory.

This lesson is the daily habit. Module 14 returns to the record alongside incidents and reporting duties.

A question to sit with

Eight months after a job, a customer's supplier quality engineer asks which of your inspection instructions were drafted with AI, which print revision each was checked against, and who approved them. How much of your answer would come from a record, and how much from memory?

What goes wrong

Writing the record at month-end. By then the details are gone. The entry says "setup sheets, checked," not which part, which revision, what was corrected and who approved.

Recording that AI was used, and nothing else. "Used assistant for work instruction" shows nothing about documents, screen, checks or approval.

Leaving out the revision. On a part whose print changed during the month, a check against revision D says nothing about revision E.

Leaving out the screen. If the record does not show that export status and data class were settled before the prompt, nobody can later show they were.

Leaving out the corrections. What the check caught is the most useful thing a record can show. Without it nobody can tell whether the tool, the prompt or the checks are working.

Copying sensitive material into the record. The record is itself a document. It needs a reference to find the work, not the dimensions from a customer print, a process recipe or an employee's personal details.

Treating the record as blame. If people fear that a recorded correction counts against them, they stop recording corrections.

The practical answer

Write the triage line before you start and the rest as you finish.

Field What to write Example (fictional)
Date and preparer When, and who did the work 9 September, L. Batiste
Task and reference Work order, part or document number and one line Part 7730; draft setup sheet
Triage Consequence, data class, export exposure, verifiability, signer, route Floor; process data, approved; recorded not controlled; fully verifiable; H. Okafor; Route B
Screen Who settled export status and on what record; trade-secret handling Export record EC-118 by R. Salazar; die table rows for this part only
System and prompt Which approved tool, which library prompt and version Plant assistant; setup-sheet prompt v2.1
Documents supplied Each with revision and release date Print 7730 rev E (2 Sep); router R-7730 rev 3; MS-40 rev A
Checks What was checked against what 22 values against the three documents
Corrections What the check caught Flange 18.5 to 15.8 mm; lubricant removed; shipment sentence removed; burr note restored
Referred decisions What went to an authority, and to whom None this task
Signer's decision and issue Who decided what, and who issues it H. Okafor approved; document control to issue
Location Where the approved output is held Document control, DC-7730-SS

Why "while the work happens". Two reasons. Accuracy: details written at the time are specific, and in a plant specificity means revisions, values and document numbers. Design: automation bias grows when nobody feels answerable for the check.

The screen and referred-decisions fields matter most in this trade. The screen field shows that export status and data class were settled before any file was supplied, by whom, and on what record. That is evidence of a control the plant actually applied.

The referred-decisions field shows every time a draft touched a decision and was sent to the right authority: a disposition question to the quality authority, a restart question to maintenance, a classification question to the export contact. A month of drafts that strayed with no referrals recorded is a warning.

What the record lets a plant see. After a month, the corrections column answers questions nobody can answer from memory:

  • Which task produces the most corrections, and of what kind?
  • Does one library prompt keep inventing values or dropping print notes? Module 03 covers what to do about that.
  • How often did a draft rely on a superseded revision?
  • How often did a draft stray into release or disposition language, and was it caught?
  • How long does checking take compared with doing the task by hand?

Best practice: the NIST AI RMF 1.0 (January 2023; voluntary, and being revised) says that after instituting its GOVERN outcomes, most users would start with the MAP function and continue to MEASURE or MANAGE, iteratively. For a plant, a use record with a corrections column is a plain form of measuring. Nothing in the framework requires a manufacturer to adopt it.

Fair to the preparer. A caught error is the workflow working. The quality manager or engineering lead reviews the corrections column for patterns in the tool and the prompt, not for individual fault.

Not a substitute. The task AI use record is a plant practice. It does not replace any controlled record your quality system, your customer or a regulator requires.

Remember this

  • Write the triage line before the task and the rest as you finish it, never at month-end.
  • Record the revision of every document; a check against a superseded revision is not a check.
  • The screen field shows who settled export status and data class before the prompt.
  • The corrections and referred-decisions fields are the most valuable parts of the record.
  • Record references, not customer dimensions, recipes or personal details, and never let this record replace a required one.

Manufacturing example

Ostara Medical Devices is a fictional contract manufacturer of device components. On a Thursday the quality technician, Priyanka Holm, uses the approved assistant three times. At 8:05 she writes the triage line for the first task: a draft inspection instruction for a fictional housing, part OM-2208, a controlled document, company data, export status recorded as not controlled on record EC-044, fully verifiable against drawing OM-2208 revision F and inspection plan IP-2208 revision 4, signer the quality engineer, Callum Nwosu, Route B. The draft gives a wall thickness tolerance as plus or minus 0.05 mm; revision F says plus or minus 0.03 mm. Priyanka corrects it and records the correction. The draft also ends "parts meeting these checks are released," which nobody authorised; she removes it and records a referral: release stays with the quality authority. Callum approves at 9:10 and document control issues it. The second task, a summary of a customer's quality agreement for the receiving team, gets its own line: agreement dated 12 May, 9 items checked, one correction where the draft invented a retention period. The third, a supplier email with an attached model whose export status nobody has recorded, is logged in one line: Route C, sent to the export contact, no AI draft. At month-end Callum reviews the column: 3 of 8 inspection instructions added release wording, all from prompt v1.3. He asks the prompt owner to retest it, and notes that none of the three release sentences reached an issued document.

Responsible-use warning

Do not reconstruct the record afterwards, and do not leave out the revision or the screen. A month-end entry loses the specific correction, the document revision, the export decision and the signer's approval, which are what an audit question or a customer complaint turns on. Do not strip corrections or referrals out to make the record look clean: an empty column hides a prompt that keeps adding release wording. Do not copy customer dimensions or recipes into it, and never treat it as a substitute for a record the quality system or a customer requires.

Human-review requirement

The quality manager or engineering lead reviews the task AI use record on a schedule the plant sets and records, looking for patterns in corrections and referrals by task and by library prompt rather than individual fault. The plant manager decides where records are kept, who may read them and how long they are held. The person the plant named for export questions reviews any entry where the screen field is blank or says undetermined. Each reviewer confirms entries were written at the time, every task names a signer and dated, revised documents, and caught errors lead to action on the prompt or workflow.

Practical exercise

Use a fictional plant, parts and customers only.

  1. Copy the eleven record fields from this lesson into your workbook.
  2. Invent three AI-assisted tasks for one fictional day: one Route A, one Route B and one Route C or D.
  3. Write the triage line for each before describing the work.
  4. Complete the screen field for each, naming who settled export status and on what fictional record.
  5. For the Route A and B tasks, list the documents supplied, each with a fictional revision and release date, and the checks run.
  6. Invent at least one correction for each, including one wrong tolerance and one sentence that sounds like a release.
  7. Complete the referred-decisions field, naming the authority each item went to.
  8. For the Route C or D task, write the one-line entry showing where it went.
  9. Review your entries and delete any customer dimension, recipe or personal detail, noting why.
  10. Invent a month of entries showing one prompt that keeps producing the same error, and write the note to its owner.
  11. Invent a print revision released midweek and write how you would mark an entry checked against the superseded revision.
  12. Ask a colleague to read your entries cold and say which one they could not use to find the work again, then fix it and note what you changed.

Knowledge check

  1. Why must the record give the revision of every document supplied?

    Answer guidance: Prints, routers and specifications are revised during a job. A check against a superseded revision says nothing about the current released one.

  2. What does the screen field show, and why does it matter for trade secrets?

    Answer guidance: It shows who settled export status and data class before the prompt, and on what record. Trade-secret protection turns on reasonable measures actually applied, and the dated entry shows what was done.

  3. Does the task AI use record replace a controlled record the quality system requires?

    Answer guidance: No. It is a plant practice recommended by this programme and never stands in for a record the quality system, a customer or a regulator requires.

  4. Why should the corrections column not be used for discipline?

    Answer guidance: A caught error is the workflow working. If people fear recording errors they stop, and the plant loses its evidence of how the tool and prompts perform.

Sources and further reading