How many hours a week does chasing supplier certificates actually take?

A mid-market plant with somewhere between 60 and 150 approved suppliers spends roughly 4 to 8 hours a week on supplier certificate chasing. That is the sweep of the tracker on Monday, the first email, the second email ten days later, the phone call to the account manager who has left, and the renaming and filing of the PDF that eventually arrives. Across a year it comes to 200 to 400 hours. At a UK quality assurance coordinator's rate, with employer costs added, that is somewhere between about £3,600 and £7,200 of salaried time a year, and most of it lands in the six weeks before an audit rather than evenly across the calendar.

That range is arithmetic, not a survey finding, and you should not take it on faith. It is built from a slot count, a renewal rate and a minutes-per-chase figure, all of which you can replace with your own. Below is the model, the cost calculation and a ten-day method for measuring your actual number. The useful outcome is not the headline figure, it is knowing which of those hours are recoverable and which are not.

Build the number from your own certificate count

Start with slots, not suppliers. A supplier with three required document types, say an allergen declaration, a certificate of analysis and a third-party audit certificate, is three slots. Eighty suppliers at three types each is 240 slots.

Most of those documents run on an annual cycle, so you are looking at roughly 240 renewals a year, about five a week. Split them by how they behave:

• The clean renewal. The supplier sends the new certificate before you ask, or on the first email. Six to ten minutes, nearly all of it filing: downloading the attachment, checking the expiry date, renaming to your convention, saving to the right folder, updating the tracker row.
• The sticky renewal. Two or three emails, a bounce because the contact has moved on, a chase to a general inbox, a document that arrives as a photo of a certificate rather than the certificate. Twenty-five to forty minutes spread over three weeks, and each touch costs you the two minutes of reloading the context.

If 60 percent of your 240 renewals are clean at eight minutes and 40 percent are sticky at thirty-two minutes, renewals alone are about 70 hours a year. That is only 1.4 hours a week, which is why the headline figure surprises people when they first add it up. The rest comes from everything that is not a renewal.

Where the other hours sit

• The reconciliation sweep. Thirty to forty-five minutes a week comparing the tracker against the folder, because the two drift. Call it 30 hours a year.
• New supplier onboarding. Fifteen new or reinstated suppliers a year, each needing a full document set collected from scratch, is forty-five minutes to an hour apiece. Around 11 hours.
• The pre-audit reconstruction. The two to four weeks before a recertification audit when you go slot by slot and close every gap. Two audit cycles, including customer audits, at fifteen to twenty hours each is 40 hours.
• Ad hoc requests. A customer's technical team asking for the allergen statement of one ingredient supplier, a complaint investigation that needs the certificate of analysis for a specific batch, a buyer asking whether a new supplier can be approved by Friday. Unpredictable, rarely under an hour a week in aggregate.

Add those to the renewal load and 80 suppliers gets you to about 200 hours a year, or four hours a week. Double the slot count to 150 suppliers and the renewal and sweep lines roughly double too, which is how a plant reaches 350 or 400 hours. That is the range, and it is the reason two QA managers can give honestly different answers to the same question.

What those hours cost

PayScale puts the average UK quality assurance coordinator salary at £25,906, in a range from £20,000 to £33,000. Add employer national insurance and pension, roughly a fifth on top, and you are at about £31,000 fully loaded. Divide by the hours a person actually works, around 1,740 after holiday and bank holidays, and the rate is close to £18 an hour.

So the chasing costs:

• 200 hours a year, about £3,600
• 300 hours a year, about £5,400
• 400 hours a year, about £7,200

If the chasing sits with the QA manager rather than a coordinator, which it often does at a single-site plant with no coordinator to delegate to, the rate roughly doubles and so does the figure.

Why the wage figure understates it

Two reasons, and neither shows up on a payroll line.

The first is displacement. Nobody has 300 spare hours. Those hours come out of verification work, internal audit schedules, complaint investigation, specification review, the things a QA function exists to do. The hour spent on the third chase email to a packaging supplier is an hour not spent on the deviation that turns into a customer complaint next month.

The second is timing. The hours are not spread evenly, they concentrate exactly when you have least slack. The reconstruction before a recertification audit lands in the same fortnight as document pack preparation, training records and the internal audit close-out. When a slot cannot be closed in time, an expired certificate becomes a nonconformance, and a nonconformance becomes corrective action paperwork, evidence submission and, in the worse cases, a re-audit fee and a grade that your customers can see. That cost is not in the 300 hours. It is what the 300 hours was buying insurance against.

Measure your own number in ten working days

The model above is a starting estimate. Replace it with observation:

1. Keep a tally sheet for ten working days. Four columns: minutes on the tracker, chase emails or calls sent, documents received and filed, and minutes on requests from customers or auditors.
2. Log in five-minute increments, same day. Reconstructed timesheets always undercount fragmented work.
3. Multiply the two-week total by 25 for an annual figure, then add your audit reconstruction hours separately, because a normal fortnight does not contain them.
4. Sanity check against your slot count. If you have 240 slots and your model says 40 hours a year, you have missed the sticky renewals.

Most people find the chase and filing columns are larger than the tracker column, which matters, because a better spreadsheet only fixes the tracker column.

Which hours are actually recoverable

Be precise about this. Tidying the tracker removes the reconciliation sweep, perhaps 30 hours. It does not touch the 70 hours of renewal chasing or the 40 hours of pre-audit reconstruction, because those hours exist for one reason: the supplier has not sent the document, and a human is the mechanism that asks.

The hours come back when the asking stops being manual and the supplier has a route that does not require them to find your email, attach a file and reply. That is what Certly is built to do when it launches. It holds suppliers with their contact details and required certificate types, tracks each expiry date against configurable alert thresholds at 90, 60 and 30 days, and runs automated email chase sequences to the supplier contact for certificates approaching expiry or already lapsed, each send logged against the certificate. Each chase carries a one-click upload link that lets the supplier submit the document with no login, through a single-use link that expires. You can also set a per-certificate-type renewal period, which matters for allergen declarations and vendor forms that carry no printed expiry date and get tracked as three years from the date on the form. When an auditor asks, there is a single screen showing current, expiring soon, expired and missing per supplier, exportable as a PDF.

What does not disappear is the review hour. Someone still has to open the document and decide whether it is the right certificate, for the right site, in date, and signed. Certly tracks and reminds on certificate expiry, it does not verify certificate authenticity or guarantee regulatory compliance, and that disclaimer appears on the dashboard and on the exported PDF rather than in a footer somewhere. The honest version of the saving is this: the asking, the remembering and the reconstructing are automatable, the judgement is not. In most plants' arithmetic, the asking is the larger half.