PCB & PCBA Engineering Blog | OrinewPCB

NRE Costs in PCB Assembly: Setup, Reuse & Reorder Checklist

highqualitypcb — Sun, 01 Nov 2026 22:55:26 +0000

PCB ASSEMBLY PROCUREMENT · SMALL BATCH & HIGH MIX

Quick answer: NRE means non-recurring engineering: work needed to prepare a specific product or manufacturing release, rather than a charge for making each board. In a PCB assembly quotation, separate that initial work from setup repeated for each production run and recurring per-board work. Ask what each fee delivers, which revisions and variants it covers, what can be reused, and what changes trigger another charge. A line labeled “setup/NRE” does not answer those questions by itself.

A small PCBA order can have a modest component bill yet still need stencil preparation, manufacturing programs and a usable test arrangement. The right purchasing question is not simply whether the first order has a setup fee. It is what you receive for that fee, and what you will pay again on the next build.

This guide helps hardware engineers, product managers and purchasing teams review NRE and repeat-order conditions for small-to-medium, high-mix turnkey PCB assembly. For the wider material and production cost picture, use our PCB assembly cost breakdown. This article focuses specifically on initial engineering, reusable tooling and repeat-run charges.

Preparing a build now? Send your files, quantities and variants for a turnkey PCBA and BOM review, and ask for initial and repeat-order costs to be identified separately.

1. NRE, run setup and unit cost are different questions

In product development, non-recurring engineering can include the engineering effort needed to develop, test and bring a product into production. An assembly supplier’s quotation may cover a much narrower manufacturing-preparation scope. Do not assume that an assembly NRE line includes circuit design, firmware development, compliance testing or product qualification.

Use three categories when comparing quotations:

Cost category	What it may cover	Question to settle
Initial engineering and tooling	Product-specific data preparation, stencil creation, fixture development or test-software development, where included in the agreed scope.	What deliverable is being created, for which release, and under what reuse conditions?
Production-run setup	Preparing and verifying a line or station for a particular run, including loading, configuration and changeover work as quoted.	Does this charge recur for each order, lot, side, variant or production release?
Recurring unit work	Bare boards, fitted components, assembly, programming, agreed inspection/test and packing for each unit.	What is included per delivered acceptable board, and what is excluded?

Commercial labels vary. Some suppliers combine these categories, include preparation in a unit price or waive a separate fee under stated conditions. Ask for the scope and recurrence rule rather than judging the offer by the label alone. A reusable program does not mean a production line stays configured between your orders.

2. Review the deliverables behind the engineering charge

An actionable NRE line connects a task to an output and an acceptance point. “Engineering: included” is harder to manage than “manufacturing data reviewed against assembly A100 revision B; unresolved items returned for approval before release.” The latter wording identifies a boundary without implying that every design problem has been solved.

Data preparation: identify the released PCB package, assembly drawing, placement data, BOM and variants used to create manufacturing outputs. Clarify whether design edits are included or need separate approval.
Stencil: identify the relevant board/panel and side, the approved paste-aperture design, and any process assumptions. The stencil belongs to a controlled manufacturing configuration, not just a product nickname.
Inspection and assembly programs: clarify which variants and processes the preparation covers, and which changes require review or revalidation.
Programming setup: define the target device, approved image/configuration, access method and required verification. Loading a supplied image is different from writing or debugging the product’s firmware.
Test development: distinguish developing a fixture or test sequence from running that sequence on every delivered board.

For programming, correct device selection, connection, power and access conditions matter; a firmware file alone is not the complete station handoff. Our PCB programming release checklist lists the engineering inputs. For test-development work, provide the functional test plan and identify who approves the station and acceptance limits.

3. Ask what actually survives into the repeat order

Reuse should be tied to an identifiable, compatible release and usable tooling. An unchanged product name does not establish that the stencil, fixture, software and production instructions are still suitable.

Original OrinewPCB purchasing illustration. This is a decision framework, not a customer project or a promise that a particular fee will be waived.

Item	Possible reuse basis	Reason to review again
Paste stencil	Approved aperture design, board/panel identity, side and process remain suitable; stencil is available and serviceable.	Changed pads, panel arrangement, paste requirements, physical condition or incompatible printer setup.
Assembly or inspection program	Controlled data, packages, placement, orientation and variant instructions remain applicable.	Changed BOM/placement, a package substitution, new variant or changed equipment/process.
Programming arrangement	Device, interface, wiring, approved images and required verification remain compatible.	New device/image/security configuration or different access and power requirements.
Functional fixture and test software	Mechanical fit, connections, approved limits and tested functions remain applicable; station readiness is checked.	Changed connectors, test points, firmware behavior, functions, loads or required evidence.

This is a review checklist, not a rule that every change requires completely new tooling. Ask the supplier to identify what can be retained, what needs an update and how that decision affects cost and release timing. Use a controlled PCB assembly engineering change when the approved configuration changes.

Before placing the first order, also agree the practical stewardship of reusable items: identifier and revision, storage location and period, condition checks, maintenance/replacement, and what files or physical items can be returned or transferred. Paying an NRE invoice should not be treated as a substitute for a written agreement about ownership, access and reuse.

4. Compare first and repeat orders with a transparent calculation

A useful comparison keeps initial engineering, run setup and per-board work visible:

Illustrative order total = initial engineering/tooling applicable to this order + run setup applicable to this order + (delivered quantity × recurring unit cost) + separately agreed charges.

Allocated cost per delivered board = that order total ÷ delivered quantity.

The example below uses fictional planning numbers in USD. It is not an OrinewPCB price, industry benchmark or quotation. It assumes the same approved product and scope, no new engineering on the repeat order, and a constant unit cost solely to show the arithmetic. Freight, taxes and other exclusions are not included.

Planning scenario	Initial / run / unit inputs	Order total	Allocated per board
First build: 50 boards	$600 initial + $150 run setup + 50 × $30	$2,250	$45.00
Repeat: 50 boards	$0 new engineering + $150 run setup + 50 × $30	$1,650	$33.00
First build: 200 boards	$600 initial + $150 run setup + 200 × $30	$6,750	$33.75

The calculation demonstrates cost allocation, not a reason to buy more boards than needed. Material availability, unit-price breaks, cash tied up in stock, revision risk and the delivery plan can change the purchasing decision. For a high-mix order, compare each variant’s quantities and preparation needs; do not divide one setup fee across all variants unless the quoted scope actually permits it.

If a supplier spreads NRE into the unit price, ask for the quantity or commitment assumed and what happens on a repeat order. Avoid counting the same tooling cost both as a separate line and inside the unit price. Compare total payable amounts for the same scope, not only the displayed assembly price.

5. Use this checklist before approving the quotation

Freeze the comparison baseline. Give every supplier the same PCB revision, BOM/variant, quantity, shipped state and required quality/test scope.
Separate the three cost categories. Ask which items are initial, which repeat per run and which apply to every board.
Name the deliverables. Record the stencil, fixture, manufacturing-data or test-software output, applicable revision and required approval.
State the reuse conditions. Identify what is retained, for how long, and when an update or replacement is chargeable.
Price a realistic repeat scenario. Request the same revision and quantity again, plus any likely alternate quantity or variant. Mark forecasts separately from committed orders.
Expose exclusions. Clarify design corrections, development/debugging, unusual materials, extra inspections, retests after an approved change, storage and shipment charges.
Link payments to an agreed scope. Define any review, delivery or approval milestones without assuming that “NRE paid” means the product is production-ready.
Confirm the release and delivery dependencies. Identify pending approvals, components, tooling and test inputs before treating a requested date as a confirmed shipment date.

Record unresolved questions in the quotation review. A missing answer is an open scope item, not automatically a free service. Equally, a separate engineering line is not evidence of an unreasonable charge; assess the work and deliverables it represents.

6. Reduce avoidable preparation work without weakening quality

The most useful opportunities usually come from a stable, complete handoff. Align fabrication files, assembly drawings and BOM variants before release. Identify approved alternatives before a shortage forces a package change. Supply the firmware and test requirements early enough for the supplier to review station needs with the assembly quote.

For low-volume PCB assembly, ask whether a proposed test approach suits the quantity, access and required coverage. A lower tooling investment is only useful if the agreed checks still address the product’s requirements. Bare-board electrical testing, optical inspection, structural electrical testing and functional testing answer different questions; they should not be removed from scope simply to make quotations look comparable.

For multiple variants, provide a clear fitted/DNP matrix and discuss shared tooling where compatible. Do not assume that all variants using the same bare PCB can share every program or test sequence. If an engineering change is likely soon, compare the cost of a limited pilot with the risk of committing to tooling or materials that may become unsuitable.

These steps help suppliers quote the intended job. They do not guarantee a particular saving, price or lead time.

7. What to send OrinewPCB for an initial and repeat-build review

OrinewPCB provides one-stop PCB assembly, combining PCB manufacturing, component sourcing and assembly, with particular strengths in small-to-medium, high-mix builds. We review the complete build scope so that purchasing and engineering can discuss material, manufacturing and delivery requirements together.

PCB fabrication outputs and specification; assembly drawing and placement data.
Exact manufacturer part numbers, quantities, fitted/DNP variants and approved alternatives.
Initial quantity, likely repeat quantities and timing; distinguish forecasts from commitments.
Required shipped state: assembled, programmed, tested, coated or integrated, as applicable.
Programming/test requirements, fixture information and any existing reusable tooling.
Required inspection evidence, traceability and acceptance requirements.
Requested delivery date and destination, plus any missing files or unresolved decisions.

Our component policy is to supply and assemble with 100% new, original and genuine electronic components. Cooperation with component manufacturers and distributors supports project-specific sourcing reviews; actual availability, price and delivery are confirmed against your BOM and order scope. Sourcing-only inquiries can start with our electronic components catalog.

We emphasize quality through our nine-stage PCBA quality workflow and 100% flying-probe testing of the bare PCBs we manufacture. Those are distinct scopes: a bare-board electrical result does not replace an agreed assembled-board functional test. State the project-specific inspection, test and records you need. More brand information is available at OrinewPCB.

Know the first-build scope—and the repeat-build conditions

Send your PCB files, BOM variants, quantities and test requirements. Ask us to review genuine component sourcing, assembly, initial preparation, recurring work and the delivery plan in one coordinated turnkey quotation.

Request a Turnkey PCBA & BOM Review

Include any existing tooling and anticipated revisions. Final pricing, reuse terms and lead time depend on the reviewed files and agreed scope.

PCB assembly NRE and setup-cost FAQ

What does NRE mean in a PCB assembly quote?

PCB Assembly ECO: BOM Revision & Change-Control Checklist

highqualitypcb — Fri, 30 Oct 2026 00:16:44 +0000

HIGH-MIX PCB ASSEMBLY · ENGINEERING & PROCUREMENT

Quick answer: To change a PCB or BOM after a turnkey assembly order has started, issue a controlled engineering change order (ECO) that identifies the old and new configurations, the affected orders and material, the approved disposition of existing work, and the exact point at which the new revision takes effect. Release matching production files and obtain supplier acknowledgment before the affected work resumes. A replacement BOM attachment alone does not answer those questions.

A connector changes, a component becomes unavailable, or a prototype reveals a circuit improvement. The engineering edit may be small, but purchasing, bare boards, assembly programs, firmware, fixtures and labels can all be at different stages. This guide explains how to control that revision cutover without leaving the assembly supplier to guess which configuration to build.

Use the ECO checklist, disposition table and illustrative example below for small-to-medium, high-mix PCBA orders. If a current order needs a revision review, send the released package, proposed change and affected quantities for a turnkey PCB assembly and BOM review.

1. What an ECO must do for a PCB assembly order

An engineering change order is a controlled authorization to change a released product configuration and implement the change under defined conditions. Organizations may use different names or approval workflows. The important questions are what changes, why it changes, who approves it, which units are affected, and how implementation is verified.

A request to investigate a change is not the same as authorization to build it. An engineering change notice can communicate an approved change, but its name alone does not establish the required approval. Agree the customer’s and supplier’s authority, release states and acknowledgment process.

A CAD ECO is only one part of the handoff. Design tools can generate an ECO to synchronize schematic and PCB differences. That does not by itself update the supplier’s purchased material, work orders, manufacturing outputs, firmware or inspection instructions. Treat the production release as a separate, reviewed handoff.

The objective is a known as-built configuration: which approved PCB revision, assembly/BOM variant, firmware and controlled instructions were used for the units being shipped. A revision letter without those relationships is incomplete.

2. First contain the affected work and identify the baseline

Before sending replacement files, ask the supplier for the status of the affected orders. Identify the part number, current released revision and proposed revision. Then establish what has already been bought, fabricated, kitted, assembled, programmed, tested or shipped. The response should use actual quantities and locations, not an assumption that the whole order is at the same stage.

Define a targeted hold. State which orders, variants, materials or operations must stop pending a decision. Do not assume an email automatically stopped purchasing or production.
Preserve the old release. Keep the exact files and approvals used for work already performed. Do not overwrite the only record of an earlier build.
Identify current commitments. Ask about supplier orders, noncancelable items, fabricated boards, tooling and scheduled operations relevant to the change.
Separate affected and unaffected work. If another variant can continue, document that boundary and the basis for the decision.
Assign an owner and response point. Engineering, purchasing, quality and production need a clear route for resolving open decisions.

If units have already shipped, include their identities and destination in the impact assessment. Product engineering and the responsible quality team should decide any field action; a new production revision does not automatically resolve the status of delivered units.

3. Release one matched configuration, not a mixture of files

BOM revision control is the discipline of identifying, approving and retaining the correct bill of materials for a configuration. For PCBA, it must stay aligned with the rest of the manufacturing package. A fitted resistor value, an optional connector and a firmware setting can distinguish assemblies made on the same bare PCB.

