A SharePoint risk register with a Power Apps form looks free, because you already pay for Microsoft 365. Here is what the build has to do for a property insurance programme, who keeps it running, and when it is the right call.
You track one register for a few sites. You have a maker who will stay and who has the time. The data must stay inside your own Microsoft tenant.
You collect values and COPE from ten or more sites every renewal, in more than one currency. Your broker and insurer need the data, and nobody has time to run a software project.
Microsoft 365 is a strong toolbox, and a list with a form demos well. A property insurance programme asks for more than the demo.
A list and a form take days. Then come renewal periods, currencies, TIV, site access and the question the insurer added this year. Someone has to design all of it, and change it again next year.
Most builds have one maker, and that person has another job. When they move on, the lists stay and the knowledge of how the lists fit together goes with them.
Microsoft 365 holds what you type into it. Natural hazard scores for your addresses and country risk have to come from somewhere else, and someone has to load them.
Job by job: what a build on SharePoint and Power Apps has to do, and what 21RISK does from day one.
| The job | In your build | In 21RISK |
|---|---|---|
| Getting started | Someone designs the lists, forms, flows and permissions, then tests them with the sites. | Two Excel imports: your sites and last year’s values. |
| Forms for the sites | You build each form, and change it when the insurer asks a new question. | Forms for values and COPE are ready. Each period sets which values you collect. |
| Who sees which site | Item permissions or filtered views, which you set up and keep right when people move. | Site access per user, user group or AI agent. |
| A new renewal | A year column, a copied list or a new site. You choose, and you live with the choice. | Open the new period. Values carry over, and review progress shows which sites have not reviewed theirs. |
| Totals, TIV and currencies | Calculated columns, flows or a Power BI model you maintain, plus exchange rates you load. | Totals per site and period. Period comparison keeps changes in value apart from exchange rate effects. |
| Natcat data | Not in Microsoft 365. You license hazard data and load it yourself. | Earthquake, storm and flood scores from Munich Re on every site. |
| Engineering reports | PDFs in a library, and recommendations typed into a list by hand. | Reports on the site record, linked to risk improvements. On Enterprise, AI reads the recommendations out of the PDF for you to review. |
| Your broker and insurer | Guest access in your Microsoft tenant, if your IT policy allows it. A guest who runs a Power App needs the same licence as your own staff. | A login limited to the sites you choose, or a pull over the REST API. |
| When things change | A task for your maker, next to their real job. | New features arrive in the product, and the changelog says what changed. |
A labelled scenario at list price, so you can set it against the hours of the person who would build and maintain it.
Apps on SharePoint lists come with most Microsoft 365 plans. Dataverse and premium connectors need Power Apps Premium, listed at $20 per user a month, also for guests. The real cost is the maker’s time, every year.
43 users at the €34 Enterprise list price, before volume discounts: €17,544 a year. Every login counts, internal or external. Nilfisk calls it “good value compared to the annual cost of having the system”.
Checked on by 21RISK. Every 21RISK claim on this page comes from our documentation, the pricing page or a published customer case. The build column describes a typical SharePoint and Power Apps project.
Your lists are not wasted work. They are a clean starting point for the import.
A SharePoint list exports to Excel in a few clicks. That workbook is your starting point.
Bulk import the site list with its hierarchy, then last year’s values. Review the what-if preview before anything is written.
From here on, sites update their values in 21RISK. Your maker gets their time back.
| 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% |
21RISK does not replace your Microsoft tools. It works next to them.
21RISK is in the Microsoft Marketplace as an agent. Ask about your sites and overdue risk improvements from Copilot, within the access you grant.
ENTRASign in with Microsoft Entra over SAML or OIDC, and let SCIM add and remove users from Entra.
POWER BIStart from the template app, or connect your analytics team straight to the data 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."
Yes. A SharePoint risk register with a Power Apps form is a real option, and a good maker can have a first version running quickly. The question is who designs periods, currencies and site access, and who keeps it working for the next ten renewals.
For size, yes: Microsoft allows 30 million items in a list. A single view or query is limited to 5,000 items unless it filters on an indexed column, so a list with one row per site, value and year needs planning before it grows. 40 sites, 30 values and 5 years is already 6,000 rows.
Yes. Sign in with Microsoft Entra over SAML or OIDC, and provision users with SCIM. 21RISK is in the Microsoft Marketplace as an agent for Microsoft 365 Copilot, the Office app and Teams. Power BI has a template app and can read the data directly.
Yes. SharePoint is a good home for policies, procedures and team files. 21RISK holds the structured work: sites, values, COPE, natcat, risk improvements and claims. Files that support an answer, such as a valuation report, can sit on the site’s answer in 21RISK.
A SharePoint build stays inside your own Microsoft tenant, and if that is a hard requirement, build it. 21RISK stores data in AWS in the EU (eu-central-1). Every table exports to Excel, and the REST API and a direct Postgres connection give you the data without an export.
On the invoice, often yes. The maker’s hours do not show on an invoice, but they are the real price of a build, every year. The scenario above prices 40 sites at €1,462 a month at list price.
Show us the lists you have, or the build you are planning. We will show you the same renewal in 21RISK.