Every value, COPE record, finding and report in 21RISK hangs off a site. Keep the register current in one place — hierarchy, groups, custom columns, map and history — and every suite reads the same list.
The insurance schedule, the audit plan, the SAP export and the broker’s spreadsheet all name the same sites — each slightly differently.
"Aalborg plant", "Aalborg Production A/S" and "DK-AAL-01" are one site on three lists. Nobody merges them until renewal.
Which sites roll up to which division is known, not written down — so regional totals get rebuilt by hand every time.
A sold plant stays on the schedule for two more renewals, because deleting it would lose its history.
A site is created once and placed in the hierarchy. Every insurance and safety workflow picks it up from there.
Bulk import the list you already have, or add sites one by one. Names are unique, and an address puts the site on the map.
Global › Europe › Germany › Munich for structure. "All warehouses" or "Critical facilities" for scopes you reuse across boards.
Values, COPE information, NatCat scores, findings and actions attach to the site — one list, read by every board, the API and your AI.
| Site | SAP code | Area | Groups | Status |
|---|---|---|---|---|
| Europe | active | |||
| └Aalborg plant | DK-AAL-01 | 18,400 m² | Production · Critical | active |
| └Hamburg DC | DE-HAM-04 | 42,000 m² | Warehouses | active |
| └Lyon plant | FR-LYO-02 | 11,900 m² | Production | active |
| North America | active | |||
| └Toronto plant | CA-TOR-01 | 9,300 m² | Production | active |
| └Detroit warehouse | US-DET-03 | 7,100 m² | Warehouses | inactive |
Parent–child sites, so Global › Europe › Germany › Munich rolls up in reports and access. Move a parent and its children move with it.
"All warehouses", "Nordic sites", "Fire safety program" — create a group once and put it on any board, instead of picking the same 40 sites again.
SAP code, floor area, priority, inspection date — add the columns your organisation runs on and edit them straight in the table.
Drag a marker to the correct spot; 21RISK reverse-geocodes it and shows a before/after so the address stays right. Proximity analysis flags sites within 5 km of each other — accumulation risk, or a duplicate.
Name, address, status and custom-field edits are versioned with who changed what, and when — the audit trail an underwriter asks for.
A sold or closed plant goes inactive: gone from dropdowns, history kept, and it can be reactivated when needed. Permanent deletion needs a group owner and two-factor authentication.
The same site record carries the insurance and safety work — so the register you maintain here is the one your broker, your auditors and your AI assistant read.
Insured values are requested and answered per site — the register decides who gets asked.
Learn more → COPEConstruction, occupancy, protection and exposure documented on the site itself, next to its engineering reports.
Learn more → NATCATMunich Re hazard scores are computed from the site’s coordinates — a correct pin is a correct score.
Learn more → FINDINGSAudit findings and follow-up actions land on the site where they were found.
Learn more → REST APICreate, update and query sites programmatically — keep the register in sync with the systems that own it.
Learn more → MCP SERVER"Which sites in Germany have no sprinklers?" — answered from the same list, through any assistant.
Learn more →Anything you track work against: a factory, warehouse, office or store — or an organisational level such as a country, division or supplier group. The Sites area holds them all in one hierarchy.
Yes. Bulk import thousands of sites with their hierarchy and custom columns from an Excel template, then keep the register current in the table, over the REST API, or through the MCP server from your AI assistant.
Hierarchy for structure that rarely changes: country › region › facility. Groups for reusable scopes that cut across it — all warehouses, or every site in a fire safety program. Most teams use both.
Set it inactive. It disappears from dropdowns and current-work views, while its values, audits and reports stay on record. It can be reactivated later, and only a group owner with two-factor authentication can delete it for good.
Every member can look up every site. Site access — granted per user, user group or AI agent — decides where they can enter values, answer audits or close findings.
Bring the list you have today. We will show you how insurance and safety hang off it.