How to obtain Gerber, BOM and source files when commissioning PCB design

The circuit schematic and PCB layout are different files

The circuit schematic shows how components are electrically connected. PCB design places those connections on the physical board with defined dimensions and layers. Having a schematic does not mean the layout and all manufacturing outputs are complete. A board photograph or PDF schematic also does not replace an editable design project. Such images help assessment, but the available sources must be evaluated separately before further development.

When commissioning PCB layout, the board outline, mounting holes, connector positions and tall components are coordinated with mechanical design. For a control device with a display, for example, the connector must align with the rear enclosure opening and allow cable insertion. File checks also cover this physical fit. The delivery scope specifies the editable electronics project and, where required, mechanical CAD, library information and approved drawings.

What is a Gerber file, what does it contain and what does it not replace?

Gerber is a widely used format for transferring PCB manufacturing information. It defines data such as copper layers, solder mask and silkscreen; the manufacturing package also includes appropriate drill and board-outline information. Ucamco publishes the format definition and technical documentation. The file format and additional instructions supplied to the manufacturer must match the manufacturing process. Files are checked by viewing and comparing them, not simply by their names.

Having a Gerber archive does not establish that editable schematics and embedded software sources are also available. Some tools can import Gerber geometry; KiCad explains that this does not automatically create a normal design project. It is therefore incorrect to conclude that receiving Gerbers means receiving the entire project. If you intend to modify the board later, request the original CAD project and related sources separately.

Why are both the BOM and component placement file needed?

The BOM is the electronic bill of materials. It identifies the component and quantity for each reference designator; accurate manufacturer part numbers reduce purchasing errors. Generic descriptions such as 'resistor' or 'processor' are insufficient for production. Unpopulated parts and approved alternatives are explicitly identified. Two components with the same nominal value may differ in package dimensions, temperature range or other characteristics.

The pick-and-place or placement file specifies each component's position, orientation and board side. It must correspond to the same PCB revision as the BOM. Verify the manufacturer's required units, origin and orientation conventions. An assembly drawing can provide additional explanation. These files do not replace firmware programming instructions or functional tests; producing an electronic board requires managing these complementary steps together.

Manufacturability checks and working-product tests are different

Manufacturability review assesses whether the design can be produced using the selected manufacturing capabilities. It may examine board geometry, holes, spacing and assembly access. Design-rule checks can help identify certain errors. However, a clean rule-check report does not prove that the board functions correctly in the intended device. Manufacturing-file suitability and electrical or functional validation require separate records.

For example, a sensor board whose layer files all open correctly may still contain an unsuitable component, overheat inside its enclosure or suffer a software failure when disconnected. Acceptance uses real operating tasks under defined conditions. The delivery package should show which checks were performed and which tests were outside scope. The prototype-approved revision, manufacturing files and installed program must correspond.

Source code, compiled programs and settings are separate deliverables

The program file loaded into the processor may operate the device, but that file alone does not enable software editing. Source code, the development environment and version, dependencies and build instructions matter for continued development. Programming methods, connection points and device settings are also specified. If serial numbers or calibration data are used, their preparation during production is explained.

Connected products may include server or application work alongside board firmware. Their deliverables, account ownership and operating costs are defined separately. Third-party licences are not presented as transferable without restriction; their usage and distribution conditions are documented. Customer credentials, keys and confidential settings require a secure delivery method rather than inclusion in a public project archive.

Create a delivery list corresponding to one consistent revision

Ask for more than a folder name: the design revision, software version, date and contents list should be clear. Gerbers, BOMs, placement files and programs must not be mixed across versions. Sources should open with their custom symbol and footprint libraries; required commercial software and versions should be specified. Delivering usable files and converting them to a different software package may be separate scopes.

We can work under an NDA before confidential technical information is shared. VOMRO delivers source and manufacturing files for its customer projects within the agreed scope. Begin by describing your current files and objective: repeat production, a board modification or a new product. We can assess what the existing package supports and define missing sources, validation steps and the delivery list together.

• Editable schematic and PCB project
• Manufacturing, BOM and assembly data for the approved revision
• Source code, build and programming instructions within scope
• Required CAD files, test records and licence explanations