China PCBA project kickoff: OEM readiness checklist before the line opens

When an overseas hardware team awards a China EMS or PCBA partner, the first meeting is often treated like a kickoff slide deck: introductions, a quote, a tentative date. That is not enough. A useful China PCBA kickoff freezes what this build is for, which file revisions are live, who owns BOM risk and substitutions, who owns stencil / fixtures / programming / test firmware, and what evidence must exist before the line loads. Miss those, and the delay usually shows up as “waiting on parts,” “wrong CPL,” or “fixture not ready”—not as a clean engineering decision.

This guide is for overseas founders, NPI leads, hardware/EE leads, and procurement or supply-chain owners who are starting a China / Shenzhen PCBA collaboration (including work coordinated through a Shenzhen-side product-and-manufacturing partner such as ShenzhenWorks). It is a practical readiness checklist, not a generic manufacturing FAQ for any country.

A typical scene: first China PCBA after local prototypes

A mid-size overseas team has already run two spins on a local quick-turn fab. Boards work on the bench. They move the third spin to China for cost, capacity, and a path toward small-batch OEM. At kickoff they send “latest Gerbers,” a BOM spreadsheet, and a Slack thread of open issues. The China line quotes a start date. Two weeks later:

• The BOM revision on the PO does not match the Gerber package name.
• Two critical ICs are long-lead; nobody named who may approve alternates.
• The stencil is ordered from an old paste layer.
• Functional test assumes a firmware image that only exists on one engineer’s laptop.
• DFM feedback sat in email with no disposition owner.

None of that is exotic. It is what happens when kickoff is treated as a calendar event instead of a controlled baseline.

Freeze the build purpose and validation scope first

Before debating price or MOQ, write one clear sentence for this build, for example:

• “EVT electrical bring-up, 20 boards, no conformal coat, programming + basic power-on test only.”
• “DVT candidate, 50 boards, full ICT + FCT against released test plan v1.2, firmware locked to tag X.”
• “Pilot / soft tooling bridge, 200 boards, production-intent process, ECO freeze window defined.”

Then list what this build will and will not validate (mechanicals, RF, thermal, drop, certification samples, customer pilots). China PCBA partners often optimize for throughput once material is released. If validation scope is vague, the factory will optimize for the quote you already signed—not for the learning you still need.

Decision condition: kickoff is incomplete until build purpose + out-of-scope items are written and acknowledged by customer engineering and the China-side coordinator.

Revision matching: one indexed package, not a folder of “final_final”

China EMS workflows are revision-driven. At kickoff, lock a single indexed package where these match by revision (or by an explicit mapping table):

• BOM (with MPNs, manufacturer, refdes, qty, alternates policy)
• Gerber / ODB++ (including paste, silk, outline, stackup notes)
• CPL / centroid / pick-and-place
• Schematic PDF (or controlled export) for DFM clarification
• Assembly drawing / board top-bottom callouts
• Test instruction / FCT steps (even if still draft—version it)
• Programming instruction and the exact firmware artifact identity (hash or release tag)

Require a package index (file list + revision + date + owner). “Latest files in Drive” is not a baseline. Mixed revisions can easily trigger avoidable rework or line-start delays.

Evidence gate: no material release until package index is signed (email acceptance is fine if the index ID is quoted).

BOM risk, shortages, alternates, and sign-off authority

At kickoff, classify BOM lines into at least:

1. Must-exact MPN (RF front-end, MCU, safety-related, calibrated parts)
2. Approved alternate list (already qualified)
3. Needs engineering approval before substitute
4. Commodity with documented rules (passives within tolerance/voltage)

Name a single customer-side BOM risk owner and a China-side sourcing lead. Define:

• Who may approve a shortage substitute, and within what SLA
• What evidence is required (datasheet delta, pin-compat, life-cycle, price/lead)
• Whether consignment vs turnkey changes the approval path
• How AVL changes are written back into the controlled BOM

Do not leave “use equivalent” as a verbal instruction. When sourcing alternatives in Shenzhen, multiple replacement options may become available quickly; without clear approval rules, substitutions can create engineering risk.

Tooling, fixtures, programming, and test firmware ownership

List each item with owner, due date, and “ready for line” definition:

• Stencil (paste revision, thickness, supplier)
• ICT fixture / bed-of-nails (if used)
• FCT fixture / harness / DUT interface
• Programming station setup and fixture
• Golden sample / reference boards
• Test firmware / bootloader image and checksum
• Labels, serialization, packing notes (if already needed for this stage)

Clarify who pays, who designs, who stores, and who updates after ECO. Many overseas teams assume “the factory owns fixtures”; many factories assume “customer provides FCT.” Kickoff is where that gap becomes a schedule slip.

DFM disposition and the pre-line evidence gate

