Engineering guides / PROJECT FIELD GUIDE

PCB Assembly File Requirements

Build a consistent data package before requesting an assembly quote.

Prepare your next step Compare the choices

TAKE THIS PAGE INTO YOUR NEXT REVIEW

Less guesswork. A clearer release.

Understand the relevant choices
Compare requirements and next steps
Download useful notes for your review

ENGINEERING → PROCUREMENT → PRODUCTION

THE PRACTICAL ANSWER

What to know before you decide

A PCB assembly package connects the physical board to its components, placements and acceptance instructions. The essential issue is consistency: BOM, placement file, assembly drawing, board data and firmware must describe the same revision and population variant. Part numbers alone cannot resolve an ambiguous polarity drawing. Use a file manifest and release note to identify the authoritative documents, approved alternatives and decisions still requiring engineering approval.

01 / DECISION GUIDE

Make the trade-offs explicit

Make component identity explicit

List manufacturer names and full manufacturer part numbers rather than distributor codes alone. Reconcile quantities with reference designators and mark do-not-populate rules. Ratings and package descriptions help find inconsistencies, but do not replace exact ordering codes. Where alternates are permitted, identify the approved part and who authorizes any additional substitution before it enters the build.

Check coordinates against physical orientation

State units, board side and origin for the placement export. Verify several asymmetric parts against the drawing and footprint. Rotation conventions differ, so a numerical angle is not sufficient proof of orientation. Include pin-one and polarity indicators where the assembled body hides the silkscreen, and flag any package whose convention needs explicit review.

Document operations outside placement

Include hand-soldered connectors, adhesives, mechanical hardware, heatsinks, labels and programming. Assign responsibility for supplied materials and each operation. Functional instructions need safe input limits, expected outputs and pass criteria. When programming is required, provide the controlled image and its identity rather than a link to a folder that can change without a release record.

Release a manifest instead of competing finals

List file names, purpose and revision in a short manifest. Remove superseded variants from the released archive while retaining them in your own history. Ask reviewers to identify discrepancies by reference designator or document location. Issue a new release identifier for corrected data so a late attachment cannot silently replace only part of the approved package. For example, a second product variant may use the same bare board but omit a sensor, fit a different resistor network and load different firmware. A separate variant identifier should connect all three differences. Check that placement data, labels and test expectations agree with that identifier. A reviewer should be able to reconstruct the intended assembly from the release package without searching through previous emails or inferring which version the latest spreadsheet represents.

02 / SIDE BY SIDE

Compare the choices

PCB assembly files checklist BOM pick and place — planning considerations
Choice or scope	Useful when	Review before release
BOM	What to buy and fit	MPNs, references and variants
Placement file	Automated component location	Units, origin, side and rotation
Assembly drawing	Orientation and exceptions	Polarity and mechanical notes
Board package	Bare-board construction	Matching revision
Programming/test files	Functional configuration	Image identity and limits

03 / REVIEW BEFORE RELEASE

Questions that prevent rework

Using stock codes only

Keep manufacturer and exact ordering code.

Burying DNP rules in email

Put population rules in controlled documents.

Uploading several final archives

Release one manifest and one authoritative package.

04 / COMMON QUESTIONS

Get a clear answer

Are Gerbers sufficient for assembly?

They describe board artwork, not the complete assembly. Supply component identity, placement, orientation and the additional mechanical or test instructions. Confirm accepted export formats and the data needed for the actual operations in your quotation.

How should alternates be listed?

Give exact manufacturer part numbers and the affected reference designators. State conditions and approval restrictions. A phrase such as equivalent acceptable leaves electrical and mechanical decisions unresolved and can make a later substitution hard to trace.

How do I control assembly variants?

Assign each variant an identifier and explicit population rules. Confirm whether the bare board is identical, then align firmware, labels and test instructions with the correct variant. Do not use an unmarked combined BOM as the only configuration record.

Technical references

Check each source’s scope and revision against your project requirements. Confirm the proposed construction with your manufacturing partner.

YOUR PROJECT / YOUR NEXT STEP

Build a useful project brief

Identify gaps in the assembly release package. This tool plans a review; it does not inspect uploaded CAD files.

Use this planning aid to prepare a review. It does not approve a design or estimate a price. Selections are processed locally and are not submitted by this tool.

WORK WITH YOUR OWN DATA

Check a BOM CSV before sharing

Paste CSV columns for MPN, Quantity and References. This local check finds missing values, duplicate reference designators and quantity inconsistencies. It does not check component availability, authenticity or whether a selected part fits your design.

Your CSV is processed locally. It is not sent to Swimbi or stored by this tool.

CONTINUE YOUR REVIEW

Useful next steps

01 / Services