Agency process guide
Copy / share
For AI agents
How to Handle Certificate of Insurance Requests: A Step-by-Step Guide for CSRs
It’s Thursday afternoon. A contractor client forwards an email from a property manager: they need a certificate of insurance by Friday, with their company named as additional insured and 30 days’ notice of cancellation. You can see the general liability limit on the declarations page. You can’t find the endorsement. The pressure is to send something. The right move is to send exactly what the policy supports, plus a clear status on everything else. A certificate reports coverage; it can’t create it. So check each requested item against current policy documents, put only the supported entries on the certificate, hold the rest as named open items for an authorized reviewer, and keep a record of what went out, who approved it, and who received it. This guide covers the full process, from intake to delivery, for routine requests and harder ones like this. You’ll get a worked example, a decision table for each requested item, guidance on the requests that need extra care, and how state certificate laws apply. The last section shows the same process automated with Decla, which pulls the policy documents from your AMS, checks each requested item against the coverages and endorsements, and drafts the certificate for what’s supported so your time goes to review - not to hunting down the dec page and every endorsement.
By Isaiah Hall · Published · Updated
Start with one agency workflow
Try Decla
Start a free trial and pick a practical workflow your team handles every week as your first step with Decla.
Try Decla freeOn this page
- What a certificate can and can’t do
- The process, step by step
- Deciding each requested item
- Worked example: the deadline doesn’t change the evidence
- Requests that need extra care
- When the holder rejects the certificate
- Correcting an issued certificate
- State certificate laws
- Spend your time on the review, not the retrieval
- Sources and form access
- Related pages
What a certificate can and can’t do
A certificate of insurance is a summary. It tells the holder what coverage the insured has on the day it’s issued, and nothing more. The standard ACORD 25 form says this on its face: the certificate is issued for information only, gives the holder no rights, and doesn’t change the coverage of the policies it lists.
That one rule settles most hard requests. If a holder wants to be an additional insured, the right has to come from the policy itself, through a policy provision or an endorsement. Writing “additional insured” on the certificate doesn’t create it. The same goes for a waiver of subrogation, primary and noncontributory wording, or a promise of 30 days’ notice before cancellation. The certificate can report these when the policy provides them. It can’t supply them when the policy doesn’t.
So a certificate can:
- Show the insurer, policy numbers, policy periods, lines and limits that the policy documents support
- Report additional-insured status, waivers and notice terms that an endorsement or policy provision actually provides
- Give the holder a quick, standard way to confirm coverage exists
A certificate can’t:
- Add coverage, rights or holders the policy doesn’t include
- Promise that the coverage meets the holder’s contract requirements
- Override the policy when the two disagree
Two practical points follow. First, use the certificate form your agency is authorized to use for the risk, in the edition required where the risk is located. The ACORD 25 linked in this guide is a reference copy. Second, a filled-in form is a draft, whether a person typed it or software generated it. It becomes a certificate when someone with issuing authority has checked it against the policy and released it under your agency’s procedures.
The process, step by step
Most certificate requests take a few minutes. The ones that go wrong usually skip something small: the wrong entity copied from last year’s certificate, an endorsement assumed to apply, a PDF sent but never logged. These eight steps prevent that.
Open a request note
Attach the original email or portal request to the insured’s account. Record the exact insured, the holder and where the certificate should go, the job, location and deadline, every requirement the holder listed, and who’s reviewing and issuing. Treat the requirements as asks to check, not facts about the coverage.
Match the insured and the job
Confirm the legal entity, holder and work dates match the account. If the request names a different entity or the location is unclear, ask before copying anything into a certificate. When a request arrives as a forwarded chain, confirm the recipient directly rather than trusting the last email in it.
Pull the current policy documents
Get the current declarations and every endorsement that bears on the request, and note the policy periods. An endorsement already on file still needs checking: confirm it’s current and that it actually covers this holder and this job. Use last year’s certificate only to find documents, never as a source for wording or dates.
Sort each requested item
Check each requested item against the documents and mark it supported, missing evidence, or needs review. A requirement sheet isn’t a policy document, and a missing endorsement isn’t proof the right exists. Send anything that needs interpretation, or would need a policy change, to your reviewer.
Prepare only what’s supported
Use the form and edition your agency is authorized to use for the risk. Fill in the supported entries and leave everything else off, keeping unsupported asks in the request note. Don’t edit the form’s disclaimer language to make a request fit.
Review before release
Compare the finished certificate with the source documents: insured, holder, insurer, policy numbers, dates, lines, limits, description and any checked boxes. Confirm the person releasing it has the authority to issue.
Deliver and update the record
Send the approved certificate to the confirmed recipient. Then check what your AMS actually saved: attaching the PDF to the account isn’t the same as updating the certificate and holder record your AMS uses for reissues and holder lists. If only the file saved, log the record update as an open item.
Close it so anyone can pick it up
Save the final certificate, the documents it relied on, who reviewed it, who issued it, who received it and when. Log a bounced email, portal rejection or unanswered follow-up as open. The test: could a coworker reconstruct what was asked, what supported the answer and what went out?
- Download the free COI request toolkit
A pre-issue checklist, an endorsement cheat sheet and client reply templates in one Excel file.
Deciding each requested item
Sort item by item, not request by request. Most requests mix supported items with open ones, and each gets its own next step.
| What you find | Next action | Record to retain |
|---|---|---|
| The policy documents support it | Put it on the certificate and send it for review. | The document it came from. |
| An endorsement, policy document or recipient detail is missing | Hold that item and get the missing piece. | What’s missing, who’s getting it, and the follow-up date. |
| The holder wants rights or wording the policy doesn’t provide | Send it to your reviewer. If it needs a policy change, track that as a separate request. | The ask and your reviewer’s decision. |
| The holder rejects the certificate and wants different wording | Get the exact objection in writing and send it for review. Don’t reword to get it accepted. | The original certificate, the objection, and any approved revision. |
Worked example: the deadline doesn’t change the evidence
Back to Thursday. Sample Mechanical LLC, a contractor, needs a liability certificate for Sample Property LLC’s maintenance project by Friday. The holder asks for a $1 million general liability occurrence limit, additional-insured status and 30 days’ notice of cancellation. You have the current declarations page. You don’t have the endorsements.
| Requested item | What you have | Status and next step |
|---|---|---|
| Insured and holder | Both named in the request; the holder’s mailing address isn’t confirmed | Missing: confirm the recipient |
| $1M occurrence limit | Current declarations show the limit and policy period | Supported: prepare the entry for review |
| Additional insured | No endorsement or policy provision retrieved | Missing: get the endorsement before showing it |
| 30 days’ notice of cancellation | No notice provision retrieved | Needs review: get the provision, then your reviewer’s call |
So on Thursday evening, nothing goes out yet. The request note reads: “Current dec page retrieved. Additional insured and cancellation notice pending endorsement review. Holder address unconfirmed. Reviewer assigned; follow up Friday morning.”
The reply to the client: “We have your certificate request. We’re confirming the holder’s details and checking the additional-insured and cancellation-notice requests against the policy. We’ll update you Friday.”
That reply is honest about where things stand without promising a certificate or promising the coverage meets the contract. From there, one of three things happens. The endorsement turns up and supports the request, so you prepare the full certificate. The policy needs a change, so that goes to your reviewer as its own request. Or the request can’t be supported, and you tell the client exactly which item is the problem.
Requests that need extra care
These four asks show up on most contractor requests, and they’re where certificates most often get ahead of the policy. Each one has to come from the policy before it can go on the certificate.
| The request | What it means | What has to exist first |
|---|---|---|
| Additional insured | The holder is covered under the insured’s policy for claims arising from the insured’s work. | An additional-insured endorsement, blanket or scheduled, that covers this holder. Blanket endorsements usually depend on a written contract, so check that one exists. |
| Waiver of subrogation | The insurer gives up its right to recover a paid claim from the holder. | A waiver of subrogation endorsement or policy provision that applies to this holder. |
| Primary and noncontributory | The insured’s policy pays first and doesn’t ask the holder’s own insurance to share the loss. | Policy language or an endorsement that says so for this holder. |
| Notice of cancellation | The holder is told before the policy cancels. | A notice provision or endorsement. Without one, the certificate can’t promise notice. |
When the holder rejects the certificate
Get the exact objection in writing and send it to your reviewer. Rewording a certificate to get it accepted is how unsupported language ends up on one. Keep the original, the objection and any approved revision together.
Correcting an issued certificate
Keep the original and note why it changed. Recheck the affected entries, give the correction the same review as a new certificate, send it through the same channel, and say which version it replaces.
State certificate laws
More than 20 states have laws on certificates of insurance, most based on a model act from the National Council of Insurance Legislators. The details vary, but the core rules match this process: a certificate can’t misstate the policy, can’t add coverage or rights, and can’t promise the policy meets a contract’s requirements. In those states, holding unsupported items isn’t just good practice. It’s the law.
Some states go further. Texas is the best-known example. For risks located in Texas, the certificate has to be on a form the Texas Department of Insurance has approved, wherever the holder is. Texas also limits notice wording to what the policy or endorsement actually provides, and its guidance doesn’t let you name a holder as additional insured based on a blanket endorsement alone.
The rule that matters: follow the rules where the risk is located, not where the holder is. The NAIC directory linked below lists every state insurance department. When a request involves a state you don’t know well, send the question to your reviewer and keep the deadline visible while it’s open.
Spend your time on the review, not the retrieval
Look back at the eight steps. Most of the time goes into steps 3 and 4: finding the current dec page, tracking down every endorsement, and checking each requested item against them. The judgment calls are the part that actually needs your experience, and they’re usually the part that gets rushed.
Decla handles the retrieval and checking, so your team can focus on the review. Nothing goes out without a person signing off: Decla drafts, your team decides. For each request, Decla:
- Pulls the current policy and endorsements from your AMS
- Checks each requested item against the coverages and endorsements, and marks what’s supported and what’s open
- Flags gaps between the holder’s requirements and the policy, so your reviewer starts from a short list
- Researches certificate rules in the risk’s state and points your reviewer to the regulator’s own guidance
- Drafts the certificate for what’s supported, ready for review
- Start a free trial
Run your next certificate request through Decla.
Sources and form access
- ACORD 25 (2025/12), hosted by New York DFS
Reference copy. Check the edition required where the risk is located.
- Texas Department of Insurance certificate FAQ
Texas rules on approved certificate forms and notice wording.
- NCOIL Certificates of Insurance Model Act
The model law many state certificate statutes are based on.
- NAIC directory of state insurance departments
Find the regulator for the state where the risk is located.
- Official ACORD Forms Portal
Form access through login. Use your agency’s authorized form source.