An audit request arrives with one question: which lot and date code went into serial number 1042, and where is the incoming inspection record for it. The build shipped fourteen months ago. The answer sits in a receiving log, a build traveller, a test file and an email thread, and nobody can promise the four agree. A traceability report exists to answer that question in one document, before it is asked.
Traceability is not a label on a box. It is a chain of records where every link carries an identifier the next link repeats. Where the chain breaks, the report stops at the break, and the customer is told so.
Why the request always arrives late
Three habits put a build in that position. Records are captured per department, so the receiving log knows the date code and the assembly record knows the serial, but nothing joins the two. Data is written on paper and filed at the end of the shift, so the timestamp is the filing time, not the moment. And the report is treated as an output of the quality department, when it is really an output of the production record.
The cost is not the document. The cost is the recall scope. A build traced to one reel is a build where one reel is quarantined. A build that cannot be traced to a reel is a build where every unit is suspect.
What the report has to answer
| Question | Data field | Where it is captured |
|---|---|---|
| Which part went in | Part number with full suffix, lot and date code | Receiving record, reel label, X-ray reel count |
| Where the part came from | Invoice, purchase order, country of origin | Procurement record tied to the receiving lot |
| Whether the part was genuine | Marking check, X-ray count, decapsulation and die check where flagged | Incoming inspection report |
| Which build it entered | Build order, work order, serial range, panel position | Build traveller, first article record |
| Which station ran it | Line, station, program revision, operator | Station log, first article comparison |
| Which thermal profile | Oven, zone setpoints, conveyor speed, profile date | Reflow profile record |
| What the test showed | Test station, fixture, result per serial | In process and final test log |
| Whether anything changed | Substitution approval, deviation number, approver | Change record with customer approval |
Eight rows, and a report that cannot fill one of them is a report that will be returned. The usual gap is the fourth row, because the serial range on the traveller and the serial range in the test file were written by two people who never compared them.
Three levels of traceability, three different costs
| Level | What it links | What it supports in a recall | Cost on the build |
|---|---|---|---|
| Date code level | Part to a period | Suspect window narrowed to weeks | Lowest, works without serials |
| Lot level | Part to receiving lot and build order | Quarantine a shipment, not a quarter | Needs lot control held on the line |
| Unit level | Part to serial number | Field failure traced to one reel, unit by unit | Needs serialisation, station scanning, test per unit |
Many buyers ask for unit level and actually need lot level. The question to settle first is the one the report has to answer in a recall: how many units are affected. If the honest answer may be a shipment, lot level is enough. If it may be a single installed unit in the field, serialisation has to start at the first build, because it cannot be added retrospectively.
How SUPERB PCBA keeps the chain
Material is identified at the door and stays identified. Reels are counted on X-ray, markings are checked against the drawing, and parts from an unfamiliar source are opened and die checked before release to the line. Every line on the build record carries its lot and date code, and the traveller carries the serial range the station logs use, so the two documents speak the same language.
The line side is where the record is made rather than rebuilt afterwards: 17 production steps with a 10 station quality line, 3D solder paste inspection, post reflow AOI, DIP AOI, and X-ray with void under 5 percent per IPC-7095, followed by in circuit test and functional test on customer fixtures where supplied. Work runs under ISO 9001, and under ISO 13485 for medical builds. Assembly sits on 7 SMT lines with placement down to 01005, and moisture sensitive parts are baked at 125 degrees per J-STD-033 before reflow, which is the record behind the bake column in the report.
Radio frequency parameters stay outside that chain by agreement. Production test covers direct current checks, functional test and customer fixtures. Gain, noise figure and return loss are measured by the customer laboratory or by a partner radio frequency laboratory, and their report is attached rather than restated in ours.
A report is issued from the build record, not rewritten for the occasion, and a break in the chain is named in the document instead of being smoothed over. The mechanics are set out in sourcing audit trail and incoming inspection plan, and the defence reading of the same subject is in component traceability for defence buyers.
Common questions
Can a report be issued for a build from two years ago?
If that build ran with lot control on the line, yes, from the retained record. If it ran before the control existed, the report covers what was captured at the time and says which fields are missing. Rebuilding a lot from an invoice is not traceability, and a report that pretends otherwise fails the first audit.
Does every build need serial numbers?
No. Serialisation is a cost that belongs to the risk. Medical, defence and automotive work normally needs it. An industrial board sold as a spare part often does not, and lot level answers the recall question for less.
What if a substituted part was used?
Then the substitution carries its own record: the approval, the date, the serial range it covers, and the parameter that differs. Parts are placed only after written approval. A substitution without that record turns the whole report into an opinion.
Next step
Send the BOM, the serial range and the fields your quality team needs in the report. SUPERB PCBA will reply with the fields the current build record can fill, the ones that need a change on the line, and a format your receiving inspection can read without a translation step.