Skip to content

Systems and records

Certificate of insurance verification dataset: is the requirement met?

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Test a certificate against the requirement, not against itself. Split the contract's insurance clause into single conditions, match each to the certificate field and to the policy or endorsement that actually creates it, and label each met, not met, not provable or conflict. A certificate only evidences coverage; it cannot make anyone an additional insured, add a waiver or promise notice of cancellation.

Provenance trail

Certificate insurance

This page covers certificate of insurance verification dataset: is the requirement met.Illustrative

Key takeaways

  • A certificate evidences coverage; additional insured status, waivers and notice rights come only from the policy or an endorsement.
  • Split each insurance clause into atomic conditions and label every one, with a pointer to the page and field that supports it.
  • Keep a not provable label; without it, annotators and models learn to treat a checked box as proof.
  • Record the requirement version, the certificate's form edition and the review date, because all three change.
  • Score the false met rate on endorsement-dependent conditions as the primary error, and pre-register the method before running any system.

How do you test whether a certificate satisfies a specific requirement?

Test the certificate against the requirement, one atomic condition at a time, and accept a condition as met only when a document with the power to create it says so. A certificate of insurance shows that coverage existed on the day it was issued; it does not create, amend or extend coverage, and a holder named on it gains no coverage from it. So the honest answer for several requirement types is not yes or no but not provable from the certificate alone.

ACORD, which publishes the most widely used certificate forms, says plainly that a certificate is not an insurance policy and that only an endorsement, rider or amendment to the policy changes coverage. New York goes further in statute: Insurance Law section 502 bars a certificate from amending, extending or altering coverage and bars anyone from requiring a certificate to include terms the policy does not contain. Texas limits certificates for Texas risks to forms its Department of Insurance has approved.

That framing is what makes certificate verification useful as an AI dataset. Most real archives already contain the three ingredients: the contract or vendor-onboarding requirement, the certificate a broker sent, and sometimes the endorsements and declarations that back it. What they rarely contain is a clean, per-requirement record of which document proved which condition, which version of the requirement applied, and who decided an unresolved gap. This guide specifies that record as a benchmark brief a compliance, procurement or insurance operations team can build from its own files.

What the certificate can show, and what only the policy or endorsement can prove

Sort every requirement into what the certificate can display and what only the underlying policy can establish before anyone labels a single file. The table below is the sorting key the benchmark uses. The last column is the label an annotator must apply when the certificate is the only document on hand.

Two notes sit behind the table. The current ACORD 25 edition tells the holder that if it is an additional insured, the policy must have additional insured provisions or be endorsed, and that a statement about subrogation waiver on the certificate does not confer rights in place of the endorsement. New York's Department of Financial Services has also said that certificate holder is not a synonym for additional insured, and that a holder's right to cancellation notice exists only when the holder is actually named in the policy or an endorsement.

What the certificate can show, and what only the policy or endorsement can prove
Requirement typeWhat the certificate showsWhat actually proves itLabel if only the certificate is present
Coverage line in force (general liability, auto, workers compensation, umbrella)Policy type, insurer, policy number, effective and expiration datesDeclarations page for the same policy numberMet for screening; record that declarations were not seen
Per-occurrence or each-accident limitLimit printed in the limits columnDeclarations page or limits scheduleMet for screening if the printed limit equals or exceeds the requirement
Aggregate available for this projectAggregate as written, not what remains after claimsLoss runs or insurer confirmation; per-project aggregate endorsement if requiredNot provable from certificate
Additional insured status for the requiring partyA check box and a remarks lineAdditional insured endorsement or policy provision, with its conditionsNot provable from certificate
Waiver of subrogation in favor of the requiring partyA check boxWaiver endorsement or policy wordingNot provable from certificate
Primary and noncontributory wordingFree text in the description of operations boxEndorsement or policy conditionNot provable from certificate
Notice of cancellation to the requiring partyStandard cancellation boxNotice endorsement naming the party, or statuteNot provable from certificate
Named insured matches the contracting entityInsured name and addressDeclarations named insured scheduleMet only on exact legal-name match; otherwise conflict
Coverage period covers the work datesEffective and expiration datesSame, plus renewal certificate when work runs past expiryMet or not met by date arithmetic

