Certificate of insurance request

How do we issue a certificate of insurance when an insured or broker asks, with the holder's requirements checked against the actual coverage so the certificate never says more than the policy does?

Issue the certificate from the policy, not from the request. Callvu prefills the certificate from the policies in force (the forms, limits, endorsements and dates), takes the holder's details and the requirements the holder sent (additional insured, waiver of subrogation, primary and non-contributory, notice of cancellation) on the requester's screen, checks each requirement against the policy's endorsements and limits, decides by rule where the coverage supports the request, routes a request the policy does not support to the underwriter or the agency's licensed staff in the Decision Desk with the option to endorse, and issues and logs the certificate with the holder in the policy system.

In scopeSimpleCallvu moves: prefill, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The certificate promised primary and non-contributory coverage the policy did not carry, and the general contractor relied on it at the claim.

Today, without Callvu

A subcontractor needs a certificate for a job tomorrow. The agency's assistant types what the general contractor's requirements say into the certificate form, because that is what gets the certificate accepted. The policy does not carry the endorsement. At the claim, the certificate is the document everyone holds up, and the state's unfair trade practice law and the certificate statute are the ones that apply.

Certificates of insurance are regulated in most states: a certificate may not confer rights beyond the policy, may not amend or extend coverage, must use an approved form, and issuing a false or misleading certificate is a violation. The holder's requirements can only be met by what is actually endorsed on the policy. The check is a comparison between the request and the policy data, which exists.

A certificate that is issued from the policy is accurate by construction, and a requirement the policy does not meet is an endorsement request, not a typing choice.

How it runs

From the requestto the system of record.

An insured, a broker or a certificate holder requests a certificate, through the portal, an email, a call or an AI agent. Callvu opens the request from the insured's policies.

Insured or broker: Enters the holder and the requirements, uploads the holder's request where there is one, and receives the certificate.
Underwriter or licensed agency staff: Decides requests the policy does not support in the Decision Desk.
Callvu: Prefills, checks the requirements against the policy, decides by rule, routes exceptions, issues and logs.

Prefill from the policies
The policies in force for the insured (general liability, auto, workers compensation, umbrella, property) are prefilled with the forms, limits, endorsements and effective dates from the policy system; the requester's identity and authority to request are checked.
Take the holder and the requirements
The holder's name and address, the description of operations or the project, and the requirements (additional insured and the form, waiver of subrogation, primary and non-contributory, notice of cancellation, limits) are entered on the requester's screen or read from the holder's uploaded request.
Check and decide
Each requirement is checked against the policy: the additional insured endorsement and its form, the waiver endorsement, the primary and non-contributory wording, the limits against the requested limits, the cancellation notice provision; a request the policy supports is issued by rule on the approved form with only the policy's terms; a request it does not support goes to the underwriter or the licensed staff in the Decision Desk with the gap and only issue the certificate as the policy reads, endorse the policy and then issue, or decline with the reason.
Issue and write back
The certificate is issued on the state's approved form with the disclaimer, delivered to the holder and the requester, and logged in the policy system as the system of record with the holder, the requirements asserted and the person who requested it; holders needing notice of cancellation are recorded for the cancellation process.

Where it ends: Every certificate states exactly what the policy provides, requirements the policy does not meet were handled as endorsement decisions, and the policy system holds the holder and the certificate for the cancellation notices and the claim. The Decision Trace shows each requirement's check and any decision; the Audit Trace shows the request, the issue and the delivery.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

State certificate of insurance statutes and regulations (NCOIL Certificates of Insurance Model Act as adopted): A certificate of insurance may not amend, extend or alter the coverage of the policy, may not confer rights on the holder beyond the policy, must be on a form approved or not prohibited by the state, and a person may not prepare, issue or request a certificate that contains false or misleading information or that purports to affirmatively or negatively amend the policy; violations are unfair trade practices subject to the state's penalties.
ACORD certificate forms (ACORD 25 liability, ACORD 24 property, ACORD 28 evidence of property) and the state's approved forms: The standard forms carry the disclaimer that the certificate is issued as a matter of information only and confers no rights, and the fields map to policy data (forms, limits, endorsements, dates) that must be taken from the policy.
Policy endorsements that satisfy holder requirements (additional insured forms such as CG 20 10 and CG 20 37, waiver of subrogation, primary and non-contributory wording, notice of cancellation to designated persons): A holder's requirement is met only by the corresponding endorsement on the policy; the check compares the requirement to the endorsement schedule, and an absent endorsement is an underwriting request with a premium and an approval.

Company policies

Certificates are prefilled from the policy system and state only the policy's terms; nothing is typed from the holder's requirements.
A requirement the policy does not support is an endorsement decision for a person with authority, never a certificate wording choice.
Every certificate is logged with the holder, so cancellation notices and claims can find it.
The policy system is the system of record for the certificate and the holders.

Controls

Prefill of forms, limits, endorsements and dates from the policy system.
Requester authority check.
Requirement-by-requirement comparison with the endorsement schedule.
Rule-based issue on the approved form.
Decision Desk for unsupported requirements.
Certificate and holder log for cancellation notices.

Clocks and deadlines

Issue: Immediately when the policy supports the request; the carrier's same-day service level for a Decision Desk exception.
Notice of cancellation to holders: Where the policy carries a designated-person notice endorsement, the holder log drives the notice on the endorsement's days.

Documents and checks

The policies in force and their endorsement schedules
The holder's request and requirements
The requirement checks
Any endorsement decision
The issued certificate and the holder log in the policy system

In the Decision Trace

Each requirement and whether the policy supports it.
Any endorsement decision and the person.

In the Audit Trace

The request with the requester and time.
The issue and delivery.
The holder log entry.

The handoff

Between the front doorand the back office.

The front door

The insured's or broker's portal, an email, a call or an AI agent; the requester enters the holder and uploads the requirements.

The back office

Underwriters or licensed staff see only requests the policy does not support, as endorsement decisions; nobody types certificates.

The Decision Desk

A requirement the policy does not support goes to the underwriter or the licensed agency staff in the Decision Desk with the gap and only issue as the policy reads, endorse then issue, or decline with the reason.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

Phoenix put more than 100 processes live in under 3 months.

Across Callvu customers

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Questions

What buyers ask next,answered plainly.

Can the certificate say what the holder requires?

Only where the policy actually carries the endorsement or limit; the check compares each requirement to the policy, and an unsupported one becomes an endorsement decision.

Who can approve adding an endorsement for a holder?

The underwriter or licensed agency staff with authority, in the Decision Desk, with the gap and the premium in front of them.

Why log the holder?

So that a cancellation notice endorsement can be honored and a claim can find what was certified, from the policy system.

Related processes

Small business owner policy purchase Policy changes and endorsements Proof of insurance and ID cards Workers compensation new business Try it in the sandbox All insurance processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.