Ordering a prototype circuit board is a design milestone, not a routine purchasing step. The prototype exists to reveal what the schematic cannot: whether the circuit behaves as expected, whether the layout supports assembly, whether the chosen materials suit the signal environment, and whether the board can be manufactured without avoidable surprises. The quality of the order request often determines how useful the prototype will be. A vague package leads to assumptions, clarification cycles, and boards that answer the wrong questions. A well-prepared package gives the fabrication and assembly team what they need to review the design, flag risks, and build a board that supports meaningful testing.
Define the Design Intent and Test Plan First
Before you send a request for a prototype circuit board, write down why the board is being built. Is it meant to prove circuit topology, validate form and fit, test a firmware bring-up sequence, verify RF or high-speed behavior, check thermal margins, or evaluate an assembly process? Different goals change the priorities. A board intended for firmware development may need accessible test points, clear silkscreen labels, and robust connectors. An RF or high-speed board may need controlled impedance, appropriate low-loss laminate, and careful stackup planning. An HDI design may depend on laser-drilled microvias, via-in-pad, and fine-pitch component support. Define what is fixed and what can change after the first build.
Prepare a short design intent note that includes the block diagram, supply rails, interfaces, critical nets, expected loads, mechanical constraints, and known risk areas. Include board outline, mounting holes, connector heights, keepouts, and any limits imposed by the enclosure. If the design uses controlled impedance, state the target and tolerance clearly; some manufacturers state impedance-control tolerance as ±5%. If the board involves microwave or RF materials, identify the material family rather than simply naming a color or grade. Relevant examples include Isola grades such as I-Speed, ASTRA MT77, I-TERA MT40, and IS680 AG-348; Rogers grades such as RO3203, RO3206, RO3210, RO4003C, and RO4350B; Arlon and Taconic materials; and Panasonic MEGTRON grades for high-speed networking. Explain why the material matters so the review focuses on the right risks.
The test plan is just as important as the design files. List the pass/fail criteria, the instruments you will use, the test points you need, the firmware or configuration version, and the expected signal ranges. Prototype boards are usually produced in small quantities and are expected to support modification and rework, so a clear test plan prevents the first build from becoming a simple “power-on” check. Include any mechanical fit checks and environmental assumptions that affect the design. If the prototype is also a manufacturing trial, note which assembly features need scrutiny, such as fine-pitch placement, connector alignment, or via-in-pad behavior. The goal is to make every requested feature traceable to a test or a design decision.
Gather Manufacturing-Ready Files and Process Requirements
Fabrication files should be complete, consistent, and easy to review. A typical package includes Gerber or equivalent fabrication data, drill files, layer stackup, netlist, fabrication drawing, and a short README that explains the board name, revision, and any unusual requirements. Make sure the fabrication revision matches the schematic and bill of materials. The fabrication drawing should show board outline and dimensions, hole sizes, via types, copper weights, surface finish, solder mask and legend requirements, impedance requirements, and any special processes. Do not rely on a note such as “standard” when the design includes a nonstandard feature. Reviewers need to know whether a requirement is mandatory, preferred, or open to suggestion.
Stackup and process notes deserve particular attention. Simple prototypes may use single-sided or double-sided rigid construction, while more complex designs may use higher layer counts; available constructions can range from 2 to 58 layers. HDI designs may require laser-drilled microvias, blind and buried vias, staggered, stacked, or skipped microvias, and constructions such as 9+N+9 any-layer HDI. Other features may include via-in-pad, epoxy-filled and copper-capped microvias, back drilling with a minimum hole size of 15.7 mils and depth tolerance of ±6 mils, cavity boards, heavy copper up to 30 oz., press-fit holes, countersink holes, castellated holes, and semi-flex construction. If the design uses these capabilities, state them explicitly in the fabrication drawing and discuss them during the quote review. If it does not, say so clearly to avoid unnecessary assumptions.
Fine features should be flagged rather than buried in the data. For example, BGA pitch down to 0.15 mm and minimum trace width and spacing of 0.002 in / 0.002 in are meaningful review points. Surface finish choices may include selective gold, hard gold, gold fingers, and ENEPIG. For RF and high-speed boards, connect the material choice to the impedance and loss requirements instead of treating the laminate as a generic item. When assembly is part of the order, keep the fabrication and assembly packages aligned so the review team can see how the board, components, and process interact. A consolidated requirements summary is not a substitute for the files, but it helps reviewers confirm that every special process has been captured.
Prepare Assembly Data, Quantity, and Inspection Expectations
If the prototype requires assembly, prepare a bill of materials with manufacturer part numbers, reference designators, quantities, do-not-populate notes, and approved alternates. Supply the pick-and-place data, assembly drawings, polarity information, fiducials, and test-point details. Clarify component sourcing responsibilities and identify any parts that must not be substituted. For a first prototype, order enough units to support testing, rework, and a reasonable number of assembly trials. Quantity affects setup and review effort, so describe the purpose of the build rather than treating the order as a one-off purchase. A prototype run may include boards for functional testing, fit checks, and destructive evaluation, so plan the quantity around the questions you need to answer.
Define inspection and acceptance expectations before the order is placed. State which dimensions, holes, connectors, and critical nets need attention. If impedance control is required, provide the target and tolerance and identify the relevant layers or nets; a manufacturer may state impedance-control tolerance as ±5%. If the board uses fine-pitch BGA devices, via-in-pad, back drilling, or heavy copper, call out the features that require closer process control. Ask what inspection and test documentation is available for the requested build, and make sure the answer matches the needs of your test plan. Do not wait until boards arrive to discover that a critical feature was not included in the review.
Communication is part of the preparation. Keep one revision-controlled package with a README that lists the contact person, board name, revision, special notes, and open questions. If you use an online quote and order path, including an online price calculator, have the board dimensions, layer count, material, surface finish, quantity, and assembly needs ready. The request should reflect whether the job is a prototype, quick-turn board, HDI PCB, RF PCB, rigid-flex PCB, flex PCB, or PCB assembly project. A final check is simple: can a reviewer identify every nonstandard requirement from the files alone? If not, revise the package before ordering.
Toronto indie-game developer now based in Split, Croatia. Ethan reviews roguelikes, decodes quantum computing news, and shares minimalist travel hacks. He skateboards along Roman ruins and livestreams pixel-art tutorials from seaside cafés.