A certificate of insurance expires without notice.

Most of what a company collects when it onboards a supplier stays true until something happens. A tax form stays valid until the supplier changes its legal name. A bank letter stays valid until the account moves. A signed agreement stays in force until someone terminates it. Each of those documents goes stale because of an event, and events tend to leave a trace: an email, an invoice with new remittance details, a notice.

The certificate of insurance is the exception. It goes stale on a date printed inside it, and nothing arrives when that date passes. The supplier keeps working, the invoices keep coming, and the file still holds a certificate that looks exactly as reassuring as it did the day it was uploaded. The coverage it describes has simply ended.

That makes a certificate a strange extraction problem. Reading it correctly is necessary but not enough. The value of reading it lies in three fields that each answer a different contractual question, and in turning one of them into a date on which somebody has to act.

The date at the top is not the date that matters

The document most suppliers send in the United States is the ACORD 25, the standard certificate of liability insurance. The current edition, ACORD 25 (2025/12), has a single date in its top corner, labelled DATE (MM/DD/YYYY). That is the day the certificate was issued. It says nothing about how long the coverage lasts.

The dates that matter sit in the coverage table, one pair per row: POLICY EFF and POLICY EXP. A single certificate commonly lists general liability, automobile liability, an umbrella or excess policy and workers compensation, and nothing requires those policies to renew together. They may come from different insurers, identified by the letter in the INSR LTR column, and they may have been placed at different times of the year.

So a certificate does not have one expiry. It has as many as it has rows, and the one that governs your contract is the earliest expiry among the lines your contract actually requires. A supplier whose general liability renews in March and whose umbrella renews in November holds a certificate that stops satisfying an umbrella requirement in November and a general liability requirement in March, whichever comes first.

The form is also precise about what it promises when coverage ends. Its cancellation box reads that if a policy is “cancelled before the expiration date thereof, notice will be delivered in accordance with the policy provisions.” That sentence covers cancellation before expiry. It says nothing about the expiry itself, because expiry is not an event anyone needs to announce. The date is already on the page. Whoever holds the certificate is expected to have read it.

Three fields, three consequences

A supplier agreement typically asks for insurance in terms that map directly onto columns of the certificate: a minimum limit per occurrence and in aggregate, the buyer named as an additional insured, a waiver of subrogation, and coverage kept in force for the life of the agreement. Each of those clauses is tested by a different field, and a failure in each has a different consequence.

The table is the reason a certificate cannot be reduced to “insured: yes.” The same document can satisfy the limits clause, fail the additional insured clause and be two weeks from failing the term clause. Those are three different findings with three different owners: procurement chases the renewal, risk management reviews the limits, and legal decides what an unevidenced additional insured status means for the agreement.

The checkbox is not the endorsement

The additional insured column is the field most often read as more than it is. The certificate itself says so. Its header states that it is issued “as a matter of information only” and that it does not amend, extend or alter the coverage afforded by the policies. Directly below, it adds that when the certificate holder is an additional insured, the policies must have additional insured provisions or be endorsed, and that a statement on the certificate does not confer rights in place of such an endorsement.

In extraction terms, a Y in the ADDL INSD column is a claim made by the producer who filled in the form. It is worth extracting exactly, because it tells you which lines the producer believes carry additional insureds. It is not evidence that your company is one of them. That evidence lives in the policy or in an endorsement, which the supplier may attach to the certificate, send separately, or never send at all.

The useful output is therefore a status with three values rather than a boolean:

• Evidenced — the column is marked and an endorsement or policy wording naming the buyer, or describing a class that includes the buyer, is on file for that line.
• Claimed, unevidenced — the column is marked and no supporting document has been received. This is the common case, and it is a request to the supplier, not a pass.
• Not claimed — the column is blank for a line the contract requires. The certificate itself says the requirement is not met.

The waiver of subrogation column deserves the same treatment. The form says that where subrogation is waived, certain policies may require an endorsement, subject to the policy’s terms. A mark in SUBR WVD is the start of that question, not the answer.

A limit on a certificate is a ceiling, not a balance

Limits look like the easiest field to check: compare the printed number with the contract minimum. The 2025/12 edition of the ACORD 25 is unusually direct about why that comparison proves less than it appears to. Its coverage section now states that limits shown may have been reduced by paid claims, and that limits shown are inclusive of amounts requested by the certificate holder and may not reflect policy limit amounts in excess of those requested. The first of those sentences carries an asterisk marking it as not applicable in Wyoming.

Read together, those sentences say that the number on the certificate is neither a guaranteed remaining balance nor necessarily the full policy limit. An aggregate that has been partly consumed by earlier claims can still print its original amount. A certificate prepared to show what a holder asked for can print less than the policy provides. Neither case is visible from the certificate alone.

