Statutory occupational risk prevention audits in Spain: organising software evidence and access

Preparing a statutory occupational risk prevention audit in Spain often reveals an organisational problem: the information exists, but reconstructing a case requires searching several folders and asking several people. Software is useful when it preserves the relationship between assessment, preventive decision, implementation and verification.
Preparation should support a faithful review of actual management. A folder assembled solely for the visit may conceal inconsistencies between documents or versions—the very issues worth identifying before the audit starts.
Confirm the audit scope
Articles 29 onwards of the Regulations for Prevention Services (in Spanish) govern audits of the preventive system. The requirement, scope and frequency depend on the applicable circumstances. Digital preparation should follow that determination and the audit engagement, rather than apply one schedule to every company.
The entry on OSH audits helps distinguish this process from other reviews. Document the entities, sites, activities and period being examined. Identify contacts and the method for requesting additional samples during the work.
Build an evidence index people can use
Organise documentation around management questions: how risks are identified, how action is decided, who implements it and how results are verified. For each area, identify the original source and its owner. The index should lead to current documents and relevant historical versions.
- Prevention organisation and documented responsibilities.
- Assessments with context, dates and reviews.
- Action planning and follow-up.
- Information and training linked to work.
- Relevant investigations, reviews and improvement decisions.
This list guides preparation and should be adapted to the actual scope. Preventive documentation involves more than collecting files: reviewers need to understand what each item demonstrates and how it relates to operations.
Test a sample from beginning to end
Select a job and a completed action. Find the source assessment, decision, owner, deadline, implementation evidence and verification. Check whether dates and versions tell a coherent story. If a link is missing, improve record organisation without inventing past activities.
Repeat the exercise with an open action. The audit also needs to understand outstanding matters and their follow-up decisions. An unresolved situation may have a justified plan; hiding it or retrospectively changing its date undermines the reliability of the record.
Prepare limited, understandable access
Agree with the auditor how information will be consulted: temporary access, a controlled folder or assisted sessions, depending on the service and engagement. Define the entity and documentation boundaries. Check download rights, recorded activity and when access ends.
Test an account equivalent to the one that will be used. Open attachments, follow links and review filters. A folder containing links that only work for an administrator forces improvisation during the audit and can lead to unnecessary information sharing.
An example of a useful discrepancy
In a fictional company, the software shows a maintenance action as closed, but the attachment concerns another piece of equipment. Preparation exposes the error and prompts a discussion with the owner. If correct evidence exists, it is added with its provenance; otherwise, the gap is recorded and necessary verification is decided.
The value lies in making the real situation visible. Digital evidence is stronger when it identifies who added a document and why a relationship was corrected.
Record questions that remain unresolved before the opening meeting. Assign an internal contact to each and identify the source needed for an answer. This supports a factual discussion and avoids expecting one coordinator to reconstruct every technical decision from memory.
Prepare for what happens afterwards
Agree how findings, decisions and resulting actions will be recorded. Each action needs an owner, date and closure criterion. Keep the report reference and distinguish a response sent to the auditor from internal verification that the improvement works.
If an index reference is corrected during preparation, retain the original document identifier, the reason and the person who verified the new relationship. The auditor can then distinguish an improvement in document organisation from preventive work carried out after the period being examined.
Reviewing overdue actions helps resolve barriers; managing in-house and shared prevention services provides organisational context. When evaluating Sabentis, use an anonymised sample to test case reconstruction and controlled access. Good preparation reduces searching and makes the management under review easier to understand.
Checks before giving the auditor access
A short document-retrieval exercise can reveal obstacles that reviewing an index will miss. Ask someone who did not assemble the folder to perform it and record which information they must request outside the system.
- Check that a search by job also retrieves former job names and sites reorganised during the audited period.
- Open a historical document and confirm that it is clearly distinguishable from the version currently in force.
- Test a restricted attachment using the agreed viewing profile, without unnecessarily expanding access to other records.
- Identify evidence that needs technical explanation and who will be available to clarify it during the audit.
- Test withdrawal of temporary access and establish how outstanding document requests will remain available for follow-up.
Frequently asked questions
Does an internal audit replace a statutory prevention audit in Spain?
That equivalence should not be assumed. Spanish statutory audits have their own regime under the Prevention Services Regulation. Before configuring the case, establish which review the business needs and which requirements concerning scope and independence apply to that review.
Does the auditor need an administrator account?
As a preparation measure, first define what the auditor needs to consult and how additional information will be requested. Test that scope using an equivalent profile. A demonstration through an administrator account cannot establish whether the agreed access will work during the review.
How should evidence added after the audited period be presented?
Identify both the date of the activity and the date when its document was added. Explain its provenance and any limits on reconstructing the case. Retaining both references prevents a recent filing improvement from appearing to be an activity completed at a different time.
What if a document requested by the auditor cannot be found?
Record the request, the person responsible for searching and the outcome. If it remains unavailable, communicate the gap and determine the appropriate checks. Creating an unsupported retrospective record would introduce greater uncertainty than acknowledging the absence of evidence.
Legislation and sources consulted
- Royal Decree 39/1997: Spain: chapter V sets out the regime for prevention-system audits.
- Law 31/1995 on occupational risk prevention: Spain: the prevention framework and its management documentation.
Sources consulted on 6 October 2026. The practical checklist proposes management checks; its application should reflect each organisation’s scope.



