Who approves
Set per request type. Work that needs approval waits for an account manager, and the person who prepared it can never approve it.
From a holder's request to a checked certificate, with every value showing where it came from.
An email from a customer, an account manager or a holder asking for a certificate — often with a sample certificate attached showing the holder and the wording.
Drafted, checked and approved before it goes out
The same order every time, recorded on the task as it runs. Anything unclear stops for a person instead of being guessed.
The request, the attachments and any special wording, wherever it sits.
Matches the insured, confirms the sender is the customer's contact or account rep, and checks every policy is in force.
Producer, insurers, limits and the authorized signature come from your records, not from typing.
Holder name and address, the description of operations, and additional-insured and waiver lines per policy.
Dates, coverages, holder, signature and issue date are checked; long wording is flagged for an extra remarks page.
The reply is sent to the requester with the PDF in the original thread, and the email is filed as complete.
Set per request type. Work that needs approval waits for an account manager, and the person who prepared it can never approve it.
Every step, with what it found and where each value came from, is kept on the task and in its audit trail.
More in the how it works walk-through and the glossary.
No. Every value comes from the email, the sample certificate or your records, and a failed check stops the run for a person instead of guessing.
The run pauses with the reason — for example a lapsed policy or a requester who is not the contact on file — and the task goes to a person.