A Sub's Insurance Certificate Expired Mid-Project: Decision Tree

Why this matters

A certificate of insurance you collected at the start is a snapshot from that day, and coverage can lapse while the job is still running. If a sub's coverage is genuinely gone and they injure someone or damage the property tomorrow, the policy you were relying on may not respond, and the loss can flow to your policy or your pocket. A lapse mid-project is a live exposure, not a filing chore. This tree closes the gap fast without overreacting to what is often just a paperwork lag.

Start here: stop the exposure, then verify

Do two things at once. First, if the sub is doing high-risk work (anything that can injure a person or damage the structure), pause that work until you have confirmed coverage is actually in force, because an hour of paused work is cheaper than an uninsured claim. Second, do not assume the worst yet: an expired certificate is not the same as expired coverage, since the certificate is only the proof-of-the-moment and the policy behind it may be active and simply re-issued on a new certificate. Verify which one you are dealing with before you escalate.

If the certificate expired but the policy is active (the common case)

Most of the time, the certificate date passed and nobody sent you the renewal. The coverage never stopped.

• Request an updated certificate from the sub's insurance agent, at the source, not a copy the sub edits.
• Confirm the policy dates on the new certificate actually cover the period the work has been running, with no gap in between.
• If the dates are continuous, this was a paperwork lag. Log the new expiration where you will catch it next time and let the work resume.

If coverage actually lapsed

Sometimes the policy really did end, through non-payment, cancellation, or a switch between carriers with a gap.

• Keep the high-risk work paused until new coverage is confirmed in force, with a certificate to prove it.
• Look for a gap. If there was any window where the sub worked with no coverage, flag it: a loss in that window has no policy behind it, and your agreement's insurance and indemnity terms are what you fall back on.
• Do not accept a promise of "coverage starting Monday" as cover for work done last week. Insurance does not backdate.

If they cannot or will not prove coverage

• A sub who dodges a direct request for a current certificate is telling you they may not have one. Treat continued silence as a lapse, not a delay.
• Use your agreement. A well-drafted subcontract makes current insurance a condition of working and lets you stop work or replace the sub for failing it (see the related agreement article).
• Have a backstop ready so a paused sub does not sink the schedule: your own crew or a vetted alternate.

Prevent the recurrence

• Track expirations, do not just collect certificates. Put every sub's expiration date where the system reminds you before it passes.
• Require notice of cancellation. Your agreement should require the sub to tell you if their coverage changes or cancels, so you learn it from them, not from a claim.
• Re-verify on long jobs. On any project that runs past a policy term, plan to collect a fresh certificate before the old one expires.

Recap

1. Pause high-risk work first, then verify. Do not run uninsured while you sort it out.
2. Separate an expired certificate (usually paperwork) from lapsed coverage (a real gap).
3. Verify new coverage at the source and check the dates for any gap.
4. Fall back on your agreement's insurance and indemnity terms if a gap exists.
5. Track expirations and require notice of cancellation so it does not happen again.

References

• Trade-standard practice for subcontractor insurance verification and certificate tracking
• Consult your insurance agent or broker on coverage gaps and additional-insured status
• See related: Why You Need a Certificate of Insurance From Every Sub; The Insurance and Indemnity a Sub Must Carry