勛圖tv 繚 ENGINEERING GUIDE
PCBA Design Release: Align the Board, BOM, Placement and Test Files
PCBA design release is the controlled handoff from an electronic design to a buildable and testable assembly. A routed PCB is only part of that handoff. The assembler also needs the fitted component configuration, placement intent, process exceptions and the evidence required before the assembly can be accepted.
This page focuses on release consistency. It does not replace a schematic-design tutorial or the broader design-for-assembly review. Use it when the design is approaching quotation, prototype production or an approved revision and several teams need to know which files govern the build.
Define the build before collecting files
Start with the assembly identity, quantity, variant and purpose. A functional prototype, engineering validation lot and repeat production order can require different programming, inspection and documentation. State whether components are turnkey sourced, customer supplied or split between those responsibilities. A quotation based on an incomplete BOM cannot be compared fairly with one that includes sourcing and testing.
Identify the bare-board construction and approved material/finish requirements. Record which details are fixed and which can be proposed by the manufacturer. The release should make an open stackup question visible instead of embedding a guessed thickness in one drawing while another file specifies something else.
Reconcile four representations of the same assembly
The schematic defines electrical intent, the PCB data defines physical connectivity, the BOM defines fitted parts and the placement/drawing set defines assembly configuration. Their revision labels alone do not prove that they agree. Compare reference designators, package suffixes, fitted quantities, DNP states, side and polarity across the exported outputs.
Consider a regulator substitution with the same nominal package family but a different pin assignment. A BOM-only change can produce a mechanically plausible but electrically wrong assembly. The review must reach the schematic and footprint mapping, not stop after confirming that both descriptions say QFN. Record the approved substitution and its affected outputs.
| Review item | What to establish |
|---|---|
| Configuration | Fitted/DNP states and exact package suffixes agree. |
| Manufacturing | Board, panel and assembly datum are explicit. |
| Verification | Programming and test requirements have an owner. |
| Release | Exports were checked after the final approved change. |
Release usable fabrication and assembly data
Provide the fabrication dataset in the agreed format, with drill definitions, outline, stackup and notes. Supply the component list and machine placement data in a documented coordinate convention, then add an assembly drawing for visual instructions that those files cannot express. An image of the board is useful for orientation, but it is not manufacturing data.
Name one owner for panelization and identify whether the delivered placement data represents a single board or the assembly panel. If a supplier creates the panel, specify how the single-board datum and variants are preserved. Do not include an old panel drawing just because it was used successfully on the previous revision.
Turn test intent into a deliverable
Define what will be programmed, powered, measured and recorded. Firmware identification, programming interface, power limits, fixtures, connectors and expected outputs should be available at the stage when they affect the quotation. A requirement to perform functional testing is incomplete without a test method and a decision rule.
Distinguish board fabrication continuity testing from PCBA functional testing. Likewise, optical inspection of visible joints does not prove firmware behavior or a hidden connection. The design release should connect each significant risk to a proposed verification method. Where the test is not ready, agree on the resulting prototype limitation rather than representing the build as fully verified.
PCBA release gate worksheet
PCBA release gate worksheet
Use the current inputs and keep the assumptions
Choose the question you want to resolve before entering numbers. The fields start blank. Load example deliberately if you want to understand the calculation, and keep that example separate from your project record. The example label remains visible after editing; reset the tool before preparing a record from your own data.
Use the displayed units and identify the source of each input. A dimension should refer to the same layer, reference plane and design revision as the other dimensions in the model. An entered limit is your review requirement, not an IPC value supplied by this website. Where a value is unknown, obtain it or preserve the question as open instead of guessing a familiar number.
Read the assumptions with the result. A negative margin is retained so a conflict remains visible. A positive margin only answers the stated mathematical question. It does not establish process capability, compliance, electrical performance or production yield. Checklist statuses are self-reported and do not imply that the underlying evidence has been inspected.
Changing a field invalidates the result and disables its download until you calculate again. The text download contains the current inputs, result and limitations. No CAD file is read, no project data is uploaded and nothing is automatically inserted into Contact. Attach the record manually if useful. You can request a review directly without using the worksheet.
| Input | What to establish before using it |
|---|---|
| Review reference | Connect this worksheet to a nonconfidential design/revision reference. |
| Fabrication data approved | Self-reported status; a record or rationale is required outside this worksheet. |
| BOM and substitutions controlled | Self-reported status; a record or rationale is required outside this worksheet. |
| Placement and drawing aligned | Self-reported status; a record or rationale is required outside this worksheet. |
| Firmware / programming scope | Self-reported status; a record or rationale is required outside this worksheet. |
| Inspection and functional criteria | Self-reported status; a record or rationale is required outside this worksheet. |
| Open changes assigned | Self-reported status; a record or rationale is required outside this worksheet. |
| Next action / evidence reference | Do not enter confidential project data. This worksheet does not read the underlying file. |
Handle unresolved decisions explicitly
Classify questions that block production separately from preferences that can remain open during quotation. A missing approved alternate, unclear connector orientation or unapproved via structure may block a build. A preferred report layout may not. For each open item, record its owner, required evidence, due stage and the affected file.
The worksheet lists release topics as open, evidence recorded or not applicable with reason. It intentionally avoids a readiness percentage: five easy completed items do not offset one unresolved electrical polarity issue. Marking an item recorded is your statement about evidence held elsewhere, not a software inspection of the design.
Freeze and verify the exported state
Create the release package from a controlled design state. Reopen the exported fabrication and assembly data, compare a few high-risk interfaces and retain the resulting review record. Confirm that a last-minute footprint edit appears in copper, mask, paste, placement and drawing outputs where it should. Updating the CAD file without regenerating downstream files is a common source of inconsistent releases.
For a repeat order, identify whether the instruction is exact repeat or revised build. Preserve previous approved deviations and determine whether each still applies. A new BOM source, paste, board finish or firmware version can affect the build even if the PCB outline is unchanged. The DFMA responsibility review helps assign these cross-team decisions without duplicating every technical rule in the release note.
Prepare a quotation that can be acted on
Send the current files with quantity, sourcing responsibility, inspection/test scope and open engineering questions. Use the required PCBA files guide for file preparation details. An incomplete project can still be discussed; clearly label preliminary information so it is not mistaken for authorization to manufacture. The useful outcome is one agreed build configuration and a short list of decisions needed to reach it.
Run a short cross-file release rehearsal
Choose a small set of references that exposes the likely ambiguities: one polarized component, one bottom-side component, one optional part and one mechanical attachment. Trace each through the BOM, drawing and placement data. Use the actual exports that will be sent for production, rather than relying on the CAD view alone.
For each reference, ask what is fitted, where it is fitted, which side receives it and what identifies the correct orientation. Where a special operation applies, locate the instruction and its owner. If the answer requires an undocumented conversation, improve the release package before it leaves the design team. This exercise is short enough to repeat after a consequential revision.
Next, compare identifiers across the files. The bare-board revision, assembly revision and product variant may legitimately differ, but their relationship must be explicit. Filenames can help, yet a filename alone should not be the only evidence of the intended build. Keep a concise manifest that identifies the files actually released and the unresolved questions, if any.
Assign a decision owner for proposed substitutions or manufacturing changes. The person who uploads a package is not necessarily authorized to approve a pin-compatible replacement, a copper change or a different inspection scope. Making that responsibility visible avoids a production delay being resolved through an assumption that later becomes a product problem.
After a correction, regenerate the affected outputs and re-run the representative checks. Preserve the superseded package as a historical record, while making the approved package unambiguous to the receiving team. Do not distribute two apparently current versions and expect the assembler to decide which one is authoritative.
The enquiry can contain the current package plus a short list of decisions that need help. Keep commercial details such as quantity, delivery constraints and customer-supplied materials separate from engineering exceptions, but include both where they affect the scope. A reviewer should be able to identify the next useful action without interpreting an entire email history.
Standards, source context and limits
The references below support the stated package, design or process context. Apply a component manufacturer's guidance to its named device or family and confirm the exact drawing revision. A supplier application note is not a universal manufacturing rule, and a public standards scope is not the complete controlled standard.
Agree the governing documents, revision basis, acceptance requirements and exceptions with the responsible engineering and quality teams. The official IPC revision table is useful for checking document status; it does not by itself resolve a project's contractual requirements. This page does not reproduce paid normative tables or claim certification.
Archive photographs illustrate relevant boards, components or assembly activity. They are not proof of the current equipment inventory or a completed qualification for your project. The explanatory drawings and worked examples are original teaching aids. Confirm actual process availability and the proposed inspection scope during the project review.