PCB Assembly RFQ Checklist

A PCB assembly RFQ checklist aligns the design revision, bill of materials, placement data, quantities, sourcing responsibilities, testing and shipment requirements before a supplier prices the build. Send a coherent package and identify every unresolved decision. Use a budget estimate for incomplete designs; request a firm quote against an agreed scope. For service-critical repeat production, use 100% unit-level execution of the agreed functional test, with serial-linked results, as a procurement reference target. That target defines which boards are tested; the test procedure defines what is verified.

Why Incomplete RFQs Produce Incomparable Quotes

An incomplete PCB assembly RFQ leaves pricing decisions to the estimator. The assumptions can differ. One estimator may allow for component sourcing, repeated setups and electrical testing while another prices only assembly labor, even though both responses carry the same board name and order quantity.

Consider an order for 500 boards. One quotation assumes a single build with optical inspection. Another includes five production releases, firmware loading and a powered test fixture. Comparing only the unit prices obscures the difference. A missing DNP list can be worse: components intended to remain unpopulated may enter both purchasing and assembly.

Define the quotation stage. A budget estimate supports planning using documented assumptions. A firm quotation prices a defined revision and scope for a stated validity period, with exclusions and material conditions. Production release authorizes work against the accepted package. Keep those decisions separate. A firm price alone does not approve a design change or authorize material purchases.

The objective is a quote whose assumptions can be checked before an order is placed.

The Minimum File Set for a PCB Assembly RFQ

A PCB assembly RFQ needs enough information to identify the bare board, populated parts, placement and assembly instructions for the same build revision. The minimum is an information set, not a universal number of attachments: an intelligent manufacturing export can contain data that another workflow separates into several files.

Identify the Manufacturing Data and Release

Provide Gerber artwork with drilling information and fabrication notes, or agree an alternative manufacturing export such as ODB++ or IPC-2581. State board outline, dimensions in mm, layer stack-up, thickness, copper requirements, finish and any controlled-impedance requirements. Identify who supplies the bare PCB and who designs the assembly panel.

Create a manifest with File Name, Document Revision, Build Variant and Document Owner fields. Map the revisions explicitly. Files can carry different revision labels while describing one authorized build, but an archive named final-new.zip does not establish that relationship or tell an estimator which earlier instruction it supersedes. The referenced supplier’s assembly file guidance illustrates different submission formats.

Make the BOM and Placement Data Agree

Use explicit BOM columns: Manufacturer Name, Manufacturer Part Number, Reference Designators, Quantity Per Board, Part Description, Package Type, Population Status and Approved Alternates. Keep the full ordering suffix. A Distributor Part Number can support purchasing, but it should remain separate from the manufacturer’s part identity.

The placement export needs Reference Designator, X Coordinate, Y Coordinate, Rotation and Board Side fields, with Coordinate Units and Origin Definition stated. Verify orientation against the drawing. This matters particularly for polarized and bottom-side components because the receiver must interpret coordinates and rotation in the intended convention. The referenced supplier’s assembly file requirements describe the placement information.

For DNP positions, use an explicit population-status column or a controlled variant/DNP list. Keep the reference designators traceable even if the supplier’s import workflow omits them from the placement file. Reconcile the populated count before release.

Attach drawings for special operations: coating masks, adhesive, connector installation and mechanical hardware where applicable. Include schematics and test-point information for engineering review or electrical-test development. A schematic explains circuit intent. Released manufacturing data still defines the build.

Ten Checks for a Quote-Ready RFQ

A quote-ready RFQ passes ten checks covering identity, materials, build conditions and delivery. Use the good signals below as release evidence; each red flag identifies an assumption that must be resolved or explicitly bounded in a budget estimate.

These checks assess the package, not the supplier’s overall qualification. A supplier may identify a genuine design conflict during review even when the files are complete. Assign that conflict to the engineering owner and record the disposition before comparing revised quotes.

State Quantities, Batch Splits and Repeat-Order Expectations

An RFQ should distinguish the first build, alternative order quantities, production releases and nonbinding forecast. State whether quantities mean individual assembled boards, panels or complete modules. Otherwise, both the material purchase and the assembly setup may be priced on the wrong basis.

The following quantities are illustrative comparison scenarios, not standard price breaks:

A 500-unit build stored for five shipments is different from five separate 100-unit builds. Identify the priced scenario. State whether setup, testing, storage and freight repeat, and identify any difference between pilot and production BOMs.