Controlled item	Check before release	Evidence to retain
Assembly identity	Assembly number, revision, variant and required shipped state. Distinguish the assembly revision from the bare-PCB revision.	Approved change record and configuration manifest.
BOM and approved parts	Manufacturer, exact MPN, quantity, reference designators, DNP/fitted state and allowed alternatives for each affected line.	Released BOM and an old-to-new comparison.
Bare-PCB outputs	Whether copper, drilling, stackup, finish, marking or other fabrication requirements changed.	Released fabrication package and its revision identity.
Assembly outputs	Placement data, footprint/orientation, assembly drawing, special operations and variant instructions.	Matched assembly release and supplier setup review.
Programming and test	Approved firmware/configuration, programming method, test applicability, limits and fixture impact.	Released programming/test identities and change verification results.
Marking and shipment	Unit/batch identification, labels, packing and how mixed revisions will be separated if permitted.	As-built records and agreed shipment documentation.

Provide a release manifest listing each file or controlled document and its revision. Revision labels need not all use the same letter; their approved relationship must be unambiguous. A checksum can help identify the exact file, but it does not replace engineering approval or prove technical correctness.

For detailed file preparation, use the PCB assembly drawing guide. For substitution authority, link the change to the approved manufacturer list and BOM alternatives rather than relying on a general “equivalent parts allowed” note.

4. Define effectivity: exactly where the change starts

Effectivity specifies the assemblies or production boundary to which an approved change applies. Depending on the project’s identification system, that can be a work order, lot, serial-number range or another explicit boundary. “Use the latest BOM from Monday” can be ambiguous when multiple orders, time zones and material stages are involved.

Original engineering planning illustration. The gates describe a change-control workflow, not a customer case or a mandatory certification procedure.

Define the last accepted old configuration and the first authorized new configuration. Include variant applicability and any exclusions. If serial numbers are assigned later in production, agree a usable work-order or lot boundary first and retain the relationship to final unit identifiers.

Keep the commercial and technical decisions connected. Approval of a revised unit price does not automatically authorize a design change. Likewise, engineering acceptance does not automatically resolve cancellation charges, extra material, rework costs or the new delivery plan. Confirm both before implementation.

5. Decide what happens to existing material and WIP

Work in process (WIP) includes units that have started manufacturing but have not completed the released process. A change may affect bare boards, loose components and partly assembled units differently. Record a separate disposition for each affected state.

Current state	Decision to authorize	Check before proceeding
Components on order or in stock	Use for the old build, retain for another approved use, return/cancel where possible, or otherwise segregate.	Exact MPN, ownership, commitments, quantity and traceability.
Fabricated bare boards	Use only if approved for the target assembly, retain for the old configuration, or apply an approved alternative disposition.	Layout/footprint compatibility and any electrical or marking impact.
Kitted or partly assembled units	Finish the old configuration, re-kit/rework under approved instructions, or hold.	Physical segregation, component removals/additions, setup changes and acceptance.
Completed or tested PCBA	Accept as the old revision, rework and reverify where authorized, or hold pending review.	Firmware, labels, test coverage and retained old/new configuration records.
Shipped units	Escalate for product/quality impact review and an approved field decision when required.	Which delivered units are affected and who owns customer communication.

“Use as is” and “rework” are decisions requiring the appropriate authority; neither should be inferred from a supplier’s available stock. Rework instructions should identify the permitted operation, acceptance checks, marking and records. Rework feasibility and the necessary verification depend on the actual design and condition.

6. Example: a BOM-only change in a high-mix order

Illustrative scenario, not a customer case: an assembly uses bare PCB revision C and fitted BOM revision B. Engineering proposes BOM revision C for one variant. Some units are already assembled, some are kitted and the remainder have not started. The bare-PCB artwork is believed unchanged, but that still needs review.

Identify the delta. List affected reference designators, old/new exact MPNs, fit state and the reason for change. Review package, pinout, electrical behavior and any firmware or test implications.
Review the whole package. Confirm whether PCB files, placement, drawings, programming or tests need updates. “BOM-only” is a conclusion from the review, not an instruction to ignore those items.
Set a usable cut-in. For example, authorize the new configuration on a named new work order, with the affected variant explicit. Record what happens to the partly completed old work order.
Authorize disposition. Segregate the existing kit until the approved decision is recorded. Do not silently combine old and new components in a batch.
Release and acknowledge. Issue the approved package and obtain confirmation that purchasing, setup, inspection and test use the intended release.
Verify and close. Check the first affected build against the change, retain the results and confirm the shipment identification.

A useful effectivity statement is: “Assembly A100, variant X: BOM C is authorized for work order WO-NEW only, using PCB C and the documents listed in release R2. WO-OLD remains on hold pending disposition D1. No revision mixing is authorized.” These identifiers are fictional; use your own controlled records and actual approvals.

7. Treat component PCNs and alternatives as review inputs

A semiconductor manufacturer’s product change notification (PCN) can describe a manufacturing or product change, affected part numbers, qualification information and implementation timing. It is an input to your impact assessment. It does not automatically authorize a different MPN in your assembly.

Similarly, a supplier’s available alternative is not approved just because its package or headline specification looks similar. Product engineering should review the relevant functional, electrical, mechanical, thermal, firmware and test implications. Record whether the approval is permanent for the released BOM, limited to a particular order, or still pending.

Genuine sourcing and technical suitability answer different questions. OrinewPCB’s policy is to supply and assemble with 100% new, original and genuine electronic components. The approved configuration still needs to define which genuine part is acceptable for your product. For a sourcing-only request, include the exact MPN and approval constraints through our electronic components catalog and inquiry route.

8. Verify implementation before closing the change

Closure should show that the approved change reached the affected units and documents. The depth of verification should match the change’s impact; changing a label is not the same technical exercise as changing a power-stage component.

Confirm the intended material and fitted variant against the released BOM.
Verify affected placement/orientation, work instructions and manufacturing setup.
Confirm firmware, configuration and test-plan identities where affected.
Perform the approved inspection, electrical or functional checks and retain the required evidence.
Record any deviations and their authorization rather than hiding them in an email thread.
Reconcile held material, WIP, labels and shipment records with the approved disposition.

A functional PASS result alone does not establish that the correct MPNs, markings or document revisions were used. Conversely, a correctly labeled revision does not prove its required functions passed. Use the PCB functional test plan checklist to define the test evidence separately from configuration identity.

9. What to send for a turnkey PCBA change review

A clear change package helps your supplier review the actual scope, material impact and delivery implications. Send:

Current assembly/PCB identities, variants and the approved baseline package.
Proposed new package, ECO identifier and an explicit old-to-new change list.
Affected order numbers and quantities, known material/WIP status and requested hold scope.
Proposed cut-in boundary and disposition requests for existing material and assemblies.
Component sourcing restrictions, approved alternatives and any PCN or availability issue driving the change.
Programming, inspection, test, traceability and shipment identification requirements.
Required delivery date, destination, approval owners and unresolved engineering decisions.

OrinewPCB provides one-stop PCB assembly, combining PCB production, component sourcing and assembly, with particular strengths in small-to-medium, high-mix builds. Our relationships with component manufacturers and distributors support project-specific reviews of pricing and availability; the final cost and delivery plan depend on the released files, material commitments and agreed work.

Our nine-stage PCBA quality workflow supports discussion of your inspection and test requirements. Bare-PCB flying-probe testing and PCBA configuration/functional verification are separate scopes. Review the relevant requirements with us rather than assuming one check proves all of them. Learn more about the brand at OrinewPCB.

Planning a revised build or a new high-mix order?

Send your PCB files, BOM variants, quantities and proposed changes. Ask for a coordinated review of genuine component sourcing, assembly, test scope and the delivery plan before releasing the next build.

Request a Turnkey PCBA & BOM Review

For an existing order, identify it and any required hold directly with your project contact. A quote request alone does not confirm that production has stopped.

PCB assembly ECO and revision-control FAQ

Does every BOM change require a new bare-PCB revision?

PCB Functional Test Plan: A Production Handoff Checklist

highqualitypcb — Tue, 27 Oct 2026 23:02:01 +0000

PRODUCTION TESTING · ENGINEERING TO SUPPLIER HANDOFF

Quick answer: A PCB functional test plan tells an assembly supplier how to put a specific board variant into a defined operating state, apply the required inputs and loads, measure its response, decide pass or fail, and retain the result. To make that plan usable in production, include the hardware and firmware identity, fixture connections, test conditions, limits, timing, exception handling and record requirements.

“Power it on and check that it works” leaves important decisions unresolved. A board can boot while an output, sensor channel or communication interface remains untested. A useful handoff replaces that ambiguity with repeatable instructions and an agreed acceptance scope.

This guide focuses on writing and releasing a functional test plan for turnkey PCBA. Use the checklist and illustrative test rows below when you prepare a new build or ask a supplier to quote the testing work.

For a current build, send your PCB files, BOM and available test requirements for a turnkey PCBA review, including any open decisions that still need engineering approval.

1. Define what a functional test must prove

Functional circuit testing, often called FCT, exercises selected operating functions of an assembled board under specified conditions. Depending on the product, that can mean checking power behavior, analog responses, digital inputs and outputs, communication transactions or an application-specific sequence.

Structural checks and functional checks answer different questions. AOI examines visible assembly features; ICT or flying-probe programs check selected electrical connections or components within their coverage. A functional test asks whether the released assembly produces the required behavior. Passing one method does not establish complete coverage by the others.

Start by naming the shipped state: assembled board only, programmed PCBA, calibrated board, coated assembly or a completed product in an enclosure. Then define where production acceptance ends. Environmental qualification, EMC, regulatory compliance, long-term life and every possible use condition are separate requirements unless explicitly included.

A product test is not the test station’s self-check. A fixture can communicate successfully with its instruments while a DUT connection is missing. A unit can also pass a basic boot check without exercising its fitted features. State what the board must demonstrate and separately define how the station’s readiness is established.

2. Freeze the unit identity and map variant coverage

The test plan needs a controlled identity just like the PCB and BOM. Record the assembly number, PCB revision, fitted BOM variant, firmware/configuration identity and test-plan revision. If programming is part of the build, keep the approved image and configuration handoff in the PCB programming release package; the functional plan should identify the expected operating state without duplicating uncontrolled firmware files.

Function or condition	Define for each variant	Avoid this gap
Power and startup	Permitted supply conditions, startup behavior, operating mode and required measurements.	Treating a lit power LED as proof of all rails and functions.
Analog or sensor channel	Which fitted channels are exercised, applied input, load, measurement point and accepted response.	Testing one channel while reporting that every channel passed.
Digital interface	Connector/pin mapping, levels, protocol configuration, transaction and expected data or response.	Counting a detected port as a successful application-level exchange.
Output or actuator interface	Required load or approved simulator, commanded states and observed output behavior.	Checking only an unloaded output that behaves differently in use.
Optional or not-fitted feature	Explicit variant applicability and the reason a check is not required.	Silently skipping a required test or failing a legitimate not-fitted option.

This is a planning matrix, not a universal test list. Product engineering should decide the required coverage and any sampling policy. For high-mix orders, a shared PCB layout does not mean the same test sequence and limits apply to every fitted configuration.

3. Write each test as a reproducible instruction

A good test row lets another qualified person reproduce the check without guessing. Separate what is applied, what is measured and how the result is judged. Use unique test IDs so a failed result can be traced to its requirement, work instruction and corrective action.

Original planning illustration for writing a test instruction. It is not a customer fixture, an electrical connection diagram or a production specification.

Field	What to enter	Why it is needed
Test ID and requirement	A stable identifier and the approved requirement or acceptance objective.	Connects a result to the function being accepted.
Variant and starting state	Applicable assembly variants, firmware/configuration, operating mode and prerequisite results.	Prevents the right measurement from being taken in the wrong state.
Connection and setup	Released fixture/harness mapping, reference or return, instrument configuration and required accessories.	Removes assumptions about connector orientation, measurement location and loading.
Stimulus and load	The input, command or load to apply, with units, tolerances and any required sequence.	Defines the condition under which the response has meaning.
Timing and acquisition	Settling condition, measurement interval, timeout, sample handling and method where relevant.	Distinguishes startup transients, steady operation and missing responses.
Acceptance rule	Approved lower/upper limits or expected response, comparison rule and treatment of uncertainty.	Makes the pass/fail decision explicit.
Failure and cleanup	Abort/continue policy, safe state, unit hold, permitted retries and escalation.	Prevents a failure from becoming an uncontrolled retest or an unsafe next step.
Retained result	Measured value or response, units, status and the unit/station/revision identifiers to retain.	Provides evidence beyond an isolated green “PASS” label.

For a communication check, “UART OK” is incomplete. Identify the physical interface, electrical requirements, serial settings, requested transaction, expected response and timeout. For an analog check, name the applied input, load, measurement location, units and decision limits.

4. Agree conditions and limits before running the batch

Use approved product requirements to set acceptance criteria. A working prototype is useful reference material, but its measured value is not automatically the correct production limit. Component variation, operating state, load, measurement method and instrument uncertainty can all affect the decision.

Separate startup from steady operation. Define the relevant timing or settling criterion. A single current limit or one late measurement may not capture the behavior the requirement intends to assess.
Review both sides of a requirement. An upper current limit alone may not reveal a circuit block that never enabled. Decide which lower limits, functional responses or other checks are actually appropriate for the design.
Define the measurement path. Connector contact, cable loss, grounding and fixture loading may affect the quantity being measured. Identify the intended reference and measurement point.
State the decision rule. Specify whether boundaries are inclusive, how rounding is handled, and how uncertainty or guard bands are treated where relevant. Do not silently widen limits to make unstable results pass.
Control changes. A new limit, firmware image, load or fixture revision may require review of the affected checks before production resumes.