The document requirement matching benchmark brief

The benchmark brief is the specification a team writes before collecting cases, so every case is built and graded the same way. It turns an archive of certificates and contracts into a set of tasks in which a system receives a requirement and a document packet and must return one label per atomic condition, with a pointer to the page and field that supports it.

At a glance

The document requirement matching benchmark brief

Use the components below as the brief's table of contents. Each one names a decision that changes what the benchmark measures, so record the choice and the reason in the brief itself rather than in a separate note.

The document requirement matching benchmark brief
ComponentWhat it fixesFormatWhy it matters
Task statementThe question the system answers for each caseOne sentence per task type, for example does this packet satisfy clause 7.2 as of the review dateStops a model from grading the certificate in general instead of against a clause
Requirement recordThe contract clause or vendor policy text, its version and effective dateClause ID, version, effective date, verbatim textA requirement that changed mid-relationship produces two different correct answers
Atomic condition listThe clause split into single checkable conditionsOrdered list with a condition type from the sorting keyLets scoring happen per condition rather than per document
Document packetEvery document available at review time, and nothing added laterCertificate with form number and edition, endorsements, declarations, broker letters, each with a received dateSeparates what the reviewer could know from what was learned afterward
LabelsThe allowed answers per conditionMet, not met, not provable from packet, conflictWithout a not provable label, models learn to guess yes
Evidence pointerWhere the label comes fromDocument ID, page, field or box nameMakes every label auditable by a second reviewer
Disposition historyWhat the organization actually didAccepted, rejected, accepted with follow-up, waived by named authority, with datesDistinguishes the correct label from the business decision, which may differ
Adjudication ruleHow disagreements between annotators are settledTwo independent labels, third reviewer on disagreement, reason recordedMeasures how ambiguous each condition type really is
SplitsWhich cases are used for development and which are held outSplit by requiring party or contract template, never by certificatePrevents a model from memorizing one template's wording
Exclusions and limitsWhat the benchmark does not testShort list, for example coverage interpretation, claims handling, legal sufficiencyKeeps results from being read as legal or coverage advice

Which version of the requirement and which form edition apply?

Apply the requirement version in force on the review date and record the certificate's form edition, because both change. Contract insurance exhibits are amended at renewal, after a loss or when a risk manager tightens terms, and a vendor that was compliant under the old exhibit can be noncompliant under the new one without any change in its insurance.

Form editions move too. ACORD's December 2025 bulletin lists the ACORD 25 (2025/12) Certificate of Liability Insurance as a revision of the 2016/03 edition, with revised certification language about limits; one added line says limits shown may have been reduced by paid claims. New York's approved-certificates page records approval of that edition. ACORD's July 2026 bulletin then announced a Georgia-specific ACORD 25 GA (2026/09) after Georgia's insurance regulator objected to the new limits statement, removing it from the certification paragraph; ACORD called the variant temporary and said it still needed the Georgia regulator's approval.

For the dataset, that means three dates per case: the requirement version's effective date, the certificate's issue date and form edition, and the review date. A model that learns from certificates without editions will treat wording differences between editions as signals about the insured, which they are not. Where a state limits which certificate forms may be used, as Texas does under Insurance Code Chapter 1811, record the state of the risk as well, because a request for a nonstandard form may itself be the problem.

Five conflicts the benchmark must keep instead of resolving

Label conflicts as conflicts; do not let the annotator or the model pick a winner from the certificate. In every case below, the policy and its endorsements govern, and a certificate cannot settle the disagreement. The benchmark keeps the conflict so a system learns to escalate it.

At a glance

