Design handoff ·
Gerber, BOM, STEP and editable PCB files explained
Understand which PCB files support manufacturing, assembly, mechanical fit and future edits, plus the questions to resolve before an order is released.
A PCB handoff serves several people: the fabricator making the bare board, the assembler placing parts, the person designing the enclosure and the engineer preparing the next revision. One attractive render cannot replace the information each needs.
Before ordering, ask for a file manifest that names each deliverable, its format, revision and intended use. Ohmbo's handoff covers schematic, layout, Gerber, BOM and STEP deliverables. Confirm exact formats and editability in the written order; do not infer a native KiCad project from the phrase “design files.”
Match the file to its job
| Deliverable | Main use | What to check |
|---|---|---|
| Schematic | Understand connections and circuit intent | A readable export, revision and any agreed editable source |
| PCB layout | Inspect placement and routing; revise the board if source is supplied | Native format, required application version and dependencies |
| Gerber and drill data | Define the board's manufacturing geometry | Layer map, outline, holes and one consistent released revision |
| BOM | Identify the parts to procure and assemble | Manufacturer part numbers, quantities, packages and reference designators |
| Placement data | Tell the assembler where and how to place components | Whether included; units, origin, side and rotation convention |
| STEP model | Check board and component geometry in mechanical CAD | Missing models, connector locations and component heights |
Ucamco, the Gerber format maintainer, publishes the format specification and fabrication-data examples. Gerber belongs in the manufacturing handoff; it is not a substitute for the circuit's editable source. Source checked: 2026-10-19.
JLCPCB's BOM guidance links component information to reference designators in the layout. Use that relationship to check that the intended part is assigned to the intended position. Source checked: 2026-10-19.
A mechanical model is only as complete as its inputs
A STEP model can help you inspect whether a connector faces an opening, but check its completeness before relying on it. KiCad's PCB documentation describes board-model export and the component models assigned to footprints. Missing component models can leave an incomplete representation. Source checked: 2026-10-19.
Ask for a list of omitted or approximate models. Include cable insertion space, mating connectors and fasteners in your mechanical review. They may not be part of the exported board assembly, even though they determine whether the prototype fits your enclosure.
Editable source, access and ownership are separate questions
A PDF schematic is readable, but it does not provide the same editing workflow as the original CAD project. Ask which source files are supplied, which software opens them and whether custom libraries or models are needed. If your team requires native KiCad files, make that an explicit requirement before payment; this guide does not confirm native KiCad delivery.
File access also does not, by itself, settle permission to modify, reuse or manufacture a design elsewhere. Confirm those rights in the order terms, including any restrictions on third-party libraries or supplied designs. Keep a copy of the agreed terms with the released package.
Ohmbo offers one free online design preview per account. Design and manufacturing downloads are released after payment confirmation and order release. A preview should not be treated as a downloadable fabrication package. See the pricing terms and order process.
Check the package before using it
Open the archive and compare its manifest with the agreed deliverables. Check that the schematic, layout, BOM and manufacturing outputs identify the same revision. View the exported geometry and confirm the outline and holes against the approved drawing. Investigate missing or inconsistent files before sending anything to another manufacturer.
Keep the approved engineer-review record, test-firmware identifier and per-board test reports alongside the files. Name the released package distinctly from later experiments. That gives your next engineer a clear starting point: what was designed, what was authorized for manufacture and what was actually tested.