A prototype run should answer a defined question; a production run should repeat an approved answer. Use separate quote assumptions, revision states, acceptance rules, and release decisions for the two stages. A sample that looks good is not automatically permission to make 100 more, and production pricing should not be treated as valid while the file, material, finish, or inspection method is still moving.
The clean handoff is simple: state what the prototype must prove, record what passed, identify the exact file and material that passed, then issue a written production release with quantity, acceptance checks, pack-out, and delivery requirements. If repeatability or handling is still uncertain, use a pilot batch between the prototype and the full order.
Fast stage test
- Prototype: the next part is expected to teach you about fit, function, material, geometry, assembly, or appearance.
- Bridge or pilot: the design is mostly settled, but the next run must prove repeatability, inspection, packaging, or scaled handling.
- Production: the next units are expected to match a named revision and an approved result within stated acceptance limits.
Prototype, pilot, and production are different commercial jobs
These stages may use the same supplier and printer fleet, but they buy different outcomes. A prototype buys learning. A pilot buys evidence that the release process works beyond one sample. Production buys repeatable delivered parts against an approved baseline.
| Stage | Primary question | Normal output | Exit condition |
|---|---|---|---|
| Prototype | Does the direction work? | One or a few learning parts, notes, and likely revisions | The proof questions have documented answers |
| Pilot batch | Can the chosen baseline repeat through a short run and handoff? | A limited batch with defined checks and receiving feedback | Repeatability, QC, pack-out, and workflow risks are acceptable |
| Production | Can approved parts be delivered consistently? | Released quantity tied to a fixed revision and scope | The order passes acceptance and becomes a reorder baseline |
A five-piece order can be production if all five are released against a fixed baseline. A 50-piece run can still be a pilot if its purpose is to prove packaging, labor, variation, or receiving. Quantity alone does not define the stage.
Write the proof question before ordering the prototype
"See if it works" is too vague to create a useful handoff. State the uncertainty that the part must resolve. Typical proof questions include whether two holes align to the mating assembly, a clip survives a defined number of uses, a housing clears internal components, a material holds shape near a heat source, or a visible face meets the customer's appearance threshold.
For each question, name the test, reference, and decision owner. A fit check may use the real mating part. A hole may be checked with the actual fastener rather than a blanket decimal tolerance. A cosmetic approval may apply only to named faces under normal viewing conditions. A functional test may need a load, temperature, duration, or cycle count.
The prototype 3D printing service guide helps package that learning stage. The goal is not to make the first sample carry every possible requirement. It is to learn the right things before the batch makes changes expensive.
Quote the prototype and production stages separately
Prototype pricing can include one-off setup, extra communication, unusual orientation tests, multiple variants, or measurement work that will not repeat on every production unit. Production pricing may improve through stable nesting, machine allocation, material purchasing, standardized cleanup, fixtures, gauges, and pack-out. It can also include controls that a single prototype did not need.
Ask the supplier to separate:
- prototype quantity, price, proof scope, and estimated timing;
- production quantity or meaningful quantity breaks;
- which production prices are firm and which depend on sample approval;
- setup, finishing, inspection, assembly, labeling, and packaging scope;
- what starts lead time for each stage; and
- which changes trigger a requote or schedule reset.
A production unit price shown before approval can be a planning number, but it should not masquerade as an unconditional promise. Use the guide to separate prototype and production quote logic when the buyer needs both numbers in the same buying cycle.
Freeze a baseline before releasing production
The supplier should be able to identify exactly what is authorized without reconstructing an email thread. At minimum, freeze the part number, revision, controlling file, units, material and grade, color, process assumptions that affect acceptance, critical features, finish, delivered condition, quantity, packaging, and delivery destination.
If several files control the job, use a short manifest. For example, the STEP file may control nominal geometry, a PDF may control critical dimensions, a photo may mark the cosmetic face, and a spreadsheet may control variants and quantities. Resolve conflicts before release. "Use the latest file" is not revision control.
Do not silently carry a prototype exception into production. If the sample required hand drilling, heat forming, adhesive, extra sanding, insert rework, or a hidden scaling adjustment, decide whether that operation is part of the approved production process. A sample that passed only after unpriced bench work has not proved normal production output.
The quote-prep guide provides a full request packet when the handoff includes several files, variants, and purchasing requirements.
Treat every post-quote change as a release decision
Changes are expected in prototyping. In production they affect price, fit, inspection, scheduling, and responsibility. A new CAD export, material substitution, color change, altered quantity, tighter finish rule, new label, or added assembly step can all change the commercial job even when the part still looks familiar.
Send the new revision as a replacement, not another unlabeled attachment. State what changed, what did not change, whether the previous sample still represents the result, and whether a new sample or pilot is required. Then ask the supplier to confirm price, lead time, manufacturing impact, and the new release baseline.
Use the file-change and requote guide instead of assuming a similar-looking revision is commercially interchangeable.
Approve the sample by results, not by a casual message
"Looks good" can mean the concept is promising, the visible face is acceptable, the fit passed, or the buyer is authorizing the entire batch. Those are different decisions. A useful approval names the part and revision, the sample identifier, what was checked, what passed, any accepted deviation, open items, and whether production is released.
Keep the test proportional to the risk. The sample does not need a laboratory report for every dimension. It does need evidence for the few features that decide whether the delivered part is usable. When possible, record the mating part, gauge, method, environment, or photo view used for approval.
Prototype [part/revision/sample ID] was checked for [fit, function, finish, or material questions] using [reference or method]. It passed [named results]. The following items remain open: [items or none]. This message [does / does not] authorize production. If authorized, release quantity is [quantity] under [quote or PO], with no substitutions or file changes unless approved in writing.
The first-article and sample-approval checklist goes deeper on documenting the decision.
Use a pilot batch when one sample cannot prove the operating risk
A pilot is useful when a single part can prove geometry but not variation across machines, a longer production window, several cavities on the build plate, manual finishing, assembly labor, pack-out, or receiving. It is also useful when the first customer-facing batch must be limited while the process is still being proven.
Define what the pilot must answer. Examples include whether critical dimensions stay inside an acceptance window across 20 parts, whether color and finish variation are acceptable, whether inserts survive installation at batch pace, whether labels remain matched to variants, or whether the shipment reaches receiving without cosmetic damage.
Do not let the pilot become an indefinite stage. Name the quantity, checks, decision owner, allowed corrections, and exit rule. If the pilot passes, promote that exact baseline into production. If it fails, record the cause and decide whether the next step is a corrected pilot, another prototype, or a different process. See when to use a pilot batch for the full branch.
Define acceptance around buyer risk and process reality
Production control should focus on features that decide use, assembly, appearance, count, and traceability. Blanket demands such as "perfect," "zero variation," or "tight tolerance everywhere" do not tell an operator what to measure or protect. They can also add cost without reducing the real failure risk.
State the actual acceptance method: a fastener must pass, a bracket must align to a supplied fixture, an insert must resist a defined torque, a visible face must be free of support contact, or each bag must contain one left and one right part. Separate must-pass features from informational dimensions and cosmetic preferences.
Agree on sampling frequency and records before the run. One check on the first article, first-and-last per build, a periodic fixture test, or 100 percent functional gauging are different scopes. The acceptance criteria and QC guide helps assign the right control without pretending every FDM or resin feature behaves the same way.
Release variants, left-right parts, and sizes explicitly
Approval of one member of a part family does not automatically validate every variant. A longer size may warp differently. A mirrored part may change support contact or seam placement. A different color may use a different material lot or pigment behavior. A revised label can create a pack-out error even when geometry is unchanged.
Use a release table with part number, revision, file, material, color, quantity, and approval status for each variant. State whether the approved sample represents the whole family and why. If only the common interface is covered by the shared approval, identify which variant-specific features still need checks.
For matched sets, define whether quantity means pieces, pairs, or complete kits. A production shop can print the correct total count and still deliver an unusable order if the buyer and supplier used different unit definitions.
Include finishing, packaging, and receiving in the production release
Prototype approval often happens before the buyer has seen a full shipment. Production adds handling risks: parts can be mixed, scuffed, bent, short-counted, mislabeled, or separated from their hardware after they leave the printer.
State whether supports are removed, edges are deburred, holes are drilled or tapped, inserts are installed, parts are washed and cured, cosmetic faces are protected, matched sets are bagged together, and labels include part and revision. Define whether count is by loose piece, kit, bag, or carton.
Also state what receiving will check and how a discrepancy should be isolated. If the buyer needs lot labels, a packing list, inspection records, or a PO number on the carton, include that before the batch starts. The packaging, labeling, and inspection guide covers the handoff beyond the printer.
Set lead time from technical release, not the first email
A supplier cannot schedule a controlled production run while the file, material, quantity, approval, or purchasing authorization is still open. Ask what event starts lead time. For a prototype, that may be acceptance of the quote and receipt of a usable file. For production, it may be written sample approval, deposit or PO, final files, resolved technical questions, and confirmed pack-out.
Separate quote-response time, prototype time, approval time, production time, and transit. Also distinguish a ship date from an in-hand date. If a prototype is due before the production release, ask for both milestones rather than treating one total duration as guaranteed.
The prototype and small-batch lead-time guide explains the schedule gates and when a split shipment may help.
Use a compact production-release packet
A serious print farm should not need a long narrative to know what to make. It does need one unambiguous packet. Include:
- part number, name, revision, and controlling files;
- approved material, grade, color, and allowed substitutions;
- released quantity and variant or kit breakdown;
- sample or pilot reference and what it approved;
- critical fit, function, finish, and inspection checks;
- required cleanup, secondary operations, and assembly;
- packaging, labels, records, and receiving requirements;
- delivery destination, in-hand date, and purchasing reference; and
- change authority and the person allowed to release the run.
Please release [quantity and variants] of [part number/name], revision [revision], using [controlling files] and [approved material/color]. Prototype or pilot [ID] approved [named results]. Critical acceptance checks are [checks], and delivered condition includes [cleanup, assembly, inspection, labels, and packaging]. Parts are required in hand at [destination] by [date]. No file, material, process-affecting, or pack-out substitutions are authorized without written approval from [owner]. Please confirm the production baseline, price, lead-time start, and ship plan before scheduling.
GoodPrints is the educational surface; JC Print Farm is the production operator behind it. Use that route when the release packet still needs an operator review. If the baseline is already clear, send the controlled request through the tracked quote intake.
Common prototype-to-production questions
Does one successful prototype authorize the full batch?
No. It proves only the questions that were actually checked. Production still needs an identifiable revision, quantity, acceptance scope, quote, and written release.
Can production use the same file as the prototype?
Yes. Confirm that the file is unchanged and name it as the production baseline. The commercial scope can still change through quantity, material, inspection, finishing, packaging, or delivery requirements.
When is another prototype better than a pilot?
Use another prototype when geometry, fit, function, or material direction is still changing. Use a pilot when the design is mostly settled and the remaining question concerns repeatability or the production handoff.
Who should approve the move into production?
The person with authority over the result and purchase should be named. Engineering may approve fit, operations may approve use, and purchasing may place the order, but the final release should not depend on the supplier guessing which message controls.
How do reorders stay consistent?
Preserve the approved file, material, process-affecting assumptions, checks, pack-out, and deviation history as a reorder baseline. Use the guide to keeping repeat 3D printing orders consistent once the first run has passed.
Bottom line
Keep learning work and repeat work separate. Define what the prototype must prove, record what passed, use a pilot when one sample cannot prove repeatability, and release production only against a named file, material, quantity, acceptance plan, delivered condition, and purchasing authorization.
That discipline does more than prevent revision mistakes. It gives the buyer a quote they can approve, gives the print farm a job it can schedule, and creates a baseline that both sides can receive, review, and reorder without relying on memory.