Skip to content

See Shlix IBS on sample requests first. No customer information needed. Book a walkthrough →

Workflows / Certificates of insurance

Certificates of insurance

From a holder's request to a checked certificate, with every value showing where it came from.

Drafted by Shlix6 steps · a person approves
  1. 01Read the whole thread
  2. 02Find the customer and the requester
  3. 03Load the master certificate
  4. 04Take the holder and wording off the sample
  5. 05Run the checklist
  6. 06A person approves, then it goes out
What arrivesNew request

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

What arrives, and the 6 steps behind it
[ Step by step ]

How Shlix handles certificates of insurance.

The same order every time, recorded on the task as it runs. Anything unclear stops for a person instead of being guessed.

  • From the request
  • From your AMS
  • Drafted and checked
  • Done and on record
  1. Read the whole thread

    The request, the attachments and any special wording, wherever it sits.

  2. Find the customer and the requester

    Matches the insured, confirms the sender is the customer's contact or account rep, and checks every policy is in force.

  3. Load the master certificate

    Producer, insurers, limits and the authorized signature come from your records, not from typing.

  4. Take the holder and wording off the sample

    Holder name and address, the description of operations, and additional-insured and waiver lines per policy.

  5. Run the checklist

    Dates, coverages, holder, signature and issue date are checked; long wording is flagged for an extra remarks page.

  6. A person approves, then it goes out

    The reply is sent to the requester with the PDF in the original thread, and the email is filed as complete.

[ Control ]

Who signs off, and what stays on record.

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.

What is recorded

Every step, with what it found and where each value came from, is kept on the task and in its audit trail.

[ Questions ]

About certificates of insurance.

More in the how it works walk-through and the glossary.

Does it type anything from scratch?

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.

What happens when a check fails?

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.

[ Read next ]
[ Other workflows ]

See certificates of insurance on sample data.

Book a walkthrough