Excel for insurance value collection works until the twentieth site and the third version of the file. Here is what changes when the round, the answers and the history live in one place — and where the spreadsheet still belongs.
You insure a handful of sites, and one person collects their values. Nobody asks who changed a number, or when.
You collect values from ten or more sites every renewal. Your broker wants current values, and the underwriter asks why a number moved.
Excel is good at holding numbers. Renewal is about who owes you numbers, what changed since last year and who is allowed to see them — and a file has no answer to any of it.
A workbook does not know it was sent. The "received" column is one you keep by hand, and every reminder is an email you write yourself.
Last year is a different file. A value that doubled has no author, no date and no note — so the underwriter’s question turns into an afternoon of searching old attachments.
Whoever has the file has all of it. A site cannot be limited to its own row, and a broker cannot be given current values without being sent the whole workbook.
Job by job: what the round looks like in a spreadsheet, and what it looks like in 21RISK.
| The job | In Excel | In 21RISK |
|---|---|---|
| Asking the sites | One workbook per site, or one shared file that everyone edits at once. | Open the new period. Every site updates last year’s values in its own form. |
| Knowing who has answered | A column you update by hand, and reminder emails you write. | Review progress per site. You see which sites have not reviewed their values yet, without asking. |
| Photos and valuation reports | Separate email threads, filed by whoever remembers to. | Attached to the site’s answer, next to the numbers they support. |
| Last year’s numbers | values_2026_final_v3.xlsx — somewhere. | Every answer and edit versioned: who, when and what changed. |
| Totals and TIV | Formulas you check every year, in every copy of the file. | Totals per site and period, computed from what the sites reported. |
| Sharing with your broker | Export, attach, and hope it is the latest version. | Direct access to current values, or a pull over the REST API. |
| Who can see what | Whoever has the file has all of it. | Site access per user, user group or AI agent. |
| Working with Excel | It is Excel. | Import from Excel with a what-if preview. Export the values table whenever you need a file. |
A labelled scenario at list price, so you can set it against the hours you spend today.
Excel comes with the Microsoft 365 licences you already pay for. The real cost is the hours of the round: the requests, the reminders, the merging and the questions.
43 users at the €34 Enterprise list price, before volume discounts: €17,544 a year. Every login counts, internal or external. Nilfisk estimates it saved approximately 75% of the time it spent collecting and analysing the data.
Checked by Alex Bjørlig, founder, on . Every 21RISK claim on this page comes from our documentation, the pricing page or a published customer case. The Excel column describes a renewal round run on workbooks and email.
Switching is not a re-keying exercise. The spreadsheet you maintain today is the starting point.
Bulk import the site list you already have, with its hierarchy, from an Excel template — thousands of sites in one upload.
Upload the workbook you sent to the broker. Keep your own column headers if they match the template, review the what-if preview, then import. It runs as one transaction: it either succeeds completely or changes nothing.
From here on, sites update last year’s values in 21RISK and your broker reads current values. The spreadsheet chase ends with the import.
| Site | Total PD | Total BI | TIV | LPΔ | Progress |
|---|---|---|---|---|---|
| Aalborg plant | €48.2M | €21.0M | €69.2M | +3.1% | completed |
| Hamburg DC | €31.6M | €12.4M | €44.0M | +1.4% | completed |
| Lyon plant | €27.9M | €14.8M | €42.7M | −0.6% | completed |
| Toronto plant | €22.3M | €9.1M | €31.4M | +4.8% | in progress completed |
| 24 sites | €412.7M | €186.3M | €599.0M | +2.1% |
You are not giving up the spreadsheet. You are giving up being the one who maintains it.
Bulk import insurance values, COPE area values, sites and responsibility assignments from Excel. The values and COPE imports show a what-if preview before anything is written.
Export the values table with the same columns and TIV as the application — for the broker who wants a file, or for your own analysis.
A direct Postgres connection for your analytics team: live risk data in Power BI or plain SQL, with no snapshot in between.
"By using the 21RISK system, I estimate we have saved approximately 75% of the time we normally would have spent on collecting and analyzing the data."
As an import, yes. If your columns match the template headers you upload the file as it is; if not, copy the columns into the template. After the first import, sites answer in 21RISK and the spreadsheet stops being the system of record.
Two imports: the site list and last year’s values. Nilfisk describes 21RISK as “fairly simple to implement” and “a fairly simple system to use” — the collection round runs the same way from the first period.
Each site opens its own form and enters property damage and business-interruption values, with photos and documents attached where they help. There is no workbook to download, no macros to enable and nothing to send back.
Excel is a tool you already own, so its price is the time each round takes: the reminders, the merging and the questions you cannot answer. Nilfisk estimates 75% less time on collecting and analysing the data, and calls 21RISK “good value compared to the annual cost of having the system”. The scenario above prices 40 sites at €1,462 a month.
Yes. Export the values table with the same columns and TIV the application shows. You can also give brokers direct access, or let their systems pull current values over the REST API, so the file they hold is never older than the data.
Bring the workbook you use today. We will import it and show you the same round in 21RISK.