COI Basics
David Bunch
Insurance compliance runs on documents nobody wants to read: leases, subcontracts, COIs, endorsements, broker emails, tenant replies. Most of it is unstructured, and most of it ends up in someone’s inbox.
AI is very good at making sense of that kind of information. But insurance compliance is not a place where AI should make judgment calls on its own.
At FlexWurx, we split the work four ways:
AI interprets. Rules verify. Automation resolves. People handle exceptions.
AI interprets what’s happening
A lot of compliance work starts with interpretation. What does this lease actually require? Which subcontract does this COI belong to? What is the broker responding to? What changed in the latest document? What is still outstanding?
Take a broker reply like: “Updated certificate attached. Additional insured endorsement to follow.”
That one email contains two separate findings. The certificate can be reviewed now, while the endorsement is still outstanding and needs follow-up. Reading and sorting that kind of information across hundreds of tenants or subcontractors is exactly where AI can remove a lot of manual work.
Rules verify compliance
Once the information is understood, the question becomes much simpler:
Does the coverage meet the requirement?
If the subcontract requires a specific limit, the coverage either meets it or it doesn’t. If the lease requires additional insured status, the required documentation is either there or it isn’t. If coverage has expired, the system should know.
Those checks should be consistent every time. They should not depend on whether an AI model thinks something is probably acceptable.
That’s why FlexWurx separates interpretation from verification. AI helps understand the information. The compliance logic determines whether the requirement has actually been met.
Automation resolves the normal path
Finding a gap is only the beginning. Someone still has to contact the tenant, subcontractor, or broker, explain what’s missing, review what comes back, determine whether the new document actually fixes the issue, and follow up again if it doesn’t.
That’s why the inbox so often becomes the compliance system.
FlexWurx is designed to keep that work moving. When something is missing or incorrect, the system can manage the outreach, track the response, review what comes back, and continue the workflow without someone manually pushing every step forward.
The goal is not just to identify the problem. It’s to work the problem through resolution.
People handle the exceptions
Most compliance issues should not require a person to touch them. The normal path should be automated.
People step in when the situation actually requires judgment — an exception, a variance, unusual contract language, a disputed requirement, or an edge case the system should not decide on its own.
FlexWurx should prepare the context and surface the decision. It should not quietly make consequential exceptions on someone’s behalf.
The goal is not to hand work back to the team. It’s to automate the normal path and bring people in only when a real decision needs to be made.
From tracking to resolution
Most COI tracking follows a familiar pattern:
Upload. Track. Alert.
That is useful, but it mostly answers questions like: Do we have the certificate? Is it current? Who needs a reminder?
The more important question is:
Does the coverage actually meet the agreement?
FlexWurx follows a different model:
Understand. Verify. Resolve. Maintain.
Start with the lease, subcontract, or contract. Identify the insurance requirements. Verify the coverage against them. Work the gaps until they are resolved. Keep the compliance record current over time.
We don’t think the future of insurance compliance is AI making every decision. We think it is software doing far more of the work, while people stay in control of the exceptions that actually require judgment.
AI interprets. Rules verify. Automation resolves. People handle exceptions.
If you want to see what that looks like on your own files, send us one lease or subcontract and your tenant or subcontractor list.
More From the Blog
COI Basics
Aug 6, 2026
Compliance Is No Longer a Cost Center. It's a Competitive Advantage.
For years, insurance compliance has been viewed as a necessary administrative task. Collect the Certificates of Insurance (COIs), track expiration dates, file the documents away, and hope everything is in order if a claim or audit ever occurs.
David Bunch
COI Basics
Jun 30, 2026
The Certificate Isn't the Deliverable. Contractual Risk Transfer Is.
For many organizations, Certificate of Insurance (COI) compliance begins with collecting a document and making sure it stays current. A certificate is requested, the expiration date is tracked, and the document is filed until renewal. That process is important, but it is only the beginning.
David Bunch
COI Basics
Jun 16, 2026
Your Sub Is Insured. You're Still Exposed.
A subcontract requires $2 million in general liability coverage, with your company named as additional insured. The sub sends over a certificate. It's current, it's signed, it's filed. Everyone moves on. The certificate showed $1 million in coverage, and your company was never added as additional insured. Nobody caught it, because nobody read the certificate against what the subcontract actually required. It went in the folder marked compliant. Then a claim comes in at $1.4 million. The sub's policy pays its limit and stops. You aren't named on the policy, so the sub's carrier has no duty to defend you. The rest is yours, plus your own legal bill. The certificate never expired. It was wrong from the day it arrived.
David Bunch