Define the output package before plotting
Agree which fabrication format the recipient accepts and identify each required conductor, outline, coverlay, and documentation layer. Keep drill data explicit, including plated and non-plated meaning. Connect the package to the fabrication drawing. If an intelligent format is used instead, verify that the receiving workflow preserves the same engineering intent.
Output inspection targets
| Handoff item | Required meaning | Cross-check |
|---|---|---|
| Outline | Which contour defines the finished cut? | Check continuity and intended internal cutouts |
| Copper | Which side and layer does each file represent? | Compare terminals and controlled routing |
| Openings | Are coverlay and other windows identified? | Overlay with the intended exposed metal |
| Drill data | Which holes are plated and where are they? | Compare hole table and file alignment |
Inspect the generated files independently
Open the delivered files in a viewer and check units, outline continuity, layer order, contact-side orientation, holes, and openings. Compare critical features with the source project and drawing. Follow the applicable KiCad export workflow or Altium output review for the project’s tool version. Do not assume the output settings remain correct after a stack or layer-name change.
Package a single authoritative release
Remove obsolete alternative exports from the delivery archive or clearly separate them from the approved set. Include a manifest, part revision, drawing, and agreed electrical test data. Record when the files were generated and which source revision produced them. If a manufacturer modifies the manufacturing data, require a documented approval process for changes that affect product requirements.
Before you release the design
- View the exact archive that will be sent.
- Check common origins and consistent units across files.
- Include a file-to-layer manifest with meaningful names.
- Regenerate the package after any accepted engineering change.
Watch points
- Sending several unlabeled export sets can create competing definitions of the same board.
Practical questions
Are screenshots useful fabrication deliverables?
They can explain intent or highlight a question, but they do not replace accurate manufacturing geometry and a controlled requirement drawing.
Do Gerbers include the netlist automatically?
Treat electrical connectivity data as an explicit deliverable agreed with the recipient. Do not assume the plotted image files alone convey the intended reference netlist.
Technical references
References support the material or design context. Check the exact grade, part number, document revision and project conditions before release.Updated 27 September 2026 · Technical content policy · Engineering guidance supports project review; the agreed drawing defines the build.