Five conflicts the benchmark must keep instead of resolving

  • Check box versus endorsement: the certificate marks additional insured, but the attached blanket endorsement only covers parties the insured agreed in a written contract to add, and the contract in the packet is unsigned. Label conflict and point to both documents.
  • Named insured versus contracting entity: the certificate names a parent company while the contract was signed by a subsidiary with a different legal name. Label conflict until the declarations' named insured schedule is in the packet.
  • Remarks box overreach: the description of operations box says coverage is primary and noncontributory, but no endorsement in the packet says so. Label not provable; the remarks box cannot add terms the policy lacks.
  • Policy number drift: the endorsement carries a prior-term policy number, so it may belong to an expired policy. Label conflict and record both numbers.
  • Date gap: the certificate expires before the scheduled end of the work and no renewal certificate is in the packet. Label not met for the remaining period, and keep the follow-up request and its date as part of the disposition history.

Worked example (illustrative): a subcontractor certificate against a contract exhibit

This case is invented to show the record structure; names, clauses and counts are illustrative. A general contractor's insurance exhibit, version 3 effective the first of the year, requires a subcontractor to carry general liability at limit tier A per occurrence, auto liability, workers compensation, an umbrella, additional insured status for the contractor for ongoing and completed operations, a waiver of subrogation and primary and noncontributory coverage. The packet holds one ACORD 25 (2025/12) certificate, one blanket additional insured endorsement and no declarations pages.

The exhibit splits into 9 atomic conditions. The certificate settles 4 of them for screening, 2 are not met, 1 is a conflict and 2 cannot be proven from the packet. The disposition history shows the contractor accepted the vendor with follow-up, requested the waiver and completed-operations endorsements, and received them 12 days later, which becomes a second, later packet in the dataset rather than an edit to the first.

Worked example (illustrative): a subcontractor certificate against a contract exhibit
ConditionCertificate showsOther document in packetLabelEvidence pointer
General liability in force on review datePolicy dates cover the review dateNoneMet for screeningCertificate, general liability row, dates
General liability per occurrence at tier APrinted limit at tier ANoneMet for screeningCertificate, limits column
Auto liability in forceAny auto box checked, dates currentNoneMet for screeningCertificate, automobile row
Workers compensation in forceStatutory limits box checkedNoneMet for screeningCertificate, workers compensation row
Umbrella in forceNo umbrella row completedNoneNot metCertificate, umbrella row blank
Additional insured, ongoing operationsBox checkedBlanket endorsement requiring a written contractConflictEndorsement, who is an insured section; contract signature page missing
Additional insured, completed operationsBox checkedEndorsement covers ongoing operations onlyNot metEndorsement, schedule
Waiver of subrogationBox checkedNo waiver endorsementNot provable from packetCertificate, waiver box only
Primary and noncontributoryRemarks text onlyNo endorsementNot provable from packetCertificate, description of operations

The exception: requirements a certificate can settle on its own

A certificate can settle conditions that are purely factual and printed by the issuer: that a named policy existed, its dates, the insurer and the limits shown at issue. For a screening workflow, accepting those from the certificate is normal, and the benchmark should treat them as met for screening rather than marking everything unprovable. A matcher that refuses every condition is as useless as one that accepts every check box.

The exception has its own exception. Limits printed on a certificate are the limits as written, and the current ACORD 25 edition warns that they may have been reduced by paid claims. Where a requirement says available aggregate or project-specific aggregate, the certificate cannot answer it.

Also keep the boundary between asking for proof and asking for impossible paperwork. New York prohibits requiring a certificate to contain terms the policy does not contain, and Texas lists other documents, including some questionnaires and affidavits about contract insurance requirements, that Chapter 1811 prohibits. A benchmark task whose correct next step is to request a broker-signed warranty may be teaching a system to make a request a state forbids. Mark the jurisdiction on every follow-up action and let an insurance operations reviewer approve the allowed next steps per state.

Scoring the matcher without rewarding confident guesses

Score per condition, and weight the false met error most heavily, because accepting an unproven additional insured or waiver is the mistake that leaves the requiring party exposed. Report each label's precision and recall separately, with not provable and conflict reported on their own rather than folded into not met.

