Sites, risk improvements, findings, claims and compliance questions all sit in the same kind of table. Add custom fields for the data your organisation tracks, save the worklists you open every week, and share them with your team.
When the system can’t hold your fields or remember your filters, the real work moves back into a spreadsheet beside it.
Everyone filters their own copy of the improvement list, so the numbers in Monday’s meeting depend on whose file is on screen.
SAP plant code, key exposures, certificate expiry: the fields your organisation runs on sit in a side spreadsheet nobody keeps in step.
How many are still open, and what will they cost? Someone filters, sums and pastes the answer into an email.
Fields belong to the table. Views decide how a team looks at it. Both are managed in one place.
Open Manage table and create a custom field: select, multi select, number, text, date, or an ID that must be unique.
Choose the fields, their order and width, the sorting and the filters, and save them as a view. New views are private to you.
Make the view public and everyone who can open the table works from the same setup. Filter by “Me”, and each colleague sees their own items.
| # | Risk improvement | Key exposures custom | Status | Cost estimate |
|---|---|---|---|---|
| 112 | Repair sprinkler riser valve Lyon plant | Fire | In progress | €18,500 |
| 118 | Raise transformer above flood level Hamburg DC | Flood | Quote received | €42,000 |
| 131 | Separate battery charging area Aalborg plant | FireBI | To do | €9,800 |
| 3 items | €70,300 |
Every view tab carries a label, so you always know who else sees it. A view never changes what someone can access: it only decides how the table is laid out.
Views that come with 21RISK, for everyone who can open the table. A good start before anyone has set anything up.
One setup the whole team works from, such as “My overdue” filtered by “Me”, so it shows every colleague their own items. Owners and board managers decide which views are shared.
Your own worklists, which nobody else sees. Start blank or copy the table as it looks now. An owner or board manager can make it public when the team needs it too.
The order of your view tabs is personal: rearrange them without changing anyone else’s table.
Overdue improvements, unanswered questions, sites due an inspection: save each one as a view tab, with its fields, sorting and filters.
Add custom fields to sites, reports, actions, findings, questions, risk improvements and claims. Multi select keeps everyone on the same terms.
Filter any person column by “Me” and save it. One shared view shows every colleague the items they are responsible for.
Findings, claims, risk improvements and compliance questions have a totals row: how the filtered items split across statuses, next to the summed cost estimate.
“Finding 18” in the header, a # column to sort and filter by, and the same number in the Excel export, so everyone refers to the same item.
Export a table to Excel, CSV or JSON for the broker or the board pack. The live table stays the source.
Learn it once. The register, the improvement list, the findings and the claims all use the same fields, views and totals.
SAP codes, floor area, priority and inspection dates as custom fields on the site register.
RISK IMPROVEMENTSShared views for overdue recommendations, with the open cost estimate in the totals row.
FINDINGSA view per site or per responsible person, filtered to the findings still open.
CLAIMSNumbered claims with your own fields, and totals across the claims you have filtered.
Sites, risk improvements, findings, and the Questions and Sites tables on a Compliance board. Other tables can still be filtered and sorted.
Select, multi select, number, text, date and ID. An ID field must be unique, so it suits SAP codes, policy numbers or facility IDs that other systems match on.
No. A saved view is a table setup, not a permission. Everyone who opens it still sees only the records and fields their access allows.
Anyone can create private views. Fields, public views and built-in views are managed by organisation owners, and on a board also by people allowed to manage its settings.
Deleting a custom field removes the values stored in it. Deleting a view removes only its table setup; no data is lost.
Yes. Export a table to Excel, CSV or JSON, or read the same records over the REST API, the MCP server or direct Postgres access.
Show us the columns and worklists your team keeps on the side. We’ll show you where they go in 21RISK.