Why your mill certs still live in a filing cabinet in 2026

Walk into most UK stockholders and you can still find the certs. A four-drawer cabinet by the goods-in door, or a shelf of lever-arch files sorted by year, or a shared drive folder called Certs with fourteen subfolders and a naming convention that changed twice. Somewhere in there is the 3.1 for a delivery from March.

This is not a criticism of anyone in the trade. Every stockholder I have spoken to knows the filing is a weak point. They know it costs them Friday afternoons. What is worth asking is why it has survived twenty years of everything else going digital, because the answer is not laziness and it is not budget.

Scanning the paper did not fix the problem

Plenty of firms did the obvious thing. They bought a scanner, or the mills started emailing PDFs, and the cabinet became a folder. On the face of it that is progress. In practice it moved the problem rather than solving it.

A PDF in a folder is still a piece of paper. It has a filename instead of a tab divider. You still have to know where it is before you can find it, and knowing where it is depends on somebody having filed it correctly, months ago, under pressure, at the end of a shift.

So the certs end up spread across four places at once. Some in the folder on the server. Some sat in the buyer's email, because that is where the mill sent them. Some on the supplier's own portal behind a login one person has. And some still in the cabinet, because the delivery came in on paper and nobody scanned it. All four are the official copy. None of them is complete.

The word that matters here is attachment. In almost every system a stockholder runs, a certificate is attached to something: an email, a delivery, a folder, a job bag. Attachments are cheap to create and expensive to find. That is the whole trap.

The retrieval test

Forget the filing for a second and test the other end. Pick a heat number at random from a despatch note eighteen months old. Time how long it takes to produce every certificate covering material from that heat, plus a list of every customer who received any of it.

At most stockholders that is not a five minute job. It is an afternoon, and it needs the one person who knows how the folders are organised. If that person is on holiday, it is a bad afternoon.

That test is the only measure of a filing system that counts. Not whether the certs are stored. They are always stored. Whether they can be retrieved against the thing a customer or an auditor will actually ask about, which is never a filename and is almost always a heat number, a batch, an order or a date range.

What it costs, honestly

The obvious cost is time. A cert request that should take a minute takes half an hour, and it lands at the worst moment, because customers ask for certs when their own audit or their own customer is chasing them.

The second cost is worse and much quieter. Material that cannot be evidenced does not get sold as certified material. Remnants go back on the rack with a chalk mark and the paperwork trail dies there. The steel is still good. The heat is still known, in theory. But nobody will quote it to a job that needs a 3.1 because nobody wants to be the one who cannot produce the paper. Certified stock quietly becomes scrap value.

The third cost only shows up on a bad day. If a customer raises a claim on material you cannot trace cleanly, the argument is no longer about the steel. It is about your records. That is not a position you want to negotiate from.

An attachment is not a record

Here is the distinction the whole thing turns on.

An attachment is a file that sits next to your data. Your system knows it exists. It does not know what is in it.

A record is the certificate as structured information. The heat number, the grade, the standard, the certificate type, the chemistry and the mechanical values, held as fields, with the original PDF kept alongside as the evidence. The system can now read the cert, not just store it.

Once a cert is a record, three things become possible that were never possible with a folder.

It can match itself. A certificate carrying heat 812449 finds the batch carrying heat 812449 without anyone deciding where to file it. In MetlSys certificates auto-match to batches by heat number for exactly this reason.

It can be graded. EN 10204 types rank 2.1, 2.2, 3.1 and 3.2. If the system knows which type it holds, and the customer account carries a minimum type, the software can compare the two. MetlSys gates allocation and despatch on that comparison, with a manager override where a deficiency has to be accepted, and the override is logged.

It can travel with the material. Split a bar, cut it, send it out for machining and take it back, and the child batches carry the same heat and the same certificate. Splits, cuts, remnants and subcontract returns all keep the genealogy. The trail does not break at the saw, which is exactly where a folder-based system loses it.

The gate is the part people underestimate

Most conversations about certificates are about finding them. The bigger win is not needing to.

If despatch is gated on the certificate, an uncertificated batch cannot leave the yard by accident. That single rule removes most of the retrospective searching, because the awkward requests are nearly always for material that went out before the paperwork caught up. MetlSys shows uncertificated batches on the dashboard rather than leaving them to be discovered later.

It also changes what happens at the point of delivery. Cert packs assemble into one PDF for the delivery and go out with the despatch, so the customer already has what they need. A cert request you never receive is worth more than a cert request you answer quickly.

Where a customer does come back, the customer portal lets them self-serve their own orders, certificates and documents under their own login, on short-lived secure links. That is one fewer phone call landing on the office at ten to five.

Getting the paperwork in without retyping it

The reason certs are filed badly is that filing them properly has always meant typing. Somebody has to key the heat, the grade, the standard, the type and the values off a scruffy PDF, and nobody has time to do that for every delivery, so it gets skipped and the PDF gets dropped in a folder instead.

That is the bottleneck, and it is the one thing that has genuinely changed in the last few years. MetlSys reads mill certificates, delivery notes, customer POs, supplier confirmations and subcontract paperwork into reviewable drafts. The extraction is shown against the source PDF before anyone commits to it.

The rule we hold to is that nothing posts on its own. The AI proposes and a person confirms. In this trade a machine quietly writing a wrong heat number into a traceability chain is not a convenience, it is a liability. But the typing is gone, and with the typing gone the reason to skip proper filing goes with it.

What good looks like

You can describe it in one sentence. Every certificate in the business is a record, matched to a batch by heat, ranked by type, enforced at despatch, and retrievable by anyone in the office in under a minute.

No cabinet. No naming convention. No one person who knows where things are.

The filing cabinet survived this long because the alternative used to be more typing. It is not any more. If you want to see what your own certificates look like as records, how MetlSys handles EN 10204 traceability and MTCs is the place to start.

Bring your worst mill certificate PDF to a demo and we will run it. Request a demo.