Most Certificate of Insurance tracking answers one question: do we have a certificate, and has it expired? Those are worth knowing, and they are not the question that gets anyone into trouble.
The question underneath is whether the certificate you are holding matches what this particular job requires. A COI can be current, genuine and $1,000,000 short. It can be current and name your managing agent instead of you. It can be current and evidence none of the endorsements your contract made mandatory.
Verisova tracks contractor and vendor certificates the usual way — one place, every expiration date, everything that needs attention — and compares each one against the insurance requirements recorded for the project it belongs to.
What a Date-Only Tracker Cannot See
An expiration-date tracker gives you a green row for any certificate inside its policy period. Everything in this list produces a green row:
- A general aggregate of $1,000,000 against a project that requires $2,000,000.
- Coverage that is current today and runs out eleven weeks before the work finishes.
- A certificate naming the wrong entity in your group as certificate holder.
- A contract requiring a waiver of subrogation, and a document that evidences none.
- A named insured that is the contractor’s parent company rather than the company you engaged.
None of those are date problems, and none of them are visible to a system whose only stored fact about a certificate is when it expires. COI coverage gaps works through each of them with the numbers attached.
Why the Spreadsheet Stops Working
Most teams start with a spreadsheet, and for a handful of contractors it is genuinely fine. It starts costing you at the point where the number of rows exceeds the number you can hold in your head.
- The expiration column is only as current as the last time somebody updated it.
- A renewed certificate overwrites the old row, so the history of what was approved disappears.
- The spreadsheet records that a certificate was received, not what was in it.
- Two projects with different insurance requirements share one “compliant?” column.
- It tells you nothing until somebody opens it and reads every row.
The underlying issue is that a spreadsheet tracks documents. What you need tracked is coverage, measured against requirements, over time. The COI tracking spreadsheet covers what a manual tracker needs to hold, and the four points at which it stops being reliable — including when it is still the right tool.
One Record Per Certificate, Not One Row
Every certificate you review is stored with the detail that was read out of it, so the record answers questions instead of pointing at a file:
- The coverage details extracted from each certificate, not just the file name
- Policy numbers, carriers and the producer to contact with questions
- Effective and expiration dates, and the status derived from them
- Which project each certificate is assigned to
- The findings from the last review, and what they were measured against
The certificate list can be searched, filtered by status and sorted, so “which of these has lapsed” is a filter rather than a read-through.
Expiration Tracking
Insurance expiration tracking is the part most certificate tracking systems do, so it is worth being precise about how this one does it. Every certificate carries its expiration date and the status derived from it, recalculated against the current date rather than stored once and forgotten. Coverage that has expired and coverage that expires within the next thirty days are distinguished from coverage that is fine, and the dashboard carries the counts.
Where a certificate is assigned to a project, expiration is also compared against the project’s own dates. A policy that runs out six weeks before the work finishes is a different problem from one that expires next year, and it is the kind that gets approved by accident.
Expiration is shown in the app, not emailed to you
What Needs Attention, and Why
Rather than a single compliant-or-not column, each certificate carries the specific states that apply to it:
- Expired — the expiration date has passed.
- Expiring soon — the expiration date is within the next 30 days.
- Expires during the project — coverage ends before the work it covers does.
- Below requirement — a limit falls short of what the assigned project requires.
- Missing endorsement — the project requires one and nothing on the certificate evidences it.
- Low confidence — a field could not be read reliably and is worth checking against the document.
Each one names the value it came from, so acting on it does not start with working out what it meant. The verification side covers how those findings are produced.
Managing Multiple Contractors and Vendors
Contractors are grouped by the project they are working on, and each project shows which of its contractors are ready, which need attention and which have expired coverage — along with a risk score built from those findings and the reasoning behind it.
The same contractor can be assigned to more than one project, and is evaluated against each project’s own requirements. A subcontractor whose limits are fine for one job can fall short on another without anything about their insurance having changed.
The same mechanism covers vendors and suppliers, who are usually the larger and more neglected half of the list: a project in Verisova can equally be a site, a service category or a framework agreement. Vendor insurance tracking covers the standing-vendor version of this, where the risk is renewals rather than mobilisation, and supplier insurance compliance covers it from the procurement end.
The Renewal Workflow
When coverage reaches its expiration date, the work is not marking a row green again:
- Request current documentation from the contractor through your usual process.
- Review the replacement certificate rather than assuming the renewal matches the original — carriers, limits and endorsements all change at renewal.
- Keep the previous review, so the project’s history says what was approved and when.
What to do when a contractor’s COI expires walks through that review, and the COI compliance checklist keeps a renewal from being waved through on the strength of the certificate it replaced.
Compliance Visibility
The point of tracking is being able to answer a question without preparing for it: which contractors on this project have coverage that satisfies our requirements right now, and which do not. Verisova answers that from the reviews and requirements already recorded.
What it will not tell you is that a policy is definitely in force — that means contacting the carrier, which Verisova does not do. It tracks and reviews the documentation you have been given.
Tracking one contractor end to end, from certificate received to ongoing monitoring, is covered on contractor insurance tracking software. How each certificate is read in the first place is covered on the COI scanner page.