Workflow — COI Tracking

COI tracking without the per-cert annual fee.

Sub and vendor COIs validated against contract requirements — coverage limits, additional-insured language, expiration dates, policy exclusions. Tracking and renewal alerts into myCOI, COITRACKING, or Procore. Replaces per-cert annual fees ($4–$15 per cert) at incumbent COI-tracking vendors.

$4–$15
Per cert per year at COI-tracking vendors
Acord 25
Standard COI form across the industry
60–85%
Volume off the COI vendor line after AI cutover
What This Replaces

The Per-Cert Annual Fee Stacking Up Across Subs and Vendors

The cost of leaving COI tracking with a per-cert pricing model — and what it doesn't catch.

The labor

COI tracking today moves through dedicated vendors — myCOI, COITRACKING, EBIX COI Compliance, Origami Risk's COI module — charging $4–$15 per cert per year. A GC or owner with 100–500 active subs and vendors per project across 10–40 projects has 1,000–20,000 certs in flight per year. Annual COI vendor spend often runs into low-six-figures, and the verification work itself is shallow — most vendors check expiration dates and basic limits, not contract-specific additional-insured language or policy exclusions.

The cycle time

Most COI vendors run on a quarterly review cycle, with renewal alerts going out 30–60 days before expiration. The deep contract-language verification — that the additional-insured wording matches the indemnity clause, that pollution exclusions don't gut the coverage, that umbrella endorsements actually attach — is usually skipped or done by the GC's risk manager when an issue surfaces during a claim.

The Workflow

Input · Analysis · Output

What goes into COI verification, what we do to it, and what shows up in the tracker.

Input

COIs from subs, vendors, tenants

  • Acord 25 (Certificate of Liability Insurance)
  • Acord 27 / 28 (Evidence of Property Insurance)
  • Endorsements (CG 20 10, CG 20 33, CG 20 37, etc.)
  • Umbrella and excess policy declarations
  • Workers comp certificates (Acord 130 / state forms)
  • Auto liability (Acord 25 with auto coverage)
  • Sub and vendor contract documents
Analysis

Validate, match, expire

  • Coverage-limit match against contract requirements
  • Additional-insured language match (CG 20 10 vs CG 20 33 vs CG 20 37)
  • Waiver-of-subrogation endorsement validation
  • Primary-and-noncontributory wording verification
  • Policy-exclusion analysis (pollution, lead, mold, professional liability)
  • Expiration tracking with renewal alerts
  • Confidence score per finding; exceptions to risk-management queue
Output

Compliance log into the SoR

  • myCOI (REST API)
  • COITRACKING (REST API)
  • Procore Insurance Manager (Procore Connect API)
  • Origami Risk (REST API)
  • Compliance dashboard per sub and per project
  • Expiration alerts with renewal queue
  • Field-level audit trail per cert
Side by Side

COI Tracking Today vs. With Last Rev

The numbers that matter: depth of verification, cost per cert, accuracy, and exposure reduction.

Dimension COI-Tracking VendorLast Rev COI Tracking
Pricing model $4–$15 per cert per yearVolume-tiered, benchmarked at 25–45% of vendor unit cost
Cycle time, cert received to verified 5–15 business days at vendorSame-day per cert
Additional-insured language verification Surface check, often missed CG 20 10 vs 20 33 distinctionEndorsement-form-specific match against contract
Policy-exclusion analysis Generally not performedPollution, lead, mold, professional exclusions surfaced
Audit log per finding Vendor portal status, no field-level lineageSource endorsement + contract clause + model version + confidence
Tracker-system integration Vendor portal handoffDirect via documented myCOI / COITRACKING / Procore APIs
Renegotiation leverage at next vendor renewal None — you're locked in on per-cert annual60–85% of routine verification off the contract
How It Works

From Cert Received to Compliance Status

Five steps. Every one logged. Every one reversible if your confidence threshold isn't met.

Submission Lands
COI from the sub or vendor — Acord 25, endorsements, umbrella decs, workers comp, auto. Contract requirements pulled from the sub agreement so verification matches actual contractual coverage requirements, not generic checks.
Extraction & Classification
Coverage limits matched against contract. Additional-insured language matched (CG 20 10 vs CG 20 33 vs CG 20 37). Waiver-of-subrogation, primary-and-noncontributory, and umbrella attachment validated. Policy-exclusion analysis performed for pollution, lead, mold, professional liability.
Validation Against Contract Requirements
Findings validated against the sub's contractual coverage requirements. Anything below your confidence threshold per finding is routed to a human exception queue — your call which queue, ours or yours.
Push to System of Record
Compliance log entry per cert. Expiration alert with renewal queue. Compliance dashboard per sub and per project. Into myCOI, COITRACKING, Procore Insurance Manager, or Origami Risk via the documented integration.
Audit Log Persisted
Every coverage match, endorsement validation, and exclusion finding logged with the source cert, contract clause reference, model version, and confidence score. Defensible chain of custody for any contested claim coverage.
Compliance & Defensibility

