A calendar with red push buttons pinned to it

Certificates expire on a schedule. Your tracking shouldn’t depend on memory

How to build an expiry register for insurance, accreditations, training cards such as CSCS and OSHA 10/30, equipment inspections and subcontractor certificates, with lead-time reminders, named owners, a lapse checklist and a quarterly audit routine.

Mikias Abebe 14 min read

Insurance certificates, licences, accreditations, training cards and equipment inspections all share one property: they expire on a known date. And yet "it lapsed and nobody noticed" is still a common way for a contractor to get turned away at the gate, flagged on a prequalification platform or quietly dropped from an approved-supplier list.

The dates were never secret. They were printed on the document. They were just stored somewhere nobody looks until it's too late: inside a PDF, in a spreadsheet tab, in someone's memory.

This guide shows how to build an expiry register that holds up: what to put in it, how to set reminder lead times that leave room to act, who should own each item, what to do when something lapses anyway, and how to check the register is telling the truth. Examples cover both UK and US practice. The rules for any particular card or licence are set by the scheme, the regulator or your client, so check the current requirement for anything that matters to your work.

What tends to lapse

Expiring items fall into five groups. Each has a different source, a different owner and a different lead time, which is exactly why they're hard to track together.

Company insurance

  • UK: employer's liability (a legal requirement for most employers, with a minimum of £5 million cover), public liability, professional indemnity, contract works, and motor fleet.
  • US: general liability, workers' compensation and employer's liability, commercial auto, umbrella or excess, and sometimes professional or pollution liability, usually evidenced to clients on an ACORD 25 certificate.

Most policies renew annually. Clients usually want the current certificate, not just evidence that a policy exists, and many contracts require you to keep cover in place for the length of the job and sometimes beyond.

Company accreditations and registrations

  • Health and safety schemes and prequalification platforms. In the UK that includes SSIP schemes such as CHAS and SafeContractor, plus Constructionline; in North America, ISNetworld, Avetta and similar. Most run on an annual cycle.
  • ISO certificates (9001, 14001, 45001). A certificate typically runs for three years, with surveillance audits in between. Missing a surveillance audit can put the certificate at risk long before the printed expiry date.
  • Cyber Essentials in the UK, which needs renewing every 12 months.
  • Trade registrations and contractor licences: for example Gas Safe registration in the UK, or state and local contractor licences in the US, each with its own renewal cycle.

People

This is usually the biggest group, because it multiplies by headcount.

  • UK: CSCS cards (most are valid for five years; some temporary cards are shorter and can't be renewed), plant operator cards under CPCS or NPORS, SMSTS and SSSTS for site managers and supervisors (both typically refreshed every five years), IPAF and PASMA cards, First Aid at Work and Emergency First Aid at Work certificates (valid for three years), and asbestos awareness, where refresher training is expected regularly.
  • US: OSHA 10 and OSHA 30 Outreach cards don't expire at the federal level, but some states and cities set their own rules (New York City's Site Safety Training cards must be renewed, for example) and many clients require a refresher every few years. Other common items include first aid and CPR certificates (often two years), forklift operator evaluations (at least every three years under OSHA), respirator fit tests (at least annually), crane operator certification (five years) and DOT medical cards for commercial drivers.
  • Everywhere: client-specific inductions and site orientations, which sometimes expire annually or when a site's rules change.

Equipment and vehicles

  • UK: thorough examination of lifting equipment under LOLER (at least every 12 months, or every six months for lifting accessories and equipment used to lift people, unless a written scheme of examination says otherwise), vehicle MOTs and servicing, gas and pressure system inspections. Portable appliance testing has no fixed legal interval; the frequency should follow your risk assessment, so record the interval you've chosen and why.
  • US: annual crane inspections, vehicle inspections required by DOT for commercial vehicles, and any inspections required by your own programs or by the equipment manufacturer.

Subcontractors and suppliers

Your subcontractors' insurance, accreditations and operatives' cards expire too, and if a sub's cover lapses mid-job, it's often your problem. Collect their documents at onboarding (see subcontractor onboarding: the documents to collect on day one) and put their expiry dates in the same register as yours.

Each item on its own is easy. Together, for a 30-person contractor with a dozen regular subcontractors, they can easily run to several hundred dates with different owners and lead times.

