9 Essential COI Tracker Fields for Multi-State Subcontractor Compliance

9 Essential COI Tracker Fields for Multi-State Subcontractor Compliance

State law mostly changes which workers' compensation documents you need from a subcontractor. Your contract sets most of the other limits. So the job is less about memorising 50 states and more about running one tracker that records the contract's requirements, flags the state exceptions, and chases renewals before they lapse.

The model in one paragraph: track each sub per project state, store the contract's minimums on the row, verify the endorsements rather than trusting the certificate, escalate renewals at 60, 30, 14 and 7 days, and archive expired certificates instead of deleting them. The rest of this post shows how.

ExpiryEdge runs the date-tracking part of this: it records each certificate's expiry, reminds the right person, escalates overdue items and keeps the audit trail.

What actually changes from state to state

Three areas vary enough to need their own field or flag in the tracker.

Workers' compensation varies most. In Texas, private employers usually aren't required to carry it; the Texas Department of Insurance says those that don't must notify their employees and the state. In Florida, construction-industry corporate officers can elect an exemption, and the certificate is valid for 2 years. And in Washington, Ohio, North Dakota and Wyoming, coverage comes from a monopolistic state fund, so a private carrier's certificate may not cover work there.

Licensing can carry its own insurance floor. Some state licensing boards require proof of insurance for certain trades, separate from your contract. When that happens, log the licence requirement and the contract requirement as two numbers, because they can differ.

Bonding belongs to the project, not the sub. Federal construction contracts fall under the Miller Act, and many states have their own versions for public works, requiring payment and performance bonds above set contract values. The same sub may need a bond on one job and not the next, so track bonds against the project row.

Don't hardcode state minimums into your tracker

Statutory minimums vary by state, trade and type of project, and they change when legislatures meet. A tracker with fixed state numbers built in will be wrong within a year.

Store the contract's required minimum on each subcontractor row instead, taken from the signed agreement. Your legal or risk team sets that number for each contract. The tracker just checks the certificate meets it.

Where a state requires something beyond a standard certificate, such as an exemption certificate or a bond, add it as a checklist item on the row and verify it the same way you verify an endorsement.

The nine fields every COI tracker row needs

One "insurance status" column isn't a tracker. These fields hold up in an audit:

1. Subcontractor legal name and EIN, so every certificate ties to one verified entity.
2. Policy types, listed separately: general liability, workers' comp, auto, umbrella, professional.
3. Effective and expiration dates for each policy.
4. Limits, per occurrence and aggregate, next to the contract's required minimums.
5. Carrier name and NAIC number, so you can look the insurer up in the NAIC's Consumer Insurance Search.
6. Endorsements on file: yes or no, plus the endorsement PDF itself.
7. Days to expiry, calculated automatically every day.
8. Status: current, expiring soon, pending renewal or expired.
9. Last reviewed date and reviewer name, which is your audit trail.

Make the status mechanical. At 60 days the row flips to expiring soon and sends the first request. Inside 14 days with nothing received, it becomes pending renewal. At zero, it becomes expired and creates a payment hold and stop-work task for the project team.

Never type days-to-expiry by hand. A manual number is right on the day you enter it and wrong every day after.

Check these before you accept a certificate

Collecting a PDF and verifying it are different jobs. Treating them as one is the most common gap in subcontractor compliance. The certificate is a summary; it doesn't change the policy.

Run this on every certificate before you mark it approved:

• Compare each limit with the contract's minimum, line by line.
• Get the actual additional insured endorsement (often CG 20 10 for ongoing work and CG 20 37 for completed work) instead of trusting a ticked box.
• Confirm the waiver of subrogation wording if the contract requires it.
• Confirm primary and noncontributory wording, which decides whose policy pays first.
• For high-risk trades or big contracts, look up the carrier and call the agent to confirm the policy is in force.

Record the verification date and reviewer, and attach the endorsement PDF to the row. Without that, "verified" is a claim you can't defend six months later when someone files a claim.

A renewal escalation that skips subs who've already renewed

Every step should first check whether a verified renewal has already arrived, and skip itself if so. That one rule separates automation that helps from automation that spams compliant subs.

1. 60 days out: request the renewal certificate from the subcontractor.
2. 30 days out: follow up and copy the sub's insurance broker.
3. 14 days out: assign a direct call to your compliance contact.
4. 7 days out: escalate to the sub's owner and flag a payment hold.
5. Day zero: create a stop-work task and block new work orders.

Done this way, a sub who renewed early hears nothing more, while one who's gone quiet gets escalated properly.

Never delete an expired certificate. Claims and disputes can surface years later, and the old certificate with your verification notes shows what you relied on at the time.

Subcontractors who work in more than one state

The same sub can have a different workers' comp position, different exemptions and different licence requirements in each state where it sends a crew.

Track at project level as well as company level. A sub with one general liability policy might still need separate workers' comp evidence for each state. Let one subcontractor have several active rows, one per state or project, each with its own status and clock.

Check the states listed on the workers' comp policy itself, usually on the information page, not just the certificate. If a crew crosses into a state that isn't listed, the policy may not respond there. Before each new state's first mobilisation, give the sub a fresh review instead of assuming last job's approval carries over.

Exemptions expire too