Include a forecast period and confidence level. For example, an expected annual demand of 1,000 units can inform component planning without authorizing a 1,000-unit purchase. State who must approve minimum-order quantities, excess material and noncancelable purchases.

Separate arrival dates from ship dates. Request feasible dates against the file-release, material-availability and first-article approval assumptions. Define partial-shipment rules. State the minimum useful quantity and which revisions may be shipped together.

Define Sourcing, Substitutions and Consigned Materials

A sourcing instruction must name a purchasing owner for every PCB, component and module. Define the arrangement explicitly. In this RFQ, turnkey means the supplier sources the agreed materials; consigned means the buyer supplies them; partial turnkey divides responsibility by item.

These labels do not automatically include firmware development, fixtures, display bonding or enclosure assembly. List those operations separately. For each supplier-purchased BOM line, specify approved manufacturers or sources, permitted alternatives and the person authorized to approve changes.

Control Substitutions at Part-Number Level

Distinguish an approved alternate from a proposed substitute. A proposed substitute needs the relevant electrical, package, environmental and software review before approval. Matching resistance, capacitance or footprint alone is insufficient. A changed regulator, memory device or touch controller can alter behavior while fitting the same land pattern.

Price substitutions separately. Keep the original BOM basis visible until the exact alternative and its consequences have been approved by the engineering owner, including any required firmware change or repeat validation. A purchasing note should not silently revise that baseline.

Make Consignment Quotable

List supplied part numbers, usable quantities, packaging format, condition, arrival dates and any handling restrictions. Ask the assembler to specify required setup allowances by part and packaging type; there is no universal extra-parts percentage suitable for every build.

Agree incoming count checks, shortage notification, moisture-sensitive handling, responsibility for damaged or unusable material and the treatment of unused stock. If bare PCBs are consigned, include panel drawings and identify who resolves fabrication defects. The RFQ should also state whether excess material is returned, held for the next release or disposed of only under buyer authorization.

Specify Testing, Acceptance and Shipment Deliverables

A PCBA acceptance scope should define workmanship, electrical verification, special processes and the evidence shipped with the product. Name the applicable document revision and product class, then add the circuit-specific test requirements. “IPC compliant” and “fully tested” do not define a comparable quotation.

Select the Applicable IPC Class and Revision

The base product classes are Class 1, Class 2 and Class 3. Class 1 addresses applications primarily requiring the completed assembly to function. Class 2 addresses sustained service where interruption is undesirable but not critical. Class 3 addresses critical performance or availability, potentially under harsh conditions. The publisher’s J-STD-001J public scope excerpt describes this classification.

Choose the class from end-use requirements. A premium purchasing strategy does not make Class 3 appropriate for every control board. Record the agreed edition and any applicable addendum; do not leave the contract basis as an undefined “latest standard.”

IPC J-STD-001J concerns soldered assembly materials, processes and requirements; IPC-A-610J concerns post-assembly acceptance. These are separate documents that can be specified together, as described in the publisher’s 2024 revision announcement. Neither designation substitutes for a functional-test procedure.

Define the Actual Test Work

Identify the required visual/AOI, hidden-joint inspection, accessible electrical checks and functional tests. Separate inspection coverage from electrical coverage. In-circuit testing and functional testing assess different aspects of an assembly, as outlined by Keysight’s ICT overview.

For each test, specify the supply conditions, stimulus, load, measurement points, limits, sequence, test duration where relevant and pass/fail rule. State which units are tested, who supplies or develops the fixture, and who maintains the program. Separate fixture development from recurring test labor.

For service-critical repeat production, request 100% unit-level execution of the agreed functional test with serial-linked results at the procedure’s defined power, loading and ambient conditions. This reference target means every shipped board runs that routine. It does not mean every possible fault is detectable. Quote environmental qualification or extended stress screening separately when required.

Specify Programming and Shipment Records

Identify the firmware release. Include its programming interface, configuration rules and verification method, then supply a checksum or other agreed image identifier through the controlled package. Keep credentials and private signing keys outside ordinary RFQ attachments.

Require the agreed certificate of conformity, inspection summary, serial/lot list and test results. Define packaging, ESD protection, connector/display protection, labels and shipment identification. State whether coating, cleaning or calibration records are included. Assign receiving acceptance and exception approval to named roles so a conforming shipment has a clear release path.

Resolve Missing Inputs Before Requesting a Firm Quote

