- Sector
- Industrial group
- Company size
- One of the group's companies
- Business lines
- GRC and ESG
- Solutions
- Corporate criminal compliance, GRC platforms
The model existed, but it lived in a spreadsheet
The company kept its criminal compliance model in a matrix: the map of criminal risks with their assessment and, for each control, its nature, its strength, its owner, the person responsible for it and how often it is reviewed.
Two other companies in the group already ran theirs in eramba. This one had nothing in the tool, and a matrix in a file doesn't remind anyone that a control is due for review, or keep proof that they reviewed it.
- Offences, risks and controls that had to go in without losing the company's own assessments
- Seven people with controls in their charge who had never used the platform
- The model's general controls, kept separate from the business activity controls
- An annual review still to be scheduled
The matrix, turned into risks, controls and people
Its assessments, as they were
Inherent risk goes in as the company calculated it, and each control's starting strength is the one the matrix gave it.
From offence to control
Each offence is broken down into its risks, and each risk is linked to the controls that cover it.
General controls kept apart
The nine general controls of the prevention model are kept separate from the 92 business activity controls, just as in the group's other companies.
Each control, with its people
Seven people at the company, set up with their role: control owner, responsible for the evidence, or both.
Residual risk that updates itself
The platform recalculates residual risk from the strength of the controls. A control reviewed without stating its maturity counts as zero, and the risk goes up.
Guides for each role
One guide for the people who upload evidence and close reviews, and another for whoever manages the model, with the new company within its scope.
Two rehearsals before loading anything
The matrix arrived at the end of September. A few days later it was ready for the platform: more than 70 risks, more than 90 business activity controls and the general controls required by Article 31 bis of the Spanish Criminal Code, following the same approach the other two companies already used.
Before touching production, we rehearsed the load twice. The first rehearsal left more than a hundred owner gaps: controls pointing to someone who didn't have a user account yet. For the second, the company sent us the details of the seven people, and along the way it turned out that one of them had left the organisation and their replacement had to go in instead. That version left no gaps.
The hardest part was making sure every control had a named person. Only one was left without an owner or a responsible person in the matrix itself. Rather than paper over it, we flagged it to be resolved with the group's compliance team.
The final load followed a fixed order: people first, then controls, risks and the review date. It was completed at the end of October, the day before the launch training, which was given on the company's own matrix so that each person logged in for the first time with their user already created and their control assigned.
The first annual review of the model is set for January. The matrices of two more companies in the group will arrive from December and will go in the same way.
The product is explained at eramba. How we work on a prevention model from start to finish, in corporate criminal compliance.
The whole matrix, in the platform
Is your prevention model still in a spreadsheet?
Send us the matrix you have. We'll tell you how it would look in the platform and which controls currently have no owner.