This guide walks hardware engineers, NPI teams, and sourcing managers through every file that belongs in a professional PCBA manufacturing data package, how those files must reference each other, and where most first-build failures actually originate. It focuses on the exact submission behaviors that reduce quotation errors, engineering clarification loops, obsolete-component surprises, and SMT programming delays across industrial control, automotive, medical, IoT, and communication projects.
Why a Complete BOM and Gerber Checklist Decides Your Build
Every PCBA project is a translation problem. The design team encodes intent into schematics, layout data, and part numbers; the manufacturer must decode that intent into purchasing, panelization, stencil design, placement programs, and test procedures. The bom gerber checklist is the contract that makes that translation lossless.
When any single file in the package is missing, outdated, or ambiguous, downstream teams begin making assumptions. Purchasing may guess at a manufacturer part number, the SMT engineer may reconstruct rotations from silkscreen, and the test team may build fixtures for the wrong revision. Those assumptions compound into first-build defects, rework cycles, and quotations that shift after material commitment.
The True Cost of an Incomplete Manufacturing Package
An incomplete package rarely fails loudly at the RFQ stage. It fails quietly, as a preliminary quotation that is later revised, a delivery date that slips two weeks for engineering clarification, or a scrap cost after DFM issues are discovered post-purchase. In many overseas OEM projects, the real cost of a missing pick-and-place file is not the reprogramming labor — it is the lost production slot on an SMT line that has already been booked.
What “Complete” Actually Means for a PCBA Data Package
A complete package is not simply “all files attached.” It is a set of files that all describe the same product revision, at the same point in time, with a documented change history. The manufacturer must be able to open each file, cross-reference reference designators between BOM and placement data, match the PCB revision on the Gerber to the revision printed on the assembly drawing, and confirm that the testing specification applies to the exact firmware version being programmed. Anything less produces a quotation built on assumptions.
The BOM: What Must Be Submitted for Accurate Component Pricing
The Bill of Materials is where most projects lose their first week. A BOM written for internal engineering use — with generic descriptions, marketing part numbers, or missing package data — cannot be priced accurately by any supplier. Procurement teams often underestimate how much a professional BOM file requirements for PCB assembly review depends on structural completeness, not just line count.
Mandatory BOM Columns for a Quotable File
At minimum, a quotable BOM contains: line item number, reference designators (comma-separated, no ranges without expansion), quantity per board, manufacturer name, manufacturer part number (MPN), package or footprint, value or specification, tolerance where applicable, approved alternates or “no substitute” flag, and revision or issue date. Description-only lines force the supplier to guess between multiple valid parts, and MPN-only lines without package data create risk when the same MPN exists in multiple form factors.
Handling Alternates, Obsolescence, and Approval Rules
Every BOM should carry an explicit alternate policy. Which parts are frozen? Which brands are pre-approved? Do lifecycle-risk substitutions require written engineering sign-off, or is the manufacturer authorized to select equivalents within a defined specification window? Before approving the component cost, conduct a BOM Risk Check to identify obsolete parts, long-lead components, package mismatches, single-source items, and alternatives requiring buyer approval. Without this policy in the file, the supplier defaults to raising every ambiguous line as a clarification — and the quotation stalls.
Gerber Files and Drill Data: The Fabrication Language
Gerber is the language your PCB is fabricated in, and it is a fabrication language only. It defines copper geometry, solder mask, silkscreen, board outline, and drill or route information — but it does not, by itself, tell the assembler which component goes where, in what orientation, or with what test coverage.
Modern Gerber Versus Obsolete RS-274-D Data
The current Gerber format is maintained by Ucamco as the open PCB data transfer standard, and it is the format your fabricator expects. The older Standard Gerber (RS-274-D) was revoked in 2014 and no longer conforms to the specification, as Ucamco documents directly on its Standard Gerber page. If your CAD tool still exports RS-274-D, the fabricator must reconstruct aperture definitions manually, which introduces risk and delay. Extended Gerber (RS-274X) and the newer X2/X3 revisions carry aperture and attribute data inside the file itself, which is what the manufacturer needs.
Drill Files, Stack-Up, and Fabrication Drawing Alignment
Drill data (Excellon format is standard) must include plated and non-plated hole distinctions, via structures, and any routing or slot definitions. The fabrication drawing then defines the layer stack-up, controlled impedance requirements, copper weights, board thickness, surface finish, tolerances, materials, and any special process notes such as edge plating or castellations. Baseline dimensional and design requirements for these files are defined in IPC-2221, the generic standard on printed board design. Without a fabrication drawing, the Gerber alone cannot specify controlled impedance, finished thickness, or via fill — and the supplier will quote a default stack-up that may not match your product.
Pick-and-Place, Assembly Drawing, and Placement Intent
Where Gerber describes the board, the pick-and-place file and assembly drawing describe the assembly. These two documents translate BOM parts into physical positions on the PCB, and together they are what enables SMT programming, first-article inspection, and polarity verification.
Centroid File Requirements: Coordinates, Rotation, and Origin
A usable centroid or pick-and-place file must contain, per component: reference designator, X and Y coordinates, rotation angle (with a defined convention, typically counter-clockwise from positive X), side designation (top or bottom), and part identifier that maps back to the BOM line. The file must state its origin and units clearly — an offset origin between the pick-and-place data and the Gerber board outline is one of the most common causes of misplaced first-article boards. When the centroid file is missing or its rotations do not match the manufacturer’s convention, SMT programmers reconstruct placement manually from silkscreen, which slows NPI and introduces placement risk.
Assembly Drawings and Polarity Communication
The assembly drawing is the human-readable layer of the package. It shows polarity indicators for diodes, electrolytic capacitors, tantalum capacitors, LEDs, and connectors; pin-1 orientation for ICs and QFPs; keep-out zones; mechanical mounting details; special assembly notes for press-fit or hand-solder items; and any workmanship references. Even when silkscreen is complete, the assembly drawing serves as the operator’s authoritative reference at the line. Acceptance criteria for the finished assembly — solder joint quality, component alignment, foreign material, and mechanical damage — are defined in IPC-A-610, the industry acceptability standard for electronic assemblies, which the assembly drawing should reference by class (Class 2 for most industrial products, Class 3 for high-reliability).
Revision Control: The Silent Cause of First-Build Failures
More PCBA projects fail from revision drift than from bad design. A team ships a new Gerber revision on Monday, updates the BOM on Wednesday after a component obsolescence, and forgets to regenerate the pick-and-place file — which still references the old footprint. The manufacturer builds against files that individually look correct but collectively describe three different products.
Matching Revisions Across Every File
Every file in the package must carry the same revision identifier, issue date, and — ideally — an approval signature or PLM release status. A quick check: open the BOM header, the Gerber ZIP filename, the pick-and-place header, and the assembly drawing title block. If all four do not show the same revision, the package is not ready to quote. The Gerber, drill, stack-up, placement, and assembly files should also pass a DFM Review before materials are purchased or the SMT line is scheduled.
To avoid revision drift entirely, many teams are moving to consolidated formats. IPC-2581 is a vendor-neutral, XML-based intelligent data format that carries board design, assembly, and test information in a single file. ODB++ serves a similar purpose in Mentor/Siemens-based flows. These formats do not eliminate the need for a BOM and testing specification, but they collapse the fabrication and placement layers into one revision-locked artifact — which is why many high-volume EMS partners now accept them as a preferred input.
Testing Specifications: What Must Be Defined Before Quotation
Testing is where the largest quotation surprises hide. A buyer submits BOM and Gerber, receives a competitive quote, and then adds ICT, functional testing, and firmware programming after PO — at which point tooling, fixtures, cycle time, and NRE all change. Testing must be specified at RFQ, not after.
ICT, FCT, and Functional Test Definition
For in-circuit testing (ICT), the supplier needs the netlist (IPC-D-356 or equivalent), test point coordinates, coverage expectations, and whether a bed-of-nails fixture will be supplied or built. For functional testing (FCT), the specification should describe power sequencing, input stimuli, expected outputs, pass/fail limits, cycle time budget, and any golden-sample availability. Where flying-probe testing is preferred over fixtured ICT — common for low-volume or high-mix products — the supplier still needs the netlist to program the probe path.
Firmware programming requirements should specify: the exact hex or binary file, programming interface (JTAG, SWD, UART, ISP), programmer tool, verification method, and unique-ID or serialization rules. Conformal coating, if required, must specify material class (AR, UR, SR, ER per IPC-CC-830), thickness range, keep-out areas, and cure conditions. Solder workmanship for these processes should be defined against IPC J-STD-001, the requirements for soldered electrical and electronic assemblies, which the buyer can specify by class in the test specification header.
The PCBA Manufacturing File Checklist at a Glance
The table below summarizes the core files, their function, and how they must reference each other. A complete package should let the manufacturer verify not only that each file opens correctly, but that all files describe the same product revision — the criterion that separates a quotable RFQ from a preliminary one.
Reading this table as a checklist rather than a reference list is the practical difference between a supplier who quotes in three days and one who quotes in ten. The right question at submission is not “did I attach everything?” but “does every file in the package point to the same product revision?”
Submission Behavior: One Zipped Package, One Owner
To close the revision-drift loop, treat the manufacturing package as a single controlled artifact. One zipped folder, one internal document owner, one revision identifier that appears in every file header. Procurement and engineering should agree on the owner before RFQ so the supplier receives one authoritative package instead of parallel emails. The essential PCB assembly files for manufacturing success — BOM, Gerber, pick-and-place, and assembly or test documentation — belong in that same folder, not in separate threads.
Decision Matrix: Deciding What to Include Before You Submit
Not every project needs an IPC-2581 file, and not every project needs full ICT coverage. The table below helps engineering and sourcing teams calibrate what belongs in the submission package based on project stage, volume, and reliability class.
Conclusion
A disciplined bom gerber checklist is the lowest-cost engineering practice with the highest impact on PCBA cost, quality, and lead time. When BOM, Gerber, pick-and-place, assembly drawing, fabrication drawing, testing specification, and revision history all describe the same product revision and travel together as one controlled package, quotations become firm, DFM issues surface before purchasing, and first-article builds succeed on the first pass.
Have a BOM, Gerber package, pick-and-place file, assembly drawing, or test specification ready for your next project? Submit files for review with your target quantity, delivery date, and budget window, and let the GNS engineering and sourcing teams verify file completeness, revision consistency, component risks, and manufacturability before the quotation is issued.
FAQ
Q1.What is the single most common cause of PCBA quotation delays?
Missing or mismatched revisions across the BOM, Gerber, and pick-and-place files. Suppliers can quote a slightly incomplete BOM by raising clarifications, but they cannot quote confidently when the Gerber shows Rev C and the pick-and-place file shows Rev B — because the placement data is no longer trustworthy for the fabricated board.
Q2.Do I need to send a pick-and-place file if my Gerber includes component data (Gerber X3)?
Gerber X3 carries component attributes and can serve as a placement source for some flows, but most SMT programming systems still expect a dedicated centroid file with standardized columns. Sending both is the safe default; the manufacturer will confirm which they consumed.
Q3.Can the manufacturer substitute components if my BOM has obsolete parts?
Only if your alternate policy explicitly authorizes it. Without a written policy in the BOM or a covering document, most manufacturers will hold the line and request written engineering approval for every substitution — which extends the quotation cycle. Define frozen parts, approved brands, and substitution rules before RFQ.
Q4.Is IPC-2581 required, or is a traditional Gerber-plus-BOM package still acceptable?
Traditional Gerber-plus-BOM packages remain fully acceptable and are still the majority of RFQs. IPC-2581 or ODB++ is preferred when revision drift is a known risk, when the design uses advanced features like embedded components, or when your PLM system already exports it natively.
Q5.When should I submit the testing specification — with the RFQ or after PO?
With the RFQ. Test scope directly affects fixtures, NRE, cycle time, and lead time; submitting it after PO forces the quotation to be revised and can push the delivery date. Even a one-page test intent document at RFQ is far better than sending nothing.
