Expiry date: tracking the things that quietly stop being valid

An expiry date is the most reliably ignored field in any organisation, because nothing happens when it passes. The insurance certificate does not disappear, the licence stays in the folder, the training still appears to have been done. The consequence arrives separately and later — at an audit, at a claim, at the moment a client asks for current evidence and you cannot produce it.

What carries an expiry date

• Insurance certificates, usually annual and usually renewed by somebody who does not tell the person holding the register.
• Professional licences, certifications and memberships, including those held by individuals rather than the company.
• Training and competence records, where expiry is the point — a lapsed certification is a person no longer qualified to do the task.
• Supplier evidence: their insurance, their certifications, their data agreements.
• Equipment: calibration, inspection, servicing and statutory testing.
• Access and credentials — contractor accounts, temporary permissions, API keys.
• Contractual rights with notice periods, where the date that matters is earlier than the expiry itself.

One register, not six

The failure is almost never that nobody tracked an expiry date; it is that four people each tracked a different subset in their own spreadsheet, and the one that lapsed belonged to the person who left. A single register with a type, an owner and the date beats any number of well-maintained partial lists, because the question asked under pressure is "what is expired or about to", and that cannot be answered by combining four files that nobody can find.

Record the lead time, not just the date. Renewal of a certification can take weeks and a licence application can take months, so a reminder on the expiry date itself is a reminder that you are already too late. The useful field is "start chasing on", derived from the date minus the realistic lead time.

Making the chase happen

1. Put everything with a date into one register, even where the subjects are unrelated — insurance, training and calibration belong in the same filter.
2. Give each row a named owner, because the register sends no reminders by itself.
3. Derive a chase date from expiry minus lead time, and work from that column rather than from the expiry column.
4. Review the overdue and near-due list on a fixed day each month rather than when somebody remembers.
5. Record the new evidence when it arrives, and only then update the date — a date updated in anticipation is the most dangerous entry in the register.
6. Keep the superseded document, which is what evidences continuous cover rather than a gap.

The gap nobody notices

The expensive case is not an expired certificate but a period with no cover that nobody recorded — the policy lapsed in March, was renewed in May, and work continued in between. Continuous evidence matters more than current evidence in almost every dispute, which is why keeping the previous document and the dates of each period is worth the small effort of not deleting anything on renewal.

Ettex Records holds the register directly: item, type, owner, expiry, lead time and the evidence attached, with superseded versions retained. Filtering by chase date produces the month's work, which is the only report this process actually needs.