Batch Management and Traceability in PCBA Production
Batch management is the part of production that nobody notices until it is needed. As long as every unit works, the record of which material was used and which settings were applied is invisible overhead. On the day a problem appears, the same record is the difference between identifying the affected units in an afternoon and recalling a year of production because nobody knows where the boundary is. This is what the record contains and why each element of it earns its place.
The Work Order as the Unit of Production
A work order is the document that turns a customer requirement into a production instruction. It carries the product, the revision, the quantity, the delivery date and the process documents that apply, and it is the reference against which everything that follows is recorded. Without it, the production of a batch is a series of events rather than an identifiable entity, and an event cannot be traced.
The work order is also where the boundary of a batch is defined, and the definition matters more than it first appears. A batch is normally the quantity produced in one run, on one line, with one set of material and one set of process parameters. Where a run is interrupted, where material is exchanged part way through or where the line is changed, the natural response is to treat the run as one batch because the quantity is the same. That response destroys the boundary that the traceability depends on, because the units on either side of the interruption were not produced under the same conditions.
Splitting the record at those points costs a few minutes of documentation and preserves the ability to answer the question that will eventually be asked: which units were built with this material, on this machine, with these parameters.

Recording the Material Lot
Every material that enters a product carries an identity that has to be connected to the units it became. The laminate batch, the solder paste lot, the component reel, the stencil revision and any coating or adhesive used are all part of that chain. Where the material is a component, the record identifies the reel rather than only the part number, because two reels of the same part from different production lots can behave differently.
The record is kept at the level at which a question would be asked. If a supplier reports a problem with a specific lot, the record has to identify every order that consumed it. If a customer reports a fault in a specific unit, the record has to identify the material and the settings behind that unit. Both directions are needed, and both are served by the same data.
The process parameters belong in the same chain. The stencil identification, the placement programme revision, the paste inspection results, the reflow profile revision and the test results are all part of what defines the batch, and they are recorded against the work order rather than left in the machine.
What the Traceability Is For
Traceability is commonly associated with a recall, and containment is certainly its most visible use. When a defect is found in one unit, the immediate questions are how far the condition extends, which other units share it and where the boundary of the affected population lies. A record that answers those questions in hours limits the response to a defined group; a record that does not converts the response into an investigation of the entire product history.
The second use is diagnostic. When a defect appears in a batch but not in the batches around it, the difference between them is in the record, and the cause is usually found by comparing the two rather than by examining the failed units alone. Material lot, machine, operator, profile revision and environment are the usual candidates, and one of them will differ.
The third use is commercial. A customer who has to demonstrate control of their own process, whether for a certification or for a demanding end user, will ask for the records of the assemblies they buy. Being able to produce them on request is what allows a supplier to be considered for that class of work at all.

Keeping the Record Usable
A record that exists but cannot be searched is a record in name only. The practical requirements are that the identity of the batch can be found from the unit, that the material can be found from the batch, and that both can be retrieved in a reasonable time by somebody who did not produce them. That implies a consistent identifier, a structured store and a retention period that matches the product’s life.
The retention period is often set by the customer. An industrial product that will be in service for fifteen years needs its records for at least that long, while a consumer product with a two year life has a shorter requirement. Where the product carries a safety function or a certification, the retention is dictated by the standard rather than by preference.
Where It Breaks Down
The failure mode is almost never a missing document. It is a document that describes what should have happened rather than what did. Material that was substituted without being recorded, a programme that was edited on the machine, a reel that was replaced from a different lot and a batch that was split around a shift change are the events that break the chain, and each of them is a small omission at the time.
The defence is procedural and it is simple. Any change to the plan is recorded at the moment it happens, by the person who made it, in the record that the rest of the batch uses. Our production operation keeps the record with the quality management system, the material is verified on receipt through component procurement, the assemblies are built under SMT assembly, the results are captured at PCBA testing and the boards themselves come from PCB manufacturing.
Making the Chain Automatic
A manually compiled record is accurate on the day it is written and unreliable six months later, because the accuracy depends on somebody remembering to write things down during a shift that is already busy. The practical answer is to let the equipment produce the record as a by-product of doing the work, which is the direction most assembly operations have moved in.
The placement machine already knows which programme it is running, which feeders are mounted and what it placed. The printer knows the print parameters and the identified stencil. The reflow oven records the profile it executed. The test station records the result and the identifier it read. All of that data exists at the moment it is produced, and connecting it to the work order converts the traceability record from an administrative task into an export.
Where a manual entry is still required, the useful rule is that it should be a confirmation rather than an original entry. An operator who scans a reel and confirms it against the programme is providing a check; an operator who writes the lot number onto a form is providing a transcription error that will be discovered later. The design of the record matters as much as the discipline of keeping it.
FAQ
What defines the boundary of a batch? One run, one line, one set of material and one set of process parameters. An interruption or a material change splits it.
Why record the reel rather than the part number? Because two production lots of the same part can behave differently, and the reel is the level at which a supplier question is asked.
How long are records kept? For at least the service life of the product, and longer where a certification or a safety function requires it.



