Why subcontractors don't send their COIs on time (and what to do about it).

If you have ever sent the same COI request three times and still waited a week, the instinct is to blame the sub. But most delays come from the GC side of the process — unclear requests, wrong contacts, and collection workflows that require more effort than a busy sub will put in before the day is over.

It is usually not the sub's fault

A subcontractor running a small crew does not think about certificates of insurance the way a GC's compliance team does. For the sub, the COI is one item on a list that also includes scheduling, materials, equipment, and payroll. If your request requires more than a few minutes to act on, it gets pushed.

That is not negligence — it is triage. The subs who respond quickly are almost always the ones who got a frictionless request: a direct link, a clear list of what is needed, and a reminder when they forget.

The four friction points that slow every collection cycle

• The request went to the wrong person. The sub's PM got the email, but insurance is handled by their office manager or broker. The request sat until someone remembered to forward it.
• The sub does not know exactly what you need. "Send your COI" is not enough. Different projects require different limits, endorsements, or additional insured language. If the sub guesses wrong and you reject it, you lose another three days.
• The upload method is too hard. Asking a sub to create an account, navigate a portal, or attach a file to a reply to a specific email thread adds friction that kills response rates.
• There is no follow-up system. The first request went out and then nothing happened until a PM noticed the sub was still on a blocked list. By then, the window to fix it without delaying the project has closed.

Reaching the right contact from the start

On smaller subs, the person who handles insurance is often the owner's spouse, a part-time bookkeeper, or the broker directly. The PM who accepted the bid does not always know where the COI lives.

When you onboard a new subcontractor, ask explicitly: "Who should we send compliance requests to?" Get that contact on file and route requests there from the start. It is a small step that removes the single most common reason for a delayed first response.

Sending requests that actually get acted on

The most effective request includes the exact documents needed, the minimum coverage limits, whether an additional insured endorsement is required, and who to name on it. The sub should be able to forward the request directly to their broker and get the right document back without a phone call.

If your requests are consistently producing incomplete or incorrect submissions, the problem is usually in what you sent, not what the sub provided.

Three changes that reduce collection time

1. Replace email with a direct upload link. A link the sub can open on their phone, see exactly what is needed, and upload in one step removes every friction point in the current workflow. No login, no portal, no back-and-forth.
2. Send automated reminders on a schedule. Manual follow-up depends on someone remembering. Automated reminders at 7, 14, and 30 days before expiration run without anyone on your team touching it.
3. Make status visible to everyone who needs it. When field and finance teams can see whether a sub is compliant without asking, the informal pressure to get compliant becomes part of the work relationship — not just an admin task.

For more on how this fits into a broader subcontractor compliance workflow, see the subcontractor COI tracking guide, the no-login vendor portal, and the COI tracking software overview.