Certificate of insurance requests
Same-day certificates, because every request is logged, checked and teed up so your team only has to issue and send.
Hours back
2
hours a week back, typically
How it runs
What we build, step by step.
This is the usual shape. Yours gets built around how your team actually does the job.
- 01
Requests logged from the inbox
Each request is read for the client, the certificate holder, the project, and any special wording such as an interested party or waiver of subrogation.
- 02
Checked against the policy on file
If the request asks for a limit or endorsement the policy doesn't have, it's flagged before anyone issues anything.
- 03
A ready-to-issue queue
Clean requests sit in one list with every detail filled in. The handler issues the certificate in your broking system and sends it.
- 04
Repeat holders remembered
Contractors who ask for the same holder every month get it pre-filled from last time.
Shown with software we see a lot. If your team uses something else, we build it into that instead.
Built for your business
Same job, different business. We build yours.
Two firms in the same trade rarely run a job the same way. Different software, different steps, different people signing off. We build it for your business, around how your team actually does the job.
Your steps
Built around the order your team already works in, odd exceptions included.
Your software
Runs inside the tools you already pay for, set up the way you use them.
Your rules
Your wording, your limits, your sign-offs. Nothing generic goes out in your name.
You sign off
Your team keeps the final say.
A person issues every certificate. Any request for cover the policy doesn't have goes to the account manager.
What it's worth
What those hours add up to.
2 hours a week, over 46 working weeks, is 92 hours a year. At $50 an hour, that’s
$4,600
back in the business, every year.
Typical, not promised.
Before and after
The job, before and after.
How it runs today
Requests come by email from clients, head contractors and landlords, usually marked urgent. An account handler reads each one, looks up the policy, checks the holder and wording, then builds the certificate.
What we build
- Requests logged from the inbox
- Checked against the policy on file
- A ready-to-issue queue
- Repeat holders remembered
A month in
Clean requests go out the same day, and the account handler's day stops getting broken up by emails marked urgent.
FAQ
Does it issue certificates of insurance on its own?
No. It prepares each certificate request and checks it against the policy. A person issues the certificate from your broking system.
What if a certificate request asks for something we can't provide?
The request is flagged with the reason, such as a higher limit or a missing endorsement, so the account manager can talk to the client before anything is issued.
More for insurance agencies
See them all →Next step
Bring this one to a free live build.
Thirty minutes on certificate of insurance requests. We build its elf with you, live, and you keep it.