Built to Meet the Quality Bar Risk Management Already Runs On

Acord and ISO endorsement form awareness
CG 20 10, CG 20 33, CG 20 37, CG 20 38 distinctions enforced at validation. Acord 25, 27, 28, 130 form-specific extraction. Endorsement updates from ISO and Acord flow into the validation engine within days of effective dates.
Contract-specific coverage matching
Sub contract pulled into the same review so the verification matches the actual contractual coverage requirements, not generic per-cert checks. Custom indemnity language, waiver-of-subro requirements, and umbrella minimums all checked.
Coverage-gap claim defensibility
When a claim arises and coverage is contested, the audit log produces what was verified at the time of contract, what endorsements were on file, and what exclusions were noted. Cleaner than reconstructing from a vendor portal months later.
Sub data residency
COIs contain insurance carrier identifiers, policy numbers, and contractual coverage data. Deployable in your VPC or our SOC 2 environment. Encryption in transit and at rest; retention policies set against your project closeout schedule.
Common Questions

What GCs & Owners Ask About COI Tracking

How is this different from myCOI, COITRACKING, EBIX, or Origami Risk's COI module?
Those are the systems where COI compliance status lives. The competitor on this page is the per-cert annual fee model — typically $4–$15 per cert per year — that compounds across hundreds or thousands of subs. We integrate directly into your existing COI-tracking deployment and deliver deeper verification (additional-insured form-specificity, exclusion analysis, contract-clause matching) at materially lower per-cert cost.
We have a COI-tracking vendor on retainer. How does this work alongside that?
Most GCs and owners keep the vendor in place during pilot and early production — we run alongside on the verification depth and route exceptions back to the vendor or to in-house risk management. Volume to the vendor drops 60–85% on routine verification once cutover completes. You renegotiate at the next renewal from a much better position, or shift the relationship to higher-complexity work like claim coverage disputes.
What's your accuracy bar versus a COI vendor?
Our pilot success threshold is COI-verification accuracy at parity with or above your incumbent vendor, measured on the same shadow-data sample of certs and validated against the risk-management calibration set. We typically beat vendor depth on additional-insured language and policy-exclusion analysis. Anything below your defined confidence threshold per finding is routed to a human exception queue — your call which queue, ours or yours.
How do you handle the additional-insured form-specificity (CG 20 10 vs CG 20 33 vs CG 20 37)?
Each ISO endorsement form has distinct coverage scope (ongoing operations, completed operations, automatic vs scheduled). The validation engine matches the endorsement form on the cert against the contract requirement and surfaces any mismatch. The audit log records the form-specific basis for any flag.
How do you handle policy exclusions (pollution, lead, mold, professional)?
Policy declaration pages and endorsement schedules are extracted alongside the cert. Pollution, lead, mold, and professional-liability exclusions are surfaced when they appear, with the exclusion language cited so risk management has the basis for any contractual remediation request.
Can you actually integrate with myCOI, COITRACKING, Procore Insurance Manager, and Origami Risk?
Yes — through the documented integration surface each platform supports. myCOI and COITRACKING via REST APIs; Procore Insurance Manager via the Procore Connect API; Origami Risk via its REST API. Your IT team reviews and approves a service account, and we connect through the documented integration. We do not require platform-side custom development.
How long until a pilot is running on a live portfolio?
COI-tracking pilots typically run 6–8 weeks: 1–2 weeks of integration and contract-template mapping with risk management, 4 weeks of shadow-mode running on real certs with no system-of-record writes, 1–2 weeks of supervised cutover on a constrained scope (one project, one trade tier). Production rollout is staged after the pilot meets your accuracy and SLA bar.
What does pricing look like compared to our current per-cert annual fee?
We benchmark against your current per-cert annual cost ($4–$15). Our target is 25–45% of that per-cert cost at higher verification depth and faster cycle time. Pricing structures around volume tiers and outcome SLAs, not per-cert annual fees.

Two Ways to Start

Take the AI assessment for a structured read on COI-tracking feasibility. Or talk to us if you already know the per-cert annual fee is the line item you want off your operating budget.

Other Workflows

More Construction Workflows We Replace

The same approach, applied to the other document-heavy labor lines on your project-controls budget.