Safety-related connections, protective measures, supply sequencing and failure shutdown must be engineered for the actual product and equipment. A general blog checklist cannot provide an approved power-up procedure for an unknown board.

5. Release the fixture and verify the test system

A functional test can be manual, automated or mixed. The important requirement is a controlled, repeatable method with the necessary access and evidence. Low quantity does not automatically eliminate the need for a fixture, and automation does not automatically prove that the selected tests detect the intended faults.

Provide a released interface drawing or connection table, including board orientation, connector identities, pin mapping, reference/return connections, required loads or simulators and any prohibited connections. Review mechanical support, access before coating or enclosure closure, and protection against connecting the wrong variant. Agree who supplies, owns, stores and maintains any tooling.

Confirm station setup, software and limits revisions, instrument identities and calibration requirements.
Verify fixture/harness connectivity and readiness using an approved method; identify consumable contacts and maintenance checks where needed.
Demonstrate repeatability on representative units and appropriate setups. One successful run is limited evidence.
Use approved known-fault samples or suitable simulations to check that required failures are detected, without introducing uncontrolled damage.
Distinguish a station or connection error from a valid DUT failure. A missing response caused by a disconnected cable is not the same result as a measured out-of-limit output.
Review affected coverage after fixture repair, instrument replacement, software changes or product revisions.

A reference or “golden” unit can support station checks, but it should have controlled identity and known status. It does not replace released requirements, traceable measurement practice or evidence that the test responds correctly to the faults it is supposed to detect.

6. Example: document a small-batch functional test

Illustrative document example—not a customer case or a test recipe: a team plans two variants of a control board. Both have a regulated supply rail and a communication interface; only Variant B has an optional output stage. The plan identifies each unit and variant before selecting its checks.

Test row	Released instruction needs	Recorded example or decision
FCT-01: supply rail	For this fictitious example only, assume engineering has approved a 4.75–5.25 V inclusive acceptance window under a separately defined supply, load and measurement method.	Measured 5.03 V: passes this example’s numeric comparison. Retain the value and units. These values are not recommended limits for your design.
FCT-02: communications	The released transaction, interface configuration, expected response and timeout, using the applicable firmware state.	Store the response/status and any required timing evidence. A timeout or wrong response must not be recorded as a pass.
FCT-03: optional output	Variant B only: defined stimulus, approved load, measurement and acceptance criteria. Variant A: explicitly not applicable.	A missing required result on B holds the unit. The not-applicable status on A is linked to the variant rule, not a generic “PASS.”

The sample voltage row illustrates the document structure only; it does not establish a complete test, instrument capability or uncertainty decision. Before use, the actual plan must define all conditions and engineering-approved acceptance rules. A measured value without its state and method cannot be interpreted reliably.

Keep production acceptance separate from debugging. A technician may investigate a failure using additional measurements, but those measurements and any repair need an approved disposition. Repeating the same test until one reading passes hides useful evidence and does not resolve the cause.

7. Retain useful records and control retesting

Agree the records before the order, including the format and delivery scope. A practical unit record links the assembly/variant and unit identifier to the test-plan and software revisions, fixture/station identity, date, required measured values or responses, limits and final status. Include the information necessary to reproduce and interpret a failure.

Keep pass, fail, error, aborted and not-applicable/skipped outcomes distinct under the agreed rules. A required check that never ran cannot support a passing acceptance decision. Preserve earlier attempts, failure information and any approved rework or retest rather than replacing the history with the latest pass.

Define who may authorize a retry, change a limit or release a held unit. If rework occurs, state which inspections and tests must be repeated. Required records and traceability are project-specific; do not assume every build includes the same report or retention period.

8. Include functional testing in the turnkey PCBA quote

A test plan also defines commercial scope. Fixture and software preparation, loads or simulators, unit handling, execution time, variant changeovers, calibration and maintenance needs, reporting and failure investigation can affect the quotation and schedule. Separate one-time preparation from recurring testing and identify work that is still undefined.

PCB, BOM and assembly revisions; fitted variants and quantities for each build.
Required shipped state and approved firmware/configuration identity.
Functional coverage matrix and the current test-plan status, including open engineering decisions.
Connector/pin mapping, fixture/harness files, approved loads, instruments or supplied tooling, and ownership responsibilities.
Acceptance limits, operating conditions, timing and the agreed station-validation approach.
Inspection and electrical test requirements in addition to functional acceptance, with any required sample or unit coverage.
Result format, unit identification, retest/repair authorization and shipment-release requirements.
Required delivery date and destination, plus component sourcing or substitution constraints.

OrinewPCB provides one-stop PCB assembly covering PCB production, component sourcing and assembly coordination, with a particular focus on small-to-medium, high-mix builds. Its policy is to supply and assemble with 100% new, original and genuine components. Cooperation with component manufacturers and distributors supports review of BOM pricing and availability; actual offers and delivery plans require project confirmation.

The company’s nine-step PCBA quality workflow provides a basis for discussing quality requirements. Specify the functional checks needed for your build rather than assuming that a named workflow covers every product function. Bare-PCB flying-probe electrical testing and assembled-product functional acceptance are separate scopes. Learn more at the OrinewPCB brand website.

Ask for a quote that includes the required test scope

Send your PCB files, BOM, quantities and functional test requirements for a coordinated turnkey PCBA review. If the test procedure is incomplete, send the current requirements and identify the missing items so responsibilities, preparation work and acceptance can be clarified before release.

Request a Turnkey PCBA & Test-Scope Review

Include your required date, destination, variant quantities and any customer-supplied fixture or software.

PCB functional test plan FAQ

Is a functional test the same as ICT or flying-probe testing?

PCB Programming: Firmware Release & Production Checklist

highqualitypcb — Fri, 23 Oct 2026 04:54:56 +0000

ENGINEERING & PROCUREMENT · TURNKEY PCB ASSEMBLY

Quick answer: PCB programming usually means loading firmware into a programmable component on an assembled circuit board. Before an assembler can quote a repeatable process, release the exact device and board variant, approved firmware files, programming interface, memory and configuration instructions, and acceptance checks. A successful download does not establish that the finished product works.

For a small-batch, high-mix build, the expensive mistake is often a mismatch: the right PCB receives the wrong firmware, a fixture cannot reach its programming pads, or a programmed board leaves without the required functional check. These problems start in the handoff package, before the first production unit is connected.

This guide explains what hardware engineers and product managers should prepare for turnkey PCB assembly with programming requirements. It focuses on a manufacturing handoff, rather than teaching software development or supplying a universal pinout. Confirm the device-specific procedure and the supplier’s supported scope for your project.

1. What does PCB programming include?

The bare PCB itself is not normally the item being programmed. Firmware or configuration data is written to a microcontroller, programmable memory, or another supported device on the assembly. A product may need more than one image: for example, application firmware plus a bootloader or external-memory content.

Programming, inspection and testing are separate activities. AOI can assess visible assembly features; it cannot establish which application version is running. A memory verification result addresses the programmed data under the chosen verification method. A functional test checks the board against a defined operating procedure and limits.

Activity	Question it answers	What still needs a separate check
Firmware programming	Was the selected programming operation completed?	Correct build variant, configuration, boot behavior and product function.
Memory verification	Does the checked memory match the expected data or approved verification result?	Unverified regions, device-specific data and actual operating behavior.
Boot/version check	Does the application start and report the expected identity?	Required inputs, outputs, communications and performance limits.
Functional acceptance	Does this unit pass the agreed operating checks?	Functions and conditions outside the approved test coverage.

A useful RFQ states which of these activities is required and what evidence the customer expects. “Program and test every board” needs a defined procedure before it becomes an executable production instruction.

2. Choose the programming route before fixing the build plan

Device support, access, variant count and expected repeat orders all affect the route. A quick laboratory method may be practical for engineering samples, while a repeat build may justify dedicated fixturing or a different programming setup. Quantity alone is not enough to select the process.

Route	When to discuss it	Release questions
Program devices before placement	The exact device supports the proposed off-board process and the firmware can be fixed before assembly.	Who supplies the programming service? How are programmed MPNs/lots identified? What happens if firmware changes?
Program after assembly through a connector	A compatible programming interface is accessible on the assembled board.	What are the connector pinout, target voltage, power source, reset and boot conditions? Is access retained after later assembly?
Program through a contact fixture	Repeated batches or access constraints make a fixture worth evaluating.	Which drawing controls pad access and board support? Who designs, validates, owns and maintains the fixture?
Use a supported bootloader or update path	The device and released firmware support that route in the incoming state.	Is the bootloader actually present? What enables the mode? How are the application image and successful completion verified?

Do not assume that a USB connector makes a board directly programmable. The device, boot mode, firmware and hardware must support the proposed path. Equally, a programmer’s compatibility with a device family does not establish compatibility with every exact device, memory layout or protection state.

Confirm that the chosen tools and licenses are suitable for the intended production use. For example, ST’s current guidance distinguishes STM32CubeProgrammer development use from production programming and points production users toward appropriate partner solutions. This distinction should be resolved during process review, not after an order is scheduled.

3. Release a complete firmware package

Send a controlled package with a short manifest. The person programming the board should not have to choose between attachments called “final”, “latest” and “new final”. Keep the approved image, configuration instructions and work instruction tied to a release identifier.

Item to release	What to include	Decision it prevents the operator from guessing
Hardware identity	Assembly number, PCB revision, BOM revision, build variant and exact target device ordering code.	Which physical boards are eligible for this release?
Approved images	File names, firmware versions, release ID and expected file hashes using the agreed algorithm.	Which exact files were approved?
Memory instructions	Destination for each image; required loader or configuration; areas to preserve and permitted erase scope.	Where should data be written, and what must remain intact?
Programming setup	Supported programmer, tool/project version, interface, connection drawing, power and reset/boot sequence.	Which approved setup should the supplier reproduce?
Configuration and unique data	Approved device settings; serial allocation or calibration data if required; ownership and access responsibilities.	Which values are common, which vary by unit, and who authorizes them?
Acceptance and exceptions	Verification method, boot/version response, functional-test procedure, records, failure hold and change approval.	What is a pass, and what happens after a failure or revision change?

File extensions alone do not define a safe programming job. A raw binary needs its intended destination specified; address-bearing formats still need to match the target memory map and approved tool setup. If several images are required, document all destinations and the sequence. Identify external-memory loaders where applicable.

A release-file hash identifies the approved input file. It does not replace verification of the device’s programmed memory. If serial numbers or other per-unit data change the image, define how the verification method handles those approved variable regions.

Use the same revision discipline as the PCB assembly drawing. State the relationship between hardware, BOM variant and firmware explicitly, even when the copper layout is shared.

Original planning illustration: a firmware release connects to the hardware variant, approved process and per-unit result. It is not a customer project or production specification.

4. Check physical access, power and process sequence

A diagram of the interface is more useful than the instruction “use SWD”. Identify the signals required by the selected device and setup, connector orientation, ground, voltage reference, reset and boot controls where needed. SWD, JTAG and device bootloaders are different interfaces; do not interchange their pin assignments or assume a universal programming voltage.

Confirm the power source. State whether the board or the programming setup supplies power, and define the approved power-up and shutdown conditions. Do not assume the voltage-reference connection is a power output.
Show actual access. Provide the relevant assembly view and keep-outs. Include fixture approach, board support and any connector, heatsink or enclosure that could obstruct the contacts.
Review the assembled electrical environment. Ask the hardware owner to review loading, shared signals, reset behavior and other circuitry that may affect the interface.
Place programming in the process sequence. Confirm access before coating, potting or final enclosure operations, or provide an approved access arrangement for the later stage.
Separate factory and application images if used. Define whether a temporary test image must be replaced and how the final shipped state is checked.

For coated assemblies, coordinate this review with the coating masking and keep-out drawing. A programming pad that becomes inaccessible is a process-planning issue, not something to leave for the operator to improvise.

5. Agree on programming, verification and release gates

The following is a suggested handoff workflow. It does not replace the target-device documentation or prescribe the order of irreversible device settings.

Confirm the released build. Match the board, fitted variant and target device to the approved package. Resolve conflicts before programming.
Validate the setup on approved samples. Confirm access, tools, power, process timing and expected results. Record the approved setup before processing the remaining units.
Run the approved programming job. Use the specified files, destinations, permitted erase operations and configuration. Stop if the device identity or initial state is unexpected.
Perform the agreed memory verification. Retain the result and apply the defined treatment of variable data. A command completing without an error is not an interchangeable substitute for every verification requirement.
Check the intended shipped application. Reset or power-cycle as specified, confirm the expected image identity and carry out the agreed functional acceptance procedure.
Reconcile records and release the units. Separate accepted units from failures and pending work. Link the result to the build lot or unit identifier at the agreed traceability level.

Configuration, read protection and one-time-programmable settings need a device-specific, engineering-approved sequence. Some changes can restrict later access or affect recovery. Do not use a generic internet command as a production instruction, and do not let an operator choose protection settings to clear an unexpected error.

For secure provisioning, define the approved transfer method and responsibility for sensitive material separately. Do not put private signing keys or production credentials in an ordinary quotation attachment. Describe the requirement first so both teams can agree on the supported process.

Suggested release gates for discussion. Programming, memory verification and functional acceptance answer different questions.

6. Example: two firmware variants on one PCB revision

Fictional planning example: a team orders 60 controller assemblies, split between two product variants using PCB revision C. These are example quantities and file names, not an OrinewPCB customer case or an instruction to program a real device.

Release field	Variant A: 40 units	Variant B: 20 units
Hardware and BOM	PCB C; assembly A; approved BOM A3.	PCB C; assembly B; approved BOM B2.
Application file	controller_A_2.1.0.hex; approved file hash in manifest.	controller_B_2.1.0.hex; separate approved file hash.
Per-unit identity	40 identifiers from the customer’s approved allocation.	20 identifiers from a separate approved allocation.
Acceptance response	Reports variant A and firmware 2.1.0; passes test procedure A.	Reports variant B and firmware 2.1.0; passes test procedure B.
Release evidence	Unit/lot mapping, programming and test results, failure holds.	Separate variant mapping and corresponding results.

