Certificate of insurance automation

What you can delegate, and what stays with the agency

For a commercial-lines service or operations lead, the repeatable part of certificate work is collecting the request, tracing each entry to policy documents and preparing a draft for review. In the draft-only workflow evaluated here, the workflow prepares drafts, and named, authorized people remain responsible for policy meaning, additional-insured and notice wording, and for issuance and delivery. Responsibility does not mean every step is done by hand: whether a send or record update is automated is a separate configured decision that needs its own proof. Issuance authority, policy endorsement terms, the license to use a form and the right to write to a record are also separate questions. A prepared draft is not an issued certificate, a change to your agency management system or an insurer authorization.

Decla is an AI workforce for insurance agencies, and its public website describes COI and ACORD-form work. Run the sequence below as your own test of any provider, Decla included.

A good first scope is a repeatable liability-certificate request with identifiable sources, a named reviewer and an established issuance channel. Requests for changed coverage, unsupported rights or conflicting wording need a separate agency decision.

What starts the task and what it needs

A holder or client request starts the task. Test the workflow with:

• The request: exact insured and holder, project or operations description, deadline, recipient and requested wording.
• Policy sources: declarations, relevant policy provisions and endorsements for the applicable term.
• Agency settings: the permitted form and edition, the system that prepares or issues the certificate, and who may authorize issuance and delivery.

A previous certificate shows how an earlier request was handled. Use it to find sources, not as proof of current coverage.

Delegation boundary from request to delivery

An approval, a generated file, an issued certificate and a sent message are four separate records. Holder status, including additional-insured status, cannot be inferred from the request or the contract text.

A sample acceptance test

Run these six tests on a safe sample request. The issuance and delivery rows apply after agency review, through your established channel.

Keep policy rights and issuance authority with the agency

The regulator-hosted ACORD 25 (2025/12) says the certificate conveys information and does not change the policy’s coverage. It also ties additional-insured status to policy provisions or endorsements; certificate wording alone does not confer those rights.

Texas-specific guidance adds concrete review tests. TDI’s certificate FAQ, last updated October 31, 2022, says a blanket additional-insured endorsement does not by itself justify naming the holder as an additional insured on the certificate. Its notice guidance says the certificate cannot promise more than the policy provides. These are scoped Texas references, not a nationwide issuance rule.

Your qualified agency reviewer determines applicable requirements and whether the sources support the requested entries. Automation should preserve the question and its source, rather than silently turn a request into a coverage finding.

Ask for proof of the exact operation

The public COI description does not specify an agency management system interface, form edition or issuer for your agency. Before relying on a workflow, ask for a dated demonstration in your environment: what it reads, what it prepares or writes, where the approval boundary sits and what comes back from the system. A vendor demo, sandbox or test credential shows a test environment, not your system’s current operation.

• Record types. For each record your process touches, such as the certificate record, an attached file or the holder record, ask what can be read and written, the prerequisites, what is unsupported and the date of the current evidence.
• Certificate record or attachment. Whether saving a certificate file also updates your system’s certificate record depends on the system. Confirm it with current proof, and keep an open item if the record is not updated.
• Writes. For any write, ask for the target record, whether the change was applied or committed, the result, the acting identity and a readback of the stored value.
• Self-serve requests. An agency has asked us about self-serve certificate request links that work from the policy and additional-insured documents on file. If a client or holder request link is offered, ask how it verifies the requester, checks source endorsements and routes exceptions. Treat it as open until it is demonstrated.
• Failure cases. Include one incomplete-source case and one failure after approval. Check whether unresolved questions are preserved, whether changed inputs require fresh review, and whether a delivery retry can be distinguished from a second issuance.

For official forms, use ACORD’s Forms Portal through your agency’s authorized access. The portal requires login to download forms. Use the regulator-hosted PDF here only as a source reference.

Related guides

• How to handle certificate of insurance requests

  request intake and review steps in depth.

• COI request checklist template

  an editable worksheet for intake fields and review status.

Discuss your certificate workflow

Start with one repeatable liability-certificate request and run the six tests on it. Bring the certificate system you use, a safe sample request, the permitted form edition and your review rule. Ask which steps can be demonstrated now and which remain manual or need setup, and agree on the evidence for a completed request before deciding what to delegate.

Frequently asked questions