Requirement Categories

Availability: Hiring Company accounts (Self-Service). On Full-Service accounts, requirement categories are configured by the BCS team.

A requirement category defines what a vendor or tenant has to carry to be considered compliant — policies, limits, endorsements and documents. This article walks through the requirement editor. 📋

A note on labels: this article says "assignment" and "location." If your account renames these to Jobs, Leases, Projects, Properties or something else, everything below works the same under your own labels.

1. Find your categories

Go to Module Settings → Requirements (or the gear icon → Requirements under Insurance Tracking).
Choose Vendors or Tenants at the top — each has its own categories.
The top of the page sets two account-wide options: whether certificate holder and additional insured come from a Global Requirement or are Location-Specific, and whether categories are selected Manually or Automatically.
Your categories are listed under Requirements Categories. Click one to open it, click Add Category to start a new one, or use Set up with RiskBot to build a category from a contract or requirements document. 🤖

2. Category details and policies

Each category has a Category Name, a Description and a Minimum AM Best rating (strength and size). Certificate holder and additional insured names come from the location on each assignment — edit those in Locations.

Under Policies & Limits, each policy card shows how many limits, provisions and endorsements it carries. Click Edit requirements to configure a policy, or Add Policy to add one. The icons down the left side switch between policies.

3. Configure a policy

Inside a policy, the sections on the left group everything the policy must show:

Section	What it covers
Limits	Minimum limits (each occurrence, aggregate…), verified from the COI limits fields, plus the policy's Deficiency Severity
Checkbox	The standard ACORD checkboxes
Additional Insured Entities	Additional insured status for the location's entities
Description of Operations	Wording that must appear in the Description of Operations box
Other Requirements	Anything else on the policy
Endorsements	Endorsements tracked for this policy, verified from scheduled or blanket endorsement forms
Policy page review	Terms only the policy document itself can prove, such as exclusions

Terms marked SYSTEM are built in; terms marked CUSTOM are your own. The RiskBot badge on a term means RiskBot reviews it automatically; the person icon means your team reviews it by hand.

4. Add a custom requirement

In the policy, open the section the requirement belongs to — for example Description of Operations.
Click + Add custom … requirement and describe it.
Choose whether it applies to new records only or to all records. Applying to new records only lets you tighten a category without reopening work that's already closed; apply to all records when you genuinely need it evidenced on existing vendors.
Write the RiskBot prompt — a plain-language instruction such as Make sure that [location name] is mentioned in the Description of Operations. Use variables (like the location name) wherever the value differs by record. RiskBot accepts any wording that satisfies the instruction.
Save.

5. Notice settings

Each term can be worded separately for the automated email notices, the sample certificate of insurance the vendor passes to their agent, and the upload flag shown when a COI misses the requirement. Write these for the agent who has to reissue the certificate. ✍️

6. Check coverage and preview

RiskBot Insights shows what share of the category's requirements are auto-reviewed, which policies are all automatic, and which terms your team reviews manually. Which terms RiskBot can review automatically depends on your plan.
Preview COI template renders a mock certificate using the category's current requirements — the same template vendors receive — so you can check what their agent will be asked to produce. 👀

Tips

💡 Preview before you apply a category to live assignments.
💡 Default to new records only when tightening an existing category.
💡 Keep each RiskBot prompt to a single, checkable statement — split bundled conditions into separate terms.
💡 Check RiskBot Insights after each round of edits.
💡 Need one assignment to differ from its category? See Edit Requirements for One Assignment.

Full-Service clients

On Full-Service accounts, requirement categories are configured by the BCS team. Reach out to your Customer Success Manager or email customersupport@getbcs.com for changes. 📬