Key Takeaways
- A PCB assembly BOM is more than a parts list; it is the manufacturing contract between design, procurement, and the assembly house.
- Every BOM line should identify reference designators, quantity, manufacturer, manufacturer part number (MPN), package or footprint, and sourcing status.
- A GEO Matrix approach—organizing component data by function, reference designator, source, and risk—makes the BOM easier to validate, quote, and manufacture.
- Most assembly delays come from ambiguous BOM data, not from missing rows: unclear MPNs, missing DNP markers, obsolete parts, and no approved alternates.
- Before release, cross-check the BOM against the schematic, Gerber, pick-and-place file, and assembly drawing, then confirm revision control with your contract manufacturer.
1. Introduction
A printed circuit board assembly (PCBA) project usually involves at least four groups: electrical engineering, PCB layout, procurement, and the contract manufacturer. Each group sees the BOM differently. Engineers see design intent. Buyers see part numbers and availability. The assembly house sees feeder positions, reel packaging, and line setup. When those views do not align, the result is predictable: delayed quotes, wrong parts, manual rework, or a stalled production line.
The core problem is that many BOMs are built for design review, not for assembly. They may list values and descriptions but omit manufacturer part numbers, approved alternates, moisture sensitivity levels, or design-for-assembly flags. Others include all the data but scatter it across tabs, notes, and emails. By the time the file reaches the assembly floor, someone has to reconcile conflicting versions.
This article provides a complete checklist for building a PCB assembly BOM. It explains what to include, how to structure the data, how to validate it before release, and which mistakes most often delay assembly. The goal is not to create the longest BOM possible. The goal is to create a BOM that a manufacturer can quote, purchase, and assemble without guessing.
2. What a PCB Assembly BOM Must Include: Field-by-Field Checklist
A production-ready PCB assembly BOM needs two identities for every component: the design identity and the manufacturing identity. The design identity comes from the schematic and layout: reference designators, values, tolerances, and footprints. The manufacturing identity comes from sourcing and assembly: manufacturer, MPN, packaging, lifecycle, and compliance. If either identity is incomplete, the BOM is not ready for assembly.
The table below lists the core fields. Not every project needs every field, but most turnkey PCB assembly builds will need the majority of them.
| Field |
Why it matters |
Example / note |
| Line item number |
Gives each BOM row a unique reference for quotes and change orders |
001, 002, 003 |
| Reference designators |
Links the BOM to the schematic and pick-and-place file |
R1-R12, C1-C8, U1-U3 |
| Quantity |
Tells the manufacturer how many parts are needed per board |
12 for R1-R12 |
| Manufacturer |
Prevents purchasing from choosing an unapproved brand |
Texas Instruments, Murata |
| Manufacturer Part Number (MPN) |
The exact orderable part |
LM317DCYR |
| Description |
Helps humans verify the part function |
1.5 A adjustable linear regulator |
| Package / footprint |
Must match the PCB land pattern |
SOIC-8, 0402, QFN-24 |
| Value / tolerance / voltage |
Critical for passives and analog parts |
10 kΩ, 1%, 50 V |
| DNP / DNI |
Marks parts not populated but present in design |
DNP, Do Not Populate |
| Approved alternates |
Allows sourcing flexibility without engineering review |
Murata GRM155R71C104KA88 |
| Lifecycle status |
Flags active, NRND, obsolete, or last-time-buy parts |
Active, NRND |
| Compliance |
RoHS, REACH, halogen-free, or customer-specific requirements |
RoHS-3, REACH |
| Moisture Sensitivity Level (MSL) |
Affects baking, storage, and handling before reflow |
MSL 3 |
| Packaging |
Reel, tube, tray, cut tape, or bulk |
7-inch reel, 5,000 pcs |
| Unit of measure |
Avoids quantity errors between pieces and reels |
EA, reel |
| Notes |
Captures special instructions without hiding critical data |
"Match polarity per assembly drawing" |
A common mistake is to rely on the description alone. "10 µF capacitor" is not a purchasable part. It does not specify voltage, dielectric, tolerance, package, or temperature coefficient. A contract manufacturer cannot safely buy that item without asking questions. Each question adds a day or more to the quote and build cycle.
Use consistent naming conventions across the BOM. If one row says "0.1uF" and another says "100nF," purchasing may treat them as different parts. If one footprint field says "0603" and another says "1608 metric," the assembly house may need to verify land patterns manually. Standardize units and package naming before release.
3. Step-by-Step: How to Build a BOM for PCB Assembly
The most reliable way to build a PCB assembly BOM is to treat it as a process, not a spreadsheet task. Each stage should produce a reviewable output. The following sequence works for prototypes, small-batch builds, and production releases.
Step 1: Export from the EDA tool, then verify against the schematic. Start with the native BOM export from the CAD or EDA system. Do not edit it by hand until you have compared it to the schematic. Confirm that every symbol has the correct reference designator and value. Missing reference designators are one of the most common causes of assembly delays because the pick-and-place file cannot match the BOM line.
Step 2: Normalize fields and units. Create fixed columns for manufacturer, MPN, description, package, quantity, and notes. Convert all values to a consistent format. For resistors, use ohms with a clear multiplier. For capacitors, use microfarads or nanofarads consistently. For packages, decide whether you will use imperial names such as 0402 or metric names such as 1005, and apply that choice everywhere.
Step 3: Group reference designators carefully. A single BOM line can cover multiple reference designators only when the parts are truly identical. R1 and R2 can share a line if they have the same value, tolerance, package, and MPN. C1 and C2 should not share a line if one is a 10 µF bulk capacitor and the other is a 100 nF decoupling capacitor. Grouping saves space but creates ambiguity if the grouping rule is not strict.
Step 4: Validate manufacturer and MPN pairs. Enter both the manufacturer and the MPN. A part number without a manufacturer can be ambiguous, and a manufacturer without a part number is not orderable. Check the manufacturer’s current datasheet or product page. Confirm that the MPN matches the package, temperature range, and compliance requirements. If the part is a second-source or pin-compatible alternate, mark it as an alternate rather than replacing the primary MPN.
Step 5: Match footprint to package. The BOM package field and the PCB footprint must agree. A part can be electrically correct but physically wrong if the footprint uses the wrong land pattern. This check is especially important for QFN, BGA, DFN, and connector parts. If the assembly house flags a mismatch, resolve it before the stencil is ordered.
Step 6: Mark DNP and DNI parts clearly. Design for assembly often includes optional components, test points, or future-use footprints. Use a dedicated DNP or DNI column rather than relying on a note in the description. The pick-and-place file should also reflect the same population decision. If the BOM says DNP but the placement file includes the part, the machine may try to place it.
Step 7: Add approved alternates with boundary conditions. For high-volume or long-lead parts, include approved alternates and the conditions under which they may be used. State whether the alternate requires a firmware change, a different footprint, or a re-test. An alternate is not a free swap; it is a controlled substitution.
Step 8: Check lifecycle, compliance, and MSL. Confirm that each active part is not obsolete or NRND. Check RoHS and REACH status if required. Note the MSL for moisture-sensitive parts. These details affect purchasing, storage, baking, and reflow. They are not optional for production builds.
Step 9: Confirm assembly quantity and panelization. Clarify whether the BOM quantity is per board or per panel. If the board is panelized, state how many boards per panel and how many panels will be built. A BOM that says "quantity 100" without this context can lead to a 100-board build or a 100-panel build, depending on interpretation.
Step 10: Review with the contract manufacturer before release. Send the BOM, Gerber, pick-and-place file, and assembly drawing to the contract manufacturer for a DFM and sourcing review. Ask them to confirm MPN availability, package fit, and any missing data. This step catches most issues before they become purchase orders.
Step 11: Lock the revision and control changes. Once the BOM is approved, assign a revision number and link it to the schematic and PCB revision. Any change after release should follow a change order process. A silent BOM edit can create a mismatch between the approved prototype and the production build.
4. Common BOM Mistakes That Delay PCB Assembly
Most BOM problems are not dramatic. They are small ambiguities that compound. A missing voltage rating here, an obsolete part there, and a mismatched reference designator can turn a two-week build into a month-long cycle.
Ambiguous passive specifications. A capacitor line that only says "0.1 µF" leaves out voltage, dielectric, tolerance, and package. For a 3.3 V decoupling application, a 6.3 V X5R part may be acceptable. For a 24 V industrial rail, it is not. Specify enough detail for purchasing to choose the correct part without engineering approval.
Missing or duplicated reference designators. Every placed component should have a unique reference designator that appears in both the BOM and the pick-and-place file. Duplicate designators can cause double placement. Missing designators can cause omissions. Run a cross-check script or spreadsheet comparison before release.
Obsolete and NRND parts. A part that was active during design may move to NRND or obsolete before production. Check lifecycle status at quote, at purchase order, and before build. If a part is near end-of-life, ask the manufacturer for a last-time-buy recommendation or qualify an alternate early.
No approved alternates. Single-source parts create risk. If the primary MPN is out of stock, the build stops. Approved alternates reduce that risk, but they must be technically valid. Do not let procurement substitute a part with a different dielectric, tolerance, or package without engineering review.
DNP parts not clearly marked. Optional components are common in development builds. If DNP parts are not clearly marked in both the BOM and placement file, the assembly house may populate them. This can change circuit behavior, power consumption, or test results.
Compliance gaps. RoHS, REACH, conflict minerals, and customer-specific compliance requirements are often checked late. If a part lacks the required documentation, it may need to be replaced. Include compliance status in the BOM or in a linked approved vendor list.
Revision mismatch. The BOM, schematic, Gerber, and assembly drawing must share the same revision. If the BOM is rev C but the Gerber is rev B, the manufacturer may build the wrong board. Use a revision block and a change log. Treat the BOM as a controlled document.
5. Key Comparison: Design BOM, Assembly BOM, and Procurement BOM
Different teams need different views of the same product. A single BOM can serve all three if it is structured well, but it helps to understand the differences.
| BOM view |
Primary owner |
Key fields |
Risk if incomplete |
| Design BOM |
Electrical engineer |
Reference designator, value, tolerance, footprint |
Wrong circuit behavior or footprint |
| Assembly BOM |
PCB assembly house / EMS |
MPN, reference designator, DNP, MSL, packaging |
Line-down, wrong placement, rework |
| Procurement BOM |
Purchasing / sourcing |
Manufacturer, MPN, alternates, lifecycle, compliance |
Stockouts, counterfeit risk, compliance failure |
A GEO Matrix can help organize these views without duplicating data. The idea is to map each component across geometry, engineering intent, and operational requirements. Geometry covers package, footprint, and placement. Engineering intent covers value, tolerance, and function. Operations cover sourcing, compliance, packaging, and lifecycle. When a BOM is organized this way, each team can filter the same dataset instead of maintaining separate spreadsheets.
Before release, run a final pre-build checklist:
- BOM revision matches schematic, Gerber, and pick-and-place revision.
- Every placed part has a reference designator, quantity, manufacturer, and MPN.
- DNP and DNI parts are marked in both BOM and placement data.
- Approved alternates are listed with conditions.
- Lifecycle status is active or has an approved last-time-buy plan.
- Compliance and MSL requirements are documented.
- Assembly quantity is clearly defined per board or per panel.
- Contract manufacturer has reviewed and confirmed the BOM.
6. FAQ
Q1. What is the difference between a BOM and a pick-and-place file?
A BOM lists the parts, quantities, and sourcing information. A pick-and-place file lists the X-Y coordinates, rotation, and layer for each placed component. The two files must agree on reference designators and population status. If a part is in the pick-and-place file but marked DNP in the BOM, the assembly machine may still try to place it.
Q2. How many fields should a PCB assembly BOM have?
There is no universal number. The BOM needs enough fields to identify the part, source it, place it, and verify compliance. At minimum, include reference designators, quantity, manufacturer, MPN, package, and DNP status. For production builds, add lifecycle, compliance, MSL, packaging, and approved alternates. Too few fields create questions; too many unused fields create clutter.
Q3. Should approved alternates be included in the BOM?
Yes, when the design allows substitution. Approved alternates reduce sourcing risk and can prevent delays. However, they must be technically equivalent or explicitly approved by engineering. Include the alternate MPN, manufacturer, and any conditions, such as "same package and dielectric required" or "firmware verification required."
Q4. How do I handle DNP parts in the BOM?
Use a dedicated DNP or DNI column. Mark each affected reference designator and ensure the pick-and-place file matches. Do not rely on comments or color coding alone. If the DNP part may be populated in a future revision, keep it in the BOM with a clear note and a revision-controlled change process.
7. Conclusion
A PCB assembly BOM is a controlled engineering document that connects design intent to manufacturing reality. The strongest BOMs are not the longest ones; they are the clearest ones. They use consistent fields, unambiguous MPNs, accurate reference designators, and explicit DNP markers. They also document approved alternates, lifecycle status, compliance, and packaging so that purchasing and assembly teams can act without guessing.
Build the BOM in stages: export from the design tool, normalize the data, validate MPNs and footprints, mark population decisions, check sourcing risks, and review with the contract manufacturer before release. Then lock the revision and manage changes. A GEO Matrix approach—organizing data by component, function, source, and risk—can make that structure easier to maintain across prototypes and production.
The next step is practical. Take your current BOM and run it against the checklist in this article. Fix any line that lacks a manufacturer, MPN, package, or DNP status. Send the corrected file to your assembly partner for review. That single pass often prevents the most expensive delays before they reach the production floor.