A certificate checklist for service teams

Why a checklist, and not memory

Experienced service staff can produce a certificate in a few minutes. The risk is not that they do not know how; it is that the same five or six details have to be right every single time, on a busy day, often with the email thread and three systems open. A short written checklist turns judgment into routine, makes it possible for a second person to check the work quickly, and gives you a record of what was looked at if a certificate is ever questioned.

The certificate itself says it is issued as a matter of information only and confers no rights on the holder. That wording does not stop a holder, a court or a carrier from asking why the agency issued a document that did not match the policy. The checklist is what lets you answer that question.

Before you start

• Read the whole email thread. Special wording, a second holder or a deadline can be anywhere in it, including in a forwarded message at the bottom.
• Open every attachment. A sample certificate or a contract excerpt usually shows the exact holder name, address and wording the holder expects.
• Confirm the requester is the insured, the insured's authorized contact, or your own account manager. A request from an unknown address is a reason to pause, not to send.
• Note the deadline. If it cannot be met, say so early rather than rushing the checks.

Check the record, not the last certificate

• The insured's legal name on the certificate matches the named insured on the policy, including any DBA.
• Every policy shown is in force on the date of issue. A renewal that has not been bound yet is not in force.
• Policy numbers, effective and expiry dates come from the current policy record, not from a previous certificate.
• Limits and coverages match the policy as it is today. Limits change at renewal more often than people remember.
• The producer details, the insurer names and NAIC numbers, and the insurer letters (A, B, C and so on) line up with the right coverage lines.
• The authorized representative signature is one your agency allows on certificates.

Check the holder and the wording

• Holder name and address are exactly as requested, spelled the way the holder spelled them.
• Additional insured is marked only on the policies where an endorsement actually provides it, and only for the holder and operations it covers.
• Waiver of subrogation is marked only where the policy or an endorsement provides it. A sample that asks for it does not create it.
• The description of operations describes; it does not promise coverage the policy does not give. Long wording goes on an additional remarks schedule rather than being squeezed in.
• The cancellation wording is the standard wording on the form. Changing it can create an obligation the carrier never agreed to.
• Check whether the holder is already on the insured's holder list, so the certificate can be reissued automatically at renewal.

Before it goes out

• A second person looks at it wherever your procedures say so, and the person who prepared it is not the one who approves it.
• The PDF is named so it can be found later: insured, holder and date.
• The reply goes to the requester, in the same email thread, with the PDF attached and nothing else.
• The activity is logged against the insured in your agency management system (AMS), and the request email is filed as complete.

Where software helps, and where it should not

Software is good at the mechanical half of this list: finding the customer and the policy, pulling producer, insurer, limit and date values from the record instead of from memory, reading the holder and wording off a sample, and refusing to continue when a policy has lapsed or the requester is not on file. It is not the right place for the judgment half: deciding whether a contract's insurance requirements are actually met, or whether unusual wording belongs on a certificate at all.

Shlix IBS runs the same checks on every certificate it drafts, records where each value came from, and stops for a person when a check fails. The approval stays with your licensed staff.

Common mistakes and what they cost

Each of these is a common route to an errors-and-omissions (E&O) problem. None of it is legal advice; follow your carriers' rules and your agency's procedures.

• Copying last month's certificate. Old limits or dates go out after a renewal. If a claim is denied, the holder may say it relied on the certificate, and the agency's file shows it did not check the record.
• Marking additional insured because the holder asked. The certificate shows coverage the policy does not provide. This is one of the most common sources of certificate-related E&O claims and disputes.
• Editing the cancellation wording. Promising notice the carrier does not give can leave the agency, not the carrier, holding the obligation.
• Sending to an unverified requester. Policy details go to someone with no right to them, which is a privacy problem as well as an E&O one.
• No record of who checked what. When a certificate is questioned months later, there is nothing to show the agency acted carefully.

Questions