Supplier document renewal calendar: a practical checklist

A renewal calendar works when every supplier document has exactly one date that drives it, a follow-up that starts well before that date, and a rule that the old document stays in force until the new one has been checked. Everything else is detail. Here is how to set it up, with typical cycles for the documents most buyers collect.

Which date should drive each renewal?

Use the expiry or next review date printed on the document, not the date you received it. A certificate uploaded in June that expires in January needs chasing in December, not next June. Where a document has no expiry date, such as a signed policy acknowledgement, set a review date under your own policy and record why.

Write dates unambiguously. A date printed 03/04/2027 is 3 April in the UK, Australia and New Zealand but 4 March in the United States. If the document does not settle it, ask the issuer rather than guessing, and store the answer in the ISO 8601 form 2027-04-03.

How far ahead should you start asking?

Certificates follow the cycle in ISO/IEC 17021-1: a certificate normally lasts three years, with surveillance audits in between, so it can be suspended before its printed expiry date. Insurance needs the most frequent attention, because, as the Connecticut Insurance Department notes, a certificate holder is owed no notice if a policy is cancelled. In Ontario a WSIB clearance lasts up to 90 days. UK organisations with a turnover of £36 million or more publish a modern slavery statement each year, and Canadian reporting entities file their supply chain report by 31 May.

What does a good follow-up sequence look like?

One request rarely does it. A sequence that escalates calmly works better than a single urgent email. This is the default schedule Vendarity uses, which you can adapt to any tool:

• Renewals: ask 30 days before expiry, then remind at 14, 7 and 1 days.
• Missing documents: ask on day 0, then remind on days 7, 14 and 28.
• Overdue: one reminder seven days after the due date, then no more than monthly.
• Internal escalation: tell the relationship owner when a document becomes overdue, and again after 14 days without a supplier response.

Send to a named contact who has agreed to receive the requests, at a sensible time in their working day, and stop reminding as soon as they submit a document.

What should you check when the replacement arrives?

• The legal entity and site are the same as before, or the change is explained.
• The new period starts on or before the old expiry date, so there is no gap.
• The scope, cover or limits still meet your requirement.
• The issuer is the same, or the new issuer passes the same checks.
• Every date is unambiguous and recorded in full.
• You record who reviewed it and when.

How do you avoid a gap while you review?

Keep the current document in force until its own expiry date while the replacement is checked. Rejecting a poor replacement should not wipe out evidence that is still valid. If a document does lapse and you decide to keep working with the supplier, record a time-limited exception with a reason and an owner, rather than quietly extending the old date.

A checklist to set up your renewal calendar

• List each supplier and the documents you require from them.
• For each document, record the expiry or review date exactly as printed.
• Name an owner for each supplier relationship.
• Choose a follow-up sequence and the contact who receives it.
• Decide how you will record exceptions and who can approve them.
• Review the calendar monthly for documents expiring in the next 60 days.

How does Vendarity run the calendar for you?

In Vendarity, the confirmed expiry and review dates on each accepted document drive the follow-ups, using the default schedule above or your own. Accepted evidence stays effective while a replacement is reviewed, exceptions are time-limited and recorded, and the coverage report shows what expires next. If your dates live in a spreadsheet today, the free renewal preview shows your upcoming renewals without uploading the file anywhere.