The control point is not just the total of 60 boards. It is the relationship between the physical variant, approved image, unique data and acceptance result. Mark the transition between variants in the work instruction, reconcile quantities and prevent pending or failed units from entering the accepted group.

If firmware changes after approval, identify the affected units and release a revised instruction. Define which units require reprogramming, what verification and functional checks must be repeated, and how the final shipping record distinguishes the approved state.

7. Specify useful records and a failure-hold process

Choose a traceability level that fits the product and commercial scope. Lot-level evidence and per-unit records are different deliverables. If each unit needs a programming and functional-test record, state that in the quotation request and agree on the data fields and retention arrangements.

A practical proposed record includes build/variant, unit or lot ID, release ID, image identity, approved setup version, programming result, verification result, functional-test result, time or run reference, and any exception disposition. Ask the supplier to confirm which fields can be provided.

Observed result	Review before repeating the process	Disposition to define
Cannot connect to target	Approved power, connector orientation, contact condition, device identity and reset/boot state.	Hold the unit; distinguish fixture/setup issues from board faults.
Programming or verification fails	Exact error, image/destination, target memory support, connection stability and allowed erase scope.	Follow the approved retry limit and engineering escalation; preserve the evidence.
Programming passes but application does not start	Required images, configuration, expected boot path and hardware compatibility.	Keep separate from accepted boards; investigate using the agreed procedure.
Wrong variant or duplicate identifier	Release mapping, identifier allocation and records for other affected units.	Contain the affected batch and approve a controlled correction and retest.

Repeatedly erasing and retrying until a green indicator appears can destroy useful diagnostic information or alter data that should have been preserved. Define permitted recovery steps, retry limits and the person who can approve further work.

8. What affects programming cost and delivery?

Ask for a quote that separates setup or fixture work from recurring unit operations. Relevant inputs include the exact target device, image size and count, interface, access arrangement, variant changes, unique data, verification, functional-test coverage and required records. Do not assume a universal programming time or a fixed extra fee per board.

For small batches, engineering setup and approval can matter more than the download operation itself. For repeat orders, keeping an unchanged approved package and a maintained fixture may reduce avoidable requalification work; the supplier should confirm what can be reused.

OrinewPCB provides PCB fabrication, component procurement and turnkey assembly, with particular emphasis on small-to-medium batches and high-mix projects. Our component policy is to supply and assemble with 100% new, original genuine electronic components. Programming feasibility, supported tools, test scope, price and schedule are confirmed for the particular build.

Learn how the broader service fits together on the OrinewPCB brand website. For a manufacturing handoff, state your required delivered condition clearly: assembled only, programmed and verified, or programmed with an agreed functional acceptance test.

PCB programming FAQ

Does every PCB need programming?

PCB Component Kitting: Quantity, Packaging & Handoff Checklist

highqualitypcb — Wed, 21 Oct 2026 02:49:51 +0000

PCB component kitting means preparing a verified set of parts for a specific assembly build. A useful kit links each component to the released BOM, required quantity, usable packaging, source records and production variant. It also identifies shortages and the person authorized to resolve them before the material is released to the line.

How do you prepare a PCB assembly kit? Start with one approved board revision and BOM, calculate populated quantities for every variant, agree setup and handling allowances with the assembler, and reconcile the received material against a kit manifest. Keep packaging and identification intact. A purchase order marked “delivered” is not, by itself, confirmation that the right parts are ready for assembly.

Planning a small or medium batch? Request a turnkey PCBA and BOM review with your board files, BOM, quantities and any components you intend to supply.

1. What belongs in a PCB assembly kit?

A kit can include SMT and through-hole components, connectors and other BOM items needed at the agreed assembly stages. It should have a material list that can be checked against the actual packages. If bare PCBs, mechanical parts, labels or cables are managed separately, identify those dependencies rather than silently treating the component kit as the complete product.

Kitting is an activity within the manufacturing workflow. In a full turnkey project, the assembly partner can purchase and organize the agreed materials. In a customer-supplied build, the customer prepares the supplied material package. A partial turnkey order divides sourcing responsibility by BOM line. Our partial turnkey PCBA guide discusses that purchasing decision; this checklist focuses on making the resulting material package ready for a particular build.

Original OrinewPCB workflow illustration. The release sequence is a planning concept; the actual receiving and production procedure must be agreed for your project.

2. Tie the kit to one revision and variant plan

Give the kit a build identifier, board revision and BOM revision. Use the same identifiers in the purchase instructions, packing list and assembly documentation. A board revision alone is insufficient if the BOM or population variant can change independently.

At minimum, connect the following information. Keep the actual files together in a controlled release package rather than relying on several uncoordinated email attachments.

A practical kit manifest for engineering and purchasing
Item	Record or attach	Question it answers
Build identity	Project, board revision, BOM revision and build identifier.	Which released configuration does this material belong to?
Part identity	Manufacturer, complete manufacturer part number and reference designators.	Is this the approved device, package and ordering option?
Population plan	Quantity per assembly, finished quantity per variant and explicit DNP positions.	Which locations are populated in this build?
Material ownership	Who purchases each line, what is customer supplied and what stock is allocated.	Who must resolve a shortage or source question?
Physical supply	Received count, reel or strip count, packaging type and condition.	What is physically available in a usable form?
Identification records	Supplier labels, source documents and lot/date information where required.	Can each package be reconciled to the approved line and agreed traceability scope?
Exceptions	Missing parts, proposed alternatives, packaging issues and approval owner.	Which items are holding the kit, and who can release them?

On a phone, swipe within the table. Keyboard users can focus its frame and use the arrow keys.

Keep alternatives separate from approved material. A similar value or footprint does not authorize a replacement. Record design-owner approval and update the controlled BOM before using an alternative. The approved manufacturer list checklist explains that approval boundary.

3. Calculate quantities by populated position, then agree allowances

For each exact part number, add the required placements across the variants being built:

Build quantity for one part = sum of (assemblies in each variant × populated quantity of that part per assembly).

Planned material quantity = build quantity + agreed setup and handling allowance.

Additional purchase need = planned material quantity − usable stock already allocated to this build, with a minimum of zero. Then check supplier pack quantities and order increments.

The allowance belongs to the actual part, packaging and process. Ask the assembler to confirm it before ordering. Do not apply an unexplained percentage to every BOM line. An expensive IC and a frequently placed small passive can need different material-planning decisions. Blank leader tape is a packaging requirement, not a count of additional electronic components.

A worked quantity example

Suppose a fictional build contains 50 assemblies, each using eight of one resistor MPN. The placement requirement is 400 resistors. If the project team agrees a 20-piece allowance and has 120 usable pieces allocated to this build, the planned total is 420 and the additional purchase need is 300, before any supplier order-increment adjustment.

The 20-piece allowance is an illustration, not an OrinewPCB policy or a recommended standard rate. Confirm the real requirement against the proposed assembly process. Stock that is reserved for another order, unverified or still in transit is not the same as released stock available at the line.

Why a high-mix build needs a variant-aware quantity calculation
Illustrative BOM line	Variant A: 30 boards	Variant B: 20 boards	Placement need
Common resistor MPN	4 per board	4 per board	200 pieces
Optional connector MPN	1 per board	DNP: 0 per board	30 pieces
Variant-specific IC MPN	DNP: 0 per board	1 per board	20 pieces

Fictional planning example. Counts exclude setup allowances, inspection samples and supplier pack rounding; agree those separately. DNP means do not populate.

Count by complete MPN and approved configuration, not by a short description such as “10 kΩ resistor.” Keep electrically different parts or packaging options on separate controlled lines where necessary. For repeat builds, reconcile unused material before carrying its quantity into a new kit.

4. Confirm the packaging can reach the assembly line

Packaging affects how a component can be handled and presented to placement equipment. A reel, several short tape strips, a tube and a tray are not automatically interchangeable inputs. Tell the assembler what will actually arrive, including the number and length of cut-tape strips when relevant.

Tape-and-reel packaging holds components in carrier pockets under cover tape for automated handling. The pocket arrangement and component orientation are part of the packaging information. Check the exact device’s packing drawing and the assembler’s feeder requirements. Avoid assuming that all parts with the same package name use identical presentation.

Full or partial reels: retain the label and confirm actual quantity, tape condition and any preparation needed for the intended feeder.
Cut tape: report strip count and available identification. Ask about minimum usable strip length, leader/trailer preparation and handling before purchasing. Avoid opening protected packages merely to create a photograph.
Tubes and trays: keep parts protected and identified; confirm compatibility with the planned handling method. Do not send loose mixed components as a substitute for an agreed packaging format.
Ordering suffixes: preserve the full approved manufacturer ordering code. Confirm what the suffix means for that manufacturer and device rather than deleting it from the BOM.

Original OrinewPCB kit-label concept using fictional identifiers. It is not a supplier label, authenticity certificate or customer production record.

Keep ESD protection and moisture records with the material

Use packaging appropriate to the component’s ESD sensitivity and handling environment. A moisture barrier bag and an ESD protection requirement describe different aspects of material control; confirm both where applicable. Unpack and handle sensitive parts within the agreed ESD control procedure.

For moisture-sensitive devices, retain the applicable label and available dry-pack and exposure records. A recently resealed bag does not establish an unused floor-life allowance. Have the responsible process engineer decide what handling or drying is appropriate for the actual device, package and exposure history. See our MSL and floor-life handoff guide for that separate decision.

5. Reconcile receipt, shortages and production release

Separate four statuses in the material tracker: ordered, received, checked and released. A shipment notice proves neither a usable quantity nor approval to assemble an alternative. Give every exception an owner and a written disposition.

Match each package to the manifest. Reconcile the manufacturer MPN, label, count and BOM references. Record differences without silently editing the released design.
Check the packaging and handling information. Flag damaged tape, unidentified strips, compromised protective packaging or missing history requiring review.
Identify the exact shortage. State the required quantity, accepted available quantity, missing quantity and purchasing responsibility. Link it to the affected board or variant.
Agree the disposition. Options can include replenishment, an approved alternative or a separately authorized split build. Reassess setup, tests and delivery consequences before accepting the change.
Release the defined scope. Record which configurations and quantities are ready. Do not convert a temporary assembly omission into a new DNP instruction without design-owner approval.

For split deliveries, agree what constitutes a complete, accepted assembly and what must happen to work in progress. A partially populated board may need additional handling, tracking and verification; it is not automatically the fastest or least expensive recovery plan.

After the build, reconcile unused, consumed and rejected material against the agreed reporting scope. Define whether remaining customer-owned stock is returned or held for a future order, including its identification, packaging and any required handling records.

6. Use one kit review to plan a full turnkey build

For a small-batch, high-mix project, buying each line independently can leave engineering to coordinate packaging, shortages and several arrival dates. A turnkey review lets the PCB, sourcing, assembly and verification requirements be discussed together. It does not eliminate the need for approved files and a clear material-release decision.

OrinewPCB provides PCB manufacturing, component procurement and one-stop PCB assembly, with particular focus on small and medium batches and high-mix work. We supply and use 100% new, original genuine electronic components in our component sourcing and turnkey PCBA work. Identify customer-supplied material separately so its records and acceptance requirements can be reviewed.

Our cooperation with component manufacturers and distributors supports project-specific sourcing options and competitive quotations. Exact availability, packaging, price and delivery must be confirmed for the released BOM and required quantity. Ask for a quote that identifies material exceptions rather than assuming that every listed part is immediately available.

Discuss the complete scope through our turnkey PCB assembly service or low-volume, high-mix assembly service. The brand’s OrinewPCB assembly overview provides further service context.

7. Send a kit-ready RFQ package

Request a Turnkey PCBA & BOM Review

Send your current files and tell us what you want delivered: bare PCBs, components, or tested assemblies within an agreed scope. For a full turnkey order, ask us to review the BOM and packaging needs before material is purchased.

Board files and revision, plus assembly and placement information.
BOM with complete MPNs, reference designators, DNPs and approved alternatives.
Finished quantity per variant and any pilot or staged delivery requirement.
Customer-supplied stock, actual counts, packaging and available identification records.
Programming, inspection and test requirements, with the required delivery date and destination.

Suggested inquiry: “Please review a full turnkey build for [board/revision], [quantities per variant]. Our BOM is [revision]. We plan to supply [listed parts, counts and packaging], and need you to source the remaining approved lines. Please confirm the kit requirements, shortages, assembly/test scope and delivery proposal.”

Request a Turnkey PCBA & BOM Review

For component-only inquiries, include exact MPNs, quantities and packaging requirements through our electronic component sourcing directory.

8. PCB component kitting FAQ

Is component kitting the same as turnkey PCB assembly?

Conformal Coating Masking: PCB Keep-Out Drawing & Checklist

highqualitypcb — Mon, 19 Oct 2026 03:02:07 +0000

Conformal coating masking keeps specified contacts, openings and functional interfaces free of coating while the required areas receive protection. For a turnkey PCB assembly order, release a coating drawing with top and bottom views, identified keep-outs, boundary tolerances, the approved coating system and an agreed inspection plan. “Mask all connectors” is not a complete production instruction.

This guide answers a practical engineering and purchasing question: what must you put in a coating masking drawing so your PCBA supplier can quote and build the intended result? It focuses on the release package and acceptance decisions, rather than choosing a universal coating chemistry or inventing one masking clearance for every board.

For a complete build, send your PCB files, BOM and coating requirements for a turnkey PCBA review. Include your quantities for each model and variant.

1. What masking must preserve

