Why Your Subcontractors Hate Your COI Process (And What to Do About It)
Subcontractor compliance fatigue is real, and it's the silent killer of your COI tracking program. Here's why your vendors push back — and how to redesign the experience without lowering the bar.
Here's an inconvenient truth: every subcontractor on every jobsite is going through the same uniquely irritating experience with someone's COI tracking system, right now, today.
We've been on a lot of calls. We've heard every variation of the same story. The certificate the platform demanded didn't match what the broker actually issued. The portal kicked them out three times. The "just upload the certificate" workflow turned into a 45-minute fight with PDF formatting. The compliance email had a tone that suggested the platform thought the sub was operating a meth lab.
This experience matters because compliance fatigue is real, and compliance fatigue is the silent killer of your COI program. Here's how to recognize it and what to do about it.
What compliance fatigue looks like
You can spot it in your data:
- Lengthening time-to-compliance. Subs used to upload within 3 days; now it's averaging 12.
- Rising "lost in the system" rate. Vendors swear they uploaded; the platform has no record. Both are sometimes correct.
- Shrinking response rate to renewal reminders. Vendors stop opening the emails.
- Calls to your AP team to circumvent the COI process. The classic: "Can you just accept this PDF over email so we can get paid?"
- Broker complaints reaching your account management team. Brokers don't usually escalate. When they do, it's bad.
If you're seeing two or more of these, your subs are fatigued. The platform might be good. The implementation might be wrong. Either way, it's a problem.
Why fatigue happens
Three root causes, usually in combination.
Cause one: the vendor experience is bad. Some COI platforms (we won't name names; we don't have to) optimize the admin dashboard at the expense of the vendor portal. Subs get a clunky upload flow, confusing requirements, and error messages that don't explain what went wrong. They give up. Or worse, they upload anything and hope it sticks.
Cause two: the requirements are wrong, but the platform doesn't know. Your contract says $1M general liability. The platform's requirement template says $2M. The sub uploads $1M, the platform rejects it, the sub gets confused, your team has to manually override. Every override teaches your sub that the platform's outputs are negotiable, which undermines the whole compliance signal.
Cause three: the communication is generic and impersonal. Compliance reminders from noreply@platform.com with templated language that doesn't reference the actual project, contract, or relationship feel like spam. Subs treat them like spam. The platform thinks the sub is unresponsive; the sub never saw the message.
The redesign principles
Fixing this isn't about lowering the compliance bar. It's about making the bar achievable without subs needing to file a Geneva Convention complaint.
Principle 1: Test the experience as a sub. Quarterly. Walk through your own onboarding flow. Try to upload a certificate. Try to clear an exception. Try to communicate back. If you find friction, your subs found it three months ago and stopped engaging.
Principle 2: Audit your requirements. Compare your platform's requirement template to your actual contractual requirements. Wherever the platform is stricter than the contract, you're creating manual work for your team and frustration for your subs without any compliance benefit.
Principle 3: Personalize the communication. The best platforms let you (or do for you) communications that reference the project name, the specific contract, the actual missing item, and a real human contact. "Hi Maria, your COI for the Tampa Logistics Center is missing the additional insured endorsement. Reply to this email or call John at extension 412 and we can resolve in five minutes." That's a 5x response rate over generic compliance spam.
Principle 4: Review before automation. This is where Jones gets it wrong, in our research. Auto-blasting noncompliance notices to vendors before a human has reviewed them creates relationship damage out of proportion to the workflow benefit. The right model is automated drafting with human approval, then send.
Principle 5: Make compliance visible to the sub. A sub who can log in and see their own compliance status, what's required, what's resolved, and what's outstanding — without calling your team — is a sub who self-services. That reduces your inbound volume and increases their compliance rate. Win-win.
What to look for in a platform
If you're evaluating COI trackers with vendor experience in mind:
- Demo the vendor portal yourself. Not the admin side. The portal a real subcontractor will use.
- Look at the communication templates. Generic? Personalized? Editable?
- Check the review queue model. Automated send? Human review? Hybrid?
- Ask about vendor self-service. Can subs check their own status? Renew without contacting your team?
TrustLayer's vendor experience is one of the more frequently-praised in the category, particularly the modern interface and the network effects from a 298,000+ company database (vendors who've already onboarded once don't have to redo their data). The bcs platform also rates highly on vendor experience, with no-login submission flows. The platforms that score lowest on this criterion in our research tend to be the older players (myCOI, certain legacy systems) and Jones — the latter for the auto-outreach problem rather than the portal itself.
The bottom line
Your subs aren't the problem. The process is. The platform is downstream of the process, but it can either compound the friction or reduce it. Pick accordingly.
If you want a comparison shaped around vendor experience as a top-weighted criterion, our tool will surface the platforms that handle this well. Three minutes, shortlist at the end. Your subs will thank you. Eventually. Or at least stop calling AP at 4:50 on a Friday.