A prototype should not be sent to production merely because it appears finished. Before making a production decision, the team needs to connect the physical sample with the intended design, communicate relevant information to manufacturing and inspection activities, and identify the criteria against which the sample will be judged.
ASQ says a quality control plan may specify product tolerances, testing parameters, and acceptance criteria. NIST says design and manufacturing information must be communicated to inspection activities, with design intent conveyed to digital manufacturing and inspection activities. These statements provide a practical starting point, not a universal release checklist or a requirement that every project use a quality control plan.
What to check before production
The review should establish what the prototype is expected to demonstrate, how that expectation will be checked, and what outcome counts as acceptable.
| Review point | Question for the team | Useful record |
|---|---|---|
| Product tolerances | Which characteristics have an applicable tolerance, and what does the prototype show against it? | The applicable requirement and observed comparison |
| Testing parameters | Which parameters are to be tested? | The test requirement and result |
| Acceptance criteria | What outcome satisfies the requirement? | The stated criterion and resulting decision |
| Information handoff | Have design intent and relevant manufacturing information been communicated to the activities performing manufacturing and inspection? | The reference information available to those activities |
This table is a working aid rather than a mandatory form. The cited ASQ statement identifies categories that a quality control plan may cover; it does not provide project-specific limits, testing procedures, or acceptance thresholds.
Keep observation separate from acceptance
A visual inspection can reveal obvious differences, but visual agreement alone does not establish conformity to an unstated tolerance. Likewise, a measurement or test result does not explain the decision clearly if the testing parameters or acceptance criteria are missing.
Each reviewed characteristic can therefore be placed into one of three states:
- Supported by the requirements: The observation or result agrees with the applicable reference.
- Contradicted by the requirements: The observation or result differs from that reference.
- Not yet evaluable: The reference, parameter, or acceptance criterion needed for judgment is missing or unclear.
A mismatch does not automatically establish that the design is defective. It may indicate a difference between the design intent, the prototype, the manufacturing information, or the inspection criteria. The discrepancy should be recorded and resolved against the governing project documents rather than silently changing either the sample or the requirement.
Check that the information has reached inspection
Communication is part of the review itself. If manufacturing and inspection activities rely on different descriptions of the intended product, a physical comparison may not resolve the difference.
The team should confirm which design intent and manufacturing information are relevant and whether the inspection activity has access to them. Any missing, ambiguous, or contradictory information remains an unresolved review issue. The cited NIST statement does not prescribe one document-management method, so the appropriate procedure must be established within the project.
What the reader must still confirm
The two cited statements do not establish the complete requirements for a particular production release. The reader must confirm:
- Whether a quality control plan applies to the project and which document governs the prototype.
- Which product tolerances and testing parameters are applicable.
- What acceptance criteria determine the result.
- How discrepancies or exceptions are reviewed and who may authorize them.
- Whether customer, contractual, regulatory, or other project-specific requirements add conditions not covered by the cited guidance.
A general statement that a quality control plan may specify tolerances, tests, and acceptance criteria is not evidence that a particular project’s plan contains them. Likewise, the available statements do not supply numerical limits, required approvals, or a universal production-release procedure.
The defensible conclusion is conditional: when design and manufacturing information have been communicated, the applicable criteria are explicit, and the prototype’s status can be demonstrated against them, the team has a documented basis for a production decision. Missing or contradictory information leaves that decision unresolved.