Sabentis App Ecosystem

What the five-app Sabentis ecosystem is

The Sabentis mobile ecosystem comprises five applications for different audiences: Sabentis Elite, Sabentis Lean, Sabentis One, Sabentis Go and Sabentis Conmigo. Its purpose is to bring prevention closer to each person’s responsibilities and working context, from organisational leadership to self-employment.

The suite combines tools for decisions, field records, worker participation, small-business prevention and personal safety guidance. These are distinct experiences, with different availability stages.

This profile explains each app’s role in occupational safety and health. It distinguishes published applications, functional developments and concepts under design. Download links refer only to verified official listings; a product description does not imply public access to every function.

The five apps and their intended users

• Elite: senior leaders interpreting indicators, reviewing priorities and making decisions.
• Lean: OSH professionals and supervisors performing workplace inspections, checks and observations.
• One: workers consulting prevention information and participating in assigned tasks, signatures, questionnaires and activities.
• Go: owners of microbusinesses, small companies and independent activities needing guided prevention workflows.
• Conmigo: self-employed people needing understandable everyday guidance, with emphasis on accessibility and limited connectivity.

Selection depends on the task as well as company size. One environment may require fieldwork, individual participation and leadership review. Each workflow should define information access, recording responsibilities and verification of subsequent action.

Sabentis Elite: information and decisions for leadership

Sabentis Elite is designed for senior leadership. Its concept brings together an overview of the OSH system, organisation or site indicators and decisions awaiting review. It aims to make priorities visible without requiring leaders to navigate every operational screen.

The planned scope covers policies and plans, results, deadlines, audits and findings. It also envisages traceable decision signatures and assistance interpreting information. These are design capabilities; implementation, authentication and signature conditions must be confirmed for the relevant edition.

Relationship with OSH

A leadership view should identify what needs a decision, the supporting evidence and who will verify execution. A favourable indicator does not remove the need to review deviations, operational changes or uncertainty. The aim is oversight and accountability with access to the detail explaining each result.

Documented status: under design. General availability has not yet been announced.

Sabentis Lean: safety work in the field

Lean provides access to available organisational information and supports inspections, checks and observations on a mobile device. Current documentation also describes permits to work: requesting, viewing, authorising and closing them depends on the person’s role and the company’s configuration. Installing the app does not automatically grant those permissions.

Access requires a Sabentis environment and an account enabled by the organisation. Before a visit without coverage, import the necessary data while connected. Work can then be recorded on the device and exported when the connection returns. Initial access and synchronisation require internet access; distinguish a locally saved record from one already available to the team.

A practical use is to prepare an inspection with the assigned checklist, identify the location of a finding and attach enough evidence for someone else to understand and follow it up.

Reference documentation: Sabentis Lean — App Store · Sabentis Lean — Google Play · Sabentis Lean: renovación de la app de campo.

Sabentis One: worker participation and prevention records

Sabentis One focuses on workers’ everyday participation in prevention. It prioritises pending activities and organises prevention information: documents to read, assigned tasks, appointments and activities associated with the role.

The described scope includes signatures and reading acknowledgements, health and psychosocial questionnaires, personal protective equipment, appointments and training. Product documentation envisages consent records and timestamps. The existence of these screens does not establish that every integration is enabled in every organisation.

Relationship with OSH

Participation improves when people understand what is requested, why and how to complete it. Receiving, signing and understanding a document are different events. Sensitive questionnaires require separating individual access from aggregate information used to analyse trends.

A sample workflow involves checking a pending activity, opening the relevant material and recording the requested action. The responsible person then verifies receipt and whether the result supports the next step. The app should fit the environment’s defined responsibilities and permissions.

Documented status: a delivered functional development, with integration and availability dependent on deployment.

Sabentis Go: guided prevention for micro and small businesses

Sabentis Go is conceived as a guided mobile experience within the Sabentis ecosystem for micro and small businesses. Its purpose is to make occupational safety and health organisation more approachable for people who need understandable starting steps, a way to record workplace situations and continuity in preventive actions. The starting point is the company’s context: its activity, size, sites and jobs.

Its functional approach combines several ways of collecting and organising information:

• Guided setup: structure basic company information and place preventive needs within its activity and organisation.
• Photographs and voice: support descriptions of observed situations, inspections and accidents, reducing dependence on lengthy text entered on a phone.
• AI assistance: support the identification of findings, preparation of proposed measures and drafting of documents, with user review and validation.
• Tasks and obligations: connect findings to actions requiring follow-up, without confusing a recorded task with its actual implementation.
• Contextual documentation: organise documents by their relationship to people or sites and their validity periods, preserving the context of the information.

How it relates to occupational safety and health

