September 2026 - Requirement Categories Redesign

Setting up a requirement category has meant configuring policies in one place and terms in another, with little to tell you which provision belonged to which policy — or whether a term was an ACORD checkbox, Description of Operations language, or an endorsement. Endorsements sat in a separate experience again. Requirement Categories has been redesigned around the policy: open a category, click a policy, and the page shows that policy and every term attached to it. On top of that, you can now build custom requirements of your own and control how RiskBot reads them.

Here's what you can do

• Work one policy at a time. The category page lists its policies. Click one and the page focuses on that policy and all of its terms, and you can toggle between policies to configure each in turn.
• See terms grouped by policy — limits, the ACORD checkboxes, additional insured and Description of Operations language, other Description of Operations language, other requirements, endorsements, and terms that live in the policy pages rather than on the COI.
• Find endorsements inside the policy they belong to, instead of in a separate screen, so you can see exactly which endorsements you're tracking per policy.
• Add a policy to a category directly from the category page.
• Create custom requirements. Write your own term on a policy — for example, that the location name has to appear in the Description of Operations.
• Choose whether a new requirement applies to existing records. When you add a requirement to a category that's already in use, you decide whether it affects only records going forward or all existing ones. Previously, any change re-evaluated every record, and a mostly-compliant portfolio could go non-compliant overnight.
• Tell RiskBot what to check, in plain language. Write the prompt RiskBot uses to review your custom term, and insert variables — the location name, for instance — so the instruction combines fixed wording with values from the record. RiskBot then accepts any wording that satisfies the instruction, rather than an exact letter-for-letter match.
• Set how each term is worded to vendors. Per term, configure how it reads in automated email notices, on the sample certificate of insurance the vendor receives, and in the flag raised when a vendor uploads a COI that misses it. Variables work in all three.
• See which terms RiskBot reviews. Each term carries an icon showing whether RiskBot reviews it automatically or it's a manual term. When a submission comes in on a category with manual terms, the system prompts your team to answer those questions.
• Check your automation level in RiskBot Insights, which shows how much of the category as configured is reviewed automatically.
• Preview your requirements on a mock COI — a rendering of how they'll display on a certificate, using the same template vendors receive in email communications.

The practical effect is that a requirement category is now readable. You can look at a policy and see what's being asked for, where it has to appear, and who or what checks it — and where the standard terms don't cover your case, you can write the term yourself instead of working around it.

If you're on a full-service account, our team configures your requirement categories for you — these tools are what we're now using on your behalf, and your account manager can walk you through what's set up.

Available to hiring company users on self-service accounts. Which terms RiskBot reviews automatically depends on your plan — if you want a manual term automated, contact your account manager.

Learn more about Requirement Categories →