Operational Efficiency
Renewal Chasing on a 60/30/15 Cadence: Closing the Gap Before a Policy Lapses
Most COI lapses are not cancellations. They are renewals that happened on time but never reached your file. A fixed 60, 30, 15 and 0 day cadence, sent to the right person, closes that gap.
- Published
- Reading time
- 5 minutes
In this article
Most lapses are paperwork, not cancellations
When a subcontractor's policy shows as expired, the usual story is not that the subcontractor stopped buying insurance. The policy renewed on time. The renewal certificate went to the subcontractor's office, sat in an inbox and never reached your file, or it arrived with the new policy number but without the endorsements.
The result looks the same in an audit. When tracking lives in spreadsheets, 25% to 35% of active subcontractor policies expire mid-project without anyone noticing (Pikorua Security Benchmark Data). In Pikorua Security's 2026 benchmark, expired policies or policies expiring within 30 days accounted for 22% of deficient files.
A subcontractor usually carries several policies on different cycles: general liability renewing January 1, auto on March 15, workers compensation on July 1 and an umbrella on its own date. Each one is a separate renewal to catch, and a single spreadsheet column labeled "expiration" usually holds only the earliest of them.
Why the cadence starts at 60 days
Commercial renewals are usually marketed in the months before expiration and bound in the final weeks. A notice at 60 days reaches the broker while terms are still being set. That timing matters for more than the expiration date. If the subcontractor is moving to a new carrier, the new policy may use a different additional insured form, a different edition or a carrier-specific exclusion, and the time to ask for the right endorsement is before the renewal binds.
Starting much earlier than 60 days tends to produce notices nobody can act on yet. Starting later leaves no time to correct an endorsement before the old policy expires, and leaves the project manager choosing between a hold and a waiver.
The cadence also has to handle policies that do not run on an annual cycle. Some subcontractors carry short-term or project-specific policies, and coverage under a wrap-up program ends when the project closes out. The 60-day clock runs from each policy's own expiration date, not from a calendar date the whole vendor list shares.
What each touchpoint should say
Each step in the cadence has one job, and each message should say only what the recipient needs to do next. Keep the tone factual: a subcontractor that renews on time every year should experience the cadence as a courtesy, not an accusation.
- 60 days: notice to the vendor and its retail broker listing the policies expiring, the contract requirements that apply and the endorsements needed on renewal. The only action is confirming the broker contact.
- 30 days: a request for the renewal certificate and endorsements as soon as the renewal binds, with a zero-login upload link.
- 15 days: escalation to the vendor's principal and the project manager, with the hold date stated plainly.
- 0 days: status changes to Expired, payment hold and site access rules apply, and a daily reminder starts.
Send it to the broker, not just the subcontractor
The subcontractor's office manager can forward a request but cannot issue a certificate or an endorsement. The retail broker can. Renewal notices that go only to the subcontractor add a hop to every exchange, and each hop adds days.
Brokers also respond better to specific requests. "Please send an updated COI" gets a new certificate with the same gaps. A request that lists the policy, the required forms and editions, the additional insured entity names and an upload link gets a complete packet. Across Pikorua Security customers, sending specific requests directly to brokers cut average resolution time from 28 days to 4.2 days.
Broker contacts go stale, too. Subcontractors change agencies, and account managers move on. An unanswered 60-day notice is a signal in its own right: confirm the broker contact with the subcontractor before the 30-day request goes out, rather than discovering at expiration that every request went to someone who left the agency.
Mid-term cancellations are a separate problem
A renewal cadence watches expiration dates. It does not see a policy cancelled mid-term for nonpayment. Under the ISO Common Policy Conditions, IL 00 17, the insurer sends cancellation notice to the first Named Insured: at least 10 days before the effective date for nonpayment of premium and 30 days for other reasons, subject to state amendatory endorsements. Certificate holders and additional insureds are not on that list unless the policy is endorsed to include them, and the ACORD 25 says only that notice will be delivered in accordance with the policy provisions.
Non-renewal is the other gap. A carrier that decides not to renew owes notice to the first Named Insured under the policy and state law, not to you. If the subcontractor fails to find replacement coverage, the first sign in your file may be the 15-day escalation, which is one reason the cadence brings in the vendor's principal at that step.
If your contracts require notice of cancellation, require the endorsement that provides it, and treat any notice you receive as an immediate status change rather than a filing task.
Measuring whether the cadence works
Pikorua Security runs the 60, 30, 15 and 0 day cadence automatically for every policy on every vendor, addresses it to the vendor and its broker, and reports the results by project and by vendor. Whatever system runs your renewals, four numbers tell you whether they are under control. Track them monthly for a quarter after you change the process, then quarterly once they settle:
- The share of renewals verified before the expiration date.
- Median days from expiration to verified renewal for the ones that miss.
- The number of vendors that reach the 0-day hold, and how long they stay there.
- Vendors with repeat lapses, which usually point to a broker contact problem rather than a coverage problem.
Related reading
About the author
Arjun Bhatia
VP Product, Pikorua Security
Arjun leads product at Pikorua Security, including the contract rule builder, AM Best checks and the renewal cadence. He previously built insurance platforms at Tata Consultancy Services.
The Risk Transfer Brief explains insurance and contract concepts in general terms. Pikorua Security is software, not a law firm, insurer or broker. For contract drafting, or a coverage position on a specific claim, work with your coverage counsel.