Skip to Content

Risk management in SAI360 for an industrial multinational and an insurer

Two SAI360 implementations where we provided the design and project management, as specialists, alongside another integrator. We don't sell SAI360 licences.
17 November 2026 by
Risk management in SAI360 for an industrial multinational and an insurer
OdooBot
Sector
Industry and insurance
Company size
Large companies
Business lines
GRC and ESG
Solutions
GRC platforms
The challenge

A well-thought-out risk model, scattered across spreadsheets

The multinational had defined its risk management model in detail. It lived in six matrices, one per risk family, from financial to sustainability risks, and each organisational unit maintained its own part in spreadsheets.

It wanted to bring that model into SAI360 to unify the information, support the reviews and action plans, and keep the evidence of each review.

  • Every risk and every control validated by its owner and overseen by the risk management function
  • An annual review of the whole model, unit by unit
  • Action plans when residual risk comes out high or evidence is missing
  • Risk indicators to spot deviations in time
The solution

The client's model, brought into the platform

Organisational structure

The company, division and business unit hierarchy, which is at the centre of everything: risks, controls and plans all hang from it.

Profiles by role

Risk management with global access, owners for each unit, management, and a read-only profile for the executive committee.

Reference risks

The client's categories and subcategories, with reference risks that each unit turns into its own specific risks.

Assessment and action plans

Impact and likelihood, inherent and residual, on the client's own scale. A high residual risk calls for an action plan.

Indicators and dashboards

Risk indicators and dashboards to track each unit's exposure and the progress of the action plans.

User manual

A user manual covering the pending tasks inbox, risks, assessment campaigns and reports.

How we did it

Design first, in writing

At the multinational, the project started in October 2025. Before anything was configured, the model was written up in functional specifications: the structure, the profiles, the attributes of each risk and each control, the assessment formulas, the review workflows and the dashboards.

Follow-up meetings with the client were monthly until January 2026. Each review of a risk or a control has its evidence attached, and each action plan has someone who carries it out and someone who oversees it, who is the person who created it.

The final documentation, from March 2026, brings together the specifications and the user manual. It's what remains when the project ends: whoever comes later can see why the platform is configured the way it is.

On both projects we provided the design and project management, as specialists in the platform; the integrator we worked with took care of loading the data.

What we learned

In a suite like this, the structure is what matters most

The structure you decide on at the start shapes everything else. If the unit hierarchy and the risk taxonomy don't match how risk will be consolidated, redoing them once the platform is live is expensive.

We don't sell SAI360 licences. The licence is bought from the vendor, and we bring our knowledge of the platform, including alongside another integrator when they hold the client relationship.

And when SAI360 is more than an organisation needs, we tell them. We're an eramba Gold Partner, and we know well where one platform ends and the other begins.

How we choose a platform with each client, in GRC platforms. The product, at SAI360.

Does your risk model live in spreadsheets?

Tell us how you manage it today and which platform you have or are considering. We'll tell you where we would start.