A prototype should be planned around the intended production method, with its purpose, evaluation method, and inspection records defined in advance. A one-off sample is more informative when it tests the same assumptions expected to matter in production rather than merely demonstrating that one version can be made.
Start with the production intent
The prototype brief should identify what the intended production method must demonstrate. A useful planning record can include:
| Planning field | Central question |
|---|---|
| Production intent | Which production method is the prototype intended to represent? |
| Configuration | Which design revision, material condition, and geometry are being assessed? |
| Purpose | Is the prototype checking form, function, process feasibility, or another defined requirement? |
| Evaluation | Which observations or measurements will support the intended conclusion? |
| Assumptions | Which conditions are confirmed, and which remain unverified? |
| Inspection | Which characteristics will be checked, and against which stated criteria? |
Confirmed requirements and assumptions should remain distinguishable. Otherwise, a successful prototype may be treated as evidence for a production condition that was never actually tested.
Match the evaluation to the question
ASQ includes prototyping, lab testing, and validation testing among methods for evaluating supplier samples. The appropriate choice depends on the question being asked; the methods should not be treated as interchangeable.
- Prototyping can reveal whether a design can be formed, assembled, or handled while exposing practical process issues.
- Lab testing can examine properties under defined testing conditions.
- Validation testing can assess whether a sample performs as required under conditions representing its intended use.
The selected method should therefore correspond to the claim the prototype is expected to support. A planned demonstration of one condition does not automatically establish performance under another.
Connect design, production, and inspection
NIST describes a manufacturing digital thread as connected data that enables model-based definition, manufacturing, and inspection to work together. Applied to prototype planning, this means preserving the relationship between the design used, the production assumptions tested, and the inspection evidence produced.
The project record should make clear:
- which design revision was used;
- which production conditions were represented;
- what changes were made during fabrication or evaluation;
- which characteristics were inspected;
- how the results relate to the intended production method; and
- which questions remained unresolved.
If the design, material condition, production method, or inspection requirement changes, the downstream records should be reviewed rather than left connected to an earlier assumption.
What still needs project-specific confirmation
Nothing in the cited statements establishes a universal set of mandatory tests, acceptance thresholds, certification requirements, regulatory approvals, fees, or delivery schedules. Those points must be confirmed for the specific project.
Before treating a prototype as production evidence, readers should check the controlling design and production documents, applicable contractual requirements, relevant test criteria, and any regulatory or certification documents that genuinely apply to the product and intended market. The authority responsible for accepting deviations should also be identified.
Where a requirement cannot be verified, it should remain an open question. Recording that uncertainty is more useful than presenting a prototype result as proof of production readiness.