The value of this approach lies in connecting observation, interpretation and action. A photograph may provide evidence of a visible condition, but cannot independently establish every exposure, the frequency of a task or people’s circumstances. Distinguish observed facts from inferences, complete the context and assess the risk before selecting measures. AI is positioned as support for that process, with people involved in decisions.

Hypothetical use example

Materials obstruct a passage in a small workshop. The responsible person could document the situation with an image and a voice explanation, review the description and specify the necessary action. They would then need to check that the action was implemented and the situation did not recur. This example illustrates Go’s approach; recording or describing a measure does not demonstrate its effectiveness.

The specific scope of functions should be confirmed for each edition and operating environment. Images, recordings and documents should contain only necessary information, avoiding people or sensitive data without a justified purpose.

Documented status: a functional prototype intended for iPhone and Android. It is not yet available for public download.

Sabentis Conmigo: prevention for self-employed people

Sabentis Conmigo is intended for self-employed people needing understandable everyday guidance. Its design starts with the occupation and proposes access without creating an account, read-aloud support, dictation and content suited to limited connectivity.

The documented functional scope groups the experience into:

• Today and my risks: everyday precautions and occupation-related risks, explained briefly with supporting images.
• Advice: content adapted to work and conditions, with audio options.
• What should I do if: guidance for common situations, requiring localisation and validation for each country.
• Working alone: periodic check-ins and a planned alert to a trusted contact when the person does not confirm their status.
• Protection and help: information for locating appropriate resources.

The proposal also envisages guidance through photographs and voice questions. Effective AI capabilities must be distinguished from existing functional content and workflows: planned additions are not presented as generally available services.

Relationship with OSH

Conmigo aims to reduce barriers to understanding and accessing prevention information. A person can recognise a situation associated with their occupation and consult brief guidance. This does not replace assessment of the work or identify every exposure from a photograph.

Working-alone alerts are not a rescue service. Contact notification depends on the device, permissions, coverage and communication channel. Storing telephone numbers does not guarantee calling or sending SMS without a network. Test the support arrangement rather than relying on the existence of a button.

Documented status: a functional version in internal testing. It is not yet available for public installation. Content, help resources and enabled features require confirmation for each edition and territory.

A common ecosystem with distinct workflows

The suite is conceived around the Sabentis platform with experiences adapted to each role. In organisational use, relationships between people, sites, jobs and records preserve context. Conmigo proposes lighter personal access; it should not be assumed to require the same account or automatically share all enterprise-app data.

Design principles include understandable language, useful voice and image input, preparation for limited connectivity and human confirmation of assisted proposals. Their implementation varies by product, device and deployment.

Define the complete workflow: what the person needs, records and reviews, and who receives the result. With AI, distinguish suggestions from confirmed facts. With synchronisation, verify both local saving and receipt at the destination.

Identity and documented development

The official listings identify SABENTIS as the developer and EASY TECH GLOBAL, SL as the provider. The application named Sabentis and Sabentis Lean have separate store identities. The ecosystem name explains their relationship; it is not an additional application to install.

The Lean update described by Sabentis on 5 November 2026 brings together a revised interface and work permits within the field workflow. The App Store version history reviewed also records improvements to importing, exporting and stability. An application’s development includes these operational changes alongside new modules.

Release notes help prepare an update, but a useful test checks the organisation’s process: access, available tasks, recording and retrieval of the result. This profile’s review date provides context for the information; specific installation requirements should be checked in the relevant store.

Reference documentation: Sabentis Lean — App Store · Sabentis Lean: renovación de la app de campo · Sabentis — App Store España.

Published downloads under the Sabentis name

The Sabentis app, published by EASY TECH GLOBAL under the developer name SABENTIS, is available for iPhone, iPad and Android. Its official description includes reporting incidents, preparing reports and managing occupational risks from a mobile device. For OSH, this brings those tasks closer to the location where a situation requiring attention is identified.

The iOS download is listed as free; the store descriptions do not specify account or service-licensing conditions. Before use, confirm access and enabled functions with your organisation.

Sabentis on the App Store · Sabentis on Google Play

Reference documentation: Sabentis — App Store España · Sabentis — Google Play.

Downloads and access

Sabentis Lean is available for iOS and Android. Use the listings published by Sabentis and check the current device requirements in the relevant store.

Downloading an application and having an enabled account are separate steps. Confirm which organisation provides access before entering information.

Reference documentation: Sabentis Lean — App Store · Sabentis Lean — Google Play.

What information should accompany a record

For an inspection, observation or report, information is valuable when another person can interpret it. A practical working approach brings together four elements:

• Context: the company, site, location and task needed to place the observation.
• Description: what has been checked and what remains unverified, using terms the team understands.
• Evidence: relevant, readable photographs or files linked to the correct record.
• Follow-up: who receives the information and how subsequent action is checked.

