Translate turnkey into a deliverable
Describe exactly what will arrive at your receiving location: populated boards, programmed modules, assemblies with cables, or units in enclosures. List included accessories and records. A complete board is not automatically a complete product, and functional testing is not implied merely because components and bare boards are purchased together.
Identify the responsible party for every major input. Even a broadly managed project may depend on customer supplied firmware, proprietary components or a reference test fixture. Keep those dependencies visible in the schedule. Engineering review confirms which activities are available and how they fit together; marketing shorthand cannot replace an agreed statement of work.
- 01Design files
- 02Engineering review
- 03Fabrication
- 04Inspection
- 05Delivery
Build a responsibility matrix around decisions
Purchasing authority and technical authority are different. A supplier may source a listed part but still need the design owner’s approval to change it. Likewise, a fabricator may propose a stackup without owning the system’s impedance requirement. Give each technical decision an approval route, and specify when a proposal can be treated as accepted.
Compare turnkey with consigned and mixed sourcing based on your team’s constraints. Supplier purchasing can reduce the number of shipments you coordinate, while customer supply may preserve control of proprietary or already qualified stock. Neither arrangement removes the need for complete documentation and a way to resolve discrepancies.
| Activity | Customer decision | Scope to confirm |
|---|---|---|
| Component purchasing | Exact parts and substitution authority | Sources, quantities and commitments |
| Bare-board fabrication | Design and performance requirements | Panel, material and documentation |
| Assembly | Population and special instructions | Process route and inspection |
| Programming and test | Firmware and acceptance limits | Equipment, coverage and results |
| Excess material | Ownership and future use | Storage or return arrangements |
Make the BOM suitable for purchasing
Provide exact manufacturer names and part numbers, quantities per assembly, reference designators, population variants and any approved alternates. Distinguish orderable packaging suffixes from a generic device family. Include mechanical parts and accessories if they belong in the scope; leaving them in a separate unreferenced spreadsheet makes completeness difficult to verify.
Identify parts that require customer approval of source, date information or documentation. State restrictions as requirements rather than assuming they are universal practice. The inquiry should also flag components still under selection. Their availability and suitability must be resolved before a reliable material commitment or assembly release can be made.
Coordinate fabrication with assembly before release
The panel, finish, board thickness, component clearances and stencil data interact. A fabrication package that can produce an individual board may still need an assembly-compatible panel and a defined separation method. Confirm who prepares and approves those details before tooling is ordered.
Use a single revision manifest for fabrication and assembly outputs. If engineering review proposes a change to panel rails or orientation, check its effect on placement coordinates, paste tooling and documentation. Require the approved output package to remain identifiable. This prevents purchasing, fabrication and assembly from each working from a slightly different interpretation of the latest design.
Agree how commercial uncertainties are handled
Separate the requested finished quantity from the material purchase quantity. Minimum purchasing increments, setup allowance and replacement needs can create excess stock. Agree ownership, storage, return and future-use arrangements before procurement. Identify which commitments can change and which may become noncancelable under the eventual quotation terms.
A useful schedule distinguishes engineering closure, material readiness, board readiness, assembly, test and shipment. Provide your target milestone and explain which date is critical. Do not infer a guaranteed completion date from the generic sequence. Confirm the actual plan after the documents, material position and process scope have been reviewed.
Close the project with a reusable record
Request the agreed configuration record, deviations, test evidence and residual material information with delivery. Keep the approved BOM separate from a sourcing worksheet so procurement notes do not accidentally become design instructions. If a substitution was accepted for this order only, ensure it does not become the default for the next build.
For the next decision, compare consigned assembly, review component sourcing, and use PCB assembly planning to define the full route. Request a turnkey engineering review with a responsibility matrix, complete release files and explicit acceptance requirements.
Turnkey PCB Assembly readiness checklist
Use this checklist to prepare your inquiry. These selections stay in this browser and do not submit a project.
Frequently asked questions
Does turnkey mean no engineering input is required from me?
No. The design owner still defines requirements and approves technical changes. Turnkey can coordinate agreed activities, but unresolved design choices remain dependencies.
Can I supply one proprietary component in a turnkey project?
A mixed arrangement can be reviewed. Identify that component, quantity, packaging, expected arrival and ownership while marking other lines for supplier purchasing.
Are substitutions automatically permitted?
They should not be assumed. Define an approved alternate list or an explicit approval process so procurement does not unintentionally change the product.
Who owns unused purchased components?
That must be stated in the commercial agreement. Ask how excess quantities, storage, returns and later consumption will be recorded before purchasing is authorized.
Is firmware programming included?
Only if agreed. Supply the image, version, programming method, security requirements and verification procedure, then confirm equipment and handling responsibilities.