Small-business outsourcing research

What share of certificates of insurance expire without a renewal reminder?

A protocol for measuring how many certificates of insurance lapse without a recorded renewal reminder and which contract types carry the most risk.

What share of certificates of insurance expire without a renewal reminder?

Research question and scope

This protocol asks what share of certificates of insurance reach their expiration date without a recorded renewal reminder. The unit is one certificate tracked by the business, whether received from a supplier or issued to a client. The study measures the share with no reminder, the share that lapsed, and the time between the lapse and the first action. It does not judge the insurance coverage itself.

Set the scope to one business, one certificate tracker, and one reminder rule. Record the policy types, the contract types, and the person responsible for each certificate. If the business changes the tracker or the reminder rule during the window, analyze the certificates before and after the change separately. A new reminder tool can reduce lapses without any change in vendor behavior.

Define the population as every certificate with an expiration date in the window, including certificates that were replaced before the date. Exclude certificates for contracts that ended before the expiration date only if the exclusion is stated and counted. Test the definition on two recent certificates before collection begins. Keep the excluded certificates in a separate list with the reason for each.

Definitions that make the measure reproducible

Define a reminder as a recorded message or task assigned to a named person before the expiration date. A calendar entry that nobody owns is not a reminder. Define lapsed as an expiration date that passed with no renewed certificate on file. A certificate that was renewed on the expiration date is not lapsed if the renewal was recorded before the end of that day.

Measure the lead time between the reminder and the expiration date in calendar days. A reminder sent on the last day is different from one sent thirty days earlier even if both are recorded. Record the channel and the recipient. A reminder sent to a general inbox may never reach the person who can act.

Record the certificate holder, the insured entity, the coverage type, and the required limit. A certificate can be current but still fail the contract because the entity or the limit is wrong. Report document defects separately from lapses. The reader should be able to see whether the problem is timing, accuracy, or both.

Evidence standard and data dictionary

For each certificate, capture the policy number, the effective date, the expiration date, the coverage type, the limit, and the certificate holder. Add the contract reference, the responsible owner, the reminder dates, and the renewal date. Keep the certificate PDF and the delivery email linked to the record. An endorsement that was requested but not received belongs in the open items.

Capture whether the certificate was received from a broker, a supplier, or a portal, and the date it was received. Record any endorsement request and the response. If the certificate was accepted without the required endorsement, mark that as a defect rather than a clean file. An accepted defect is still a defect.

Record the action taken after a lapse: a renewal request, a work pause, a risk acceptance, or no action. A lapse with no recorded action is an open exposure. Record the owner and the date of the next check. Do not mark the case closed merely because someone sent an email.

Sampling and collection

Collect every certificate in the tracker with an expiration date in the window, or a random sample drawn from the tracker with the method recorded. Do not select only the certificates that lapsed, because the denominator is what makes the share meaningful. Record the export date, the filters, and the number of certificates excluded. Keep the excluded certificates in a separate list with the reason for each.

If the business has several contract types or entities, collect each separately and record the group. A combined rate can hide one contract type with a persistent gap. Report the number of certificates and the number of contracts behind every percentage. A rate without its denominator is not a finding.

Ask the owner to identify the certificates that were difficult to renew and why. A broker delay, a missing endorsement, and a changed entity each point to a different repair. Record the reason before looking at the overall share so the explanation is not fitted to the result. Use the same reason codes across certificates.

Analysis and reporting

Report the share of certificates with no recorded reminder, the share that lapsed, and the median lead time for the reminders that were sent. Show the results by contract type, owner, and month. Present the number of certificates still unresolved at the end of the window separately. An unresolved certificate is not a current one.

Separate certificates that lapsed because no reminder was sent from those that lapsed despite a reminder. The first is a tracking problem, while the second is a response problem. Report the two shares together with the action taken. The owner needs to know which fix would prevent the next lapse.

Compare the lapse rate with the contract value and the work dependency. A lapsed certificate for a low-value supplier may be a paperwork issue, while one for a critical contractor may stop work. Report the dependency beside the rate. The reader should be able to see which gaps carry operational risk.

Limits of the evidence

The tracker can show whether a reminder was recorded, but it cannot show whether the person acted on it. A reminder that was read and ignored looks the same as one that was never opened. The protocol also cannot capture a phone call that produced a renewal without a record. State that limitation before presenting the share.

A small business may have too few certificates to support a stable rate. Describe the certificates and the contract types instead of ranking owners. If one person manages every certificate, the result may reflect that person's availability more than the reminder design. Do not use the share as a performance score without the context of leave and turnover.

Do not compare a business that requires certificates before payment with one that collects them annually. The two have different enforcement points even when the lapse rate looks similar. Report the enforcement rule beside the result. A target that can be met by dropping suppliers is not a risk target.

What to change

Give the result to the owner and the contract manager and ask them to choose one observable change. The change might be a reminder thirty days before expiration, a named backup owner, a certificate requirement at invoice approval, or a quarterly contract review. Record the owner, the effective date, and the measure that will show whether the change worked. Bring the tracker to that review so the choice is based on evidence.

If the reminder share rises but the lapse rate does not, the problem may be the response rather than the reminder. If the lapse rate falls but endorsement defects rise, the team may be accepting the first document it receives. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.

Ask the contract manager which certificate was hardest to renew and what was missing. A concrete answer is more useful than a general complaint. Add the missing requirement to the request template. The next measurement should test whether that contract type renews earlier.

Sources

Frequently asked questions

Does a favorable sample prove the routine caused the result?

No. The design is observational and supports a bounded operating decision, not a universal causal claim.

What should an owner review first?

Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.

Related research