Building a BOM for SMT Prototype Assembly

On an SMT prototype build, the BOM is not a purchasing document that sits beside the design. It is the data set the placement machine is programmed from, the list incoming inspection checks against, and the file that decides whether the build can start on the planned date. A BOM for SMT prototype assembly that is clear, complete and unambiguous saves more time than any other document the designer produces.

What the BOM Controls on the Line

The assembly house uses the BOM together with the placement file to prepare the line. The BOM identifies what each reference designator is, which package it uses and which manufacturer part number to buy; the placement file says where it goes and in what rotation. If the reference designators in the two files do not match exactly, the machine program cannot be generated and the build stops before it starts.

For prototypes the stakes are higher than in mass production, because there is no time to rework a wrong reel. A single incorrect part number that has been purchased and loaded costs days, while the same mistake caught in the design phase costs a few minutes. This is why the BOM deserves the same review discipline as the schematic, and why it belongs inside the PCBA development process rather than beside it.

Checking Part Availability First

Before the BOM is issued, every line should be checked for part availability at the quantities required. Early checking matters most for components with long lead times: connectors, crystals, power inductors and any device on a tight allocation. If a part cannot be sourced within the build window, the design still has time to change, provided the footprint is compatible with an alternative.

A second check is lifecycle status. Parts marked as not recommended for new designs, or with a last-time-buy date, should be avoided at the prototype stage unless the design is already committed. Substituting a part later may require a different footprint, which turns a component change into a board revision.

Availability and approval are different questions, and the second one governs whether the purchasing team is allowed to buy the part at all.

Approved Vendor List and Component Substitution

The approved vendor list defines which manufacturers and suppliers may be used for a given line. Some parts must be sourced exactly as specified, because a substitute would change a critical parameter; others can be substituted freely as long as the electrical and mechanical characteristics match. Marking that distinction in the BOM is the single most useful piece of information the designer can provide.

Where component substitution is permitted, state the parameters that must be preserved: tolerance, temperature coefficient, voltage rating, package size and dielectric type. Where it is not permitted, say so explicitly. Leaving the decision to the buyer results in either an unnecessary delay or an unapproved substitution that changes board behaviour in a way that nobody tested.

Reference Designator Mapping and Placement Data

Reference designators are the link between documentation and hardware. They should follow a consistent scheme across the schematic, the BOM, the placement file and the assembly drawing, with no duplicates and no gaps. Duplicated designators are the classic cause of a part being soldered in the wrong place, because two lines in the machine program point at the same location.

Position data must be exported with the same origin and rotation convention the assembly house expects. Rotations are a common source of confusion: a part defined as zero degrees in one tool may be defined as 90 degrees in another. Supplying the placement file together with a clear mechanical outline and fiducial positions lets the process engineer verify the mapping before the first board is built.

Single-Level or Multi-Level Structure

A single-level BOM lists every part on one flat sheet and is the right choice for most prototype builds, especially when the assembler is making the board from scratch. A multi-level BOM groups parts into sub-assemblies and is useful when the product is built in stages, or when the assembly house only needs part of the structure and the sub-assemblies arrive pre-built.

Whichever structure is used, the level of detail should be consistent. Mixing a flat list with references to sub-assemblies that are not supplied creates ambiguity about what is included in the quote. For prototypes the simpler structure is almost always better, because it reduces the chance that a part is missed.

A BOM is a living document, and the way changes are recorded determines whether the build can be repeated and audited.

Documenting Changes and Revision Control

Prototype BOMs change often, and each change should be recorded with a revision, a date and a reason. Keeping a change log attached to the BOM and the schematic ensures that everyone is working from the same version. The practical rule is that no component may change without a corresponding change in the documentation, including the placement data if the footprint is affected.

Version control also makes troubleshooting possible. When a board fails in test, the first question is which revision was built and what changed since the last known-good build. Without that record the failure has to be re-diagnosed from scratch, which is exactly the cost the documentation is meant to avoid.

Common BOM Errors That Stop a Build

The recurring problems are predictable. Missing reference designators, part numbers that do not match the manufacturer current ordering code, package names that mean different things to different suppliers, quantity errors, and parts listed without a package or footprint. Each of them stops the line for at least a day.

A short checklist before release catches most of them: every designator appears exactly once, every part number resolves to a real orderable item, every package matches the board footprint, and every line has a quantity and a unit of measure. Checking a BOM against that list takes minutes and prevents most delays. Further guidance on preparing manufacturable output is available in these PCB design guidelines for manufacturability.

Quantities, Units and Packaging

Quantity errors are quiet and expensive. A line that says 10 where the board uses 10 per unit, or a resistor listed in ohms when the house expects a value in kilohms, produces a wrong purchase order that nobody notices until the parts arrive. State the unit of measure for every line and make the quantity unambiguous, including for parts that are supplied in multiples such as resistors on a reel.

Packaging and moisture sensitivity also belong in the data set. Parts supplied in cut tape are not always compatible with a reel-fed placement machine, and a moisture sensitive device that has absorbed water will crack during reflow unless it is baked and used within its floor life. Noting the moisture sensitivity level and the packaging format for each line prevents the assembly house from discovering the problem after the reels are loaded.

FAQ

Does the assembly house create the BOM for me? Some will draft one from the schematic or the placement data, but responsibility stays with the designer. A BOM generated by a third party still has to be checked against the design before anything is purchased.

How much detail should the BOM include for passives? At minimum, value, tolerance, package and voltage rating. For capacitors the dielectric type matters as well, because a substitute with a different dielectric can change circuit behaviour.

Can a prototype BOM be reused for production? The structure can be, but each line should be rechecked for lifecycle status, availability at volume and pricing. Parts that suited a prototype build are not always appropriate for sustained production.