Skip to Content

Risk and compliance for an international airline, in eramba

We implemented eramba for its compliance team, with its controls and questionnaires in one place. Since then, we have run it for them every year.
17 November 2026 by
Risk and compliance for an international airline, in eramba
OdooBot
Sector
Air transport
Company size
International airline
Business lines
GRC and ESG
Solutions
GRC platforms, GDPR
The challenge

Clear owners and something to show management

The airline's compliance team wanted to strengthen its compliance management model and automate whatever it could. It came with a lot of work already done: its inventory of internal controls and its analysis of the data protection rules that apply to it, with the documents for its model.

What it lacked was a platform where every control had an owner and the state of compliance could be shown to management. The other departments also had to be able to answer what they were asked.

  • Roles and owners defined for every control
  • Tracking that management can see
  • Business and purchasing teams who have to answer questionnaires
  • Licences renewed on time and in line with its budget
The solution

Phased implementation, then operation

Implementation workshop

Detailed training for its team in eramba's risk and compliance management, while we gathered its requirements.

Data model and profiles

A data model designed from its own information, with access profiles by role.

Loading its inventory

Internal controls and the documents of its data protection model, imported from its own templates.

Questionnaires for other teams

A data protection questionnaire for the purchasing and business teams, who answer it through the questionnaire portal.

Notifications and reports

Forms, custom statuses, filters, email notifications and reports tailored to the way its team works.

Licence and yearly operation

We manage the licence with the vendor, plus an annual contract to support and operate the platform.

How we did it

From training to go-live

The project followed five phases: kick-off, discovery, design, build and deployment. The method asks the client's team to complete the vendor's online training first, so the workshops can focus on its requirements.

After the workshops, the client gathers its master data, its questionnaires, who should see what and what it wants to see in the reports. We prepare the upload templates with that information and import it. Then comes the client's review: it tests the profiles, questionnaires, notifications and reports, and we fix whatever doesn't fit.

We configured only what eramba offers out of the box, with no custom development and no changes to its code. That way, the vendor's new releases are applied on top of a standard configuration.

More than 250 internal controls and more than 30 documents from the data protection model were loaded.

After the implementation

A client asking how to organise its team

The relationship didn't end with deployment. Every year we renew the licence and the operation contract with them, and in 2025 the client asked us to bring the renewal invoice forward to fit its budget cycle. So we did.

In summer 2026 another question came in, this time about organisation: how to set up the team that runs eramba, as part of a review of its operating model. We sent them an anonymised comparison the same day, drawn from our experience with the organisations where we run the tool.

It's a question we often get from clients who have been on the platform for a while. By then, what's under review is who does what.

How we choose a platform with each client: GRC platforms. Our data protection work: GDPR. The product itself: eramba.

Is your compliance still spread across spreadsheets and emails?

Tell us which standards apply to you and who is responsible for each control. We'll tell you how it would look on a platform and where we'd start.