Prototype manufacturing is judged twice: once when the sample part arrives, and again when someone asks how it was made. The second question decides whether a prototype can be repeated, quoted for production, or defended when a customer disputes a result. Buyers of prototype and low-volume manufacturing services — a start-up hardware team, an R&D group, an engineer commissioning a fixture or a small production cell — usually focus on drawings and lead times, then discover that the paperwork arriving with the parts is thin. This article sets out the documentation package that should accompany a prototype delivery, and why each item earns its place.
1. A controlled record of the design intent you actually paid for
The package starts with a revision-controlled drawing set and the model files, with revision numbers and dates that match what was manufactured — not what was sent at the start of the job. During prototyping, dimensions change on email. If the delivered parts correspond to revision C while the paperwork says revision A, the whole exercise is untraceable.
Ask for a short change log: what changed, when, who authorised it, and whether the change affects function or only form. That log is the difference between an engineering record and a folder of files.
2. Process parameters, not just process names
"Bonded under vacuum" is not a record. The parameters are: temperature, pressure, vacuum level, dwell or cycle time, alignment method, tooling used, and the sequence in which steps were performed. Prototype work succeeds or fails on these values, and without them a batch that performed well cannot be reproduced, and a batch that failed cannot be diagnosed.
This is where a supplier that builds process equipment rather than only parts has an advantage in documentation discipline. Suppliers listing bonding and lamination machines with explicit fitting-error, working-temperature and working-vacuum figures are working to parameter sheets as a matter of course — see, for example, the vacuum hot-pressing equipment listed with a stated fitting error and vacuum limit. If the parameter sheet exists, ask for it with the delivery; if it does not exist, ask why the process was run without one.
3. Material traceability
For every input material, the package should carry: supplier and grade, batch or lot number, the certificate of analysis or conformity, and where the material was stored and for how long. For films, adhesives and coatings, add shelf life and any pre-conditioning the process required — a laminate made from adhesive stored past its intended window behaves differently from one made to spec.
4. Inspection results with the method stated
A report that says "within tolerance" is worth nothing. A useful inspection record names each measured characteristic, the nominal and tolerance, the measured value, the gauge or instrument, and the operator and date. Where optical or vision systems were used, state what was inspected and what was not.
Ask for the parts to be identified individually — serial, batch or nest number — so a measurement can be tied to a physical part in your hands. Prototype quantities are small enough that full individual reporting is affordable, and it is the single most useful document when a prototype is later scaled into production.
5. Nonconformances and deviations, written up
Prototypes go wrong; that is the point. What matters is whether the deviation is documented. The package should include a deviation note for anything that departed from the plan — a re-run step, a substitute material, a fixture that was modified, an out-of-tolerance characteristic accepted under concession — with the reason and the signature of whoever accepted it. A supplier who sends a clean-looking file with no deviations has usually just not recorded them.
6. Test and validation evidence
If the prototype was tested — functional, environmental, cycle-life, adhesion, leak — record the test method, the equipment, the pass criteria, the result, and which sample was tested. Where testing was not performed, state that explicitly. Silence in a documentation package reads as a pass until someone repeats the test themselves.
Where independent verification is the deliverable, a supplier with a hardware-testing function can supply the evidence as a separate document rather than as a line on an invoice — see the hardware testing service listing.
7. Equipment and tooling records
For a prototype produced on tooling, include the tool identity, its condition and any modification made for this batch, plus which machine and fixture held the part. Where the equipment itself is the deliverable — a production cell, a bonding machine, a cleaning installation — the delivery package shifts to machine documentation: the specification and parameter tables, wiring and utility schedules, the safety protection list, the operating and maintenance manual, the spare-parts list with lead times, and commissioning records.
8. Configuration, software and recipe records
If any part of the process is software-controlled, record the software version, the recipe or program used, and who could change it. A bonded assembly produced under recipe 3 behaves differently from recipe 4, and nobody can reconstruct which was used unless the machine log says so. Include the recipe file or an exported copy in the package.
9. Commercial and qualification records
Close the package with the purchase-order reference, the quantity and serial range delivered, the quotation the work was performed against, and any qualification document required by your industry — first-article style reports, a conformity statement, or a signed process review. These are the items your procurement and quality teams will ask for months later, when nobody remembers the project.
How to get this package without arguing for it
Put the documentation list in the purchase order before the work starts, not after delivery. Nine sections, each with a named deliverable and an acceptance signature, costs nothing to add at quotation stage and removes the awkward conversation later. It also changes the supplier's behaviour: a vendor asked for a parameter sheet and a deviation log runs the job differently from one who is only asked for parts.
Where the prototype is really a development programme rather than a batch of parts, the same logic applies upstream: an engineering service that runs development, testing and prototype builds under one accountable record keeps the documentation continuous instead of stitched together from three vendors. Engineering services of that kind are specified with the record they produce as part of the deliverable, which is what makes the paper trail survive handover into production.
