PCB Assembly Guidelines
Turn a finished layout into a clear, build-ready assembly package. Align the files, materials and verification plan before the first board reaches the production line.
- Define the product
Revision, quantity and fitted variant
- Define the process
Packages, materials and assembly notes
- Define the evidence
Inspection, programming and test records
Assembly readiness is more than a Gerber export.
An assembly handoff should explain what is fitted, where it is fitted and how the completed product will be evaluated. A BOM identifies the parts; placement data identifies their positions, sides and rotations.
Use this guide as a proposed release workflow. Resolve conflicting files and open decisions before authorizing a build. Drawing-specific requirements, component documentation and the agreed manufacturing process take priority over generic advice.
- DFM
- Can the bare board and its features be manufactured?
- DFA
- Can the specified parts be assembled, inspected and reworked?
- DFT
- Can the required faults and product functions be tested?
What to resolve before release
Use these review prompts with the actual design, component documentation and agreed manufacturing process.
Freeze the fitted configuration
Give the project, board, BOM and assembly drawing a common release identity. List do-not-populate positions explicitly and distinguish mutually exclusive variants. Record who may approve substitutions.
Validate packages against actual parts
Check the complete manufacturer part number and package drawing, not only a generic library name. Review pin numbering, polarity, exposed pads and mounting features against the device documentation.
Agree the assembly sequence
Identify single- or double-sided SMT, through-hole steps, hand-installed items and any parts fitted after reflow. Flag connectors, batteries, optics, switches or other items with process restrictions.
Treat the stencil as a separate design
Copper lands, mask openings and paste apertures serve different purposes. Ask for a package-by-package review of thermal-pad printing and dense packages rather than assuming every aperture must match the copper.
Keep sensitive material identifiable
Include package handling requirements and lot information. The exact device determines its moisture sensitivity and allowed temperature exposure; an attractive dry-pack bag alone does not establish its history.
Define verification before ordering
Name the required inspection and electrical tests, programming revision and records. J-STD-001 concerns soldering requirements; IPC-A-610 concerns assembly acceptability. Neither is a substitute for a product-specific functional test plan.
What belongs in the release package?
A suggested handoff structure. Export formats and delivery methods must be agreed with the project team.
On a small screen, scroll the table horizontally to see every column.
| Deliverable | Include | Resolve before release |
|---|---|---|
| BOM and fitted variant | Manufacturer, exact MPN, references, quantity per assembly, package and DNP list. | Ambiguous descriptions, duplicate references and unapproved alternates. |
| Placement data | Reference, X/Y coordinates, side, rotation, units and origin convention. | Bottom-side conventions and pin-1 orientation. |
| Board data | Fabrication output, drill information, board outline and controlled revision. | Mismatch between panel data and assembly data. |
| Assembly drawing | Polarity, connectors, hardware, special installations and process notes. | Requirements that appear only in email or an old photograph. |
| Programming package | Released image, version, checksum, interface and verification sequence. | Programming before or after assembly; handling of unique data. |
| Inspection and test plan | Methods, limits, fixtures, coverage gaps and records to retain. | What is included in the quote and what needs development. |
Keep the approved project requirements in control. Record uncertainties, agreed exceptions and the supporting evidence before the affected operation is released.
Small discrepancies become expensive build questions.
A correct part placed at the wrong rotation can still match a BOM. A correct board revision fitted with an old firmware image can still look perfect. Reconcile the complete release package as one configuration, not as independent attachments.
- Polarity review
- Cross-check pin 1, diode orientation, LED polarity and connector mating direction.
- Mechanical review
- Check component height, mounting screws, enclosure fit and cable access.
- Change review
- Record the reason, owner and approval for every manufacturing deviation.
Move from open questions to controlled decisions.
These steps organize a project review. They do not replace your formal release or acceptance process.
Prepare
Collect the design, BOM, variant and process restrictions.
Review
Resolve layout, material and inspection questions.
Approve
Freeze the configuration and acceptance plan.
Retain
Keep the agreed build records and final deviations.
Record the review.
Keep the evidence.
12 checks for this topic. Record status and notes, then export a text copy for your project discussion. A completed checklist is not certification or production approval.
Session only. Nothing is saved automatically or transmitted. Export before closing or reloading. “Reviewed” records evaluation—not a pass verdict. Explain blocked and not-applicable items in the notes.
Showing 12 of 12 checks. Export always includes all checks.
The board, BOM and drawing share a controlled release.
Record the revision identifiers.
The fitted variant and every DNP position are explicit.
Compare the schematic, BOM and placement list.
Units, origin, side and rotation conventions are documented.
Verify at least one asymmetric package on each fitted side.
MPNs and footprint/package identities have been checked.
Include package options and terminal layouts.
Alternates require a named approval.
Do not substitute by value alone.
Moisture, ESD and temperature restrictions are known.
Use the exact device documentation.
Panel rails, tooling and support requirements are agreed.
Review the chosen assembly line.
Paste, mask and exposed-pad features have been reviewed.
Flag dense and bottom-terminated packages.
Special installations and post-reflow parts are documented.
Include torque, adhesive and cure requirements where needed.
Inspection methods and acceptance documents are named.
Specify revision, class and applicable addenda.
Firmware, fixtures and test limits are released.
Identify exclusions and uncovered functions.
Open issues have owners and a release disposition.
A reviewed checklist is not automatic manufacturing approval.
No checks match these filters. Change a filter to view other items.
Export your checklist and resolve outstanding items with your engineering team before production. Confirm any changes through your normal approval process.
Practical answers
before release.
Use these answers to frame the discussion. The approved project requirements remain the authority for the build.
Are Gerber files enough for PCB assembly?
No. Prepare the BOM and placement data as well as an assembly drawing and relevant process or test instructions. Gerber data alone does not identify every part or its fitted configuration.
Is there one component-spacing rule for every assembly?
No single spacing value covers all packages, placement tools, soldering processes and rework needs. Agree the relevant clearances with the assembler and validate them against the mechanical design.
Should the drawing specify an IPC class?
Where the project uses IPC acceptance requirements, identify the agreed class, document revision and applicable addenda. Also define customer-specific requirements and precedence when documents conflict.
Does a no-clean process eliminate all cleaning decisions?
No-clean is not a blanket instruction to ignore residues. Consider the flux process, product environment, electrical sensitivity and any coating or bonding operations. Agree the validated cleaning or residue-control approach.
Does completing this guide submit an order?
No. The review below works locally in your browser. Export the notes and share them through your agreed GlobalWellPCB project contact; nothing is uploaded or submitted by this page.
Technical references & scope
- KiCad — PCB Editor: Manufacturing Outputs and Design Rules
KiCad documentation for PCB manufacturing outputs, component positions and design rules.
- Texas Instruments — SMT and packaging application notes
Starting point for the application note appropriate to the actual package.
- Analog Devices — QFN PCB design and SMT assembly guidance
Package-specific discussion of pads, paste, thermal lands and inspection; not a universal process recipe.
- Texas Instruments — quality, reliability and packaging FAQs
Device-specific MSL, storage and package-temperature information.
- IPC — J revisions of the two assembly standards
Public explanation of the different roles of J-STD-001 and IPC-A-610.
- IPC Standards — official revision register
Document names, revision history and addendum compatibility; checked 28 September 2026.
Use these engineering references alongside your component documentation and the standards specified for your order. Share your completed checklist with us to confirm assembly, testing and material requirements.