Missing RFQ inputs should have an owner, a pricing consequence and a release check. A budget estimate can carry bounded assumptions; a firm quotation needs agreement on every unresolved item that can materially change cost, schedule or acceptance. Completion is about decisions, not attachment count.

Use this matrix as the missing-information checklist. Each row names the evidence needed to close the gap.

Follow a Six-Step RFQ Handoff

1. Choose the Quotation Stage. Purchasing labels the request budgetary or firm and states the decision it must support. Engineering lists open design decisions.
2. Establish the File Baseline. Engineering creates the manifest and reconciles BOM, placement and DNP data. Quality identifies the governing acceptance documents.
3. Close the Ownership Gaps. Purchasing assigns material owners; test engineering assigns fixture, procedure and firmware responsibilities. Each open item receives a closure date.
4. Issue the Same Package. Send each bidder identical revision-controlled data and quantity scenarios. Share subsequent clarifications consistently so quote bases remain comparable.
5. Reconcile the Responses. Compare inclusions, exceptions, unit basis, setup/NRE, test development, delivery assumptions, currency, quote validity and excess-material exposure. Request revised pricing for changed scope.
6. Release the Accepted Baseline. Record approvals and tie the purchase order to the accepted quotation, manifest and deviations. Authorize procurement and production through the agreed release process.

The handoff is: Define scope → Reconcile files → Assign owners → Request pricing → Close exceptions → Release the accepted package. An unresolved issue returns to its owner; it should not disappear into an email thread.

If a connector choice is still open, request an estimate with that line identified and its price basis stated. If the acceptance test is undefined, ask for a bounded testing allowance or a separate development quotation. Neither response makes the missing engineering decision disappear.

A Copy-Ready RFQ Template with an HMI Module Appendix

A reusable PCBA RFQ combines a short request with a controlled attachment manifest and explicit commercial and acceptance fields. Copy the field names below and replace the completed example values with the project’s released information. The example is fictional; its document identifiers, dates and quantities illustrate what the buyer supplies.

Core RFQ: Completed Example

Subject: PCBA RFQ — CB-24 Rev C — 20, 100 and 500 assembled units

Please quote the following scope, identify exceptions against each requirement, and separate recurring charges from setup, tooling and test-development charges.

The electrical values illustrate a test instruction. Use circuit-specific limits. A complete procedure also defines measurement method, stimulus, sequencing and duration, so copying the example voltage and load into another board’s acceptance plan would leave important decisions unresolved.

HMI Module Appendix: Add to the Same RFQ

An HMI appendix should identify the selected display, touch system, connections and mechanical integration without creating a second procurement workflow. Carry the same project ID and identify the HMI variant. Module selection and host architecture should already have an engineering owner.

For a concrete field example, Newhaven’s NHD-5.0-800480TF-ASXN-CTP datasheet identifies a 5.0-inch, 800 × 480 display with separate 24-bit RGB and I2C touch interfaces. The display connector has 40 pins at 0.5 mm pitch; the touch connector has 6 pins at 1.0 mm pitch. Those separate definitions explain why “5-inch touchscreen” is inadequate for an RFQ.

Record whether bonding, cover glass, keypad, harness and enclosure work are included or excluded. Specify who provides host software and who checks display orientation and touch-coordinate mapping in the installed assembly. These boundaries make the integration effort quotable without substituting for HMI engineering selection.

Eight Signals That Require Escalation

An RFQ should return for clarification when an unresolved item could change the delivered product or invalidate the comparison. Escalation means obtaining a documented decision from the responsible owner before the affected commitment is made.

Reject a quote as non-comparable if material exceptions remain hidden or the supplier declines to identify what its price includes. A documented exception can be evaluated. An unstated assumption cannot.

Frequently Asked Questions

A PCB assembly RFQ is ready for firm pricing when its build identity, purchasing scope, quantity basis and acceptance requirements agree. These answers address common gaps before the package reaches the estimator.

Prepare the Package for Review

Prepare the RFQ by assigning one owner to the manifest and one owner to each open decision. Reconcile the BOM and DNP list, select quantity scenarios, define material responsibility and attach the acceptance procedure. Use the missing-input matrix to decide whether the request is budgetary or ready for firm pricing.

For a JASPER enquiry, start with the project scope covered by PCB assembly services and send the controlled package with the HMI appendix when integration is included. Ask for a response that maps price, exclusions and delivery assumptions to that exact revision.