OHS Software as the Operating System in Large Enterprises
Digitalisation of the in-house occupational risk prevention service with OHS software
In many organisations, Occupational Risk Prevention (ORP) and Occupational Health and Safety (OHS) do not fail due to a lack of technical knowledge. They fail because of something far more everyday: dispersion. Risk assessments in Excel, evidence in emails, inspections in PDFs, actions in different tools… and each site operating “in its own way”. A good OHS software works as the operating system of prevention: see how in the Sabentis platform. This shift is at the heart of the digitalization of occupational risk prevention.
In this interview, Ramón Corrales, Chief Executive Officer of Technology and Product at Sabentis, shares a very clear idea: when OHS software is designed merely to “help complete tasks”, it falls short. When it is designed to organise how OHS actually works, it can become the “operating system” of prevention—defining structure, processes, traceability, metrics, and continuous improvement.
30-second summary
- The enemy is dispersion, not lack of technical expertise.
- OHS software should not be “just another tool”: it should function as an operating system that organises structure, processes, evidence, responsibilities, metrics, and continuous improvement.
- AI only adds value when it is embedded in the real workflow: capture evidence → analyse → prioritise → generate actions → verify closure.
- Without integration (SSO, APIs, BI) and governance (roles, traceability), you are not digitalising OHS—you are merely computerising it.
Why OHS management does not scale without OHS software in large enterprises
Interviewer:
Ramón, when you speak with large companies about OHS, what would you say is the main obstacle?
Ramón Corrales:
It is almost never a lack of technical knowledge. OHS teams know very well what needs to be done. The problem is something else: fragmentation.
When data and evidence are scattered across folders, emails, and disconnected tools, management becomes slow, difficult to standardise, and almost impossible to scale. And there is a critical consequence: if something is not recorded in a traceable way, it “does not exist” when an audit, inspection, or incident occurs. Aligning these processes with standards such as ISO 45001 is essential.
From “tool” to “operating system”: what truly changes in occupational risk prevention with OHS software
A tool helps you complete tasks (log an inspection, store a document, close an action).
An operating system defines how OHS works across the entire organisation: what is recorded, where, with what structure, who approves it, how it is measured, how learning happens, and how the system evolves. This is exactly what distinguishes advanced OHS management software.
Ramón Corrales:
“A tool helps you do tasks. An operating system defines how OHS works in your organisation—even when you grow, change sites, or onboard new people.”
The difference can be summed up in one sentence:
“We have inspections” (in folders, emails, and Excel)
v.s
“We have a living process: inspection → finding → action → evidence → closure, with clear responsibilities and deadlines.”
The 7 pillars you should demand from OHS software for large enterprises
If you are evaluating OHS management platforms, this section works as a checklist. Ramón frames it as “seven pillars”:
1) A data model that reflects your reality
In OHS, everything depends on fast answers: where, who, which role, which task, which exposure.
A minimum data foundation should cover:
- Physical structure: company → sites → locations → zones → … (where applicable)
- Operational structure: occupations → activities → …
- Material agents
- And a key point: the job position as the link between physical structure, operations, and material agents, with inherited risks to avoid duplicated assessments.
‼️ If you cannot list “people exposed to X at site Y” without cross-checking multiple Excel files, you have structural debt.
2) OHS workflows: from evidence to closure
In large enterprises, prevention only holds if the system maintains the full cycle:
inspection → finding → action plan → evidence → closure
🔄 A closed loop with responsibilities, deadlines, validations, and full traceability.
3) Evidence and traceability (audit-ready)
A mature system allows evidence to be attached at the exact point where it belongs: to a question, an inspection, a finding, or an action.
⚡ Evidence must also be centralised and retrievable in seconds—tags, source, context, filters. In practical terms: moving from “half a morning searching” to “I’ve got it in 30 seconds”.
4) AI in OHS: useful, explainable, and bounded
The AI that matters is the one that saves time without inventing reality. This connects directly to how AI anticipates accidents.
Examples include:
- Video analysis for ergonomics/posture with structured outputs (e.g. timestamps).
- Support for prioritising risks and proposing measures without replacing technical judgement.
- Clear rules for data retention and deletion, without requesting unnecessary sensitive data.
5) Dashboards for Management
Management needs:
- Stable, comparable KPIs
- Trend analysis
- Segmentation (by site, role, process, etc.)
- The ability to drill down when something does not add up
🚨 If the system does not provide this, OHS becomes blind and reactive.
6) Integrations as a standard: SSO + API + BI
In multinationals (and growing mid-sized companies), isolated software “dies” due to operational friction. This is why data acts as the nervous system of the OHS management system.
You need:
- SSO for corporate access (e.g. SAML)
- APIs to connect with ERP, HR, maintenance, etc.
- BI outputs for fast decision-making and executive reporting
🏝️ Without integrations, “OHS digitalisation” turns into isolated islands.
7) Security and compliance at the real level of a large enterprise
“It’s not enough to say ‘we have a username and password’.” Large organisations expect, at a minimum:
- Strong security controls
- Business continuity
- RPO/RTO-type metrics
- Recognised frameworks (e.g. ISO 27001 or equivalents, depending on context)
🔒 In OHS, data and evidence are sensitive due to their legal, operational, and reputational impact. Security is not an extra.
AI in OHS: when it adds value—and when it does not
Ramón’s criterion is straightforward:
Is AI embedded in the workflow and does it reduce friction?
- If AI is just a “demo button” disconnected from the real process, it gets in the way.
- If it helps capture evidence, structure it, prioritise risks, and push actions through to closure, it adds value.
And there is one key condition: explainability.
In OHS, “because the system says so” is not acceptable. It must be clear:
- what was detected
- where
- based on what evidence
- and with what level of confidence
AI should support—not dictate.
Digitalising vs. computerising: the difference that changes everything
Interviewer:
You used a powerful phrase: “without integration and governance, you are not digitalising—you are computerising.”
Ramón Corrales:
Computerising means taking what you used to do on paper or in Excel and putting it on a screen… without changing the way work is actually done.
Digitalising OHS means the software becomes the place where OHS happens, with:
- Clear roles (who does what)
- Traceability (what happened, when, who validated it)
- Metrics (how we are performing)
- Continuous improvement (what we learned and what changed)
The most common mistake in OHS software implementations
3 classics that repeat themselves:
- Buying based on a feature checklist instead of the real process.
- Not resolving the data model at the start (leading to patch after patch later).
- Assuming “people will just use it” without minimum governance: roles, closure criteria, follow-up.
Software does not fix a lack of agreements. But when agreements exist, software makes them sustainable.
How return on investment is measured in OHS
Ramón grounds it in business and control indicators:
- Reduced action-closure time (less open risk)
- Fewer recurrences (findings repeat less often)
- Audit-ready traceability (less time preparing audits)
- Better prioritisation (investment goes where risk is highest, not where noise is loudest)
“Today, I can’t see the real OHS status by site and by role without three people manually pulling data together; with a system, I have it in two clicks, fully traceable.”
The question every company should be asking today
To close, Ramón proposes one practical question:
“Can we demonstrate, in minutes, which risks are open, who is responsible, what evidence exists, and what has been closed—without chasing emails or Excel files?”
If the answer is “no”, it is rarely the fault of the OHS team. It is usually a symptom that the system—or the lack of one—is not working in their favour.
About the interviewee
Ramón Corrales is Chief Executive Officer of Technology and Product at Sabentis. His approach focuses on turning OHS management into a traceable, scalable, and integrated system, where data, workflows, and continuous improvement operate at a corporate level.
