A useful PCB copy checklist records the board identity, sample condition, available files, firmware requirements and acceptance criteria before anything is shipped or altered. Start with clear photographs and a short project brief. Agree which sample must remain intact, what investigation is permitted and exactly what you expect to receive.
This guide is for engineers and purchasing teams preparing a board for duplication, documentation recovery or an obsolete-equipment replacement. Use the intake table below to separate essential information from helpful extras. If a detail is unknown, mark it as unknown instead of guessing. You can then request a PCB copy assessment with a clear scope.
1. Define what your PCB copy project must achieve
“Copy this board” can describe several different jobs. You might need fabrication files for a bare board, a readable schematic for maintenance, an assembled replacement, or a working replacement that also depends on firmware and calibration. These outcomes need different evidence and verification.
Write one sentence stating the required outcome, then list the constraints: the enclosure must fit, the original connector must mate, specified interfaces must work, or a particular component must be replaced. Identify optional improvements separately. This prevents a layout-copy request from quietly becoming a redesign project.
For example: “We need an assembled replacement for board revision C, using the existing enclosure and harness. The firmware file is available, but its compatibility has not been verified. The original sample must remain intact.” This is an illustrative brief, not a customer case. It gives the engineer more useful information than a general request for an identical board.
2. Record the assembly revision and connector labels
Photograph every board number, revision label and relevant assembly marking before packing. A bare-board identifier and an assembled-product number can describe different things. Record both when present. If several boards look similar, give each sample a unique ID and keep its photographs, notes and files together.
- Board identity: equipment model, board number, printed revision and assembly label.
- Population differences: empty footprints, fitted jumpers and alternative components.
- Field changes: added wires, cut tracks, repairs and replaced parts, with their history if known.
- Interfaces: connector labels, keying, mating harness references and known signal assignments.
- Configuration: switch positions, removable modules and any settings needed by the equipment.
State whether the intended replacement should reproduce the sample as received or a documented earlier configuration. Do not silently treat a repair wire as an original design feature. Equally, do not assume an empty footprint means a missing component.
For photographs, capture both sides straight on, then add close-ups of markings and connectors. Include a ruler in the same plane as the board where practical. Keep unedited originals and put annotations on separate copies. Readable detail and controlled perspective matter more than an arbitrary camera megapixel requirement. Photographs alone do not establish all hidden connections or a complete multilayer stackup.
3. Choose the samples and preserve a working reference
Label each sample working, failed or untested, and explain what that label means. “Powers on” is different from “all channels tested under the specified load.” Include known fault symptoms, previous repairs and any operating conditions already documented.
There is no universal sample-count rule based only on layer count. Required samples depend on hidden structures, condition, available documentation, verification needs and whether any destructive investigation is proposed. A second board may provide a useful reference, but two samples do not automatically authorize sacrificing one.
If you have only one irreplaceable board, state that in the first enquiry. Agree a preservation-first assessment and explicit approval points before component removal, coating removal or destructive inspection. A failed board may still contain useful geometric and connectivity evidence, but it cannot by itself demonstrate the original unit’s complete functional performance.
Preserve the as-received state until an inspection plan is agreed. Do not clean, desolder, remove potting or change device programming just to make the sample look ready. Identify contamination, loose parts and damaged areas in photographs. An unplanned intervention can remove markings or evidence that would help explain the board.
4. Define the files and acceptance evidence you need
List existing schematics, BOMs, fabrication data, assembly drawings, firmware files and test records. Include the revision and origin of each file. An older document can be useful, but it should not be described as the current design until compared with the sample.
Specify requested outputs separately. KiCad’s official documentation, for example, distinguishes fabrication plots, drill files, component placement files and other production outputs. Those are separate parts of a handoff, not interchangeable names for one file. See the KiCad PCB Editor output documentation.
| Requested output | What to specify | Evidence to request |
|---|---|---|
| Bare-board fabrication package | Layer files, outline, drilling information and required fabrication notes | File manifest, matching revisions and review of unresolved manufacturing assumptions |
| Recovered schematic | Readable PDF and agreed editable format | Connectivity review and a visible list of uncertain values or identities |
| BOM and assembly package | Part identities, unresolved parts, placement and assembly information | Population comparison against the selected sample revision |
| Firmware or configuration | Exact devices, required memory regions and accepted file formats | Acquisition provenance, verification records and any unreadable or unverified regions |
| Assembled replacement | Mechanical, electrical and functional requirements | Agreed tests, conditions, coverage and recorded deviations |
For Gerber-based delivery, agree the format and the accompanying information with the receiving fabricator. Ucamco maintains the official Gerber and related format specifications. Naming a format alone does not define your entire project package.
A design-rule check is useful evidence about the configured rules; it is not proof that a recovered circuit behaves like the reference equipment. Decide which mechanical dimensions, connections and functions need separate verification. The broader PCB reverse engineering service scope can help distinguish documentation recovery from a validated replacement.
Keep firmware requirements visible
If the board uses an MCU, FPGA or external memory, identify what software and configuration you already possess. Do not assume that recreating the PCB also recovers its program. Record the full chip marking and whether preserving original contents is essential. Reading a file, producing a usable replacement and recovering original source code are different outcomes.
Request a device-specific IC unlock and firmware feasibility review where needed. Define the authorized scope before changes to device state. Do not reset or erase an irreplaceable sample simply to see whether access becomes available.
5. Complete the PCB copy sample intake checklist
Use this table as a project record. “Essential” means the question should be answered; “unknown” is an acceptable answer when evidence is missing. Supporting files are helpful when available, not a prerequisite for every assessment.
| Field | Priority | Record or attach |
|---|---|---|
| Project outcome | Essential | Files, assembled replacement, redesign or another defined result |
| Board identity | Essential | Board and assembly numbers, revision, equipment context, or unknown |
| Sample inventory | Essential | Unique sample IDs, quantities and working/failed/untested status |
| Preservation limits | Essential | Which sample must remain intact and what requires approval |
| Photographs | Essential for initial visual review | Both sides, labels, connectors, chip markings and damaged areas |
| Modifications | Essential | Known repairs, missing parts, jumper settings and intended baseline |
| Firmware scope | Essential | Required/not required/unknown; existing files and preservation needs |
| Deliverables | Essential | File types, editable formats and required physical outputs |
| Acceptance checks | Essential | Dimensions, interfaces, functions and unresolved test requirements |
| Existing design files | If available | Schematic, BOM, layout, Gerber and assembly files with revisions |
| Supporting hardware | As agreed | Mating connectors, harness information, fixtures or enclosure drawings |
| Operating records | If available | Documented settings, fault history and test conditions |
| Project authority | Essential | Authorized contact, permitted use and confidentiality requirements |
Pack for both electrostatic and mechanical protection
Choose packaging suitable for the assembly, protect projecting connectors and prevent movement inside a rigid outer container. Keep sample labels associated with the correct board. Loose accessories should not strike components during transport.
The EOS/ESD Association distinguishes low-charging materials from discharge-shielding protection and states that packaging used outside an ESD protected area should also provide discharge shielding. Do not assume that any bag described as “anti-static” is suitable shipping protection. Follow the association’s packaging guidance and the packaging supplier’s specified properties.
Confirm the receiving address and shipping instructions with the project contact before dispatch. Include a sample inventory and retain the packing photographs and tracking reference. Disclose batteries or other special handling requirements before choosing the transport method.
6. Resolve these questions before proceeding
Can I request PCB copying without original files?
Yes, you can request an assessment using the physical board and available photographs. State that the original files are unavailable. The assessment should identify what can be reconstructed, what remains uncertain and which outputs need additional evidence.
Should I send my only working board immediately?
First explain that it is your only working reference. Agree the required investigation, preservation limits and return arrangements. The sample plan should follow the project needs rather than a blanket rule about layer count.
Can a non-working board support a copy project?
It may support reconstruction, depending on the damage and available evidence. Record its failure history. Treat functional equivalence as a separate verification question, especially if no working reference or operating specification exists.
What should be settled before accepting a quotation?
Confirm deliverables, unresolved parts, firmware scope, sample consumption, verification coverage and approval milestones. Compare the same scope when reviewing prices. Use the PCB project pricing guide to structure those questions.
Does a completed checklist guarantee successful recovery?
No. It improves the information available for assessment. Hidden damage, unidentified parts, unavailable firmware or incomplete test requirements can still limit the result. A useful proposal makes those dependencies explicit.
Send a focused project brief
Include the board revision, clear photos, sample condition, required files or replacement functions, and any restriction on altering the original. Add your most important unanswered question. PCB-Copy can use that information to review the scope before you arrange shipment.
Check feasibility for your project
Send the chip marking or board details and tell us what you need to recover. Add clear photos if available.
Request a feasibility reviewWorking on a board like this?
Send the chip marking or two photos. You get feasibility, lead time and price within 24 hours, and the check costs nothing.
Get a free quote