For example, “route obstructed” is less precise than identifying the aisle, material and affected section. A general photograph can show the context and another the detail; adding many repeated images does not necessarily improve understanding. The record should preserve what was observed without presenting an initial interpretation as an already validated technical conclusion.

This is editorial guidance for using the tools, not a claim that all five applications share identical fields or automated processes.

Reference documentation: Sabentis Lean: renovación de la app de campo.

Work permits: responsibilities and status

Lean’s documentation describes permit management according to each organisation’s roles and configuration. A team may include people requesting an intervention, people checking its conditions and people authorised to approve or close it. The app brings recording closer to the work location while those responsibilities remain important.

A review should identify the planned intervention, location, recorded measures, responsible people and validity period. During a pilot, check what each role can see and what happens when a permit is pending, authorised or closed. It is also useful to rehearse a change in conditions under the organisation’s procedure, without automatically reusing an earlier authorisation.

The aim is for the team to understand the permit’s status and scope. A screen or signature alone does not establish that the physical conditions for performing the work have been checked.

Reference documentation: Sabentis Lean — App Store · Sabentis Lean: renovación de la app de campo.

Worked example: from a field record to follow-up

Hypothetical example using Lean. A team needs to inspect a receiving area with intermittent coverage. It wants evidence that allows the observation to be checked later.

1. Before leaving, confirm the active company, site and assigned checklist. Import the data onto the device that will be used.
2. During the visit, describe the finding and its location. A photograph should support the description and avoid capturing information unrelated to the purpose.
3. Check that the recorded response reflects what was observed. If something could not be verified, preserve that uncertainty instead of marking it as satisfactory.
4. When connectivity returns, export the records and check their status and attachments. Saved on the phone does not mean received by the platform.
5. Confirm with the responsible team that the information can be found and understood. Actions and closure should retain the evidence supporting each decision.

The acceptance criterion is being able to reconstruct what was observed, where and what happened next. This example illustrates a review process; it does not claim a measured implementation outcome.

Reference documentation: Sabentis Lean: renovación de la app de campo.

Device use, data and continuity

Preparation also includes the device: sufficient battery power, space for the required files, correct access and readable forms in the environment where they will be used. Tests should use the team’s actual devices and account for each person’s reading, language and handling needs.

When using photographs or documents, define in advance which information is needed and where it should be kept. A photograph may show people, number plates or details of another activity that contribute nothing to the finding. Reviewing the framing and file destination helps keep the record focused on its purpose.

The team should know what to do if a device is lost, access fails or records remain unsent. Before replacing a phone, signing out or reinstalling the app, check the status of local work and consult the support procedure. These are organisational practices for using the tools; the specific recovery process depends on the environment and application.

Choosing an app and preparing a pilot

Test a complete journey with test information: access, preparation, recording, restored connectivity and finding the result as the person responsible for review. Record usability issues and verify what each role can do. For the wider management processes, see the Sabentis profile; for organised learning, see the Sabentis Plus profile.

Reference documentation: Sabentis Lean — App Store · Sabentis Lean: renovación de la app de campo · Sabentis — App Store España.

How to assess usefulness for an OSH team

A pilot can focus on one site, one inspection type and a small group of users with different roles. Before starting, agree which workflow needs improvement and retain a reference for the previous process. This makes it possible to distinguish a change of tool from an observed improvement.

Simple indicators include the time between an observation and its receipt, records requiring clarification, attachments that fail to identify the finding and work awaiting synchronisation. These are proposed pilot measures, not results attributed to Sabentis. More records may reflect better communication rather than worsening conditions.

The review should include both the person recording in the field and the person receiving the information. If the first completes the form but the second cannot locate the finding, the workflow still needs adjustment. Before expanding use, resolve recurring difficulties, review permissions and explain how to request support.

Frequently asked questions about Sabentis apps

Which five apps belong to the ecosystem?

Elite serves leadership, Lean field teams, One workers, Go small businesses and Conmigo self-employed people. Each has its own scope and availability status.

Are all five publicly downloadable?

No. Lean has verified official listings; Elite is under design, One depends on integration and deployment, Go is documented as a functional prototype and Conmigo as an internally tested version. Listings named Sabentis retain their official name.

Can I use Lean offline from the outset?

Initial access and importing data require a connection. Working without coverage means preparing the necessary data in advance and checking synchronisation afterwards.

Does sending an inspection mean an action is closed?

No. Sending communicates information. Closing an action requires the checks and evidence defined by the organisation’s process.

Reference documentation: Sabentis Lean — App Store · Sabentis Lean: renovación de la app de campo · Sabentis — App Store España.