A certificate of insurance shows what a policy provides on the day it is issued. It cannot add coverage, and it cannot make anyone an additional insured. Handle every request on that basis: confirm the policy already does what the holder is asking for, build the certificate from your system, and attach the endorsement when status depends on it.
The ACORD 25 says this itself. Its disclaimer states that the certificate is issued as a matter of information only, confers no rights on the holder, and does not affirmatively or negatively amend, extend or alter the coverage. Most certificate problems come from treating the form as if it could.
Step 1: Log the request and the holder's requirements
Record who asked, who the holder is, and what their contract requires. Typical asks are additional insured status, waiver of subrogation, primary and noncontributory wording, and specific limits. Save the contract clause or the holder's sample if they sent one.
Step 2: Confirm the policies are in force
Check that every policy you are about to list is active, and note any pending cancellation. Confirming coverage on a policy that has been cancelled is one of the most common certificate errors.
Step 3: Check whether the policy already provides what is asked
For each requirement, find where the policy provides it:
- Additional insured. Is there a blanket additional insured endorsement that applies "where required by written contract", or does the holder need to be scheduled by name?
- Waiver of subrogation. Is there a blanket waiver, or a scheduled one?
- Limits. Do the policy limits meet the contract minimums?
If the policy does not already provide something, the answer is an endorsement request to the carrier, not a certificate. Send that to the account manager. The certificate waits until the endorsement is issued.
Step 4: Build the certificate from your system, not by hand
Generate the certificate from your agency management system so the named insured, carrier, policy numbers, dates and limits come from the policy record. Manual certificates are where transposed numbers and stale limits creep in.
Keep the description of operations factual. "Additional insured status applies where required by written contract, per the attached endorsement" is accurate. Promising coverage the policy does not grant is not.
Step 5: Attach endorsements where status depends on them
When additional insured or waiver status comes from an endorsement, attach a copy. It shows the holder exactly what applies and the limits and conditions that come with it. Only release what your client has approved; the policy is their confidential information.
Step 6: Record what was sent, to whom and when
Save the issued certificate, the request and any attachments to the client file. If the holder later relies on the certificate in a dispute, your record shows what you represented and why.
Where AI agents fit
Most certificate requests are routine: a known holder, a blanket endorsement, standard limits. That makes them a good match for an agent, provided the agent checks the policy rather than just filling a form. In the Agentic MSP servicing pack, the agent reads the request, checks current policy data and the forms on the policy, builds the certificate and flags anything the policy does not already provide. Non-standard wording goes to your team for approval. A certificate is billed only when it has been issued from current policy data and delivered.