How to Collect COIs from Subcontractors (Without Chasing for Weeks)

Collecting COIs from subcontractors is slow for one structural reason: the person you're asking usually isn't the person who produces the document. The sub forwards your request to their insurance agent, the agent issues a certificate from what's already on file, and if anything needs to change — an endorsement added, an entity corrected — that's an underwriting touch, another round trip, and another week. Most collection pain is really correction pain.

Which means a good collection process is designed to prevent rounds, not just send requests. Here's the version that works.

Ask at the moment of leverage

There are exactly three moments a sub reliably responds: contract signing, mobilization, and payment. Use all three:

• Put the requirement in the subcontract — including the specific endorsement forms and the phrase "with all required endorsements attached." Blanket additional insured endorsements only activate where "required by written contract," so the written contract is doing legal work, not just administrative work.
• Gate mobilization on a reviewed-and-compliant cert, not a received one.
• Gate pay apps on continued compliance. This is the only follow-up mechanism that runs without anyone sending an email.

A request sent outside those moments is a favor you're asking. Inside them, it's a step in the sub getting paid.

Ask for the right thing, precisely, once

Half of correction rounds are caused by vague requests. "Send us your COI" produces a bare ACORD 25 with nothing attached, and the round-trip begins. The request that prevents rounds specifies everything the review will check:

• Certificate holder: your exact entity name and address
• Additional insureds: the exact entities (GC, owner, others your contract requires), by endorsement, forms attached — ongoing operations (CG 20 10 or equivalent) and completed operations (CG 20 37 or equivalent)
• Primary and noncontributory wording; waiver of subrogation (GL and workers' comp)
• Limits per the subcontract, with the umbrella shown
• All endorsement pages attached to the certificate

Send it to the agent, not just the sub. The sub's role is forwarding; every hop adds days. Ask the sub once for their agent's contact, then work agent-direct. Agents issue certificates all day — a precise request from you is easier for them than a vague one relayed through their client.

The templates

Initial request (to the sub, agent cc'd):

Subject: Insurance certificate needed before mobilization — [Project name]

Hi [name] — before we can get you started on [project], we need your certificate of insurance per Section [X] of the subcontract. To save your agent a second round, the certificate needs: [Entity names] as additional insureds by endorsement for ongoing and completed operations (CG 20 10 and CG 20 37 or equivalents), primary and noncontributory wording, waiver of subrogation, limits per the subcontract, and all endorsement pages attached. Certificate holder: [exact entity + address]. Your agent can send it directly to [email]. We can't release the NTP / first pay app until this is on file — happy to get on a call with your agent if that's faster.

Correction request (agent-direct):

Subject: Corrected COI needed — [Sub name], [Project]

Hi [name] — thanks for the certificate for [sub]. Two items before we can mark them compliant: (1) [specific gap, e.g. "the CG 20 37 completed-operations endorsement isn't attached — the description box references additional insured status but we need the form itself"], (2) [specific gap]. Everything else checks out. Can you reissue with those attached? [Sub] is scheduled to mobilize [date], so we'd love to close this out this week.

Specific gaps, named forms, a date, and a consequence. That email closes in one round far more often than "this doesn't meet our requirements."

Run the follow-up like a system, not a memory

The first request is never the problem — rounds two through five are, multiplied by every sub on every project. Whatever you use (spreadsheet, platform, or a tracking template), every open item needs three fields: what's missing (specifically), who's on the hook (agent, with contact), and the next follow-up date. Escalate on a fixed cadence — email, then phone, then the sub's PM, then the pay-app hold — rather than when someone remembers. An open item without a next-action date is how "requested 3/12" becomes the file's permanent state.

And then verify what arrives — collection isn't the finish line. A certificate nobody reads against the subcontract is a filed rumor. That's the verification half of the job, and it's where the claims actually get decided.

This whole loop — the precise initial request, reading what comes back against the subcontract, and the multi-round, multi-channel chase with subs and agents until the corrected cert lands — is what Tightrope's agent Travis does end to end. Your team sets the requirements; Travis runs the correspondence.

FAQ

How long does it take to get a COI from a subcontractor? A bare certificate: a few days. A certificate with corrected endorsements: one to three weeks, because endorsement changes go through underwriting. Which is the argument for requesting precisely, agent-direct, before mobilization pressure builds.

Should I request the COI from the sub or their insurance agent? Route the first request through the sub (they choose their agent), then work directly with the agent for everything after. Every relay through the sub adds days and loses specifics.

Can a subcontractor start work before providing a COI? They can — at your risk, and with your leverage gone. If an exception is unavoidable, put it in writing with a hard deadline and hold the first pay app until the cert clears review.

---

Tired of being the one sending round four? Put Travis on it — Tightrope's free plan will run the chase on a real sub so you can watch it work.