The Spreadsheet That Looked Fine Until It Wasn't
A regional franchise system with 67 locations had been tracking franchisee COIs in a shared Excel spreadsheet for four years. The spreadsheet tracked franchisee name, policy types, expiration dates, and a "compliant" checkbox updated by whichever team member last reviewed the file. When the company's insurance broker conducted an annual review, they flagged something: 19 of the 67 "compliant" franchisees had COIs on file that listed coverage limits below the franchise agreement minimums. Three more had the wrong entity named as additional insured. Several had endorsements that did not satisfy the "primary and non-contributory" requirement in the standard agreement.
The spreadsheet had 67 checkboxes marked as compliant. The actual compliance rate was closer to 67 percent.
Why Manual COI Tracking Fails at Scale
Manual franchisee COI tracking is manageable at a very small scale - perhaps 10 to 15 locations. Beyond that, the combination of volume, complexity, and human error creates a system that looks like it is working while producing unreliable results.
Volume compresses review time. A compliance coordinator managing 100 franchisees with three policies each is handling 300 COIs per year at renewal, plus midterm changes, new vendor additions, and follow-up on deficiencies. With competing priorities, the review for each COI shrinks to a few minutes - just enough time to verify the expiration date and check that a certificate exists, not enough to verify every field against the franchise agreement.
Requirements vary across franchisees. A franchise system with agreements signed over a decade may have meaningfully different insurance requirements by vintage. Manual tracking requires the reviewer to know which requirements apply to each franchisee and check the COI against those specific requirements. In practice, most manual reviewers use a single checklist for the entire system.
COIs are not self-validating. The ACORD 25 certificate of insurance shows coverage summaries, not policy details. A COI can show "$2 million per occurrence" without revealing that the policy excludes the specific activity that caused the franchisee's last three claims. It can show "Additional Insured: [Franchisor Name]" without confirming the endorsement basis. Manual reviewers who are not trained insurance professionals will miss these distinctions consistently.
Expiration tracking is a full-time job. A 100-franchisee system with policies renewing year-round means someone is expiring every week or two. Manual expiration tracking requires proactive calendar management, follow-up sequences, and re-verification after renewal - all while managing the current compliance caseload.
What Collection Platforms Miss
Several technology platforms address part of the franchisee COI tracking problem: they digitize the collection process, send automated renewal reminders, and store COIs in a searchable database. For franchise systems still relying on email and spreadsheets, these platforms are a genuine improvement.
But collection is not compliance. The gap between collecting a COI and verifying that it satisfies the franchise agreement requirements is where most non-compliance lives.
A collection platform will tell you that a franchisee has submitted a COI. It will not tell you:
- Whether the coverage limits match what the franchise agreement requires
- Whether the additional insured endorsement satisfies "primary and non-contributory" language
- Whether the named insured on the COI matches the franchisee entity in the franchise agreement
- Whether the waiver of subrogation is in place
- Whether the umbrella policy follows form over the primary coverages
These are the fields that determine whether a franchisee's insurance will actually respond when the franchisor needs it to.
The Contract-to-COI Comparison Problem
True franchisee COI compliance requires comparing every data point on the submitted COI against every requirement in the franchise agreement. This sounds straightforward but creates several practical challenges.
Requirements are in legal documents. Franchise agreement insurance sections are written in legal language, not insurance terms. "The franchisee shall maintain commercial general liability insurance with limits of not less than One Million Dollars ($1,000,000) per occurrence and Two Million Dollars ($2,000,000) in the aggregate" must be translated into a verification rule. At scale, that translation must happen consistently and automatically.
Requirements vary by field. The same franchise system may have different requirements for a food service franchisee versus a retail franchisee, a legacy franchisee versus a recent signing, or a franchisee operating in a high-risk territory versus a standard one. A contract-to-COI comparison must be anchored to the individual franchise agreement, not a system-wide average.
COI data must be extracted accurately. Comparing a COI to a franchise agreement means extracting the relevant data from both documents and comparing them field by field. Manual extraction is error-prone. Automated extraction must handle the variability in how different brokers present the same information on ACORD 25 forms.
What Compliance Dashboard Numbers Actually Mean
Most franchise operations teams have a compliance dashboard - a summary view showing what percentage of franchisees are "compliant." The number is typically above 90 percent. The problem is how it is calculated.
| Compliance Metric | What It Measures | What It Misses |
|---|---|---|
| "Has submitted a COI" | COI exists on file | Everything about whether the COI is adequate |
| "COI not expired" | Expiration date is future | Limit adequacy, endorsements, named insured |
| "Coverage types present" | Policy types are listed | Limits, exclusions, endorsement specifics |
| "Additional insured listed" | AI name appears on COI | Whether AI is primary & non-contributory |
| "Contract-to-COI match" | Every field verified vs. agreement | Nothing - this is the only complete metric |
A dashboard showing 94% compliance based on "COI not expired" may reflect a true compliance rate of 60-70% when measured against the full requirements of the franchise agreements. That gap is where litigation risk lives.
Building a Scalable Tracking System
Franchisee COI tracking at scale requires a system architecture that addresses four functions:
1. Structured collection. COIs must be collected in a format that enables automated processing. This means a submission portal or email integration, not a folder of PDFs.
2. Automated data extraction. Every relevant field from the ACORD 25 must be extracted without manual re-entry - coverage types, limits, effective dates, named insureds, additional insureds, and endorsement indicators.
3. Contract-anchored verification. Each COI must be compared against the requirements specific to that franchisee's agreement. This requires the system to ingest and parse franchise agreements, not just COIs.
4. Exception management. Deficiencies must be flagged, communicated to franchisees, tracked through remediation, and documented in a compliance record. The workflow around exceptions is where most manual systems break down.
Bramble addresses all four. It reads franchise agreements to extract insurance requirements, compares submitted COIs against those requirements field by field, and flags deficiencies with citations to the specific agreement language that is not satisfied. For franchise systems with 50 to 500 locations, it replaces a spreadsheet and a part-time compliance coordinator with a system that produces audit-ready compliance records.