Published by Forsured Worth Reading in your inbox, every Tuesday
COI Journal

Construction insurance compliance, reported. The resource center for contractor COIs.

Resource Center · Reports

R-13White paperResource Center

What to require from any COI tool: a vendor-neutral specification

We don't rank software. But we can tell you what to ask for. This is a specification any COI tool, service or spreadsheet process can be measured against, with a way to test each line yourself.

Docket COIJ-26-0014November 13, 20262 min read

By The editors, COI Journal ·

The questionWhat should a general contractor look for in COI tracking software, and which checks matter most when choosing one?

Key findings

  1. The line that separates tools is whether they review endorsements against each project's requirements, or only store certificates and dates.
  2. Test every claim with your own documents: one real project's requirements and a handful of real certificates and endorsements.
  3. Ask how each pass or fail is explained, who handles exceptions, and how the broker gets the fix request.
  4. COI Journal doesn't rank or review vendors, including our publisher. This specification is meant to be used on all of them.

How to use this

Take one real project. Write down its insurance requirements. Pull three to five real certificates and the endorsements behind them, including at least one you know has a gap. Then run every tool, service or process you're considering against the same packet, line by line, using the specification below.

The specification

Requirements

  1. Holds different requirements per project, and per trade tier within a project.
  2. Captures coverages, limits, endorsements, durations, named additional insureds, carrier rating, deductible caps and notice rules.
  3. Records where each requirement came from in the contract.

Review

  1. Reads the certificate and extracts carriers, policy numbers, dates, limits and names.
  2. Reads the endorsements, not just the certificate's checkboxes. See additional insured.
  3. Checks ongoing and completed operations separately. See completed operations.
  4. Checks primary and noncontributory, waivers of subrogation and per project aggregates as separate requirements.
  5. Flags a missing document as a failure, not a pass.
  6. Explains each failure: the requirement, what was found, and the document that would fix it.

Renewals and lapses

  1. Tracks expiration dates at the policy level, across every project a trade works on.
  2. Requests renewals, with endorsements, before expiration.
  3. Treats a policy with no renewal on its expiration date as lapsed. See notice of cancellation.

Fixing gaps

  1. Sends deficiency requests to the trade's broker with the requirement quoted.
  2. Lets the broker respond with documents, and re-checks what comes back.
  3. Keeps an audit trail of who checked what, and when.

Fit and governance

  1. Works with the project tools you already use.
  2. Says clearly what is automated and what a person reviews.
  3. Says how its accuracy is tested and how errors are caught. See Can AI review a COI?.
  4. Says where your documents are stored and who can see them.
  5. Publishes its pricing, or quotes it in writing.

Demo questions

  • Show me a certificate with a checked additional insured box and no endorsement. What happens?
  • Show me how you check completed operations separately from ongoing operations.
  • Show me a project with different limits than my standard subcontract.
  • Show me what the broker receives when something fails.
  • Show me the audit trail for one certificate.

Scoring

Mark each of the 20 lines pass, partial or fail on your packet, not on the slide deck. Weight lines 5 to 9 most heavily: they decide whether the tool finds the gaps that cost money.

How we wrote this

This is a vendor-neutral specification. It names no products and makes no claims about any. COI Journal is published by Forsured, which sells COI compliance software; this paper is written so it can be applied to Forsured's product as easily as to any other. General information, not legal or insurance advice.

Sources

  1. ACORD 25 Certificate of Liability Insurance (2025/12), as posted by the New York State Department of Financial Services, ACORD / NY DFS

General information, not legal or insurance advice. Read your contracts and policies with your broker or attorney. COI Journal is published by Forsured, which sells construction insurance compliance software. How we keep editorial separate.

More from Reports

R-01White paperResource Center

A certificate is not coverage: six ways contractor COIs fail project requirements

The certificate is the one document everyone collects and almost nobody can rely on by itself. Here is where it breaks, in the order we would check it.

Docket COIJ-26-0002November 13, 20266 min read

R-20Analyst briefResource Center

Two public owners, two insurance exhibits: Oregon DOT and Sonoma County compared

Public owners publish their insurance requirements, which makes them a rare window into how requirements are actually written. We read two side by side.

Docket COIJ-26-0021November 13, 20262 min read

R-07White paperResource Center

What goes into subcontract insurance requirements: a field guide for GCs and brokers

Every subcontract insurance exhibit is built from the same parts. This guide walks through each one, what it's for, and how two public owners actually wrote theirs.

Docket COIJ-26-0008November 13, 20263 min read

New reports in The COI Digest

Get The COI Digest

Worth Reading, our picks of the week's best construction insurance reporting, plus one term and one gap. Tuesday mornings, five minutes.

By subscribing, you agree to Forsured's Terms of Service and Privacy Policy. Unsubscribe from any email.

From our publisher

Check a contractor COI against your project requirements, free.

Forsured, which publishes COI Journal, will read one project's requirements and a contractor COI or two, and show you every gap it finds.