← Resources

Certificate of Insurance (COI)

A summary document — most commonly the ACORD 25 form — issued as evidence that an insurance policy exists, listing coverage types, limits, effective dates, and the certificate holder. A COI is evidence of insurance; it does not itself create, extend, or amend coverage.

ACORD 25

The standard "Certificate of Liability Insurance" form published by ACORD, used to summarize liability coverages (general liability, auto, umbrella, workers' compensation) for a certificate holder. The most common document in COI workflows.

ACORD 101

The "Additional Remarks Schedule" — an ACORD form used to carry information that doesn't fit on the base certificate, such as extended descriptions of operations, additional insured language, or special provisions.

Certificate holder

The party a certificate is issued to — typically the organization requiring proof of insurance from a vendor, tenant, or subcontractor. The holder relies on the certificate to confirm requirements are met.

Certificate package

The full set of documents needed to verify compliance: the ACORD 25 certificate plus the endorsements (and sometimes policy pages) that substantiate what the certificate summarizes. Verifying the certificate alone is not enough — the endorsements carry the legal weight.

Endorsement

A document that amends an insurance policy's terms — adding an additional insured, waiving subrogation, or changing coverage. Common examples in COI workflows: CG 20 10 and CG 20 37 (additional insured), CG 24 04 (waiver of subrogation).

Additional insured (AI)

A party added to someone else's policy by endorsement, gaining protection under that policy. Contracts routinely require vendors to name the hiring organization as additional insured — and the requirement is only satisfied if the endorsement actually exists.

Waiver of subrogation

An agreement that an insurer gives up its right to recover a paid claim from a specified third party. Usually required by contract and supported by endorsement. Read our full guide →

Primary & non-contributory

Contract wording requiring that the vendor's policy pays first (primary) and doesn't seek contribution from the certificate holder's own insurance (non-contributory). Verified via endorsement or policy language, not just a checkbox on the certificate.

Requirement set

In Brokermatic, the versioned definition of what a compliant certificate package must show for a given vendor, contract, or program: coverage types, minimum limits, required endorsements, carrier rating floors, and expiration rules. Every verification runs against a frozen snapshot of its requirement set, so decisions stay explainable over time.

Verification

The line-by-line comparison of an extracted certificate package against a requirement set — limits met, endorsements present, dates current, carriers acceptable — producing a compliant / non-compliant decision with an audit log.

Exception

Any verification result that can't be resolved automatically: a deficient limit, a missing endorsement, a low-confidence extraction, or an expiring policy. Exceptions route to a human review queue instead of failing silently.

Renewal tracking

Monitoring policy expiration dates across a vendor population and opening renewal requests before coverage lapses — the difference between finding a gap proactively and discovering it at claim time.

Decision log

Brokermatic's immutable record of every verification and agent action: the objective, inputs, outputs, guardrail results, and the requirement-set snapshot the decision was judged against. What makes "prove it" a query instead of a fire drill.

Governed agent

An AI agent operating under an explicit contract: defined scope, allowed tools, and approval boundaries, with guardrail checks before external actions and escalation to humans for high-stakes decisions. Supervised, not autonomous. Meet the agents →

Connector / Collector

Brokermatic's two ingestion primitives: connectors govern access to structured systems (APIs, AMS platforms, ERPs); collectors gather documents from unstructured sources (inbound email, file drops, S3, scheduled pulls). See integrations →

See these terms in action.

Watch a real certificate package get extracted, verified, and logged — on your own requirements.

Book a demo