OEMs should set a PCBA project fit gate around one identified project, configuration and supplier workshare. The gate tests whether the requested technical and commercial review can start with controlled inputs, assigned decision rights and visible conditions. Its result should be enter, enter conditionally, hold or decline, followed by a named next gate.
Project fit is narrower than a supplier capability list. A supplier may work with printed circuit board assemblies in general while the actual project depends on a particular quantity stage, component-responsibility split, programming method, fixture interface, inspection record, restricted-data path or change rule. The gate must compare those project objects with evidence that both authorised parties can review.
The gate prevents resources from entering an undefined workshare; it does not award the project, approve DFM, release production, or promise price, capacity, or lead time. A conditional result can allow bounded discovery while protecting tasks that depend on missing evidence. A decline result should identify the project-specific mismatch without turning it into a claim about either organisation as a whole.
Freeze the project identity for the PCBA project fit gate
Give the fit review a controlled identifier and link it to the preserved intake baseline. Record product and assembly identity, PCB and PCBA revisions, variants, effectivity, project stage, requested quantities, destination when relevant, requested outputs and review date. If the baseline changes, the fit result may need to reopen.
State which supplier entity and site, if relevant, the gate evaluates, but do not infer capabilities from a brand name. Identify the buyer-side project owner and supplier-side receiving owner. The result applies only to the named project, workshare and evidence period.
Define the next gate before scoring fit. It may be a qualified quotation-input review, fabrication-data review, component-risk discussion, test-scope definition or another bounded task. Use the failure-criteria review to evaluate blockers and the closure-evidence guide to preserve the final decision. “Proceed with supplier” is too broad because it does not show which resource commitment is permitted.
Keep supplier-wide qualification and project fit separate. A corporate audit or certification record may be relevant to a buyer’s process, but it does not prove that the project inputs, interfaces, timing and workshare align. Conversely, a project-specific mismatch does not prove that the supplier lacks a capability in other conditions.
Define the requested workshare line by line
List whether the request includes bare PCB, component procurement, consigned material, mixed sourcing, assembly, programming, inspection, functional test, fixture development, documentation, change support or another task. Assign buyer and supplier responsibility for each controlled group. Avoid “turnkey” or “full service” as a substitute for the actual boundary.
Record inputs, expected outputs, acceptance owner and excluded tasks for each workshare line. If the supplier reviews manufacturing data, state whether the output is a question list, DFM finding, quotation assumption or approved design change. Review ownership does not automatically transfer design authority.
Identify interfaces between work packages. Buyer-supplied firmware may affect supplier programming and test. Consigned components may affect receiving evidence, shortages and traceability. Buyer-owned fixtures may affect maintenance, calibration, interface control and return. A fit gate should expose these dependencies before either side assumes the other owns them.
The public PCB assembly services page describes service context. It does not establish a project workshare, acceptance, price, capacity or schedule.
A fit review should confirm that the planned inspection work matches the actual station, tooling and evidence route.
Fit criterion
Evidence to compare
Conditional boundary
Next gate
Project identity
Product, assembly, revisions, variant and effectivity
Review only unaffected objects
Controlled intake baseline
Workshare
Task, input, output, owner and exclusion by line
Estimate named lines only
Qualified scope review
Technical inputs
Manufacturing, BOM, firmware, test and requirement objects
Perform only checks supported by active evidence
Specialist review
Decision rights
Reviewer, approver, exception owner and receiver
Collect evidence without unowned approval
Recorded gate decision
Match input maturity to the named review
Build an object register for fabrication data, drill information, drawings, stack-up requirements, placement data, BOM and AVL, schematic when authorised, mechanical model, firmware, programming instruction, test procedure, fixture interface, requirements and change records. Mark identity, revision, access and intended use.
The fit gate asks whether the minimum controlled evidence supports the next review. A fabrication-data discussion may proceed without a final test method, while a turnkey quotation may require sourcing, programming and test boundaries. Mark missing, not applicable and out of scope separately.
IPC’s PCBA checklist maps technical domains, and IPC’s DFM materials describe review disciplines and supported manufacturing-data formats. Use those sources to frame object classes and review questions. They do not prove that a submitted design passes or that a supplier can perform the project.
When files conflict, record the object relationship, consequence and authorised owner. Do not select the newest-looking file. A conditional gate may allow review of unaffected geometry while assembly scope remains held, but the assumption and expiry must be visible.
Test project evidence instead of broad capability wording
Translate every capability question into a project object, condition and expected record. Instead of asking whether an EMS supplier can handle complex assemblies, identify the assembly configuration, manufacturing-data set, component responsibility, process requirement, inspection output and test interface that the next review must address. The answer should point to current authorised evidence or remain open.
Use a request-and-response record. For each criterion, retain the buyer’s question, object and condition; the supplier’s bounded answer; supporting evidence; limitations; reviewer; date; and next decision. If the answer depends on a future engineering review, mark the criterion conditional or held. Do not convert the future review into a present capability claim.
Check the date and access limits of project evidence
check evidence freshness. Material positions, staffing, equipment availability, review queues and target dates can change. Record when the responsible owner supplied the evidence, which project stage it covers and what change invalidates it. An older project example may inform a question, but it should not serve as current capacity or timing proof.
The page on project review before quotation describes how a later discussion may be structured. The fit gate still needs project-specific inputs, authorised findings and a saved decision before either side commits resources.
If access rules restrict the evidence, record the data class, approved reviewer and alternative proof that the parties accept. The result can remain conditional while the owners arrange access. An unsupported assurance cannot turn it into a pass, and the team should not copy restricted information into an ordinary gate worksheet.
Match quantity and project stage to the workshare
Record prototype, validation, pilot or production stage as supplied by the buyer, together with quantity by configuration and any expected transition. Do not infer that a prototype quotation automatically applies to later volumes. Each stage may change panel, sourcing, test, documentation and change-control assumptions.
Ask what evidence the current quantity requires. A small engineering build may depend on consigned parts, provisional fixtures or manual review under recorded conditions. A later-stage request may require different traceability, repeatability, test, release and material planning. The gate should state which stage the buyer submitted for review.
Separate target timing from supported timing. Record the buyer’s requested date, input availability, review dependencies, material responsibility and decision due dates. A target does not prove supplier capacity or lead time. Any commitment needs current authorised evidence from the responsible functions.
If quantity or timing is unknown, decide whether the next review can still provide a bounded output. It may be possible to identify technical questions while holding commercial or capacity conclusions. State the permitted work and the evidence needed to reopen the remaining gate.
Test sourcing and material responsibility
For a PCBA project fit gate, the NASA configuration-management reference explains baseline and change-control principles; the project record still determines fit, authority, and release.
Assign sourcing responsibility by BOM line or controlled group. Identify buyer-supplied, supplier-sourced and mixed material, approved-alternate authority, restrictions, quantity evidence and expected records. A spreadsheet showing inventory does not establish authenticity, condition or usable quantity.
For proposed alternates, record who may propose, evaluate and approve the change and which configuration it affects. Market evidence can support risk review, but it cannot create design approval. If authority or technical evidence is missing, keep the alternate outside the controlled BOM and show the quotation assumption or hold.
Define disposition for shortages, excess, nonconforming or unused buyer-supplied material when relevant. Identify who receives the evidence and who decides the next action. Unowned material disposition can make an otherwise clear assembly scope unsuitable for entry.
The components management page can guide service questions. It does not prove stock, authenticity, lifecycle condition, alternate approval or project fit.
The available inspection method sets a real boundary: magnification, image capture and acceptance criteria must be agreed before work starts. Define programming, test and fixture interfaces
For firmware, identify the image, target device, hardware compatibility, release owner, approved recipient, programming interface and verification output. Keep keys and credentials in approved systems. A fit gate can confirm that a controlled path exists without copying protected values into the gate record.
For test, state the requested operation, input conditions, fixture, cables and interfaces, firmware state, sequence, limits, expected record and disposition owner. “Functional test required” does not define who supplies the method or who accepts the result. Assign development, ownership and acceptance separately.
For buyer-owned fixtures, record availability evidence, revision, interface, maintenance or calibration responsibility, allowed modifications and return terms when provided. A photograph does not prove compatibility. If the parties have not resolved the interface, the gate may permit a concept review while holding test-scope and timing conclusions.
Separate programming verification from product acceptance. A successful readback may confirm one operation but does not establish functional coverage. The gate should name the output each work line is expected to produce and the owner who accepts it.
Set evidence access and decision-right boundaries
List restricted objects and approved recipients. Record purpose, access route, scope and expiry. A reviewer may know that a schematic or firmware package exists without holding authority to receive it. Do not mark the gate entered if the named review depends on inaccessible evidence.
Assign reviewer, design authority, component authority, test authority, exception owner, commercial owner and receiving owner as the workshare requires. A project coordinator can maintain the gate but should not absorb every approval. If authority conflicts or expires, hold the dependent criterion.
Define communication outputs rather than meeting frequency alone. State what questions, decisions, assumptions and updated objects must return, where they are retained and who accepts them. An email receipt is not acceptance evidence.
The public quality assurance page can help frame evidence questions. It does not prove certification applicability, project conformity or acceptance.
Once boards enter a controlled line route, evidence access and stop authority need named owners rather than an informal assumption. Agree change, restart and exit conditions
Record which changes reopen the fit gate: assembly or PCB revision, new variant, quantity stage, workshare, sourcing split, alternate, firmware, test limit, fixture interface, requirement, recipient or target timing. Preserve the earlier result and create a delta rather than overwriting it.
Define how either party can stop bounded discovery and what records must be returned. A decline or hold should preserve the received-object register, open questions, assumptions and disposition of restricted information. Do not turn an exit condition into a claim that the supplier or project is generally unsuitable.
For conditional entry, define the owner, evidence due, expiry, permitted tasks, prohibited tasks and decision at expiry. If the condition is not closed, the project should return to hold or decline as recorded. It should not drift into quotation or production planning by inertia.
Gate state
Evidence condition
Allowed action
Required record
Enter
Named workshare and next-review evidence are aligned
Begin the named gate only
Baseline, criteria, reviewers, result and receiver
Enter conditionally
A written assumption permits bounded work
Perform permitted tasks before expiry
Condition, owner, limits and reopen trigger
Hold
A required object, interface or authority is unresolved
Collect evidence without dependent commitment
Blocker, consequence and release evidence
Decline
The defined workshare does not align under accepted conditions
Close this project path and preserve disposition
Project-specific reason, authority and exit record
Read back the fit decision before committing resources
A second authorised reviewer should reconstruct the project identity, workshare, inputs, quantities, sourcing split, programming and test boundaries, requirements, access, decision rights, conditions and next gate. Compare the record with the preserved intake objects and current authorised evidence.
Stress-test one dependency from each work line. Ask what happens if a component alternate is rejected, firmware is delayed, a fixture interface changes, quantity moves to another stage or a decision owner becomes unavailable. If the gate record cannot show the affected tasks and restart condition, the result is incomplete.
Confirm that any capacity, timing or commercial conclusion has current source and authority. If evidence is not yet available, keep the field open. Do not convert a target date, general capability statement or earlier project experience into a project commitment.
Read back the result with both parties’ receiving owners. The buyer should confirm that the recorded workshare matches the intended request, and the supplier should confirm that its response uses the same inputs and exclusions. Record disagreements as open criteria rather than smoothing them into a single summary. Gate closure requires a shared description of the next task even when other commercial or technical decisions remain pending.
A conditional or blocked project may need a defined repair route; the gate record should state who can authorise it and what evidence closes it. Hand off one project-specific gate record
The handoff should contain project and configuration identity, requested workshare, criteria, evidence, conditions, risks, decision owners, state, next gate, restart triggers and exit terms. It should say what both parties may do next and what remains prohibited.
For an initial fit review, provide project stage, active revisions, variants, quantities, workshare, sourcing and test scope, fixture interfaces, required records, decision owners, constraints and proposed exit conditions. Keep unknowns visible.
Include the gate revision so later changes can be traced to the original decision.
For a project-specific fit review, send the controlled baseline, workshare, open conditions, and decision owners through the GNS contact page .
FAQ
Is a PCBA project fit gate the same as supplier qualification?
No. Supplier qualification may assess an organisation or site against broader criteria. The project fit gate evaluates one identified configuration and workshare using current evidence. Passing either process does not automatically prove the other.
Can a PCBA project enter the gate conditionally?
Yes, when a written assumption supports bounded work. Record permitted and prohibited tasks, the owner, evidence due, expiry and restart decision. Conditional entry should not become an unrecorded path into quotation or production release.
Does passing the PCBA project fit gate approve production?
No. It permits one named next review within recorded limits. DFM disposition, component approval, quotation, capacity, commercial agreement, test acceptance and production release remain separate decisions.
When should a PCBA project fit gate be reopened?
Reopen affected criteria when the configuration, revision, quantity stage, workshare, sourcing split, firmware, test interface, fixture, requirement, recipient, authority or target timing changes. Preserve the previous result and record the delta.