Build an expiry register

The register is a single list with one row per expiring item. A spreadsheet is fine to start. What matters is that it's shared, that there's only one, and that it's the first place anyone looks.

The columns that matter

Column What goes in it Why
Item What it is, in plain words: "Public liability certificate" So anyone can read it
Category Insurance, accreditation, person, equipment, subcontractor For filtering and ownership
Holder Whose it is: the company, a named person, a machine, a sub Cards and inspections belong to someone or something specific
Issuer Broker, scheme, training provider, inspector Who you go to for a renewal
Reference Policy, card or certificate number For checking against the document
Expiry date Copied from the document itself The hard deadline
Lead time How long renewal takes, in days Drives the act-by date
Act-by date Expiry minus lead time When the reminder fires
Owner One named person Who acts on the reminder
Used by Clients, platforms and contracts that rely on it Who needs the new copy
Status Current, renewal in progress, expired At-a-glance health
Evidence Link to the current file So the register and the document never drift apart

If you already keep a document register for prequalification, as described in the prequalification treadmill, extend it rather than starting a second list. Two registers will disagree within a month.

Rules that keep it accurate

  • Capture the date when the document arrives. Not later, when someone asks. The moment a certificate lands, someone records what it is, who or what it covers, and when it expires. Make it part of the job of whoever receives the document, the same way an invoice gets logged.
  • Copy the date from the document, not from an email. Broker emails, course booking confirmations and verbal assurances are often wrong by a day or a month. The date that counts is the one printed on the certificate.
  • One row per holder. If 18 people hold a CSCS card, that's 18 rows, not one row saying "CSCS – all".
  • Filter, don't sort by hand. Set up views for "expired", "act-by date in the next 30 days" and "no owner". Those three views are most of the day-to-day value.
  • Name files with the expiry date, for example INS - Employers Liability Certificate - exp 2027-03-31.pdf, so a folder sorted by name shows what's stale.

Set reminders by lead time, not expiry

A reminder on the expiry date is a notification that you've already failed. The reminder needs to fire when you need to start acting, which depends on how long the renewal takes and what it depends on.

Some renewals hide a dependency. A UK CSCS card renewal, for example, generally needs a current CITB Health, Safety and Environment test pass, which is itself only valid for two years. If the worker's test has expired, the renewal starts with booking a test. Similarly, an ISO surveillance audit needs booking with the certification body, and a platform renewal may need the new insurance certificate first.

Illustrative lead times, to adjust from experience:

Item Typical first reminder Why that early
Insurance policies 60–90 days before expiry Broker needs time to market the policy; clients need the new certificate before the old one expires
ISO surveillance or recertification audit 90 days Booking the auditor, closing any open actions first
Prequalification and SSIP renewals 60 days Assessor queries and resubmissions take time
Training courses (first aid, SMSTS, plant cards) 60 days Course places fill up; the worker needs release from site
Cards needing a test first (such as CSCS) 90 days Test booking, then the card application
Equipment inspections 30 days Booking the inspector and taking kit out of use briefly
Subcontractor certificates 30 days Chasing a third party always takes longer than you expect

Use staged reminders: a first reminder at the lead time, a second halfway to expiry, and an escalation to a director a fortnight before if the status still isn't "renewal in progress". The escalation step is what stops a reminder being snoozed indefinitely.

Watch for clusters too. If most of your insurance renews in March, and two platform renewals fall in April, the register should make that visible so you can plan the month, not discover it.

Give every item an owner

"The office" is not an owner. A named person gets the reminder, does or chases the renewal, and confirms when it's done. A split that works for many small and mid-sized firms:

Category Usual owner
Insurance Finance or the director who deals with the broker
Accreditations and platforms Compliance or office manager
People's cards and training The person's line manager, with HR or the training coordinator keeping the register
Equipment Plant or yard manager
Subcontractor documents Whoever manages the subcontract, usually the project or contracts manager

Two rules make ownership stick. First, the owner is a person, not a role, and their name is in the register. Second, when someone leaves, their items move to a named person on their last day. Leavers are a common reason a well-run register goes quiet.

For people's cards, make the worker part of the loop. They usually know their card is expiring before anyone else does, and they're the one who has to sit the course.

Close the loop when the renewal arrives