The common case is a small sub with no workers' comp policy because the owner is exempt. Treat that exemption as its own document type, with its own expiry and renewal reminders.

Florida's construction exemption is a good example: it runs for two years, then has to be renewed. If "exempt" sits in your tracker as a permanent status, you'll miss the lapse.

State-fund coverage needs its own path too. In a monopolistic state, the evidence may come from the state fund rather than on a standard ACORD form. Tell your reviewers that's legitimate, so they don't reject it as the wrong paperwork.

The rule holds for every kind of exemption: log the document, log its expiry, and run it through the same renewal steps as a COI.

Five ways subcontractor insurance tracking breaks

These are process failures, not knowledge gaps. Teams usually know the rules. They lose track of the paperwork.

1. Collection treated as verification. A PDF arrives, gets filed and the row turns green. Nobody checked the endorsements.
2. Exemptions with no expiry date. They're filed once and never revisited.
3. No state review for travelling subs. Approval in one state gets waved through in another.
4. No audit trail. A "verified" status with no reviewer, date or endorsement attached won't help you in a dispute.
5. Deleted records. Expired certificates get purged to keep the sheet tidy, along with the evidence you'd need later.

Put the rules in the subcontract before mobilisation

Gate mobilisation: no sub starts work until a verified COI with confirmed endorsements is on file, received through one intake point.

Clause wording you can take to your lawyer as a starting point:

• "Subcontractor shall furnish a renewal certificate of insurance no later than 30 days prior to expiration of any required policy."
• "Contractor may withhold payment on any pay application where a current, verified certificate of insurance is not on file."
• "Contractor reserves stop-work authority for any active work performed without a verified, current certificate of insurance."
• "Subcontractor's insurance broker shall be available for direct confirmation of coverage upon Contractor's request."

Rollout takes three steps. Move every existing certificate from email and paper into the tracker. Hold a weekly 15-minute review of every row inside 30 days of expiry. Each quarter, pull a few "current" rows and check them against the endorsement PDFs on file.

Where these programmes really fail

Most subcontractor insurance programmes don't fail because someone misread a state rule. They fail because tracking lives in a shared inbox and a spreadsheet, and neither copes past a few dozen active subs.

The real tension is schedule against risk. Every compliance lead has felt the pull to let a sub keep working while a renewal is "in progress", because a payment hold slows the job. Contract language agreed before mobilisation takes that call out of the middle of a live project.

My view: choose conditional automation with a real audit trail over any manual system, however disciplined the team is today. People change roles. Spreadsheets don't enforce themselves.

— Kuldeep

Run the tracker in ExpiryEdge

You can run all of this in a spreadsheet with someone checking dates every Monday. ExpiryEdge does the date work for you: it reminds the sub or their broker at the intervals you choose, by email, SMS, WhatsApp, Slack or Teams, escalates to a manager when nothing arrives, and requests and collects the renewed certificate.

Every reminder, upload and status change is kept in an exportable audit trail, so the record exists without anyone remembering to update it. If you're still chasing certificates by email, load your current sub list into a 14-day trial and watch the first reminders go out.

Related reading

For checking a single certificate quickly, see our guide to verifying a certificate of insurance. For the wider document set, see the subcontractor onboarding checklist.

Sources

• Texas Department of Insurance: workers' compensation coverage for employers
• Florida Statutes 440.05: election of exemption
• Washington DES: out-of-state workers' compensation FAQs
• NAIC Consumer Insurance Search

FAQ

What Is the Difference Between Collecting and Verifying a COI?

Collecting means you received the certificate. Verifying means you checked the policy behind it: limits against the contract, the actual additional insured and waiver endorsements, the carrier, and that the policy is still in force. Log who verified it and when. A certificate on its own is a summary written by the agent and doesn't change the policy.

How Often Should You Send Renewal Reminders?

Start 60 days before expiry with a request to the subcontractor. Follow up at 30 days with their broker copied, escalate to your compliance contact at 14, and to the sub's owner at 7 with a payment hold flagged. Each step should check first whether a verified renewal has already arrived and skip itself if it has.

What Should Happen if a Certificate Expires With No Renewal on File?

The subcontractor's project row flips to expired, and two things follow: a payment hold on their pay applications and a stop-work flag on new work orders. Both stay until a verified renewal is on file. Put those consequences in the subcontract before mobilisation, so nobody has to argue about them mid-job.

How Long Should Expired Certificates Be Kept on File?

Keep them. Claims can surface years after the work, and the expired certificate plus your verification notes show what coverage you relied on at the time. There's no single retention rule, so ask counsel to set a period based on your contracts and state limitation periods, then archive rather than delete.

Does State Law Change What Fields Belong in a COI Tracker?

Not the core fields. Dates, limits, carrier and endorsements matter everywhere. State law changes the supporting documents: a Florida construction exemption certificate, a Texas sub that doesn't carry workers' comp, or state-fund coverage in Washington, Ohio, North Dakota or Wyoming. Add a field for those and track their expiry too.

Recommended

• How Supplier Compliance Tracking Works for Procurement Teams
• How Contract Obligation Tracking Works for Businesses
• Benefits of Automated Compliance Tracking for Teams
• Verify a Certificate of Insurance in 5 Minutes for Small Businesses