Why traceability matters
A single bad fastener lot can ground a fleet. When a supplier flags a material defect, the first question every quality engineer asks is simple: which units did it go into? The second is just as urgent: what else came from the same source?
If the answer takes three weeks of digging through paper travelers and spreadsheets, the cost is measured in recalls, delayed deliveries, and lost customer trust. If the answer takes three minutes, the problem stays contained.
That difference is traceability in manufacturing: the ability to follow a product, and every component, material, process, and person that touched it, through its full history. Done well, it turns a serial number into a complete as-built record.
This post covers what traceability actually tracks, the difference between forward and backward traceability, and how aerospace and defense manufacturers build the as-built genealogy that regulators and customers expect.
What traceability in manufacturing actually tracks
Traceability is more than stamping a serial number on a part. A useful record links each unit to everything that shaped it.
| Element | What gets recorded | Why it matters |
|---|---|---|
| Identity | Part number, serial number, revision | Distinguishes this unit from every other one |
| Materials and components | Lot, batch, heat number, supplier certs | Lets you trace a supplier defect to affected units |
| Processes | Work steps, parameters, torque values, cure times | Proves the part was built to the released procedure |
| Inspections and tests | Measurements, results, pass/fail, data files | Shows the unit met spec at each gate |
| People | Operator and inspector sign-offs, certifications | Confirms qualified people did the work |
| Tools and equipment | Tool IDs, calibration status, test stations | Flags units built with out-of-cal equipment |
| Deviations | Nonconformances, repairs, MRB dispositions | Captures every departure from the plan |
The level of detail depends on the product. A consumer device may only need lot-level tracking. A flight-critical assembly usually needs serial-level tracking down to individual fasteners, plus the full process history behind each one.
Forward vs. backward traceability
Traceability runs in two directions. Most real investigations need both.
Backward traceability starts with a finished unit and works back to its origins. Given serial number SN-1042, which material lots, components, operators, tools, and procedure revisions went into it? You use backward traceability for root cause analysis, warranty claims, and customer audits.
Example: A field unit fails a functional test. Backward traceability shows it used a capacitor from lot 7731 and was torqued with a wrench that later failed calibration. Now you have two leads instead of a guess.
Forward traceability starts with an input and works forward to every place it ended up. Given material lot 7731, which assemblies, serial numbers, and shipped products contain it? You use forward traceability for recalls, containment, and supplier escapes.
Example: A supplier notifies you that heat number H-55902 failed retest. Forward traceability returns the 14 serial numbers built with that bar stock, which of them have shipped, and to which customers.
| Backward traceability | Forward traceability | |
|---|---|---|
| Starts from | A finished unit or serial number | A material lot, component, or process event |
| Answers | What went into this? | Where did this go? |
| Typical use | Root cause, audits, warranty | Recalls, containment, supplier escapes |
A system that only supports one direction leaves half the question unanswered. Both directions depend on the same thing: a connected record that links inputs to outputs at every step.
The as-built record and product genealogy
The as-designed record describes what a product should be: the engineering bill of materials, drawings, and released revisions. The as-built record describes what a specific serial number actually is: the exact parts, lots, process data, and deviations that went into that one unit.
The two rarely match perfectly. Substitutions get approved, a component is reworked, an inspection is repeated after a nonconformance. The as-built record captures that reality, and it is the version auditors, customers, and investigators care about.
Product genealogy is the as-built record organized as a tree. The top-level serial number sits at the root. Each subassembly hangs beneath it with its own serial number, and each subassembly carries its components, material lots, and process history. Walk the tree down and you get backward traceability. Search it from a lot number up and you get forward traceability.
A complete genealogy answers three questions for any unit, at any level:
What is it made of? Every component and material, by serial or lot.
How was it made? The procedure revision, step data, and inspection results.
Who and what made it? The operators, inspectors, tools, and test equipment involved.
Why aerospace and defense raise the bar
In most industries, traceability is good practice. In aerospace and defense, it is a contractual and regulatory requirement, and the consequences of a gap are severe.
Quality standards require it. AS9100, the quality management standard for aviation, space, and defense, requires organizations to identify outputs and maintain traceability throughout the product life cycle. AS9102 first article inspection adds a documented, characteristic-by-characteristic proof that the first production unit matches the design.
Counterfeit parts are a real threat. Defense contractors operate under DFARS counterfeit electronic part requirements, and many follow standards such as AS5553 and AS6174. Proving a part’s chain of custody back to an authorized source depends on traceability.
Products live for decades. An aircraft or satellite program can run 20 to 40 years. Records must stay retrievable long after the people who built the hardware have moved on.
Nonconformances are expensive to contain. In flight hardware, a single escaped defect can trigger a fleet-wide inspection or a launch delay. Fast, precise forward traceability keeps the blast radius small.
Customers audit the record. Prime contractors and government customers routinely review build records before acceptance. An incomplete as-built record can hold up delivery and payment.
How A&D manufacturers build complete as-built genealogy
The best programs don’t reconstruct genealogy after the fact. They capture it as a byproduct of doing the work.
Define what must be traced, and at what level. Decide which parts are serialized, which are lot-controlled, and which are bulk. Flight-critical and safety items usually get serial control. Write these rules into the bill of materials so they are enforced, not remembered.
Receive with traceability from day one. Capture supplier certs, lot and heat numbers, and certificates of conformance at receiving inspection. A part that enters the building untraced will stay untraced.
Execute work from structured, digital procedures. Each step should record its data as it happens: the serial or lot installed, the measured value, the tool used, the person who signed. Electronic sign-offs replace stamps and initials on paper.
Link parent and child at the moment of installation. When a subassembly goes into a higher-level assembly, scan or select both serial numbers in the procedure step. That single action builds the genealogy tree.
Enforce tool and qualification checks at the point of use. The system should block a step if a torque wrench is out of calibration or an operator lacks the required certification. Prevention is cheaper than containment.
Capture deviations in the same record. Nonconformances, redlines, and MRB dispositions should attach to the serial number and step where they happened, not live in a separate system.
Make the record searchable in both directions. Engineers should be able to start from a serial number or a lot number and get an answer in seconds.
Generate the as-built report, don’t assemble it. At shipment, the full as-built package should be an export, not a week of collating binders.
Common gaps that break the chain
Most traceability failures aren’t caused by missing policy. They come from the gaps between how work is supposed to be recorded and how it actually gets recorded.
Paper travelers. Handwritten serial numbers get transposed, pages go missing, and nothing is searchable. Answering a forward traceability question means pulling boxes from storage.
Disconnected systems. Receiving lives in the ERP, build data in spreadsheets, test results on a station PC, and nonconformances in a separate QMS. Each system holds part of the story, and nobody owns the joins.
After-the-fact data entry. Values typed in at the end of a shift are less accurate than values captured at the step. Transcription errors become permanent record.
Untracked rework. A unit gets reworked, but the replacement component’s lot number never makes it back into the record. The genealogy now describes a unit that no longer exists.
Lot-level records for serial-level risk. Tracking only by lot works until a lot spans hundreds of units and you need to know which five are affected.
Revision drift. Operators work from a printed procedure that has since been revised, and the record doesn’t capture which revision was used.
From serial number to as-built record
Traceability in manufacturing comes down to one promise: for any unit you build, you can say exactly what is in it, how it was made, and who made it, and for any input, you can say exactly where it went.
For aerospace and defense manufacturers, keeping that promise is a requirement of doing business. The programs that keep it most reliably are the ones that stop treating traceability as paperwork and start treating it as a byproduct of execution. When every procedure step captures its own data and links parent to child, the as-built genealogy builds itself, and a three-week investigation becomes a three-minute query.
Frequently Asked Questions (FAQ)
-
Traceability in manufacturing is the ability to track a product, and every component, material, process, and person involved in making it, through its full history. It lets you answer what went into a unit, how it was built, and where its inputs ended up.
-
Backward traceability starts with a finished unit and traces back to its materials, components, and process history. Forward traceability starts with an input, such as a material lot, and finds every unit and shipment that contains it. Root cause investigations rely on backward traceability; recalls and containment rely on forward traceability.
-
An as-built record documents what a specific serial number actually contains and how it was made: the exact parts, lot numbers, process data, inspection results, sign-offs, and deviations. It differs from the as-designed record, which describes what the product should be.
-
Lot traceability tracks a group of parts made or received together, such as a batch of fasteners or a heat of bar stock. Serial traceability tracks each individual unit by a unique serial number. Flight-critical and safety-critical items usually require serial traceability, while bulk or low-risk items are often lot-controlled.
-
Yes. AS9100 requires organizations to identify outputs and maintain traceability throughout the product life cycle, to the extent required by the customer, regulations, and the organization’s own risk assessment. Customer contracts and flowdowns often add more specific requirements.
-
Retention periods are set by contracts, customer flowdowns, and applicable regulations, so they vary by program. In aerospace and defense, build records are commonly kept for the service life of the product, which can span decades. That makes searchable digital records far easier to sustain than paper archives.
