One certificate, six heats: matching MTRs on real material data

Every material traceability scheme works beautifully in the clean case: one certificate, one unique heat number, look it up, done. Then real paperwork arrives. One MTR covers six heats. Two mills reuse the same heat number. The reference your ERP recorded at receiving doesn’t match the one printed on the mill’s certificate. The clean case is the demo; the mess is the job.

If you’re running this in a spreadsheet and a folder of scans, here’s how to survive the mess, and where it stops being survivable.

Making the manual version work

Name files by something you control. Heat numbers make bad filenames because they collide. Assigning your own certificate number at receiving, and naming the scan with it, gives every certificate exactly one handle. If you don’t want a new number, a composite works: PO plus line, say. The rule matters more than the choice; pick one and never improvise.

One row per heat, not per certificate. In your lookup sheet, a certificate covering six heats gets six rows pointing at the same file. That way the lookup works from any heat, and nobody files six copies of the same scan to make the folder match the sheet.

Make the key composite from day one. Where heat numbers can repeat across suppliers, heat alone will eventually match the wrong mill’s certificate, silently, which is the worst outcome available: a traceability package that’s confidently wrong. Heat plus PO, or heat plus supplier, as one concatenated key column. Cheap insurance, impossible to retrofit under deadline.

Never guess. When a lookup returns nothing, the answer is “missing certificate, go get it,” not “this other cert is probably it, same supplier, same size.” A package built on a probably is worse than a package with a visible gap, because the gap gets fixed and the guess gets shipped.

Where this stops being survivable is volume and lateness together: hundreds of equipment lines, certificates still arriving, and every late arrival meaning re-running lookups by hand and re-checking what changed. That’s the week before shipment, every time.

Where DocBoss comes in

DocBoss is built for the messy case rather than the clean one. Library fields are yours to define, so certificates are held by whatever actually identifies them, and one field holds several heats, so the six-heat certificate is found by any of them without duplicate filing. The match reference has to resolve to one certificate, but it can be a combination of fields you already record, like heat plus purchase order, defined once. The query then attaches certificates to equipment across hundreds of pieces in one run and reports what it couldn’t match, and what it will not do is guess from a partial match. As certificates are uploaded, the heat, lot and certificate references printed on them are read and proposed for you to confirm, which removes most of the data entry that used to gate all of this.

If your traceability sheet has a tab called “problem certs,” bring it to a demo.