OSH software and CAE platforms in Spain: differences, overlap and integration
A company may manage its internal occupational risk prevention while also coordinating work with contractors, suppliers or clients. These needs share information but are not identical. Software selection should begin with the workflows to be supported and the relationships between the organisations involved in the work.
In Spain, coordination of business activities, known as CAE, is governed by Royal Decree 171/2004. Obligations depend on the circumstances of concurrent work and each employer’s role. The Explora entry on CAE explains the context. A document platform supports coordination; it does not encompass the whole activity.
Understand the problem each tool addresses
OSH software may support internal risk assessments, planning, training, inspections and action tracking, depending on its scope. A CAE-focused platform commonly organises exchanges and checks between concurrent businesses. Products can include functions from both areas, so their commercial category alone does not establish the actual coverage.
The Explora entry on OSH software provides an overview. For selection, map a real task. To close an action from an internal assessment, examine assignment and verification. To coordinate external work, include companies, people, tasks, information and changes arising while the work is being performed.
Identify where information overlaps
Sites, workers, companies and documents may appear in both applications. Duplication becomes a problem when no one knows which system holds the current information. A personnel change or a revised document may be updated in one location while the other retains an outdated version.
Define an owner and an authoritative source for each shared data item. Not every field needs to travel in both directions. Integration should meet a specific operational need while preserving context: the presence of a document does not mean it is valid for every site, activity or period.
Consider three architecture scenarios
First, a company has an established internal process and works at several clients’ sites, each using different platforms. It may need to manage its own information and prepare exchanges required by each client. Before adding automation, identify formats, conditions and update responsibilities for every relevant connection.
Second, an organisation receives contractors at its premises and also needs to track preventive actions for its workforce. Check whether one solution can support both workflows with clear permissions and responsibilities, or whether specialised tools need to be connected through a defined exchange process.
Third, a group operates sites with different working conditions. A common architecture may share catalogues and rules while preserving operational decisions at each site. Test this through a complete intervention, including a work change after the initial authorisation, instead of reviewing only a central dashboard.
Test whether an integration is useful
- Identify the data that starts the exchange and its source system.
- Define which event requires an update: creation, amendment, removal or a new version.
- Check what happens when transfer fails or information arrives incomplete.
- Clarify who resolves discrepancies and which information each company can see.
- Verify how history is retained when the contractual relationship ends.
The Explora entry on OSH software integration offers criteria that also apply here. “We have an API” is not a complete answer. The proposed exchange needs a defined scope, responsible people and practical tests. Include its maintenance in the commercial evaluation.
Coordination continues while work is underway
Imagine a maintenance repair moving to another area while a second company performs a nearby task. This illustrative example shows how the original documents can remain current while coordination still needs to address a changed interaction. The tool should support the agreed process for communicating, assessing and managing that change.
A demonstration should therefore cover relevant communications, owners and operational decisions as well as entry documentation. Ask how agreements are recorded and how receipt is confirmed. Preventive effectiveness also depends on the actions people actually perform at the workplace, outside the software environment.
Prepare the purchase with the OSH software RFP and the guide to multisite management. When assessing Sabentis OSH software, describe internal workflows and your role in concurrent business activities. This supports a coherent scope and helps avoid unnecessary duplication.
A practical checklist for gaps between internal OSH and CAE
Review a complete intervention from each participating company’s perspective. The aim is to identify decisions that could disappear between the internal application and the platform used to coordinate concurrent activities.
- Map who decides whether work can start and what information they need, distinguishing physical access from preventive authorisation.
- Introduce a task change after document validation and check how interactions between the companies are reassessed.
- Identify information needed by the supervisor at the workplace and whether it is available when the intervention begins.
- Check that a critical communication reaches the people affected, rather than only the contractor’s administrative account.
- Review how a defect in the premises identified by an external company moves into the internal action-tracking process.
Frequently asked questions about OSH software and CAE platforms
Do green document statuses mean CAE has been completed?
No. Coordination includes information, instructions and means appropriate to concurrent work, according to each company’s role. Documents can support part of the process, but an on-screen status does not itself establish that interactions and overlapping activities have been controlled while the work is carried out.
Can one application support both internal prevention and CAE?
Yes, if its scope supports both workflows with appropriate responsibilities and access. This should be demonstrated through complete cases, including changes and exceptions. The decision depends on actual process coverage and use, rather than whether the product is advertised as an integrated solution.
Should every field be integrated between the two tools?
No. Exchange only information needed for a defined purpose. Decide which system maintains the data, when it changes and who resolves discrepancies. Integrating unnecessary fields can increase duplication and make it harder to establish which information was valid at a particular point in time.
Can a Spanish CAE platform be used unchanged in Colombia?
That should not be assumed. Spanish coordination and contracting within Colombia’s SG-SST have their own frameworks. A tool may support both countries, but requirements, terminology, responsibilities and evidence must be reviewed by jurisdiction before forms or automated rules are reused across operations.
Legislation and sources consulted
- Spain: Royal Decree 171/2004 on concurrent business activities: Spain, Articles 4, 5, 11 and 12: cooperation, information exchange and the selection and updating of coordination arrangements.
- Colombia: Decree 1072 of 2015: Colombia, Article 2.2.4.6.28: contracting and preventive follow-up of suppliers and contractors; a reference for distinguishing the two frameworks.
Sources consulted on 6 October 2026. Checklists and examples are practical implementation proposals.
