21RISK tracks risk improvement recommendations on every site you insure, wherever they come from. Each one carries an owner, a due date, a cost and the evidence that it was done.
Getting the recommendations is the easy part. Turning twenty of them, across forty sites, into work that actually happens is where the register breaks down.
The engineer writes twenty recommendations and sends a document. A document is not a worklist, and nobody can filter it.
A recommendation without a name and a deadline attached is a suggestion. Suggestions survive several renewals.
The insurer asks what happened to last year’s recommendations, and the answer is a search through email and a best guess.
Risk improvements live on the Insurance board — what was identified, who owns it, when it is due, what it costs and what evidence supports it.
From an engineering firm, your insurer or broker, an internal review, or the site team itself — registered against the site it belongs to.
Each one gets an owner, a due date, a cost estimate, and loss estimates before and after — so it can be prioritised rather than just listed.
Subtasks, files, comments and change history, so completion is something you can show an underwriter rather than assert.
Improvements created from an engineering report can protect the original name, description, loss estimates, external ID and site — so the recommendation an insurer made is still the recommendation on file.
Cost estimate alongside loss estimate before and after, so the case for a sprinkler upgrade is a figure rather than an opinion.
Files, subtasks, comments and full change history — quotes, photos and sign-off attached to the improvement they belong to.
Reduce routine follow-up with workflow automations that keep statuses current and send reminders about overdue improvements.
Open, overdue and unassigned improvements and their estimated cost, on one page. Time to close and the backlog over time come from the actual history of each improvement. Click any number to open the list behind it.
They are the changes a risk engineer asks a site to make after a survey. A sprinkler upgrade is one, and better storage of combustibles is another. Insurers, brokers and your own reviews add more. At the next renewal, the underwriter asks what happened to each one.
Every recommendation is filed on its site in one register on the Insurance board, with a responsible person and a due date. Saved views give each site manager their own list. Analytics show the open improvements by site, category and responsible person. Workflow automations can send reminders about overdue ones.
On the Enterprise plan, 21RISK reads the recommendations out of an uploaded engineering report and matches them against the improvements the site already has. You check the suggestions before anything is saved. On other plans you add the improvements from the report by hand, on the same site.
Internal reviews, insurance audits, engineering reports, risk engineers, brokers or local site teams. However a recommendation arrives, it ends up in the same follow-up register on the Insurance board.
When an improvement originates from an engineering report, fields such as the name, description, loss estimates, external ID and site can be protected, so the original recommendation stays intact. Group owners can override that protection when they need to.
Yes. The risk improvements table supports saved views, so recurring worklists — overdue, unassigned, high loss estimate, or one site, category or responsible person — are one click rather than a filter you rebuild each time.
Yes. Risk improvement analytics show what is open, overdue and unassigned today, the open estimated cost, the average and median time to close, and open improvements over time. The history comes from the changes made to each improvement, not from due dates.
An improvement can hold subtasks with their own owners, due dates and completion state — requesting quotes, approving budget, planning an outage window, installing, and collecting the evidence at the end.
Talk to us about the recommendations sitting in your last engineering report.