A conformal coating can protect designated circuit areas, but the same material can interfere with a connection, opening or service operation if it reaches the wrong surface. Specify the interface that must remain usable, not merely the name of the nearby component.

For example, a connector’s mating contacts and a connector’s soldered terminals have different functions. Whether the body, terminals or surrounding board can be coated depends on the exact part, coating and approved process. A sealed-looking housing is not evidence that liquid or vapor cannot enter it.

Masking also has a removal stage. A temporary protection that works during application must come off at the required point without leaving obstructive residue or damaging the assembly. Application, curing and removal conditions therefore belong in the process review.

Keep three decisions separate: which surfaces require coating, which surfaces must stay uncoated, and how each boundary will be produced and inspected. Areas with unresolved requirements should be marked for engineering review before production release.

2. Which areas need a coating keep-out review?

The table is a review checklist, not a blanket prohibition on coating every component in a category. Follow the exact component manufacturer’s instructions and your product requirements.

Interfaces to resolve before a coating quote
Interface	What to identify	Decision to release
Connectors and contacts	Mating surfaces, card-edge fingers, sockets and access openings.	Exact no-coat surfaces, allowed treatment of the body or terminals, and the check after removal.
Sensing or acoustic openings	Humidity/gas sensor openings, pressure ports and acoustic paths where applicable.	Part-specific protection method, chemical compatibility and the required open condition in service.
Programming and test contacts	Contacts required before coating, after coating or during field service.	Test sequence and which contacts must remain accessible in the shipped state.
Mechanical and bonding surfaces	Specified ground bonds, mounting interfaces, threads and fitted mating faces.	Dimensions and contact requirements; do not assume every mounting hole has the same rule.
Adjustments and moving parts	Switch mechanisms, adjustments, removable links and serviceable parts.	Allowed process exposure and post-process access or movement checks.

Sensor example: an exposed humidity-sensing opening must remain functional and free of the prohibited coating. A manufacturer-approved temporary cover can have its own removal instruction. Do not apply generic tape directly to every sensor: the permitted method and sensitivity to processing chemicals depend on the actual device.

3. Build a masking drawing that can be inspected

Start with the released assembly identity: board number, PCB revision, assembly revision and variant. Show the top and bottom sides with enough reference designators to identify each restriction. Use a clear legend for “coat,” “do not coat” and “engineering review required.” Color helps, but hatching and text should also make the meaning readable in a monochrome print.

Original OrinewPCB concept illustration. The numbered zones are fictional review examples, not a customer board, a scale drawing or approved masking dimensions. Tap to inspect the image at full size.

For each restricted area, define the surface or boundary in a view that the operator and inspector can actually use. A note pointing at a connector may not show whether the restriction covers only its opening, the whole body or adjacent PCB copper. Add a detail view when the main view is ambiguous.

Identify the build. State the board, assembly revision, variant and coating drawing revision.
Define each surface. Link the region to a reference designator, interface or dimensioned feature; identify the side.
Specify the boundary. Provide the required limit and permitted boundary variation, with units and a datum where needed. Have the assembler confirm that the process can achieve it.
Define the coating system. Identify the approved product or controlled specification, thickness requirement and cure/handling criteria appropriate to the selected material.
Record process-sensitive parts. Include component restrictions and the approved protection/removal method where needed.
Define acceptance. Specify coverage, restricted surfaces, required inspection evidence and any functional checks.

There is no single masking clearance that is suitable for every spray valve, coating viscosity, connector geometry or assembly. A tight boundary beside a tall component deserves a manufacturability discussion before the PCB layout and quote are frozen.

Keep this drawing linked to the PCB assembly drawing. If a BOM alternative changes a connector body or sensor package, revisit its masking instructions before approving that substitution.

4. Compare the masking method with the build

Temporary tapes, caps, plugs, peelable masks and fixtures can serve different geometries. Selective application controls where coating is delivered; it does not remove the need to define the finished keep-outs. The supplier should review the actual part geometry, material compatibility, exposure conditions and removal access.

Questions to compare process proposals
Approach	Useful review point	What to confirm
Tape, cap or plug	Temporary protection of a defined accessible interface.	Fit, attachment, chemical/temperature compatibility, removal and residue acceptance.
Peelable masking material	Temporary masking shaped to a particular area.	Compatibility, application and removal timing from its instructions, plus access for complete removal.
Reusable fixture or mask	A repeatable arrangement for a specified board and component geometry.	Revision control, fit, maintenance, cleaning and any variant-specific differences.
Selective coating program	A controlled application path around released no-coat regions.	Access, flow and boundary behavior on the real assembly; remaining physical masking needs.

Do not transfer the removal timing of one peelable product to another. Coating and masking suppliers provide material-specific instructions. The same caution applies to cure temperatures and cleaning: a generally suitable board-cleaning step may be unsuitable for an exposed sensor.

5. Agree on testing, removal and first-build acceptance

A practical sequence starts with an approved release package and includes inspection of the assembled board before coating hides access. Programming or functional testing may occur at a different point for different products. State the intended sequence and required contact access explicitly.

Confirm assembly identity and complete the agreed pre-coating checks.
Prepare the assembly using compatible, approved cleaning and drying procedures.
Apply the released masking and verify the protected interfaces.
Apply and cure the specified coating under its approved process.
Remove temporary protection at the stage required for that material and assembly.
Inspect coverage, boundaries, removal and interface access; perform the agreed final checks.

A visual or UV inspection, where supported by the coating system, helps assess coverage. It does not by itself prove film thickness, electrical function or environmental qualification. Define each required measurement and test separately.

For a first build, agree which views or records must be reviewed and whether a customer approval hold is required before the remainder is processed. A sample photograph is useful evidence of an identified feature; it is not a substitute for all acceptance requirements.

6. Example: resolve one masking conflict before production

Consider a fictional controller assembly whose drawing says “mask J1,” while the BOM alternative list permits two connector bodies with different shapes. The coating program was prepared around only one body. The proper next step is a controlled clarification, not an operator guessing which file wins.

Assembly: Controller Rev C, Variant B — fictional example.
Issue: approved connector choices have different masking geometry.
Required decision: identify the MPN used for this build and release the correct keep-out detail and masking/program revision.
Verification: confirm mating access and the agreed coating boundary on the first build.
Release record: record the approver, drawing revision and applicable lot or quantity before continuing.

For high-mix production, use a variant matrix rather than assuming one mask fits every product. The matrix can identify assembly revision, fitted MPN, masking drawing, fixture/program revision, removal instruction and test procedure. A new component source alone may not change geometry; a different approved MPN can. Review the actual change.

7. Checklist for a turnkey PCBA quote with coating

Help the assembler quote the finished requirement, including masking work, tooling, curing and inspection. Useful inputs are:

Gerber/manufacturing files, released BOM, placement data and assembly drawing.
Model/variant quantities and whether shipment is coated PCBA or a further assembled product.
Top/bottom coating views, keep-out details, boundary requirements and exact coating specification.
Restrictions from the component documentation, including exposed sensors, connectors and temporary covers.
Programming/test sequence, post-coating test access, fixtures and pass/fail criteria.
Required inspection records, first-build approval and any qualification or traceability requirements.
Target delivery date and whether proposed material changes need written approval.

Ask that one-time tooling or programming and recurring masking/inspection work be identified clearly in the quote. Price and schedule depend on the released design, selected materials, quantities and process scope. A standard coating material alone does not establish the suitability of the complete product for its environment.

Review the complete build with OrinewPCB

OrinewPCB provides turnkey PCB assembly, PCB manufacturing and component procurement, with particular strength in high-mix, small-to-medium batches. Our sourced components and components used for turnkey PCBA follow our 100% brand-new, original genuine material policy.

We have conformal coating equipment and can review coating and masking requirements as part of your project. Send your files, quantities and keep-out instructions so we can assess feasibility, the required process and an appropriate quote. Inspection coverage and functional testing are agreed for the build.

Request a Turnkey PCBA & Coating Review

Review our factory and quality workflow, or visit the OrinewPCB brand assembly overview.

8. Conformal coating masking FAQ

Does selective coating mean that physical masking is unnecessary?

Approved Manufacturer List for PCBA: BOM Alternatives Checklist

highqualitypcb — Fri, 16 Oct 2026 03:10:28 +0000

An approved manufacturer list (AML) maps an internal BOM item to the exact manufacturer part numbers your engineering team has approved. For turnkey PCB assembly, send that list with the board revision, approval status, permitted purchasing sources and substitution rules. A distributor’s cross-reference suggestion or an available component is a candidate for review; it is not permission to change the build.

This guide answers a specific procurement question: how do you let a PCBA supplier source available parts without losing control of the design? The practical answer is to separate component approval, source approval and production release. Engineers retain control of electrical and mechanical suitability; buyers have a defined sourcing envelope; the assembler knows which configuration it may actually build.

Preparing an order? Send your BOM and approved-parts list for a turnkey PCBA review. Include quantity and the revision you want quoted.

1. AML, AVL and BOM: agree what each list controls

The BOM describes the assembly: internal item numbers, reference designators, quantities and the parts to populate. An AML connects an internal item to one or more approved manufacturer parts. A source list identifies the organizations from which purchasing is permitted. In practice, companies use AVL, ASL and AML differently, so define these terms in your order documents instead of relying on the abbreviation alone.

Three decisions that should remain distinct
Record	Question it answers	What it does not establish
Released assembly BOM	What is fitted to this board revision and variant, and at which reference designators?	A generic description alone does not identify every acceptable manufacturer part.
Approved manufacturer list	Which exact manufacturer and orderable part numbers may satisfy this internal item?	It does not approve every seller offering that part or every application of it.
Approved source list	Which suppliers or distribution channels may provide the required part?	A permitted supplier cannot independently approve a different electrical component.
Build authorization	Which released BOM, approved alternatives and exceptions apply to this purchase order or lot?	A prototype-only approval does not automatically authorize future production.

On a phone, swipe each table horizontally. Keyboard users can focus a table region and use the arrow keys.

For the broader manufacturing service boundary, see turnkey PCB assembly. This article focuses on approval control rather than general BOM creation or cost reduction.

Original OrinewPCB workflow illustration. It is a proposed document-control model, not a customer case or a claim that all companies use identical approval terminology.

2. What should an approved manufacturer list contain?

Make the file usable by the person placing the purchase order and the person verifying the assembly. A row that says “10 kΩ, 0603, any brand” may leave tolerance, rated power, temperature behavior and the package convention unresolved. Keep the complete orderable MPN, including relevant suffixes, and explain any separately permitted packaging variants.

Identity: internal item number, manufacturer name and full approved MPN. Keep the manufacturer’s number separate from a distributor’s stock code.
Assembly context: board identifier, BOM revision, populated variant, reference designators and quantity per board. Keep do-not-populate positions explicit.
Approval scope: approved, candidate, restricted or obsolete status; permitted product/revision; any prototype-only or lot-specific restriction.
Technical evidence: datasheet revision, comparison record, qualification or test reference, and unresolved conditions.
Authority: approver, approval date, change-control reference and the person responsible for disposition of exceptions.
Sourcing conditions: permitted channels, packaging requirements, requested traceability records and any customer-specific date-code or handling requirement.

One internal item may have multiple approved MPNs if the design owner has qualified them for that use. That does not mean all reference designators sharing the same nominal value must allow the same alternatives. A timing resistor and a pull-up resistor can have different constraints even when both are described as 10 kΩ.

3. Review an alternate beyond package and nominal value

A cross-reference tool is useful for finding candidates. Its categories can distinguish a close replacement from a pin-compatible device with different parameters or a part with only similar functionality. Start with that comparison, then check the requirements of your actual circuit. “Equivalent” must have a defined scope.

Candidate-part review checklist
Review area	Questions to resolve	Evidence to retain
Mechanical and assembly	Do footprint, pin mapping, body height, terminal geometry, polarity and recommended land pattern fit the design and process?	Package drawings, pin comparison and any assembly-process review.
Electrical operating limits	Are supply range, input/output levels, accuracy, load capability and relevant temperature limits suitable? Do not use absolute maximum ratings as normal operating conditions.	Applicable datasheet limits and circuit requirements under stated conditions.
Dynamic and analog behavior	Could startup, stability, noise, timing, switching or transient behavior affect the application?	Analysis and targeted bench tests with defined pass/fail criteria.
Firmware and interfaces	Are device IDs, register behavior, programming, boot conditions and communication timing compatible?	Firmware version, configuration and interface-test results.
Materials and handling	Do finish, soldering restrictions, moisture sensitivity and supplied packaging fit the proposed process?	Manufacturer handling guidance and relevant material documentation.
Product requirements	Does the change affect required environmental performance, customer approval, safety or regulatory evidence?	Design-owner review and any required product-level evaluation.

For a genuine component, authenticity and application suitability are separate questions. A new, original part can still be wrong for the circuit. Likewise, an AOI image cannot prove all electrical characteristics or establish purchasing provenance.

Example: two capacitors with the same headline rating

Suppose a designer considers another ceramic capacitor with the same nominal capacitance, voltage rating and package size. For high-dielectric-constant MLCCs, capacitance can change under applied DC voltage. Review the exact candidate’s bias and temperature characteristics, tolerance and the circuit’s effective-capacitance requirement. The matching headline description alone is insufficient.

This is an illustrative review scenario, not a proposed interchange between specific MPNs. No performance curve, acceptance threshold or savings estimate is implied. For handling considerations after a part is selected, use our MSL and floor-life handoff guide.

4. Use a controlled substitution workflow

