Keeping track of supplier certificates without chasing email

Short answer: tracking only starts working once the document stops arriving through the inbox. As long as a supplier sends a certificate as an attachment, someone has to open the mail, judge the file, rename it, file it, and note the expiry date somewhere. Those five steps are the work. Storage was never the problem.

Why the folder and the spreadsheet lose

Almost every company starts the same way: a shared folder per supplier, and a spreadsheet with columns for document type and expiry date. That works perfectly on the day you set it up.

It breaks in two places. The first is that the spreadsheet knows nothing about the folder. Someone files a new certificate and forgets to update the date, and from that moment the spreadsheet lies without anyone noticing. The second is that nobody opens the spreadsheet in the morning. An expiry date sitting in a cell does not warn anyone.

What follows is a monthly review round: someone walks the rows, sees what has expired or is about to, and starts sending email. That is not tracking documents, that is catching up.

What goes wrong at the moment it counts

The real cost does not land in that monthly round. It lands the moment you need a document and it is not there: an audit, a customer asking for proof, a delivery waiting to go out.

That is when the current version turns out to be in the inbox of someone who is off today, or when three versions sit in the folder with no way to tell which one applies. The question is never “where is the file”, the question is “which one is valid, and as of when”.

How it works instead

Reverse the direction. Instead of the supplier sending something to you and your team processing it, you give the supplier a place to put the document themselves, attached to their own file.

That changes three things at once:

• The record is complete at upload time. Whoever puts the document there supplies the type and the valid-until date with it. There is no second administration running behind.
• The expiry date does something on its own. A document expiring in six weeks reminds the supplier itself, without anyone opening a list.
• There is one valid version. A new upload replaces the old one and keeps the history separate, so “which one applies” has a single answer.

What is left for your team is the exceptions: the document that does not check out, or the supplier who has done nothing after two reminders. That is work a person genuinely needs to look at.

What this is in practice

This is a portal, and it is smaller than it sounds. It comes down to a login per supplier, an upload screen, a handful of checks, and an overview for your own team. A first version like that goes live in weeks, not months.

We have written this pattern up as an example scenario in our work, including what it produces. If you want to know what it costs for your situation, the packages and starting prices are on one page, and otherwise we are happy to look at it together.