The Board Left for Subcontracting. Did Its History Go Too?
Outsourcing a process should not break the digital thread. Material identity, revision, process evidence and exceptions must travel with the product.
The short answer
When a circuit board leaves for subcontract processing, its manufacturing history must travel with it and return with new evidence. The external provider needs the correct product revision, unit or lot identity, process requirement and inspection criteria. The EMS manufacturer needs receipt, process, material, equipment, result and exception records linked back to the same product genealogy.
A purchase order can control price and quantity, but it cannot by itself preserve the digital thread. External processing should operate as a controlled extension of the routing, not a black box between shipment and receipt.
The moment visibility disappears at the factory gate
A board is serialized through SMT and inspection. It leaves the plant for conformal coating. In the ERP system, the status becomes “at subcontractor.” Five days later, most units return, several are delayed and two fail inspection.
The operations team now asks basic questions. Which serial numbers were coated in which batch? What material lot was used? Were the correct masking instructions followed? Why were two units separated? Did the supplier record an exception? The purchase order says that one service was delivered, but it cannot answer any of them.
The gap exists because logistics moved the product while its manufacturing identity stopped.
Treat the external step as part of the routing
If subcontract work transforms or verifies the product, it belongs in the controlled manufacturing route. It should have an operation definition, inputs, outputs, required evidence and acceptance rule.
The transaction model should connect:
- sending work order and operation;
- unit, serial, batch or lot identity;
- product and revision;
- quantity sent and physical container identity;
- external process specification;
- approved provider and site;
- planned dates and transport milestones;
- quantity received and inspection result;
- exceptions, rework and missing units.
This structure lets planning see the step as work in progress rather than simply an open purchase order.
Send the right definition with the product
The subcontractor must receive the exact requirement that applies to the shipped units. A PDF attachment sent months ago is weak control when product revisions change frequently.
The release package should identify the effective drawing, process specification, work instruction, acceptance criteria and any customer-specific conditions. If an ECN occurs while units are away, the factory must decide whether the change affects those units and communicate a controlled disposition.
The principles in The BOM Changed After Kitting. Which Version Builds? apply beyond the internal line. Effectivity should determine what the external provider does; the newest document should not silently replace the agreed requirement.
Preserve unit and container identity
Serial-level traceability can be lost when units are packed into a common container and the external provider tracks only quantity. The relationship between unit, container, shipment and process batch should remain intact.
Scanning the container can efficiently identify its contents, but the system must control additions, removals and splits. If ten units are transferred to another batch, that event should create a new relationship rather than rely on a handwritten note.
The same principle applies when lot-level control is appropriate. Traceability depth should reflect product and customer risk, but every chosen level needs consistent identity across both parties.
Receive process evidence, not only finished quantity
The return receipt proves that units came back. It does not prove that the correct process occurred.
Required evidence may include:
- process date and provider location;
- operator or equipment identity;
- material or chemical lot;
- measured parameters and results;
- inspection or test outcome;
- nonconformance and concession;
- rework performed;
- certificate or report reference.
Not every programme needs every field. The requirement should be based on product, customer and process risk. What matters is that expected evidence is defined before shipment and linked to the returned units.
Industry traceability guidance describes both internal traceability and external traceability as products and materials move between locations. The business lesson is direct: changing custody should not break the evidence chain.
Control quantity differences as genealogy events
External operations frequently return a different quantity from the shipment. Units may be scrapped, retained for analysis, split across deliveries or replaced.
A simple receipt variance records the count but not the identity and reason. The system should reconcile each unit or lot:
- returned and accepted;
- returned on hold;
- scrapped with evidence;
- retained at supplier;
- in transit;
- missing and under investigation.
This protects inventory accuracy and prevents planning from promising units that no longer exist or are not yet usable.
Make subcontract status useful to planning
“At supplier” can cover many conditions: awaiting pickup, received but queued, processing, inspection, hold, complete or returning. A single status cannot support a credible schedule.
Track expected and actual milestones. The planner should know which external batch is late, the cause, the affected downstream order and the recovery action. If the external provider cannot supply real-time integration, structured confirmations at meaningful events are still better than one estimated completion date.
This supports the broader electronics production planning and control approach. External capacity, transport and evidence readiness are part of executable production, even when the process occurs outside the company’s walls.
Quality responsibility remains with the programme
Outsourcing an operation does not outsource accountability to the customer. The EMS manufacturer still needs to ensure that the provider, process and evidence meet the agreed requirement.
Provider approval should connect capability, certification, process scope and performance. Incoming verification after return should reflect risk and supplier history. Repeated exceptions should influence sourcing and planning decisions, not remain isolated in quality reports.
If an external defect leads to rework, genealogy should retain the original process and corrective action. Replacing the record with a final pass hides the history needed for future analysis.
Connect commercial and operational control
Subcontract purchasing, production routing and inventory movement are often managed separately. That causes mismatches among service quantity, WIP status and financial liability.
A connected system should relate the subcontract purchase order to the manufacturing operation and physical transfer. Receipt can then update WIP, quality and commercial records consistently. Additional charges, scrap responsibility and rework cost can be traced to the event that created them.
The Mars platform describes unified engineering, production, supply-chain and financial visibility for EMS manufacturers. External-process control benefits when those functions share one set of job and product identifiers.
Establish a minimum external-process packet
Before any controlled product leaves, confirm:
1. Product and unit or lot identity.
2. Effective revision and process specification.
3. Quantity and container relationship.
4. Approved provider, site and scope.
5. Required completion milestones.
6. Evidence and acceptance requirements.
7. Exception and change communication route.
8. Return reconciliation and inspection plan.
On return, close each expected record rather than only the purchase order. Missing evidence should remain visible as a release blocker.
Measure the invisible part of the route
Useful measures include:
- external queue and processing lead time;
- milestone confirmation reliability;
- units without complete genealogy after return;
- quantity reconciliation time;
- missing or late process evidence;
- external defect and rework rate;
- schedule changes caused by subcontract delay;
- cost of expedited transport and external recovery.
These measures turn subcontracting from a procurement category into a managed production capability.
They also make accountability visible across organizational boundaries.
The same data improves supplier conversations. Instead of debating whether a delivery was generally late, both parties can examine the milestone at which time was lost: collection, receiving, queue, processing, inspection or return transport. Corrective action becomes specific, and future lead-time assumptions can reflect observed performance. That evidence is especially valuable when several providers offer similar prices but very different levels of operational predictability.
Frequently asked questions
Is a purchase order enough to control subcontract manufacturing?
No. It controls the commercial service but usually lacks unit genealogy, revision, process parameters, evidence and exception detail needed for manufacturing control.
What information should travel with an outsourced board?
Send identity, revision, process specification, acceptance criteria, quantity, container relationship and any customer-specific requirements.
Must external traceability always be serial-level?
Not always. The level should reflect product and customer risk. Lot or batch traceability may be appropriate, but the chosen identity must remain consistent and reconcilable.
How should missing units be handled?
Record the identity and current disposition of every missing or retained unit. Do not close the operation with a simple quantity variance.
How does subcontract visibility improve scheduling?
Milestone and exception data reveal whether external WIP will return in time for downstream operations, allowing earlier sequence or delivery decisions.