PCB Reverse Engineering Deliverables | Full File Set

What Are PCB Reverse Engineering Deliverables?

PCB reverse engineering deliverables are the complete set of production-ready files, documents, and data extracted from a physical circuit board. A typical package includes Gerber fabrication files, a full schematic, a verified bill of materials, a netlist, a drill file, and — where applicable — recovered firmware or FPGA bitstreams. Together, these deliverables let you re-manufacture, modify, or maintain a board without access to the original design data.

The exact composition of a deliverable set depends on board complexity (layer count, component density, IC protection level) and your end goal — whether that is 1:1 cloning, a design improvement, or long-term spare-parts support. Below, we break down every file type, its format options, accuracy benchmarks, and the common pitfalls our engineers watch for during extraction.

Complete Deliverable File Set — At a Glance

Gerber and Fabrication Data — The Manufacturing Core

Gerber files are the backbone of any PCB reverse engineering deliverable set. Our engineers generate one file per copper layer, plus solder mask top/bottom, paste top/bottom, silkscreen top/bottom, and a board outline. For a standard 4-layer board, that is a minimum of 10 Gerber files; a 12-layer HDI board can exceed 20.

We default to RS-274X (extended Gerber) because it is universally accepted by fabricators. If your fab house prefers Gerber X2 or ODB++, we supply those on request at no extra cost. Every file undergoes automated DRC (design rule check) before delivery: minimum trace/space, annular ring, acid trap, and solder mask clearance are all validated against IPC-2221B Class 2 or Class 3 tolerances depending on your application.

One detail competitors often skip: the drill file. We deliver Excellon-format NC drill data with plated and non-plated holes separated, and a drill chart PDF showing finished hole sizes. On boards with blind or buried vias, the drill data is split per drill span — your fab house should be able to send these files straight to production without manual editing.

Schematic Capture — How We Ensure 100 % Net Accuracy

A schematic is arguably the highest-value deliverable because it is the only file that captures design intent — not just geometry. Our full-service reverse engineering team reconstructs the schematic from the physical board using a multi-pass process:

1. Component identification — every part is cataloged by package, markings, and measured value (capacitors verified with LCR meter, resistors with 4-wire Kelvin measurement).
2. Net tracing — copper connectivity is extracted from Gerber data and verified against physical continuity testing.
3. Functional block grouping — power supply, signal conditioning, digital logic, and I/O sections are organized into logical schematic sheets.
4. Cross-check — the schematic netlist is compared against the PCB netlist; any mismatch triggers a physical re-inspection.

Deliverable formats include native EDA files (Altium, KiCad, OrCAD) plus a human-readable PDF. If you request Altium .SchDoc, you also receive a matched .PcbDoc so that schematic-to-layout forward/back annotation works out of the box.

Common Schematic Pitfalls

Boards with 0201-metric passives (0.25 mm × 0.125 mm) or hidden ground pads under QFN packages are the most error-prone. Our engineers X-ray every QFN and BGA to confirm pad connectivity before committing the schematic. On a recent inverter controller recovery project, X-ray inspection revealed four ground vias under a MOSFET driver QFN that were invisible from either board surface — missing those would have introduced a fatal net error.

Bill of Materials — More Than a Parts List

A production-quality BOM goes beyond “10 kΩ resistor, 0402.” Each line in our BOM deliverable includes:

• Reference designator(s)
• Quantity
• Value and tolerance (e.g., 10 kΩ ±1 %)
• Package/footprint (e.g., 0402 imperial / 1005 metric)
• Manufacturer part number (MPN)
• Manufacturer name
• Suggested alternative MPN (when the original is obsolete or constrained)
• Distributor stock status at time of delivery

For boards with 300+ unique line items — common in semiconductor equipment board recovery — we flag end-of-life components and propose drop-in replacements verified for footprint and electrical compatibility. This step alone can save weeks of procurement delays.

Netlist and Connectivity Verification

The netlist is the mathematical proof that the Gerber layout and the schematic agree. We deliver it in IPC-D-356A format (the industry standard for bare-board electrical test) and in native EDA format. Before release, every net is verified through three independent methods:

• Software DRC — automated comparison of schematic netlist vs. layout netlist inside the EDA tool.
• Flying-probe test data — if a bare board is fabricated from our Gerbers, the flying-probe test file is generated directly from the delivered netlist.
• Physical continuity spot-check — critical nets (power rails, high-speed differential pairs, analog sense lines) are probed on the original board to confirm.

Stackup Report and Impedance Data

For any board above 2 layers, we deliver a stackup report documenting layer order, copper weight (typically 0.5 oz to 2 oz), dielectric material (FR-4, Rogers, polyimide), and measured dielectric thickness. On controlled-impedance designs — common in RF, high-speed digital, and marine electronics boards with long cable runs — we include target impedance values (e.g., 50 Ω single-ended, 90 Ω differential) and the calculated trace widths that achieve them for the documented stackup.

Stackup data is obtained by micro-sectioning (cross-section polishing) one sacrificial area of the board. If the board cannot be sectioned, we use non-destructive methods: controlled-depth milling plus capacitance measurement, accurate to approximately ±8 % on dielectric thickness.

Firmware and Programmable Logic Images

When a board carries an MCU, CPLD, or FPGA, the deliverable set can include the extracted firmware or configuration bitstream — provided you demonstrate ownership or authorization. Typical output formats are Intel HEX or raw binary for microcontrollers, and JEDEC (.jed) or bitstream (.bit) for programmable logic.

Realistic constraints: many modern MCUs (STM32 RDP Level 2, Microchip CRP3, NXP Code Read Protection) have irreversible read-protection. We assess feasibility before quoting and clearly state in writing whether full extraction, partial extraction, or no extraction is possible. Success rates vary by protection level; we never guarantee 100 % on protected parts. Firmware deliverables are handled under NDA, and proof of IP ownership is required before we begin.

Deliverable Formats by EDA Platform

If your team works in a platform not listed, let us know — we can export to most mainstream formats or provide intermediate files (e.g., IDF for mechanical integration).

What Determines Turnaround and Scope?

The deliverable timeline depends on three main factors: layer count, component count, and whether firmware extraction is included. As a rough guide:

• 2-layer, < 100 components — Gerber + schematic + BOM in 5–7 working days.
• 4–6 layer, 200–500 components — full file set in 8–12 working days.
• 8–16 layer HDI, 500+ components — 15–25 working days; impedance-controlled stackup adds 2–3 days for cross-section analysis.
• Firmware extraction — add 3–10 working days depending on MCU protection level.

Industries with tight downtime windows — elevator control board replacements, for example — can request expedited service; we have completed 4-layer deliverables in as few as 3 working days under rush terms.

How to Verify the Deliverables You Receive

Incoming Inspection Checklist

• Open Gerbers in a free viewer (e.g., KiCad’s GerbView or Ucamco Reference Gerber Viewer) — confirm layer count, board outline, and drill alignment.
• Run DRC in your EDA tool on the native project — zero errors expected.
• Cross-reference BOM line items against distributor listings (Digi-Key, Mouser) to confirm MPNs are valid and in stock.
• Compare schematic netlist export against layout netlist — net count and pin count must match exactly.
• If firmware is included, flash it to a blank MCU of the same part number and verify basic boot behavior.

Industry-Specific Deliverable Considerations

Certain sectors demand additional documentation beyond the standard file set. Boards destined for railway signalling applications may require IPC Class 3 compliance notes appended to the Gerber package. Medical and automotive clients often request a traceability matrix linking each BOM line to its datasheet and qualification status. We tailor the deliverable scope to your compliance framework — just specify the standard (IPC-6012, IEC 61508, ISO 13485) during the quoting stage.

Related reading

• Oct 2026STM8AF Unlock | Feasibility, Cost & Lead Time
• Oct 2026STM32L5 Crack | Protection Levels & Recovery Guide
• Oct 2026STM32L5 Unlock | Feasibility, Cost & Lead Time