The most commonly missed step is the last one. A renewal isn't finished when it's paid for or booked. It's finished when:

  1. The new document is in hand, checked for the right name, entity, dates and limits.
  2. It replaces the old one in the evidence folder. The old one moves to an archive, not the bin. Clients and insurers sometimes ask what was valid on a past date, usually after an incident.
  3. The register row is updated: new expiry, new act-by date, status back to current.
  4. Everyone in the "used by" column gets the new copy. Upload it to each platform and send it to each client that holds the old one. This is the step most spreadsheets miss, and it's why contractors with a perfectly valid policy still get flagged for an expired certificate.

When something lapses anyway

Even with a good system, things slip: a broker is late, a course is cancelled, a worker is off sick on the day of their refresher. What matters is how quickly you notice and what you do next.

A lapse response checklist

  • Work out what the lapse stops. An expired training card may mean that person can't do that task, or can't enter a particular site, until it's renewed. An insurance lapse may mean the business is uninsured for that risk and in breach of contracts that require cover. Some lapses stop work; others are an administrative gap. Know which.
  • Stop the affected activity if it needs stopping. A plant operator with an expired card or lifting equipment past its thorough examination date should not carry on while you sort the paperwork.
  • Get interim evidence where it exists. Brokers can often provide a letter or cover note confirming a policy has been renewed while the full certificate is prepared. Training providers can usually confirm a booking or pass.
  • Tell the client if the contract or platform requires it. Many contracts require notice when cover changes. Telling a client early is almost always better than them finding out from their own system.
  • Be careful with insurance gaps. Cover generally doesn't reach back to fill a gap, and for claims-made policies such as professional indemnity, a lapse can affect cover for past work too. Speak to your broker straight away.
  • Record what happened and why, and change the lead time or owner so it doesn't happen again.

If you're not sure whether a lapse affects your legal position or your contracts, check with your broker, the scheme or a competent adviser rather than guessing.

Audit the register

A register is only useful if it's true. Check it on a schedule, the same way you'd check anything else that matters.

Monthly (15 minutes). Review the three filtered views: expired, due in the next 30 days, no owner. Chase anything stuck.

Quarterly (an hour).

  • Sample ten rows and check each one against the actual document. Does the expiry date match? Is the linked file the current version?
  • Reconcile people against the payroll or HR list. Every current worker should have their cards and training in the register, and leavers should be archived.
  • Reconcile subcontractors against active jobs. Anyone on site this quarter should have current documents.
  • Check each platform and client portal shows current documents. A register that says "current" while a portal shows "expired" means the loop wasn't closed.

Annually. Review lead times against what actually happened. If insurance renewals always run late, move the first reminder earlier. Check that the categories still match your work. A new service line or a new client often brings new cards or accreditations.

A simple health measure is worth tracking: the share of items that are current, and the number of items inside their lead time with no action started. The second number is the early warning.

Common mistakes

  • Tracking the policy, not the certificate. The policy renews, but clients still hold last year's certificate.
  • One row for a whole team. "All operatives first aid trained" hides the one certificate that expired.
  • Reminders on the expiry date. By then, the fix takes longer than the time left.
  • Reminders to a shared inbox. Everyone sees them; no one acts.
  • Forgetting subcontractors. Their lapse becomes your gap on site.
  • Assuming a card is valid because the worker has it. Check the date, and where the scheme offers online checking, use it.

If a date matters to whether you can work, it belongs in a shared register with an owner, not in a filename or someone's head.

Where software helps

Reading an expiry date off a certificate is tedious for people and easy for software. Tools that pull dates straight from uploaded documents and turn them into a renewal schedule remove the most error-prone step, which is the copying. Automated reminders, escalation and a "used by" list that tells you where to send the new copy handle most of the rest. Deciding whether a lapse stops work, and talking to the client about it, stays with a person.

Start here

You don't need to build the whole register this week. List the ten documents that would stop work tomorrow if they expired: usually your main insurance certificates, your key accreditations and the cards of the people doing your highest-risk tasks. Put their expiry dates in one shared place, set an act-by date for each, and give each one a named owner. That alone removes most of the risk. Then add a category a week until everything is in.

Discussion (0)

Sign in to join the discussion.

No comments yet. Start the conversation.

Installed bundles are copies — your workspace data stays in your workspace. Qonstrue Community Marketplace