You collected certificates of insurance when you onboarded your trades. That was two years ago. Policies expire quietly, and nothing in your workflow tells you when one does.
If an uninsured contractor is hurt on your site, the exposure lands on you. The information is sitting in your vendor records the whole time, but nobody is going to open forty company profiles one by one to check dates.
Your assistant pulls your company records and checks the insurance fields on each one, flagging anything expired, expiring soon, or missing entirely.
It then cross references that against how much you have actually paid each vendor, so the list comes back ranked by exposure rather than alphabetically. A lapsed policy on your biggest trade partner is a different problem from a lapsed policy on someone you used once.
What it will do, if you ask: once you have collected an updated certificate, it can write the new expiration date back to the vendor record for you. It will always show you the change before making it, and it only touches the records you approve.
What it will not do: it never edits a record without showing you first, and it cannot verify a policy is genuinely in force, only what is stored in FlipperForce.
Please audit the insurance status of the companies in my FlipperForce workspace.
1. Pull my company records and check the workers compensation and general liability fields on each
2. Flag anything expired, expiring within 60 days, or missing a date entirely
3. Flag any record where the insurance flag and the expiration date contradict each other
4. Pull expense line items for [PROJECT NAMES, or say: my active projects] and total what I have paid each company
5. Rank the flagged vendors by total spend
Give me a table with vendor, insurance status, expiration date and total paid. Change nothing.
Company records are now writable through the Public API, so this automation can go one step further than reporting. After you have chased a new certificate of insurance, you can ask your assistant to update the vendor's record with the new expiration date rather than editing it by hand in the app. Because that is a write to an existing record, review each change before you approve it.
This prompt requires a connection to the FlipperForce Public API. Once your AI agent is connected to your account, you can run any prompt in the library.
Learn how to connect your AI agent to the FlipperForce Public API
This checks what is stored in FlipperForce, not what is true. A vendor with a current policy you never recorded will show as missing. Treat the output as a list to chase, not a verdict.
Some records carry an insurance flag set to false alongside a populated expiration date. The prompt asks for these to be flagged separately, because they usually mean the record was half updated at some point.