A stale certificate does not look stale. A policy can expire, be cancelled, be nonrenewed or be replaced with one carrying different limits, and the document in the folder looks exactly as it did the day it arrived. Whether anyone tells you depends on the policy’s own provisions, not on the certificate.
The gap surfaces at the worst possible time: after a loss, during a premium audit, or in the middle of a contract dispute, when somebody finally compares the document on file against the signed agreement and the work that was actually performed.
What Goes Stale
The Things That Change Without Announcing Themselves
A file built once at onboarding drifts for reasons that rarely announce themselves.
-
Policies end
Coverage expires, gets cancelled or is nonrenewed. A renewal certificate speaks only to the new term, so an expiration date that has not passed yet is the beginning of the review, not the end of it.
-
Carriers and limits change
A subcontractor switches carriers or drops to lower limits partway through a relationship. Nothing about that is unusual. It just may no longer match what the agreement requires.
-
Coverage forms and exclusions change
Forms get replaced and exclusions get added at renewal. A certificate that lists a policy type does not show whether a new exclusion reaches the specific work that subcontractor performs for you.
-
The work changes
A subcontractor cleared for one scope starts performing something different, or takes on a project whose insurance requirements are not the ones they were originally approved against.
-
The entity changes
Legal names, assumed names and affiliated companies are not interchangeable. The named insured on the document should be the entity that signed the subcontract, employs the workers and owns the vehicles and equipment.
-
Lower-tier subcontractors appear
The company you hired hires someone else. If the agreement does not say whether that is permitted, who approves it and who collects their documents, it usually means nobody does.
What a Certificate Actually Confirms
The form says so itself. The current ACORD 25 Certificate of Liability Insurance states that it is issued as a matter of information only, that it confers no rights on the certificate holder, and that it does not amend, extend or alter the coverage described on it. It also states that if the certificate holder is meant to be an additional insured, the policy has to be endorsed. A note typed into the description box is not a substitute.
The same logic applies to waiver of subrogation and primary and noncontributory wording. Those are policy provisions or endorsements, not certificate language. Where the certificate and the policy disagree, the policy controls.
That does not make certificates useless. It makes a certificate one document among several. Read alongside the subcontract, the endorsements actually issued and the work actually performed, it is a reasonable starting point. On its own, it is not an answer.
Know What You Are Looking At
These Documents Are Not the Same Thing
-
Certificate of insurance
A summary representing that a policy existed on the date it was issued.
-
The insurance policy
The actual contract that determines what is and is not covered.
-
Additional insured endorsement
The policy document that adds a party. Requesting one is not the same as confirming it was issued and that it reaches the work in question.
-
Waiver of subrogation
An endorsement or policy provision waiving the insurer’s recovery rights. Not certificate wording.
-
Primary and noncontributory
The provision establishing how a policy responds relative to other insurance.
-
Workers’ compensation evidence
Documentation specific to that coverage and to the jurisdiction where the work is performed.
-
The subcontract
The agreement that sets the requirement in the first place. Without it, there is nothing to compare the documents against.
What Tends to Go Wrong
The same gaps turn up in real files: certificates collected only at onboarding, expiration tracked by subcontractor instead of by policy, endorsements requested but never received or never read, a company name that does not quite match the subcontract, documents scattered across individual inboxes, and nobody specifically responsible for the follow-up.
Individually, none of them look like a problem. They surface together, at a claim, an audit or a dispute.
One More Thing Worth Knowing
Collecting a certificate does not settle whether a worker or a company is properly treated as an independent contractor. For federal tax purposes the IRS looks at behavioral control, financial control and the type of relationship, and no single fact decides it. The U.S. Department of Labor applies its own test for its own purposes, and state workers’ compensation rules add another layer. They do not always line up.
There is a related point for shared job sites. Under OSHA’s multi-employer citation policy, more than one employer on a site can be cited for the same hazardous condition depending on their role and degree of control. That is a safety and liability question rather than a documentation question, and it is part of why the underlying relationship deserves more attention than a filed certificate.
Both belong with your legal, tax and safety advisers. LuxeStone does not interpret contracts or provide legal advice.
Companion Resource
Subcontractor Compliance Guide
Requirements to define in the agreement, records to keep per policy, a blank tracking template and a review workflow.
The resource is general educational material. It does not replace a review of your own operations, contracts and insurance program.
Start a Conversation
Want the Subcontractor Files Reviewed?
Bring a subcontract and a handful of certificates. Comparing what the agreements require against what the files actually show is one of the first things we do on a contracting account.
Direct line: 806-274-0382. Email: wendy@luxestoneinsadvisors.com.