A PCBA build hold scope should identify the assemblies, material, locations, and operations that cannot move, plus the evidence and authority required to change the restriction.
A PCBA build hold should tell the next person exactly which assemblies cannot move, which operation is restricted, and what evidence can change that restriction. A message saying “stop this order” leaves open questions. Material may sit on another line, pass the suspect operation, or enter another product.
For an OEM project manager or quality lead, the immediate task is to define a defensible boundary. That boundary can be wider than the confirmed defect population because exposure remains uncertain. It should also distinguish work that must stop from activities that can safely continue, such as reviewing records or preparing an unaffected fixture.
This article develops a practical PCBA build hold worksheet. The fields and examples are engineering recommendations, not a description of GNSEMS factory procedures. Use the contract, product risk, customer requirements, and actual traceability to decide the final scope. Root-cause analysis and permission to restart are separate decisions.
Define the PCBA Build Hold Scope by Operation and Population
Begin with an action that people and systems can enforce. Examples include no further component issue, no printing, no reflow, no programming, no transfer to final assembly, or no shipment. Each restriction applies at a different point. A shipment block cannot prevent suspect assemblies from accumulating downstream, while a line stop may leave finished stock available for dispatch.
Next identify the product configuration and physical population. Record the assembly number, revision, variant, manufacturing order, board or panel identifiers, and the locations where material is expected. Include a time boundary only when production records can connect time to actual units. A time range without reliable clock alignment is an investigation clue, not a precise serial range.
Keep the reason separate from the instruction. “Possible use of an unapproved component lot” describes a concern. “Prevent issue and processing of listed reels and every assembly linked to them” describes a control. The first statement helps engineering investigate; the second helps operators and stores staff avoid adding exposure.
Finally state whether the hold blocks all operations or selected ones. A team may continue document reconciliation while physical processing remains prohibited. However, any allowed action that changes a suspect board, clears a machine log, or consumes an investigation sample needs its own instruction. Administrative progress should not quietly alter the evidence.
Record the signal without deciding the cause too early
Use neutral descriptions of what was actually found. A failed functional result, a conflicting reel scan, an unexpected component marking, and a missing program revision are different signals. None automatically proves the same defect mechanism. Record the original observation, its source, the person or system that produced it, and the affected object.
Preserve the first result before repeat testing or manual intervention. If a second test passes, retain both results and their conditions. Otherwise, the scope review may rely on a clean record that hides the event which triggered the hold. A changed fixture or test limit can make two results unsuitable for direct comparison.
Mark each boundary statement as confirmed, suspected, or not yet checked. Confirmed means a record establishes the connection. Suspected means a plausible shared exposure exists. Not yet checked means the team lacks information. These labels stop an incomplete search from being interpreted as proof that other units are unaffected.
For a defect-led investigation, the existing solder-joint escalation guide explains evidence preservation and disposition in more detail. The hold worksheet should reference that investigation rather than repeat its technical conclusions.
Build a PCBA Build Hold Scope People Can Execute
The worksheet below separates identity, movement, and authority. It is a proposed starting point, not a mandatory industry form. Replace generic descriptions with the actual identifiers used by your supplier. If the supplier cannot retrieve a field, record that limitation and decide whether the initial hold must remain broader.
Suggested fields for a PCBA build hold
Field
What to record
Why it affects the boundary
Trigger reference
Original observation and evidence ID
Connects the restriction to a reviewable concern
Configuration
Assembly, PCB, BOM, variant and effective revision
Separates similar-looking products
Population
Order, lot, panel, serial or documented time interval
Defines which units require control
Exposure link
Material lot, program, equipment or route shared by units
Explains why each population is included
Location
Stores, line, test, rework, finished stock or external holder
Prevents a local search from missing remote material
Restricted action
Named operation, issue, transfer or dispatch prohibition
Makes the hold enforceable
Allowed work
Specific activities that preserve the restriction
Prevents assumptions about partial continuation
Control owner
Named role and acknowledged receipt
Identifies who implements each restriction
Review condition
Evidence needed to widen, narrow or remove the hold
Keeps an update separate from a release
Connect the worksheet to the live case
A single case ID should connect this worksheet with the nonconformance record, inventory transactions, production instructions, and customer correspondence. Those systems need not use identical forms. They do need a reliable cross-reference so a reviewer can reconstruct why an item was blocked and which decision later changed its status.
Do not insert an automatic expiry that releases material when a meeting is missed. A review date is a reminder to reassess evidence. It is not permission to resume. If a limited authorization has an expiry, reaching that expiry should restore the stated restriction unless an authorized replacement decision exists.
Trace backward from the last defensible good condition
The PCBA build hold scope should extend only as far as the traceable exposure supports, while unresolved links remain explicitly held.
The observed failure time may be later than the start of exposure. The most recent passing board is not always the last defensible good condition. Its inspection may not detect the suspected fault. For example, a visual check of population cannot exclude a wrong electrical rating when package and marking are indistinguishable. Choose a boundary using evidence that can actually separate exposed from unexposed units.
Work backward through material issue records, feeder changes, program releases, maintenance events, and relevant inspection results. Ask when the suspect condition could first have entered the route. If the exact entry point is unknown, retain the earlier plausible boundary until stronger evidence narrows it.
Also check whether production sequence remained intact. Rework loops, split panels, parallel stations, manual transfers, and delayed data uploads can break the assumption that consecutive serial numbers passed through the same conditions. A serial range may be convenient, but convenience does not establish exposure.
The PCBA traceability review is useful when assessing whether those links exist before an order. During a live hold, request the actual linked records. A statement that a supplier has traceability cannot replace a population list for the current case.
Trace forward across shared materials and destinations
Trace splits and downstream use before excluding another job. Follow the suspected exposure beyond the order where the signal appeared. A reel can be split, returned to stores, issued to another job, or moved to a second line. The same program library can serve several assemblies. A fixture fault can affect multiple batches that otherwise share no material.
Build a list of destinations for each relevant shared object. For material, connect receipt identity to splits and subsequent issues. With software, connect the effective version to stations and processing intervals. For equipment, identify the operations and products that passed through it during the unresolved condition.
Include finished units and external processing when applicable. The team should know who holds them and who can prevent further movement. If records indicate potentially affected delivered product, escalate through the contractual and product-safety process. Do not improvise a customer notification threshold from an article or assume the internal hold solves an external exposure.
Shared exposure does not mean every related product is defective. It means those products need an explicit scope decision. Keep the initial containment list and later exclusion rationale so an auditor can see why a product was removed. Deleting an entry makes an evidence-based exclusion indistinguishable from an oversight.
Match the PCBA Build Hold Scope to the Uncertainty
Different signals justify different temporary boundaries. The examples below illustrate the reasoning, not fixed response rules. Product criticality, contractual controls, available detection methods, and confidence in traceability can require a more conservative action.
Example signals and provisional restrictions
Observed situation
Provisional boundary to assess
Evidence needed before narrowing
Unapproved component lot found at one feeder
That lot, its splits, and assemblies linked to its use
Receipt, feeder, issue and assembly genealogy
Inspection program revision cannot be established
Units relying on that uncertain inspection result
Effective program history and suitable repeat verification
One board has clearly localized handling damage
The board plus units exposed to the same handling event
Event reconstruction and an exposure check
Conflicting assembly revisions are in circulation
Jobs that could have received either instruction
Controlled release, receipt and actual workstation data
Serial links are missing after a manual transfer
The full unresolved transfer population
Reconciliation that accounts for every moved unit
A narrow initial hold is defensible only when evidence supports the exclusion of other material. A broad hold should still have an investigation plan. Otherwise, “everything is blocked” becomes a substitute for finding the relevant connections and makes it harder to prioritize the work that can reduce uncertainty.
For input conflicts discovered after quotation, use the post-intake discrepancy process to reconcile the approved baseline. A supplier acknowledgement of a new drawing is useful, but it does not establish what earlier work actually used.
Reconcile physical segregation with system status
The same hold case must connect physical locations and recorded status. Define who controls each copy of the instruction. A production supervisor may manage the line restriction, stores may control component issue, and a quality representative may control disposition. Name the role that consolidates their acknowledgements. An unanswered message is not evidence that the receiving department has implemented the hold.
Use a small reconciliation example before accepting the location balance. If an order started as ten panels with four boards per panel, the potential assembly population is forty boards. Two panels still awaiting separation represent eight boards, not two. If three boards were retained for investigation and one was scrapped, those four units remain part of the accounting even though they are unavailable for the next production operation. These illustrative quantities show a counting method, not a sampling recommendation.
Record the time of the balance and freeze uncontrolled movements during reconciliation. If a necessary transfer occurs, log its source, destination, quantity, identity and approval against the same case. Otherwise, two departments can each report correct local counts taken at different times while the combined record double-counts or omits the transferred material.
Check physical and recorded controls together
A physical marker and an inventory block solve different problems. At the workstation, a marker helps someone at the location recognize a restriction. A system block helps prevent issue, transfer, completion, or dispatch through recorded transactions. Use controls appropriate to the route, then test whether they agree for the affected population.
Start with a quantity reconciliation by location and status. Separate assemblies from panels and loose components; mixing units of measure can create a false balance. Record scrap, retained samples, split lots, external processing, and material already consumed. An unexplained difference remains an open scope issue.
Choose a few representative transactions for a controlled readback. Ask the responsible person to show the blocked status and the instruction they would follow, without attempting unauthorized processing. Check that the restriction is visible to every relevant shift and department, not only to the person who opened the case.
JPL’s QC120 supplier clause provides a contract-specific example of identifying and segregating nonconforming items to prevent unintended use or delivery. Its approval rules apply within its own contractual scope. For a commercial PCBA project, use the actual agreed authority and controls rather than adopting that clause by assumption.
Use a worked example to test the proposed scope
Test the PCBA build hold scope against a worked lot, location, operation, and last-known-good condition before anyone acts on it.
Consider a hypothetical assembly job in which a component reel is questioned during placement. The receipt record shows that the reel came from one incoming lot. Stores split that lot into two reels, and the second reel went to another job. This example contains no real customer data or production result.
Blocking only the first manufacturing order would miss the second job. Blocking every order in the factory would not explain the exposure either. The initial scope should identify the incoming lot, both reel identities, their remaining quantities, the assemblies already linked to them, and any transfer whose identity is unresolved.
Suppose the second job has not started and its reel remains in stores. Its relevant control is an issue or processing restriction. Meanwhile, boards from the first job have reached functional test. Their hold must remain visible there even if the original line has stopped. The same case therefore needs different restrictions at different locations.
Now suppose records prove that an earlier batch used a different incoming lot. That can support excluding the earlier batch from this material-led hold. It does not resolve a separate program concern if one later emerges. Scope decisions should follow the reason for inclusion, not a blanket label of “good” or “bad” attached to the product.
The worksheet is useful when a new reviewer can reproduce each inclusion and exclusion from the evidence. If the explanation depends on a person’s memory, keep that limitation visible and obtain a corroborating record before relying on a narrower boundary.
Change the PCBA Build Hold Scope Without Authorising Restart
Every PCBA build hold scope change needs a reason, affected population, evidence reference, approving role, effective time, and remaining restriction.
Changing containment scope does not automatically authorize a restart. Every scope revision should show what changed, why, which records support it, who approved it, and who received the revised instruction. Keep the previous version available. If the change removes a location or serial range, state whether it is excluded as unexposed, accepted after verification, or subject to a separate disposition.
These outcomes are not interchangeable. Excluding an unexposed population corrects the containment boundary. Accepting affected units after inspection is a product decision. Restarting the process is a manufacturing decision. A single email saying “hold closed” can obscure all three unless the decision record separates them.
When a changed configuration is part of the solution, connect the case to PCBA engineering change control . Define where the change takes effect and how old work in process is handled. Approving the new configuration does not automatically approve the old population.
Before the next review, bring the affected product and revision, original signal, material and serial links, location balance, restricted operations, and remaining unknowns. Discuss the build-hold scope with GNSEMS using those inputs so the project conversation can address the actual boundary rather than an ambiguous instruction to stop an order.
Questions about PCBA build hold boundaries
Does a build hold need to include units that passed test?
It can. A pass excludes a concern only when the method and conditions can detect that concern. Units with the same suspect material, program, or process exposure may remain in scope despite passing a test aimed at another requirement. Record the reason before removing them.
Can a time interval replace a serial-number list?
Only if records reliably connect that interval to the processed population. Check clock alignment, parallel routes, delayed uploads, rework and manual transfers. When those links are uncertain, use the broader unresolved population until reconciliation provides a defensible unit boundary.
Should a hold automatically expire at the next review date?
No. The review date schedules a decision; it does not supply the missing evidence. Keep the restriction active until the designated authority records a new status. Any permitted work with a time limit should have an explicit stop condition when that permission ends.
What if the supplier cannot locate every affected assembly?
Record the missing population, last known location, responsible owner and unresolved movement. Maintain controls at plausible destinations and escalate according to product risk and the contract. A balanced spreadsheet cannot substitute for locating or otherwise accounting for the actual assemblies.
