What happens after the first review
Why small batches fail before assembly starts
Many problems begin with a mixed file package, an incomplete BOM, or an unrecorded substitution. PCBLaunch starts by naming the build revision, checking whether fabrication and assembly data describe the same board, and listing questions that could change cost, function, or repeatability.
Sourcing without hiding uncertainty
The BOM is reviewed for identifiable parts, alternates, customer-supplied items, and components that require a decision. An alternative is not treated as equivalent simply because it fits the footprint. Electrical role, package, temperature, tolerance, lifecycle, and customer approval may all matter.
A controlled first build
Where the project needs it, a first article or a small initial quantity can be used to confirm assembly direction, programming access, connector orientation, and the practical test method before the rest of the batch proceeds. The exact hold point is agreed per project.
Testing belongs in the build definition
Power-on, continuity, programmed functional checks, or another method can be added when the required fixture, firmware, procedure, and expected result are available. The site does not assume that every board can be proven by the same test.
Preparing repeat orders
A repeat order should begin from a known released package, not from an old email thread. PCBLaunch keeps the focus on revision identity, approved component decisions, known issues, and the records needed to explain what changed since the previous build.
A five-stage project path
- 01
Identify the release
Name the revision, quantity, files, variants, and approval owner.
- 02
Review sourcing
Separate fixed parts, possible alternatives, customer supply, and open decisions.
- 03
Confirm the build
Agree fabrication, assembly, first-article, programming, and test scope.
- 04
Build and record
Track issues, approvals, rework, observations, and any accepted deviation.
- 05
Prepare the next release
Return the agreed boards and records, with changes tied to the next revision.
Expected project outcomes
01
A build scope tied to one revision
02
Recorded sourcing and substitution questions
03
Assembly and test scope confirmed before execution
04
Issue and change notes that can support the next batch
05
Handover material agreed for the project
Boundaries that stay visible
Board construction, quantity, pricing, timing, component availability, test coverage, and handover records are confirmed from the submitted project. Partner facilities are coordinated when required and are not presented as PCBLaunch-owned factories.
Frequently asked questions
Do you require a fixed minimum quantity?
No universal quantity is published. Quantity, board complexity, sourcing, and test scope are reviewed together.
Can we supply some components ourselves?
Yes, customer-supplied and locally sourced parts can be separated in the BOM and receiving plan.
Can you use alternative components?
Alternatives can be proposed, but approval and technical suitability must be recorded before they enter the build.
Is testing included automatically?
No. The method, coverage, equipment or fixture, firmware, and acceptance rule are confirmed per project.
What helps the second batch run better?
A released file package, approved sourcing decisions, clear issue notes, and a record of changes from the first build.
Can you coordinate fabrication and assembly together?
Yes. PCBLaunch can coordinate fabrication, sourcing, assembly, testing, and handover through one project contact, using suitable production partners where required.