That does not make the limits check pointless. It makes it a floor check with a stated boundary. A printed limit below the contract minimum is a real failure and should stop onboarding. A printed limit at or above the minimum is consistent with the requirement, not proof of it, and the record should say so. Two details decide whether even the floor check is right:

• Which limit — each occurrence, general aggregate, products and completed operations aggregate, combined single limit and the employers’ liability limits are different numbers with different meanings. A contract that asks for a per-occurrence minimum is not satisfied by an aggregate of the same size.
• What the aggregate applies to — the general liability row has boxes for whether the aggregate applies per policy, per project or per location. A contract that expects a per-project aggregate and a certificate that ticks per policy are describing different amounts of protection.
• Umbrella or excess on top — some contracts allow an umbrella policy to make up the difference between an underlying limit and the minimum. Whether that is allowed is a contract question; the extraction only has to keep the umbrella row separate and complete.

Recollect before the earliest date

Once the certificate has been read row by row, the part that actually prevents a lapse is a small scheduling rule that sits outside the extraction. It starts from the earliest policy expiry among the lines the contract requires, not from the certificate date and not from the upload date.

• Current — every required line is in force and the earliest expiry is further away than the request window your team has chosen.
• Expiring — the earliest required expiry falls inside the request window. The supplier receives a request for a renewal certificate, addressed to the line that is ending.
• Lapsed — the earliest required expiry has passed with no replacement on file. What happens next, whether a payment hold, a site-access hold or a review, is a business decision recorded in policy, not something the extractor infers.
• Under review — a replacement certificate has arrived and is waiting for the three field checks above.

The request window is a number the business sets and versions, in the same way a retention schedule keeps its periods in configuration rather than in code. The difference is the direction of the clock. A retention schedule counts forward from an event to decide when a record may be deleted. A certificate counts down to a date the document itself declares, after which the record stops meaning what it says.

Renewals bring one more matching problem. A renewed policy usually carries a new policy number, so a replacement certificate cannot be matched to the old one by number. Match it by supplier and by line of coverage, and let the policy number change. The certificate also has a CERTIFICATE NUMBER and a REVISION NUMBER: when a producer reissues a certificate mid-term, keep the later revision, and never let an older revision received late overwrite a newer one already on file.

What the extraction has to deliver

The contract between the certificate and the tracking rule is a set of facts with evidence, per row, and no decisions about whether the supplier is compliant.

• Every coverage row as printed — line of insurance, insurer letter, insurer name, policy number, effective date and expiry date, including lines the contract does not require.
• Every limit with its label — the amount and exactly which limit it is, plus the aggregate basis boxes for general liability.
• The two marker columns, per row — ADDL INSD and SUBR WVD as marked, blank kept as blank.
• Holder, issue date and revision — the certificate holder, the issue date, the certificate number and the revision number, labelled so no one mistakes the issue date for an expiry.
• Attached endorsements, identified separately — any endorsement pages classified as their own documents and linked to the line they modify.
• A citable origin for each value — page and region under the same coordinate contract any reviewable extraction owes, so a reviewer can go from “claimed, unevidenced” straight to the cell that made the claim.

On the other side of that contract sit the contract minimums, the request window and the lapse policy, all owned by the business and all versioned. A finding then reads as a sentence someone can act on: “umbrella policy expires on the 14th; renewal requested; additional insured on general liability still unevidenced.”

Not the submission packet, not the collection checklist

Two neighbouring problems use the same forms or the same workflow and should stay separate from this one.

An insurance submission is read by an underwriter deciding whether to offer coverage, and the ACORD forms in it are applications. The submission packet article covers how those forms index a larger packet of evidence. A certificate is read by a buyer after coverage exists, to decide whether a third party’s coverage meets a contract. Same organisation behind the forms, opposite side of the transaction.

A collection portal decides what a supplier must upload and how a rejection is explained, which the collection portal article treats as a contract with a person. The certificate adds something that article does not need: an item on the checklist that was satisfied at onboarding and becomes unsatisfied on a date, without the supplier doing anything at all.

Read the rows, then watch the earliest date

A certificate of insurance is a summary written by a producer, and it says so in its own header. It is useful precisely because it summarises: one page tells you which lines exist, how large they are, who the producer believes is covered and when each line ends. It is dangerous for the same reason, because a summary that was accurate at issue keeps looking accurate after the coverage behind it has ended.

So extract it row by row, with limits labelled and the marker columns kept as claims. Hold the additional insured status at “claimed” until an endorsement turns it into “evidenced.” Treat printed limits as a floor check the certificate itself qualifies. And compute the one date the document never announces: the earliest expiry among the lines the contract requires, with a renewal request going out well before it.