This brief describes how to measure a matcher; it reports no results, and any team using it should pre-register the following before running a system on the held-out split.

  • The task types included and the requirement versions each draws from.
  • The label set and the decision rule for met for screening versus met.
  • The primary metric, for example the false met rate on additional insured, waiver and notice conditions, and the secondary metrics.
  • How evidence pointers are scored: exact field, correct page only, or wrong document.
  • Inter-annotator agreement per condition type, measured before model runs, so condition types humans disagree on are reported as uncertain rather than as model errors.
  • Confidence intervals by resampling cases within requiring parties, since cases from one contract template are not independent.
  • What the benchmark cannot show: coverage adequacy, whether an endorsement responds to a particular loss, or legal sufficiency of a contract clause.

Rights, privacy and form terms before certificate files are licensed

Certificate archives are full of other people's information: the insured's name and address, producer contacts, certificate holders, project addresses and sometimes individual owner-operators. Having those files in a compliance or procurement system is access, not a right to license them. Privacy permission, ownership of the records and the contractual right to share them for AI training are separate questions, and de-identification alone does not create the last one. Counsel should review the vendor agreements, any confidentiality terms in the contracts, and the terms that come with the certificate forms themselves before scoping.

A company with years of contracts, certificates and disposition histories that wants to explore licensing them can work through SourceX, which turns chosen business records into licensed AI datasets and handles the rights review, contracting, preparation and delivery. Scope is approved and the agreement signed before anything moves, and the de-identification step falls to SourceX through approved processing routes. Fit is checked first with a brief assessment that requires no upload.

Frequently asked questions

Does a certificate of insurance prove someone is an additional insured?

No. A certificate only evidences coverage; additional insured status comes from the policy or an endorsement. New York's insurance regulator has said a certificate holder is not the same as an additional insured, and the current ACORD 25 tells holders that the policy must have additional insured provisions or be endorsed.

Why does a certificate verification dataset need a not provable label?

Because several common requirements, such as waiver of subrogation, primary and noncontributory wording and notice of cancellation, cannot be established from the certificate at all. Without a separate label, annotators and models default to yes when a box is checked, which is the costliest error.

Which certificate form edition should the dataset record?

Record the form number and edition printed on each certificate, such as ACORD 25 (2025/12), plus any state variation. Editions change certification wording, and a model trained without them can mistake an edition difference for a difference in coverage.

Can the requiring party demand a broker letter confirming the coverage instead?

It depends on the state. New York bars requiring a certificate to include terms the policy does not contain, and Texas restricts certificates to approved forms and prohibits certain other documents. An insurance professional or counsel should confirm what may be requested for a given jurisdiction.

How should cases be split between development and held-out sets?

Split by requiring party or contract template, not by certificate. Certificates issued against the same exhibit share wording, so splitting them randomly lets a model memorize the template and inflates its score.

Sources

  • ACORD's certificate FAQ says a certificate of insurance is not a policy, does not provide, amend or extend coverage, and that liability policies typically notify only the first named insured of cancellation. Source
  • New York DFS explains that Insurance Law section 502 bars a certificate from amending, extending or altering coverage and bars requiring terms in a certificate that the policy does not contain. Source
  • A New York DFS Office of General Counsel opinion concludes that the term certificate holder is not synonymous with additional insured. Source
  • A New York DFS Office of General Counsel opinion says a certificate holder has a right to cancellation notice only when actually named in the policy or an endorsement as an additional insured. Source
  • New York DFS lists the ACORD 25 (2025/12) Certificate of Liability Insurance as approved; the form says an additional insured needs policy provisions or an endorsement and that a waiver statement on the certificate does not confer rights in place of the endorsement. Source
  • ACORD's December 2025 forms bulletin lists the ACORD 25 (2025/12) as a revised edition replacing 2016/03, with revised certification language about limits. Source
  • ACORD's August 2026 forms bulletin announces a Georgia-specific ACORD 25 GA (2026/09) that removes the limits statement from the certification paragraph after an objection from Georgia's insurance regulator. Source
  • The Texas Department of Insurance says Chapter 1811 allows only TDI-approved certificates of insurance for Texas risks, and that certain other documents about contract insurance requirements are prohibited. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies