Prototype observations become useful production notes when the observed condition is separated from its interpretation and linked to a clear design or production action. The note should identify the supporting evidence, the requirement involved, the decision made, and any further verification required. This reflects NIST’s inclusion of feedback from inspection back to design in its digital-thread work, while ASQ’s definition of a quality plan provides a broader documentation model covering standards, practices, resources, specifications, and activity sequence.
From Prototype Observation to Production Note
A practical conversion process starts by recording what was actually observed. Generic descriptions such as “does not fit” or “finish is inconsistent” leave too much uncertainty. The note can be made more useful by adding:
| Field | What to record |
|---|---|
| Observation | What was seen, including the affected part or feature |
| Evidence | The measurement, image, test record, or other available support |
| Requirement | The drawing, specification, or other reference used for comparison |
| Interpretation | Any proposed explanation, clearly distinguished from the observation |
| Action | The design clarification, production change, additional test, or review required |
| Verification | What evidence would confirm that the action has been resolved |
For example, an observation that a joint does not meet the current dimensional requirement should not automatically be written as “redesign the joint.” The first entry identifies the mismatch and its evidence. The design decision remains separate until the relevant requirement and possible causes have been checked.
This separation matters because prototype feedback can otherwise move backward into production without identifying what actually needs to change. NIST describes a feedback cycle that runs from the inspection stage back to design; a production note can preserve that feedback as a documented decision rather than an informal comment.
How to Check the Note
A note is ready to support production when another reader can distinguish the condition, the evidence, the applicable requirement, and the resulting action. Useful checks include:
- Evidence: Does the note say how the observation was identified?
- Traceability: Is the relevant drawing, specification, test, or design revision identifiable?
- Separation of fact and inference: Is the observed condition clearly different from a proposed cause?
- Action: Does the note state what must change, what must be reviewed, or what remains under test?
- Sequence: Is it clear whether the issue is awaiting design feedback, production action, verification, or another stage?
- Consistency: Do the action and acceptance condition match the current controlled information?
ASQ’s quality-plan definition offers a useful scope check: relevant quality standards, practices, resources, specifications, and activity sequence should be identifiable. However, a production note is not automatically a quality plan. ASQ defines a quality plan as a document, or several documents, for a particular product, service, project, or contract.
What Still Requires Confirmation
The cited source statements do not provide a universal production-note template or numerical acceptance limits. Before acting on a prototype observation, the reader must still confirm:
- the governing drawing, specification, and current revision;
- all applicable tolerances and acceptance conditions;
- the intended production material, process, and inspection method;
- any customer, project, or contract-specific documentation requirements;
- whether the proposed design change has been reviewed and verified.
No fee, deadline, regulatory requirement, or guaranteed production result can be inferred from these two definitions. Those matters require separate authoritative evidence.