Identify the shortage or commercial issue. Record the original MPN, required quantity, build revision and the reason an alternative is being considered. Availability information should include when it was checked.
Propose a candidate separately. Keep the original released part visible. Attach the candidate’s full MPN and a difference list; do not silently replace a BOM cell.
Assign the engineering review. The design owner determines the necessary checks and who can authorize the change. Purchasing can compare commercial terms while approval remains pending.
Run the required evaluation. Agree any sample build, inspection, electrical or functional testing before treating the candidate as production-approved.
Record the disposition. Approve for the intended scope, approve with restrictions, reject, or leave pending. Record the specific product, revision, quantity or lot restriction.
Release the purchasing and build instruction. Update the controlled AML/BOM or issue a traceable exception. Ensure the quote, purchase order, assembly data and test documents refer to the same approved configuration.
Close the loop. Confirm what was actually purchased and fitted, retain the agreed evidence, and decide whether later orders need a renewed approval.

Original OrinewPCB concept diagram. A proposed workflow for coordinating engineering and procurement; the required tests and approval authority depend on the product.

Separately authorizing sample procurement can be reasonable while qualification is pending, but distinguish that limited action from permission to populate production boards. The written instruction should say what may be bought, how it is segregated and who accepts the financial commitment.

5. A practical approval-record example

The following fields illustrate a useful record. Identifiers are fictional placeholders, not real component recommendations or a customer case.

Assembly: Controller Board, Rev C, Variant V1
Affected item: CAP-017 at C12 and C13
Original: manufacturer and full released MPN
Candidate: manufacturer and full proposed MPN
Reason: original part unavailable for the requested build window
Evidence required: package comparison, effective-capacitance review and the circuit tests defined by the engineer
Status: candidate pending; no production substitution authorized
Final disposition: record the decision, approver, date, test reference and permitted board revision or lot.

If the evaluation later approves only a pilot lot, retain that restriction in the production instruction. Do not convert “pilot accepted” into an unrestricted approved alternative merely because the first boards powered on.

6. What to send for an approval-ready turnkey quote

Give the assembler enough information to quote both the released build and any clearly identified alternatives. Request that unresolved items remain visible instead of being hidden behind a single total price.

Released BOM, board revision, variants, DNP positions, Gerber/manufacturing files, placement data and assembly drawing.
Approved manufacturer/MPN list, pending candidates and a clear “no substitution without written approval” instruction where applicable.
Prototype and production quantities, target schedule and permitted delivery splits. These are requested requirements, not confirmed availability.
Purchasing-source, traceability and supplied-material requirements; identify any customer-provided parts separately.
Functional or electrical test requirements, firmware, fixtures and acceptance criteria; identify additional qualification work needed for alternatives.
Commercial assumptions such as minimum buy quantities, excess material ownership, quote validity and any non-cancellable commitments to be reviewed before ordering.

For each unresolved BOM line, a useful supplier response identifies the exact offered MPN, approval status, available purchasing option, quantity assumption and the action required from the design owner. A quotation based on a candidate should be marked conditional until the necessary approvals are complete.

Keep sourcing flexibility and design control together

OrinewPCB supports turnkey PCB assembly, combining PCB fabrication, component procurement and assembly with the inspection or testing agreed for your project. Our policy is to supply and assemble with 100% new, original genuine electronic components. Exact MPNs, alternatives, source requirements and project documentation should be confirmed before purchasing and production.

Send your released BOM, AML and quantity. Ask us to highlight shortages and proposed alternatives separately so your engineering team can make the approval decision. Price, stock and delivery are confirmed for the specific quotation.

Request a Turnkey PCBA & BOM Review

Need materials only? See electronic component sourcing. For the brand’s manufacturing service overview, visit OrinewPCB assembly services.

7. Approved manufacturer list FAQ

What is the difference between a BOM and an AML?

Moisture Sensitive Devices: MSL, Floor Life & Turnkey PCBA Handoff

highqualitypcb — Wed, 14 Oct 2026 03:33:02 +0000

