Why one 30-day reminder fails

A single reminder 30 days before expiry works for a document you can renew online in ten minutes. It fails for anything that needs an inspection, a third-party audit, a training course or a government application. By the time the alert lands, the real work — booking, waiting, paying, uploading — no longer fits before the expiry date.

The better question is not “how many days before expiry?” but “how long does this renewal actually take, end to end, on a bad week?”

Work backwards from the renewal, not from the expiry date

For each document type, add up four pieces:

  1. Preparation. Gathering evidence, filling in forms, collecting signatures.
  2. Third-party lead time. Inspector availability, processing time at the issuing body, insurer underwriting, supplier paperwork.
  3. Internal approval. Budget sign-off, purchase order, legal or management review.
  4. Buffer. Holidays, sick leave, a rejected first submission.

The sum is your minimum lead time. The first reminder should arrive before that window opens; later reminders should land at points where a delay is still recoverable.

Typical lead-time bands (calibrate to your own history)

These are starting points, not legal deadlines. Check the issuing body’s own guidance and your last few renewals, then adjust.

  • Short, self-service renewals — TLS certificates, software license keys, domain names: first reminder around 30 days out, follow-ups at 14 and 7 days. Public TLS certificate lifetimes are shrinking under CA/Browser Forum rules (a 200-day maximum since March 2026, stepping down to 47 days by 2029), so manual tracking breaks faster every year. Automate issuance where you can and track what cannot be automated.
  • Insurance policies and supplier attestations — liability cover, cyber insurance, ISO or SOC 2 letters from suppliers: first reminder around 90 days out, because underwriting questions and broker back-and-forth take weeks.
  • Inspections and periodic certifications — lifts, fire installations, pressure equipment, electrical installations, ISO surveillance audits: first reminder 120 to 180 days out, because accredited inspectors and auditors book up.
  • Government permits and licenses — environmental permits, operating licenses, hospitality and alcohol licenses, work permits: first reminder six months or more out, depending on the processing times the authority publishes.
  • Personal qualifications — first aid, forklift, safety training, professional registrations: first reminder 60 to 90 days out, because course seats are limited and the employee has to attend in person.

Build a three-step reminder ladder

One alert is easy to ignore. A ladder makes follow-up and escalation predictable:

  1. First reminder — start. Goes to the named owner. Action: start the renewal — book, request, collect.
  2. Second reminder — checkpoint. Owner plus backup. Question: is the renewal actually in progress, with a booked date or a submitted application?
  3. Final reminder — escalation. Owner, backup and the manager or client contact who carries the risk. Decision: escalate, arrange an interim measure, or accept and document the risk.

Once the renewal is done, the owner uploads the new document and confirms the new expiry date. The remaining reminders stop and the cycle restarts from the new date.

Managed service providers: one schedule per document type, not per engineer

For a managed service provider (MSP) running many client tenants, lead times should belong to the document type, not to someone’s memory. Define the ladder once per type — for example “insurance certificate: 90 / 45 / 14 days” or “lift inspection: 150 / 60 / 21 days” — and apply it across tenants. Client-specific exceptions, such as a slower authority in one country, become a visible override on that tenant, so whoever picks up the work next sees the same schedule.

Practical checklist

  1. List your document types and the last two or three renewals for each.
  2. Measure the real duration from first action to new document in hand.
  3. Set the first reminder at that duration plus a buffer of a few weeks.
  4. Add a checkpoint and a final escalation with named recipients, not a shared alias.
  5. Stop reminders on renewal and restart the cycle from the confirmed new date.
  6. Review lead times once a year, and straight after any renewal that came close to lapsing.

How ExpiryKit helps

ExpiryKit keeps licenses, permits, insurance and certificates in one portfolio: AI extracts the expiry date for you to confirm, each document gets a named owner, and reminders go out before the date — for a single business or for multi-tenant MSP portfolios.

If your reminders still arrive too late to act on, start a free trial or contact us — we will help you map lead times per document type.