Blog > November 15, 2026

OSH software for public administrations in Spain: preparing procurement requirements

OSH software for public administrations in Spain: preparing procurement requirements

A public administration may manage buildings, workshops, street-based services and teams with very different working arrangements. Procuring OSH software requires translating that diversity into requirements that can be demonstrated. A list of modules does not explain how an issue will be handled, who will see the information or what the supplier must deliver for implementation to be accepted.

Preparation should bring together prevention, procurement, technology, data protection and operational managers. Each contributes conditions that need to connect with the contract’s purpose. The result should enable proposals to be compared and the delivered service to be checked against an agreed scope.

Describe processes and their scope

Identify the entities, sites, activities, users and information volumes to be managed. Distinguish technical staff configuring processes from supervisors implementing measures and workers consulting information or submitting reports. Also define the relationship with external prevention services where these are part of the organisation’s arrangements.

The Explore entry on planning preventive activity helps turn a need into a use case: assign a measure to a building, identify an owner and resources, provide evidence and verify the outcome. This journey can become a demonstrable functional acceptance test.

Write requirements that support comparison

Specify what the system must achieve and how it will be checked. “Advanced action management” is ambiguous. Requiring an owner, deadline, change history, linked documents and verification status is clearer, where those features respond to the identified need and can be tested consistently across proposals.

Article 126 of Spain’s Public Sector Contracts Law governs technical specifications and addresses accessibility for services or products used by people. The competent procurement body should review the final wording, supported by justified requirements and appropriate means of verification.

Define security and data protection scope

Royal Decree 311/2022 defines the scope of the National Security Framework, including certain private suppliers’ systems serving public bodies. Specifications should identify the affected system and service, its category and relevant conformity evidence; requesting a generic certificate without checking its scope is insufficient.

Describe the access, activity logging, continuity, recovery and incident-management arrangements required for the service. For personal information, determine applicable responsibilities and contractual conditions with the data protection team. Preventive conclusions and clinical documentation may require different access pathways, including for external professionals participating in the service.

Check accessibility through real tasks

Include tests of the journeys people will use: consulting an instruction, submitting an observation, completing an inspection or retrieving a document. Check keyboard navigation, understandable messages and compatibility with assistive technologies relevant to the contracted scope. A general statement should be supported by sufficient evidence and a means of addressing defects.

Apply the same attention to training and support materials. A system may provide accessible features yet lose practical usefulness if instructions are supplied only as images or the support channel cannot resolve an access difficulty. These supporting services form part of the user’s experience of the contract.

Example: start with offices and a workshop

Imagine an administration starting with two office buildings and a municipal workshop. The pilot checks permissions, job inventories and action follow-up across different operations. Managers verify that tasks reach the correct unit and that senior management can view progress without unnecessary access to personal information.

This illustrative case supports concrete deliverables: reconciled data, tested profiles, trained users and issues resolved against agreed criteria. Traceability in OSH helps retain acceptance evidence and explain what remains for the next phase, making the transition between pilot and wider rollout easier to assess.

Plan support, change and exit

Define response times according to impact, update responsibilities and the change-request procedure. Include final delivery of data, documents and their relationships in usable formats, supported by an export test. These arrangements should align with the software contract and service levels.

The guide to software requirements and demonstrations can support internal preparation. When exploring Sabentis for prevention management, use representative scenarios and request concrete evidence. The decision should rest on the connection between the need, specification, proposal and verification of the delivered service.

Checks before finalising procurement requirements

A joint review by prevention, procurement and IT can identify requirements that are difficult to verify or overlooked costs. Use the same functional sample to examine the need, acceptance criterion and evidence that each proposal should provide for the contracted service.

  • Link every mandatory requirement to a documented need and a method of verifying it during service delivery.
  • Distinguish available capabilities from promised development and identify the milestone at which each deliverable will be tested.
  • Include migration, training, support and data return when comparing the cost of the scope to be procured.
  • Review whether a test requires real personal information and replace it with fictional or appropriately anonymised data where suitable.
  • Test an export and confirm that documents, relationships and identifiers would allow work to continue in another system.

Frequently asked questions

Should specifications be written using commercial module names?

Describing the need and verifiable outcome is more useful. Technical specifications must follow the applicable procurement rules, including those concerning brand references. Review wording with procurement so that comparison rests on justified requirements and relevant evidence rather than on the names chosen by a vendor.

Does a supplier’s ENS certificate automatically cover the entire service?

Its scope must be checked against the system and service being procured. Identify the offered service, the appropriate conformity evidence and the included components. A general reference to the organisation does not by itself establish coverage for every commercial solution that it supplies.

How should a capability that still needs development be evaluated?

Clearly separate existing functionality from a future commitment and define the deliverable, date and acceptance test. Procurement should determine its treatment within the procedure. During evaluation, do not present a mock-up or commercial description as evidence that a working capability is already available.

Why test exit arrangements before procurement?

The exercise reveals which information can be recovered and under what conditions: records, documents, relationships and formats. Examine who performs the export and the support needed. Defining this check early helps specify continuity arrangements and the deliverables required when the contract ends.

Legislation and sources consulted

Sources consulted on 6 October 2026. The practical checklist proposes management checks; its application should reflect each organisation’s scope.

Request a Demo

Discover all that Sabentis can do for your organization.

Try Sabentis

request a demo
stars 5
GetApp Software Advice Capterra