.op-msl{--msl-green:#08754c;--msl-ink:#17372c;--msl-border:#d9e6de;color:var(--msl-ink);font-size:17px;line-height:1.75;max-width:100%;min-width:0;overflow-wrap:anywhere} .op-msl *{box-sizing:border-box}.op-msl h2{font-size:clamp(24px,3vw,32px);line-height:1.3;margin:44px 0 18px;scroll-margin-top:145px}.op-msl h3{font-size:21px;line-height:1.4;margin:28px 0 12px} .op-msl a{color:var(--msl-green);text-underline-offset:3px}.op-msl a:focus-visible,.op-msl summary:focus-visible,.op-msl .msl-table-scroll:focus-visible{outline:3px solid #e5a934;outline-offset:4px} .op-msl p,.op-msl li{margin-bottom:14px}.op-msl ul,.op-msl ol{padding-left:24px}.op-msl .msl-eyebrow{font-size:13px;font-weight:700;letter-spacing:.09em;color:var(--msl-green)} .op-msl .msl-answer,.op-msl .msl-cta{padding:24px;border:1px solid var(--msl-border);border-radius:12px;background:#f0f7f2;margin:22px 0}.op-msl .msl-answer p:last-child,.op-msl .msl-cta p:last-child{margin-bottom:0} .op-msl .msl-button{display:inline-flex;align-items:center;justify-content:center;min-height:48px;padding:12px 22px;border-radius:7px;background:var(--msl-green);color:#fff!important;text-decoration:none;font-weight:700;text-align:center;max-width:100%} body.postid-540991 #wrapper .op-msl a.msl-button,body.postid-540991 #wrapper .op-msl a.msl-button *{color:#ffffff!important} .op-msl .msl-button:hover{background:#065e3d}.op-msl figure{margin:26px 0}.op-msl img{display:block;width:100%;max-width:480px;margin-inline:auto;height:auto;border:1px solid var(--msl-border);border-radius:10px} .op-msl figcaption,.op-msl .msl-note{font-size:14px;color:#53695e;line-height:1.6;margin-top:10px} .op-msl .msl-table-scroll{width:100%;max-width:100%;overflow-x:auto;overscroll-behavior-x:contain;margin:20px 0;border:1px solid var(--msl-border);border-radius:8px} .op-msl .msl-table-scroll table{width:100%!important;min-width:620px;border-collapse:collapse!important;border:0!important;margin:0!important;table-layout:fixed} .op-msl .msl-table-scroll table th,.op-msl .msl-table-scroll table td{font-size:15px!important;font-weight:400!important;text-align:left!important;vertical-align:top!important;line-height:1.55!important;padding:13px 15px!important;border:1px solid var(--msl-border)!important;background:#fff!important;color:var(--msl-ink)!important;word-break:normal!important} .op-msl .msl-table-scroll table thead tr th{background:var(--msl-green)!important;color:#fff!important;font-size:15px!important;font-weight:700!important;border-color:#3f8d6f!important} .op-msl .msl-table-scroll table tbody tr:nth-child(even) td,.op-msl .msl-table-scroll table tbody tr:nth-child(even) th{background:#f4f8f5!important} .op-msl .msl-table-scroll table tbody th[scope="row"]{font-weight:700!important}.op-msl .msl-table-scroll table tr:first-child{border:0!important;font-size:inherit!important} .op-msl details{border:1px solid var(--msl-border);border-radius:8px;margin:12px 0;background:#fff}.op-msl summary{cursor:pointer;min-height:48px;padding:16px;font-weight:700;line-height:1.5}.op-msl details>div{padding:0 16px 16px}.op-msl details p:last-child{margin-bottom:0} .op-msl .msl-video{position:relative;aspect-ratio:16/9;min-height:220px;margin:18px 0;max-width:100%;overflow:hidden;border-radius:10px;background:#eef4f0}.op-msl iframe{width:100%;height:100%;position:absolute;inset:0;border:0} .op-msl .msl-example{border-left:4px solid var(--msl-green);padding:18px 20px;background:#f7faf8;margin:22px 0}.op-msl code{white-space:normal;overflow-wrap:anywhere;font-size:14px;background:#edf3ef;padding:2px 4px} @media(max-width:767px){body.postid-540991 .blog-column > .fusion-column-wrapper{padding-left:0!important;padding-right:0!important}.op-msl{font-size:16px}.op-msl h2{scroll-margin-top:130px}.op-msl .msl-answer,.op-msl .msl-cta{padding:18px}.op-msl .msl-button{width:100%}.op-msl .msl-table-scroll table{min-width:580px}.op-msl .msl-example{padding:16px}.op-msl figure{margin:22px 0}}

ORINEWPCB · COMPONENT HANDLING & TURNKEY PCB ASSEMBLY

Direct answer: Moisture sensitive devices need controlled handling before solder reflow. Check the exact component’s moisture sensitivity level (MSL), keep its dry-pack and exposure records, and confirm that the remaining floor life covers the planned build. An MSL 3 device typically has a 168-hour floor life at no more than 30°C and 60% relative humidity. Unknown exposure history needs review before assembly; putting a used reel into a new bag is not evidence that its floor-life allowance has restarted.

For a turnkey PCB assembly inquiry, send the BOM and build files with any supplied-part labels, bag-opening history and special handling instructions. This lets the engineering and sourcing teams identify material questions before they become production scheduling decisions.

Discuss My Turnkey PCBA Build

A component can be the correct part number, electrically suitable and available for placement, yet still need a handling decision. This guide focuses on the handoff between purchasing, stores and PCB assembly: what to check, what to record and what to ask when moisture exposure is known, uncertain or already over the stated allowance.

It is intended for hardware engineers releasing a board, product managers planning a batch and buyers comparing assembly quotations. The examples are illustrative planning tools, not customer case studies or a substitute for a component manufacturer’s process instructions.

What are moisture sensitive devices, and what does MSL mean?

Moisture sensitive devices are components whose packages require precautions against absorbed moisture when exposed to soldering heat. A package may take in moisture during ambient storage. During reflow, internal stresses associated with moisture and heating can contribute to cracking or delamination. Moisture sensitivity is therefore a material-handling issue as well as an assembly issue.

MSL describes a package’s moisture/reflow classification. It is not a universal shelf-life rating for every electronic component, and a higher number does not mean that the device has better electrical quality. The rating must be read together with the applicable environmental conditions and the component’s peak reflow limit.

Check the exact orderable part and shipment label. Do not assign one MSL to all QFNs, BGAs or parts from the same manufacturer. Microchip’s July 2020 MSL communication explains that even a package type can have different classifications when the package materials used at different assembly sites differ.

IPC/JEDEC J-STD-020 covers moisture/reflow classification; J-STD-033 covers handling, packing, shipping and use. The reviewed J-STD-033D document is dated April 2018. Use the revision specified for the project together with current product-specific guidance; a summary table alone does not define an approved factory process.

MSL floor-life reference table

Floor life is the permitted exposure interval outside a compliant dry environment before reflow, subject to the stated conditions. This quick reference matches the common classifications documented in TI’s SLVA840 and NXP’s AN1902. A shipment’s caution label and product requirements take precedence when they impose a specific restriction.

On a phone, swipe within the table or focus the table region and use the arrow keys.

MSL	Floor-life reference	Reference environment / instruction
1	Unlimited for moisture/reflow exposure under the stated condition	≤30°C and ≤85% RH; other storage and process limits still apply.
2	1 year	≤30°C and ≤60% RH
2a	4 weeks	≤30°C and ≤60% RH
3	168 hours	≤30°C and ≤60% RH
4	72 hours	≤30°C and ≤60% RH
5	48 hours	≤30°C and ≤60% RH
5a	24 hours	≤30°C and ≤60% RH
6	Mandatory bake before use; then reflow within the label’s time limit	Follow the component label and approved instructions.

These values are not a blanket permission to leave parts on a bench. Conditions above the reference temperature or humidity may reduce the usable exposure interval. If the actual environment differs, ask for a handling assessment rather than applying a guessed multiplier.

What to check when a reel or tray arrives

For a practical incoming review, ask for a traceable connection between the physical material and the BOM line. One photograph of a reel is rarely enough if it does not show the relevant label or bag condition.

Match identity: manufacturer, full ordering code, package, quantity and lot/date-code identifiers where available. Keep substituted or mixed lots separate in the record.
Inspect the packaging: note whether the moisture barrier bag (MBB) is sealed, damaged, opened or resealed. Retain the bag’s caution label and seal date.
Record the handling evidence: when opened under the procedure, check the humidity indicator card (HIC) as instructed and keep the result with the material record. An HIC is not a complete timeline of earlier exposure.
Clarify prior use: for a partial reel, ask who opened it, when, for how long and in what environment. “Stored carefully” is not a measurable exposure history.
Set a disposition: accepted for the planned process, held for clarification, assigned an approved drying step, or replaced. Identify the person responsible for releasing it.

Original OrinewPCB planning diagram. It illustrates a material-review workflow, not a photograph of customer material or a claim about a particular factory’s equipment.

Keep moisture control and ESD control separate in the checklist. Do not assume an antistatic bag is a compliant moisture barrier bag. Ask the supplier to identify the packaging and handling requirements for the exact device.

How to track cumulative floor life: an MSL 3 example

The useful question is how much permitted exposure has already been used before the next relevant reflow operation. Preparation, placement delays and interruptions need to be considered in the agreed process. Records should follow the lot, not just the purchase-order number.

Illustrative example: A labeled MSL 3 lot has a 168-hour allowance under the reference conditions. Its recorded ambient exposure is 18 hours during an earlier build, 6 hours during inspection and repacking, and 14 hours during later production preparation.

Recorded exposure = 18 + 6 + 14 = 38 hours
Planning balance = 168 − 38 = 130 hours

The 130 hours is a planning balance for this example, not a release approval. It assumes those exposure intervals were recorded under applicable conditions and that intervening storage was handled correctly. Unknown shipping or storage intervals cannot be entered as zero.

A useful lot record can contain: part number; lot identifier; label MSL and reflow limit; bag seal/open times; exposure intervals; temperature/RH evidence; storage or drying history; remaining allowance; planned process; and release authorization. There is no need to hide uncertainty: write “unknown” and resolve it.

Illustrative arithmetic only. A bag reseal or storage move does not, by itself, prove that absorbed moisture has been removed or that floor life has reset.

For double-sided assembly or later rework, ask how the handling plan accounts for all relevant heating steps. Record the release assumptions before parts are issued to the line. A spreadsheet that covers only the first placement step can miss a later scheduling gap.

When should parts be held instead of sent to assembly?

Make the decision visible to purchasing and production. This suggested review matrix helps teams ask the right question without pretending that every device has the same recovery process.

Material condition	Question to resolve	Suggested next step
Sealed bag; matching label	Are seal date, packaging condition and device requirements acceptable?	Review the evidence and release under the agreed handling process.
Opened lot; complete exposure record	Does remaining allowance cover the planned operations?	Confirm the schedule and storage plan before issue.
Opened lot; exposure unknown	Can the supplier reconstruct reliable history?	Hold for disposition. Review an approved drying route or replacement.
Floor life exceeded or HIC indicates excessive moisture	What recovery instructions apply to this device and carrier?	Use the manufacturer’s/approved-standard procedure before release.
Missing MSL or conflicting labels	Which rating applies to the actual shipment?	Obtain product/lot-specific clarification rather than guessing by package shape.

For a purchasing team, the commercial consequence is usually a decision dependency: extra review, drying, repacking or replacement may affect when material can be released. Request that dependency in the quotation. Do not convert it into a promised delay or a standard surcharge before the actual lot has been reviewed.

Why there is no universal baking recipe

Baking time and temperature depend on the device, package thickness, exposure history and approved drying method. Shipping carriers have their own temperature limits. Microchip specifically notes that its MSL 1 products can ship in non-bakeable trays; a tray should not be treated as heat-compatible merely because the component is.

Before authorizing a drying step, ask:

Which component instruction and standard revision define the procedure?
Is the reel, tape, tray or tube rated for that temperature, or must parts be transferred to an appropriate carrier?
What records will show the completed drying step and subsequent storage?
How will the lot remain identifiable during any transfer, splitting or repacking?
Who will confirm that the material can re-enter the assembly process?

Likewise, placing material into a dry cabinet does not automatically establish a new 168-hour allowance. The storage conditions, duration and applicable procedure must support any pause or recovery claim. Record the transition instead of deleting the earlier exposure history.

Bare PCBs need their own assessment. This component MSL table is not a universal PCB baking specification. Discuss board material, finish and fabrication guidance separately; a component-handling instruction should not be copied onto a bare-board work order without review.

Full turnkey versus supplied parts: assign the handling owner

A turnkey PCB assembly project can connect PCB fabrication, component procurement and assembly through one project review. It still needs explicit decisions about material evidence and any parts supplied by the customer. Use the following responsibility checklist when comparing scopes.

Build model	Information to agree	RFQ question
Full turnkey	Supplier sourcing route, incoming evidence, lot handling and any review exceptions.	How will moisture-sensitive BOM lines be reviewed before production release?
Partial turnkey	Separate purchased and customer-supplied lots; name the owner for each handoff.	Which supplied parts need label photos or exposure records before quotation is confirmed?
Customer-supplied parts	Shipment condition, open/reseal history, quantity and acceptance/disposition responsibility.	What happens if the received lot has unknown exposure or unsuitable packaging?
Repeat build with leftover material	Retained lot quantity, storage records and status since the previous order.	Can the remaining material be released for the new build, and what evidence supports that?

Engineers should resolve the component and process limits. Product managers should make material release a prerequisite for the planned build date. Buyers and business owners should compare responsibility and scope exclusions alongside price. These are recommended project controls, not claims that a particular supplier includes every activity by default.

For a broader scope comparison, see the partial turnkey PCBA sourcing checklist and the brand’s OrinewPCB turnkey assembly overview.

MSL handoff checklist for a turnkey PCBA quote

You can start a discussion while some documents are pending. Mark those gaps clearly so the preliminary scope is not mistaken for production release. Include these inputs:

Build identity: board name, revision, assembly variant and requested prototype/production quantities.
Fabrication and assembly data: Gerber or agreed fabrication files, BOM, placement file and assembly drawing.
BOM detail: full manufacturer part numbers, approved alternatives, DNP positions and which parts are customer-supplied.
Moisture-sensitive material: label photos, lot quantities, MSL/reflow requirements, bag status and known exposure/storage history.
Process requirements: double-sided assembly, secondary soldering, programming, testing or rework restrictions that need review.
Planning information: target date, delivery destination and the contact authorized to approve material questions or substitutions.

Copy this inquiry outline:

“Please review full turnkey PCB fabrication, BOM sourcing and assembly for [board/revision], at [quantities]. Customer-supplied parts are [list/none]. Moisture-sensitive lot labels and available exposure records are attached; unknown items are marked. Please identify handling questions, any drying or replacement decisions, scope exclusions and the information needed to confirm the build schedule. Programming/test requirements are [details/pending].”

Keep the moisture record alongside the other release documents. The prototype-to-production checklist covers the wider release decisions; this article provides the specific component-exposure handoff.

Frequently asked questions

What does MSL 3 mean for PCB assembly?

PCB Assembly Drawing: A Practical Guide for Turnkey PCBA

highqualitypcb — Tue, 13 Oct 2026 12:57:16 +0000

ORINEWPCB · DESIGN HANDOFF & TURNKEY PCBA

A PCB assembly drawing tells an assembler how to populate and finish a circuit board. It should make board identity, top and bottom views, reference designators, polarity, pin 1, do-not-populate (DNP) positions and special assembly instructions clear. Release it with a matching bill of materials (BOM) and component placement file.

For a turnkey PCB assembly inquiry, the drawing helps connect your engineering intent to component sourcing, placement, secondary assembly and the agreed test scope. This guide gives hardware engineers a practical drawing checklist, product managers a release workflow, and buyers a way to identify quotation gaps.

Request a Turnkey PCBA Quote

What a PCB assembly drawing does

A useful drawing removes ambiguity at the point where a CAD design becomes a build instruction. The assembler needs to know which component belongs at each reference, which side it belongs on and which operations are required after placement. Connector orientation, polarized parts, hardware, wires and variants deserve particular attention.

For example, a BOM may identify connector J2 precisely while a placement file supplies its location. The drawing can clarify the mating direction, fitted height or mechanical constraint that matters to the product. Those details should come from the released design and component documentation.

The drawing is also a communication reference during review. A question such as “Is R9 fitted on Variant A?” is easier to resolve when the engineer, sourcing team and assembler refer to the same marked view and revision. It does not replace a review of the other manufacturing files.

Assembly drawing vs. BOM, Gerber and placement files

Each file answers a different question. Treat the release as a coordinated package, rather than expecting one document to communicate everything. Swipe the tables horizontally on a phone.

Document	Main purpose	Check before sending
Assembly drawing	Visual placement intent, orientation, variants and assembly notes.	Readable top/bottom views, references, DNP status and revision.
BOM	Identifies the parts to procure or supply for each fitted position.	Exact manufacturer part numbers, quantities, references and approved alternatives.
Placement / CPL file	Machine-readable component position, rotation and board side.	Units, origin, reference-point convention, bottom-side convention and export filters.
Gerber + drill data	Defines the PCB layer artwork and drilling information.	Matching board revision, complete required layers, drills and outline.
Fabrication drawing	Defines bare-board specifications and requirements.	Stack-up, thickness, materials, finish, tolerances and other design requirements.
Programming / test instructions	Defines firmware loading and agreed verification.	Version, equipment, access, limits, records and responsibilities.

An integrated data format may carry fabrication and assembly information together. Confirm the assembler’s accepted format and the additional instructions still needed. For a project quotation, our turnkey assembly scope guide explains how fabrication, sourcing and assembly fit into one request.

The PCB assembly drawing checklist

1. Identify the board, document and build variant

Include the board or assembly part number, drawing number, revision, date, sheet number and variant name. Use meaningful identifiers that match the rest of the release package. If the assembly revision and bare-board revision differ, state their approved relationship explicitly.

Label the status of an early drawing as provisional or for quotation when appropriate. A product manager should be able to distinguish the package used for budgeting from the package authorized for production.

2. Show the relevant board views clearly

Provide separate top and bottom views when both sides contain fitted parts. Label the viewing direction and ensure the bottom view cannot be confused with a transparent top view. Show the board outline and enough recognizable features to orient the reader.

Use detail or side views where the normal plan view cannot explain a connector, bracket, height constraint or wire attachment. State critical dimensions from the design; do not ask the operator to infer them from print scale.

3. Make reference designators and orientation readable

Every fitted component should be traceable to its BOM reference. Keep labels out of crowded outlines where possible, and use enlarged details for dense areas. Check the PDF at normal reading size, not just while zoomed in inside the CAD tool.

For polarized parts and ICs, communicate the relevant orientation or pin 1 information. Cross-check component markings against the actual manufacturer part number and datasheet. A body stripe or dot is not a universal polarity convention across all component types.

4. Define DNP parts and variants consistently

DNP means a component position is intentionally not populated for a specific build. Mark it on the drawing and in the BOM or controlled variant list. Confirm whether the placement export excludes DNP parts or includes them with an agreed status field.

If two product variants use the same PCB, release variant-specific instructions instead of relying on a verbal note. A component alternative also needs approval; it should not become a different variant accidentally.

5. Specify secondary assembly and mechanical details

Identify through-hole connectors, leads, jumpers, wires, brackets, heatsinks, adhesive or other operations when required. Provide installation direction, material and relevant limits. Confirm these details when reviewing through-hole PCB assembly or mixed-technology work.

For coating or cleaning requirements, define the specified process, keep-outs and acceptance criteria in the relevant drawing or linked instruction. If a connector must remain accessible for programming or testing, make the process sequence clear.

6. Reference the agreed programming and acceptance instructions

Identify the test procedure and firmware release by document or file reference. Define required inspections, functional checks, fixtures and result records in the RFQ. An assembly drawing does not itself establish functional performance or certify the finished product.

If an acceptance standard is specified, identify its document, revision and class, plus customer-specific requirements. Ask the supplier to confirm the quoted scope; special testing, programming or fixture development should be explicit.

PCB assembly drawing example: five details to review

Original OrinewPCB concept illustration. It is not a customer design, production drawing or scale reference. Tap the image to open the full-size view.

J1 reference: the label connects the visual position to the corresponding BOM line.
U1 pin 1: the marked corner makes the intended orientation visible; the actual part documentation must confirm it.
J2 connector: the view shows a placement position, but an application may also need mating-direction and height details.
C1 polarity: the example uses a positive terminal callout. The released drawing should identify the real part’s required polarity.
R9 DNP: the position is deliberately unpopulated in the illustrated variant and should agree with the variant BOM.

Consider a review finding: the drawing says “R9 DNP,” but the BOM orders one R9 per board and the placement export includes it. Stop and resolve that conflict through a controlled revision or approved clarification. The assembler should not guess which file wins.

Reference	Illustrative drawing intent	Release check
J1 / J2	Install the specified connectors.	Exact part number and fitted quantity match the BOM; direction and height are clear.
U1	Fit the selected IC with pin 1 at the marked corner.	BOM package, footprint and placement orientation refer to the same approved device.
C1	Fit the specified polarized capacitor.	Drawing polarity and the actual component marking are consistent.
R9	Do not populate on Variant A.	DNP status agrees across drawing, BOM/variant list and placement-export handling.

How to create and verify the drawing

Freeze the intended revision. Confirm the board layout, BOM and variant definition before generating release outputs.
Generate views from the CAD project. Use assembly or fabrication-layer views with the relevant outlines, references and orientation information. Remove visual clutter that does not communicate build requirements.
Add the missing instructions. Include document identity, special operations, details and references to test or programming instructions.
Export a readable document. PDF is practical for review when accepted by your assembler. Keep the original CAD project under your own release control.
Compare the exports. Check drawing references and fitted quantities against the BOM and placement file. Review at least the polarized parts, ICs, connectors, DNP positions and non-standard operations.
Obtain approval and package the release. Record which package was reviewed and accepted, and keep later changes distinguishable from that release.

Altium Designer: assembly outputs and Draftsman board assembly views can produce the visual documentation. Review the selected side, component display and variant before export. Placement export configuration separately controls coordinates, units and included components.

KiCad: select the relevant documentation layers when plotting or printing; F.Fab and B.Fab can show component information and DNP indications according to export settings. Placement export separately controls units, origin and DNP handling. Verify the actual outputs for the version and settings you use.

Rotation and bottom-side conventions can differ between exports and assembly workflows. Document the convention and ask the assembler to confirm it during data review. Do not manually reverse bottom-side coordinates based on an assumed universal rule.

Common file conflicts that delay a turnkey PCBA build

Problem	Why it matters	Action before release
Mixed revisions	Procurement and placement may follow different designs.	Regenerate and identify a matching approved package.
Ambiguous pin 1 or polarity	The fitted part may face the wrong direction.	Check the actual component documentation and add an unambiguous callout.
DNP disagreement	A variant may be populated incorrectly.	Align the drawing, BOM/variant list and placement-file handling.
Units or origin not stated	Placement coordinates may be interpreted incorrectly.	State units and export origin, then confirm the assembly interpretation.
Missing mechanical details	A correctly soldered connector or heatsink may not fit the product.	Provide detail views and design dimensions where required.
Test scope left open	Quotations may exclude fixtures, programming or needed verification.	Define procedure, equipment, acceptance and reporting in the RFQ.

Use the prototype-to-production checklist for the wider release process. To compare quotations on equal scope, see our turnkey PCB assembly cost breakdown.

Watch: what to send for a PCB and PCBA quotation

In this official OrinewPCB video, the five quotation inputs include PCB manufacturing data, board specifications, quantity, a clean BOM, and assembly or testing information. Use it as a short overview alongside the drawing checks above.

Watch this video on YouTube · OrinewPCB official channel

Video: “How to Get a Fast, Accurate PCB Quote | 5 Things to Send,” OrinewPCB, published October 9, 2026. The quoted project scope and schedule still require a review of your actual requirements.

Prepare one release package for your RFQ

A clear folder structure helps the recipient identify what is current. The names below are examples, not mandatory formats:

Controller_RevB_VariantA_RFQ/
  01_PCB_Fabrication_RevB/
  02_BOM_RevB_VariantA.xlsx
  03_Placement_RevB_VariantA.csv
  04_Assembly_Drawing_RevB_VariantA.pdf
  05_Programming_and_Test_Requirements.pdf
  06_RFQ_Quantity_Date_Destination.txt

Hardware engineer: approve the file consistency, orientation, variant and technical instructions. Product manager: identify sample and batch quantities, open decisions, target date and release owner. Buyer or business owner: confirm sourcing responsibility and compare complete quoted scope, rather than assembly price alone.

For full turnkey, specify PCB fabrication, BOM sourcing and assembly together. If you supply selected components, identify those BOM lines and use the partial turnkey sourcing checklist. You can also review one-stop PCB assembly on the OrinewPCB brand website and learn about OrinewPCB.

PCB assembly drawing FAQ

What is a PCB assembly drawing?

Prototype to Production PCB Assembly: 7 Release Checks

highqualitypcb — Mon, 12 Oct 2026 01:30:49 +0000

.orinew-production-guide{max-width:980px;margin:0 auto;color:#203a2e;font-size:18px;line-height:1.75;overflow-wrap:break-word}.orinew-production-guide *{box-sizing:border-box}.orinew-production-guide h2{font-size:clamp(25px,3vw,34px);line-height:1.25;margin:44px 0 18px;color:#15362a;background:transparent!important}.orinew-production-guide h3{font-size:23px;line-height:1.3;margin:26px 0 14px;color:#15362a}.orinew-production-guide p{margin:0 0 20px}.orinew-production-guide li{margin:9px 0}.orinew-production-guide a{color:#217a3c;text-decoration:underline;text-underline-offset:3px}.orinew-production-guide section[id]{scroll-margin-top:160px}.orinew-production-guide .og-note{font-size:15px;color:#53675b}.orinew-production-guide .og-answer,.orinew-production-guide .og-cta,.orinew-production-guide .og-example{padding:26px;border:1px solid #d4e2d8;border-radius:12px;background:#eff6f1;margin:26px 0}.orinew-production-guide .og-answer h2,.orinew-production-guide .og-cta h2{margin-top:0}.orinew-production-guide .og-button{display:inline-flex;align-items:center;justify-content:center;background:#248b43;color:#fff!important;padding:14px 24px;min-height:48px;border-radius:6px;font-weight:700;text-decoration:none}.orinew-production-guide a:focus-visible,.orinew-production-guide summary:focus-visible{outline:3px solid #efae22;outline-offset:4px}.orinew-production-guide .og-table{overflow-x:auto;margin:24px 0}.orinew-production-guide table{width:100%;min-width:620px;border-collapse:collapse;font-size:16px}.orinew-production-guide th,.orinew-production-guide td{padding:15px;text-align:left;vertical-align:top;border:1px solid #d5e2d8}.orinew-production-guide th{background:#edf5ef}.orinew-production-guide figure{margin:28px 0}.orinew-production-guide figure img{width:100%;height:auto;border-radius:10px}.orinew-production-guide figcaption{font-size:15px;color:#53675b;margin-top:10px}.orinew-production-guide .og-video{aspect-ratio:16/9;min-height:200px;background:#eef3ef;border-radius:10px;overflow:hidden}.orinew-production-guide iframe{width:100%;height:100%;border:0;display:block}.orinew-production-guide .og-stages{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:18px;margin:24px 0}.orinew-production-guide .og-stages div{padding:22px;border:1px solid #d5e2d8;border-radius:10px;background:#f5f8f5}.orinew-production-guide .og-stages strong{display:block;color:#217a3c;margin-bottom:10px}.orinew-production-guide .og-faq details{border-bottom:1px solid #d5e2d8;padding:18px 0}.orinew-production-guide summary{cursor:pointer;font-weight:700}.orinew-production-guide .og-faq p{margin-top:15px}.orinew-production-guide .og-toc{padding:20px 24px;border-left:4px solid #248b43;background:#f5f8f5}.orinew-production-guide .og-toc ul{margin-bottom:0}@media(max-width:650px){.orinew-production-guide{font-size:17px}.orinew-production-guide .og-stages{grid-template-columns:1fr}.orinew-production-guide .og-answer,.orinew-production-guide .og-cta,.orinew-production-guide .og-example{padding:20px}.orinew-production-guide .og-button{width:100%;text-align:center}.orinew-production-guide h2{margin-top:34px}.orinew-production-guide th,.orinew-production-guide td{padding:12px}} #blog-content .orinew-production-guide a.og-button{color:#fff!important;background:#207a39!important;border-color:#207a39!important;text-decoration:none;min-height:50px}.orinew-production-guide a.og-button:hover{background:#15582a!important}.orinew-production-guide a.og-button:focus-visible{outline:3px solid #ffaa06;outline-offset:4px}

A practical guide from OrinewPCB for hardware teams and buyers preparing a repeatable PCBA build.

Your prototype powers up, the firmware runs, and the first demonstration succeeds. The next decision is different: is the complete manufacturing package ready for a repeatable batch? A working sample confirms what that sample did under the conditions you checked. It does not establish the consistency of future component lots, assembly setups or production tests.

This prototype-to-production PCB assembly checklist helps you define what should be reviewed before committing to a pilot build or a larger order. It applies to full turnkey projects and to builds where you supply selected PCBs or components.

What should you check before batch PCB assembly?

Review seven areas: the released file revision, BOM and approved parts, manufacturability, material and process readiness, first-article approval, inspection and functional tests, and written production release. Assign an owner and acceptance evidence to each area. Resolve open issues before releasing the affected purchasing or manufacturing work.

Request a Prototype & Batch PCBA Quote

Send your sample quantity, next-batch quantity and available files. If files are incomplete, start with your requirements.

Prototype, pilot build and production: what changes?

A prototype helps investigate the design. A pilot build checks how an agreed design and manufacturing process behave across a limited batch. Production repeats the approved build with controlled materials, instructions and acceptance checks. These are project stages, not fixed order quantities.

PrototypeUnderstand circuit behavior and record design changes.

Pilot buildReview assembly repeatability, test preparation and remaining issues.

ProductionRelease the approved build and control later changes.

For low-volume and high-mix PCB assembly, the same planning matters even when the batch is small. Different BOM variants can create more opportunities for confusion than a larger order of one stable design.

PCB assembly production checklist: seven release checks

Use these checks as a starting point for your project-specific release plan.
Check	Evidence to agree	Typical release blocker
1. File revision	One approved manufacturing package	Gerber, BOM or placement files disagree
2. BOM & sourcing	Part numbers, supply scope and approved alternatives	An unapproved replacement or unresolved shortage
3. DFM / DFA	Closed issues or documented, approved actions	A footprint, polarity or assembly-access issue remains open
4. Build readiness	Material status, panel plan and assembly instructions	Materials or process preparation are incomplete
5. First article	Agreed sample checks and approval route	The team has not defined what approval covers
6. Inspection & tests	Coverage, firmware, fixtures and pass/fail criteria	A board can look correct without its functions being checked
7. Production release	Written scope, revision and change-control instructions	Engineering and purchasing are approving different builds

1. Freeze one manufacturing revision

Package the Gerber and drill files, BOM, component placement file, assembly drawings and fabrication notes together. Identify the board revision in the package and in a short release manifest. Include firmware and programming instructions when they are part of the build.

Cross-check reference designators between the BOM, placement data and assembly drawing. Label do-not-fit positions and variant differences. For placement data, identify the units, board origin, board side and rotation convention; do not assume that every exported file uses the assembler’s expected convention.

Release question: can the manufacturer identify the intended build without choosing between conflicting files?

2. Confirm the BOM and purchasing responsibilities

Specify the manufacturer and full manufacturer part number for sourced items. A value such as “10 kΩ resistor” is not a complete purchasing instruction: package, tolerance, power rating and other design-relevant characteristics may matter. Review component availability before fixing the production schedule.

List approved alternatives and parts that must not be substituted. A matching footprint does not prove electrical or firmware compatibility. The customer’s design owner should approve material changes against the application requirements.

For full or partial turnkey PCB assembly, record who supplies each material, the available quantity and expected arrival date. Ask the assembler to confirm handling allowances and packaging requirements rather than assuming a universal spare-parts percentage.

Release question: are the purchasing list, supplied-material inventory and substitution decisions clear?

3. Close DFM and DFA questions

Design for manufacturability (DFM) checks whether the board can be fabricated using the planned process. Design for assembly (DFA) reviews how parts can be placed, soldered, handled and inspected. Neither review replaces verification of the circuit’s intended function.

Review footprints, component orientation and polarity against the released part list.
Discuss fine-pitch devices, hidden joints, connectors and temperature-sensitive parts.
Confirm panelization responsibility, tooling features, clearances and separation requirements.
Resolve assembly access and mechanical-fit questions before the build begins.

Record each issue, the proposed action and who approves it. If a review changes the design, reissue the affected files together. For the process options, see OrinewPCB SMT assembly services.

Release question: have the manufacturing issues been closed or explicitly addressed in the approved plan?

4. Check materials and process readiness

The same design can need additional preparation when the batch or material source changes. Confirm the agreed PCB specifications, component packaging, incoming-material checks and assembly instructions. Review storage and moisture-sensitive handling against the applicable material requirements.

The manufacturing team should plan stencil work, placement setup, soldering sequence and the process settings required by the actual board and components. A prototype’s manually adjusted build should not silently become the production instruction.

Release question: are the materials ready, and can the approved assembly sequence be repeated?

5. Agree on first-article approval

Define the first-article sample quantity, checks, reporting format and approval owner before production. Depending on the project, the review may include component identity and orientation, assembly workmanship, dimensional fit, programming and agreed electrical or functional checks.

A photograph can support a visual review. It does not by itself confirm component parameters, hidden solder joints or functional performance. If physical samples need to be shipped for customer testing, include that step in the schedule and state which work may proceed while approval is pending.

Release question: does everyone know what the approval proves and who can release the remaining batch?

6. Define inspection and functional test coverage

AOI and visual inspection assess placement and visible assembly features. X-ray can help assess hidden solder connections. Functional testing checks operation under a specified procedure. Each method answers a different question; the build plan should state which methods are required and what evidence is retained.

X-ray supports inspection of hidden connections. Functional performance needs its own defined checks.

For programming or functional testing, identify the firmware version, test access, fixtures, power conditions, sequence and pass/fail limits. Agree on test coverage, records and how failures are handled. A vague instruction such as “test every board” is not a complete test specification.

Review the OrinewPCB factory and quality-control workflow when preparing the scope.

Release question: can the team determine whether a board passes using the agreed instructions?

7. Release the batch and control later changes

Record the approved board revision, BOM variant, quantity, material responsibilities, inspection and test scope, and delivery requirements in the production release. Match the engineering package to the commercial order so neither team is authorizing a different build.

After approval, identify changes that require review: a substituted component, new PCB revision, different firmware, revised test limit or changed manufacturing instruction. Decide which checks must be repeated before the affected work continues.

For repeat orders, reference the approved build and identify differences explicitly. A reorder should not rely on a remembered verbal agreement.

Release question: is the build authorized in writing, with a clear route for handling changes?

Watch: why a working prototype may face batch PCBA risks

In this official OrinewPCB video, a working prototype is the starting point for reviewing component-related variables, manufacturability and pre-production quality checks. Use the seven release checks above to define the evidence your team needs before a pilot build or production batch.

Watch this video on YouTube · OrinewPCB official channel

The 500-unit batch in the video is an example, not a minimum order quantity. Inspection and functional-test scope should be agreed for your specific project.

Explore OrinewPCB factory and quality control · Review full turnkey PCB assembly scope

Example: a late component change before a pilot build

Illustrative scenario, not a customer case: a team approves its prototype with one regulator, then proposes a different part because the original is unavailable for the next batch.

The right next step is to record the exact replacement and ask the design owner to review relevant electrical, package and operating requirements. Update the approved BOM, identify any affected assembly or test instructions, and decide whether new samples or additional verification are needed before release.

The lesson is practical: solving a shortage and approving a design change are separate decisions. Both should be recorded.

What to send for a turnkey prototype-to-production review

Send the information you have now, and clearly mark what is still in progress. A useful request includes:

Application and stage: what the board does, what has been checked on the prototype, and what remains open.
Quantities: samples, the next batch and any expected repeat order. State assembled-board quantity clearly.
Files: released Gerber and drill files, BOM, placement data, drawings and fabrication notes.
Materials: full turnkey or partial turnkey scope, approved alternatives and customer-supplied inventory.
Verification: first-article requirements, firmware, fixtures, test procedure and acceptance criteria.
Schedule: target delivery date and destination, including time needed for customer sample approval.

PCB fabrication, component availability, setup work and the agreed test scope all affect the quotation. Identify these items together so you can compare the complete build, not just an assembly charge.

Planning your next PCBA batch?

OrinewPCB coordinates PCB fabrication, component sourcing and assembly for turnkey projects. Send your prototype status, board files and next-batch requirements so the team can review the build scope and inspection or test plan with your quote.

Request a Turnkey PCBA Build Review & Quote

Not ready to upload files? Describe the application, quantity and support you need in the quotation form. Material availability, test scope and delivery are confirmed for the project.

Compare full and partial turnkey services · Explore small-batch assembly

Prototype-to-production PCB assembly FAQ

Does a working PCB prototype prove that a production batch will work?