A China DFM report is useful only if dispositions are closed. At kickoff, define:

• Who answers each DFM item (customer EE / ME / China coordinator)
• Allowed responses: accept as-is / change design / change process / defer to next spin
• Deadline before stencil cut and kit release
• Component verification / incoming check expectations for high-risk parts
• What blocks line loading (open DFM Crits, missing CPL, unresolved long-lead, unsigned test plan)

Evidence gate before line load: closed DFM Crits, matched package index, kit completeness or written shortage plan, stencil/fixture ready flags, programming image verified on at least one dry-run path if programming is in scope.

What the customer should prepare before kickoff

Bring (or share in the indexed package) at least:

1. Build purpose + validation scope one-pager
2. Full revision-matched file package + index
3. BOM with risk classes and alternate policy
4. Known long-lead / sole-source list
5. Current known bugs and open ECOs (what must not ship into this spin)
6. Test intent: what must pass to call the build successful
7. Compliance constraints that affect process (RoHS, coating, cleaning limits)—only as they affect this build’s process choices
8. Shipping / sample distribution plan for the finished boards
9. Named owners: engineering, procurement, China-side day-to-day contact
10. Decision SLA for substitutes and DFM replies (e.g. 1 business day during kit pull)

Responsibility boundaries: customer · ShenzhenWorks / coordinator · factory

Keep roles explicit so messages do not bounce:

| Topic | Customer | ShenzhenWorks / project coordinator (when used) | Factory / EMS | |---|---|---|---| | Product requirements & pass/fail intent | Owns | Helps translate into build/test plan | Executes agreed plan | | Design files & revision authority | Owns | Checks package completeness; flags mismatches | Manufactures to released package | | BOM risk & substitute approval | Owns final sign-off | Surfaces options, lead times, AVL impact | Purchases to approved BOM / instructions | | Stencil / fixtures / programming setup | Defines need & accepts design | Coordinates scope, vendors, schedule | Builds/holds tooling as contracted | | DFM answers | Owns design dispositions | Tracks closures; escalates blockers | Issues DFM; applies agreed process | | Schedule & evidence gates | Sets priorities | Runs readiness review before release | Reports kit/line status |

ShenzhenWorks, when engaged as the Shenzhen-side collaboration layer, is typically strongest at package readiness, China process translation, multi-vendor coordination, and evidence gates—not at silently replacing your engineering ownership.

How readiness changes from prototype / EVT to DVT / pilot

Prototype / early EVT

• Smaller qty; more engineering change expected
• Test may be manual bring-up; fixtures can be temporary
• Alternates more restricted on critical nets; speed of ECO matters
• Document “known open issues” so the factory does not “helpfully” fix them

Late EVT → DVT

• Freeze window appears; ECO control tightens
• FCT / ICT intent should be written; fixture ownership becomes schedule-critical
• Firmware tags should be releasable artifacts, not laptop builds
• DFM dispositions should trend toward process capability, not one-off hand work

Pilot / early production-intent

• Package and BOM treated as production candidates
• Incoming quality, serialization, packing, and yield learning enter the gate
• Substitute rules must match the AVL you will live with in MP
• Do not kick off pilot with EVT-level ambiguity and expect MP-stable results

Five common kickoff failures (and how to avoid them)

1. Mixed revisions across BOM / Gerber / CPL — Use one indexed package; refuse kit pull on mismatch.
2. No substitute authority — Name the approver and SLA before sourcing starts.
3. Stencil cut before DFM Crits closed — Tie stencil release to disposition log.
4. Test/programming orphaned — Assign firmware artifact ID and fixture owner in the kickoff minutes.
5. Validation scope unclear — Write the one-sentence build purpose; if it cannot be written, you are not ready to kick off.

Kickoff readiness checklist (copy into the meeting notes)

• [ ] Build purpose + validation scope written
• [ ] Package index with matching BOM / Gerber / CPL / drawings / test docs
• [ ] BOM risk classes + substitute sign-off owner
• [ ] Long-lead / sole-source list reviewed
• [ ] Stencil / ICT / FCT / programming ownership and dates
• [ ] Firmware / image identity defined
• [ ] DFM disposition process + pre-line evidence gate agreed
• [ ] Named customer / coordinator / factory contacts and SLAs
• [ ] Stage-appropriate expectations (EVT vs DVT vs pilot) acknowledged

Kickoff is done when owners and evidence exist—not when the meeting ends.

Next step with ShenzhenWorks

If you are preparing a China / Shenzhen PCBA or early OEM build and want a readiness review before material release, share your current package index, BOM risk list, and build-purpose note with [ShenzhenWorks](https://www.shenzhenworks.com). We can help you identify what is ready, what is blocking, and what should be frozen before material release and line loading.