A customer audit of your steel distributor or service center follows a predictable pattern. The auditor has a checklist. At some point on that checklist, they ask a variation of the same question: pick a heat number from a shipment in the last six months and show me the complete documentation chain — from when you received the material to when you shipped it to us.
This is a traceability audit. The auditor wants to confirm that your quality system connects supplier receipt to customer delivery, with documentation at each step. It's a standard requirement in ISO 9001-registered facilities, in automotive supply chain audits, in aerospace approved supplier programs, and in any customer qualification process for a regulated industry.
The manual answer to that request takes 20 to 45 minutes on a good day. On a bad day — if the receiving documents are in a different physical file than the cert, if the work order records are in a system that's been archived, or if the shipment was from a peak period when filing was backlogged — the answer might take hours. Or might not be reconstructable at all.
The digital answer should take under 60 seconds. Here's what it takes to get there.
What the Auditor Is Actually Looking For
The traceability chain has three nodes that the auditor wants to see connected:
Node 1: Supplier receipt. The mill test certificate, the receiving document, the supplier PO. This proves you received material from a documented source, with documented properties, on a documented date.
Node 2: Processing records (if applicable). If your facility cut, formed, treated, or otherwise processed the material, the auditor wants to see a work order or processing record that connects the incoming heat to the processed item. This is the internal traceability link — it answers the question "what happened to this heat between when you received it and when you shipped it?"
Node 3: Customer delivery. The packing list, shipping document, and delivery confirmation. This proves the material went to the customer who is now auditing you, on the date claimed, in the quantity claimed.
The auditor wants to trace a single heat number across all three nodes and confirm that the chain is unbroken. Material arrived as Heat 98721 on this receipt → was processed into items on Work Order 4412 → shipped on Delivery Note 7823 to this customer. Each step documented. Each document available.
The Manual Version and Where It Falls Apart
In most distributors and service centers, these three document types live in three different places.
Receiving documents and certs are in the receiving file — physical binders organized by receipt date or supplier, or digital folders organized by receipt number. Work orders or processing records are in the production system — a separate software, a job sheet binder, or a whiteboard that was never formally recorded. Shipping documents are in the sales or logistics system, or in the shipping folder organized by ship date.
None of these systems are linked to each other by heat number. To reconstruct the chain, the quality manager starts with the heat number, goes to the receiving file to find the cert, writes down the receipt number, goes to the production records to find the work order that references that receipt, writes down the work order number, then goes to the shipping records to find the delivery that included items from that work order.
If each system is well-organized, this takes 20 minutes. If any filing step was skipped or inconsistent — which happens during peak periods, staff transitions, or facility moves — the reconstruction takes longer or fails entirely.
Building the 60-Second Answer
The 60-second answer requires that all three document types are linked by a common reference — the heat number — in a single queryable system.
The architecture is:
At receiving: The cert is logged in a digital system with the heat number as the primary key. The receiving document number is linked to the cert record.
At processing: The work order references the heat number and the receiving document number. When production records are entered or confirmed, the heat number carries through.
At shipping: The delivery document references the work order number (or directly the heat number, in cut-to-length and simple fulfillment scenarios). The cert is linked to the delivery document.
When the auditor asks for the chain on Heat 98721, the quality manager types the heat number into the system. The query returns: receiving document, cert link, work order references, and delivery documents — all connected, all downloadable in a single action.
The search takes 10 seconds. The package generation takes 30 seconds. The auditor has everything on screen before they finish asking the question.
What This Requires at Each Transaction Stage
Receiving: Cert intake with structured heat number field, linked to receiving document number. This is the foundation — nothing else works if the cert isn't in the system with the correct heat number.
Processing: Work order entry that captures source heat number(s). For a cut-to-length operation, this means recording which heats were used on which job. For a service center doing value-added processing, it means linking the production traveler to the incoming cert.
Shipping: Delivery document that references the heat number or work order. This step is often skipped — shipping teams focus on item count and delivery address, not cert reference. Building the cert reference into the packing list or shipment confirmation is the last link in the chain.
None of these steps are technically complex. They're process disciplines: consistent data entry at each transaction stage using the heat number as the common identifier. The payoff is audit readiness that doesn't require a crisis response when an auditor shows up.