Software for risk assessment maps the three-step method of EN ISO 12100 digitally: it structures hazard identification with prepared hazard catalogues, evaluates risks with a traceable method such as a risk graph, documents the protective measures following the three-step method and links the residual risks to the instructions for use. Compared with a spreadsheet it gains through reusability, consistent evaluation and complete traceability.
Many risk assessments are still produced in spreadsheets. That works for a single machine but scales badly and becomes risky with every change.
Similar machines have similar hazards. Software keeps hazard catalogues and evaluations you have already worded, so you can carry them over to the next product line and adjust only the differences. In a spreadsheet you copy files instead and maintain changes laboriously by hand.
Software enforces the same evaluation logic for every hazard, for instance a single risk graph with severity of harm, frequency and possibility of avoidance. Different people then evaluate comparably, and the results stay sound across projects.
Every hazard, every measure and every re-evaluation is documented and linked. In market surveillance, after an accident or during a substantial modification, you can show without gaps why a particular protective measure was chosen. A grown spreadsheet with overwritten cells cannot do that.
Standard wording, references to standards and templates are stored, the iterative re-evaluation after a measure is guided, and the export into the technical documentation happens at the push of a button. The time saved goes into the actual safety analysis instead of formatting and copy-and-paste.
Not every piece of software covers the whole process. These criteria separate a tool for a plain hazard list from a real solution for risk assessment.
| Criterion | What matters | Why it matters |
|---|---|---|
| Coverage of standards | Maps EN ISO 12100 and the three-step method completely | The basis of the presumption of conformity and of an audit-proof evaluation |
| Hazard catalogues | Maintainable libraries of typical hazards per machine type | Prevents gaps and speeds up identification |
| Evaluation method | A single risk graph or risk matrix | Produces consistent, comparable results |
| Iterative evidence | Re-evaluation after every measure, documented | Demonstrates the actual reduction in risk |
| Link to instructions | Residual risks feed into warnings and the instructions | Avoids breaks between assessment and instructions |
| Export | Output into the technical documentation | The result is directly part of the CE documentation |
| Machinery Regulation | Templates and references at the level of the Regulation | Binding from 20 January 2027, with no transition period |
Software is a tool, not a finished assessment. Whether you produce it yourself or outsource depends on capacity, frequency and complexity.
| Aspect | Doing it yourself with software | Having it done |
|---|---|---|
| Suits | Recurring documentation, series and standard machines | Complex assemblies, one-off projects, little capacity |
| Competence | Safety knowledge stays and grows in house | External engineering competence takes on the assessment |
| Effort | Some learning first, then fast and repeatable | Little effort of your own, the result arrives finished |
| Responsibility | Stays entirely with the manufacturer | Technical support, the manufacturer's duty stays with the manufacturer |
A combination is often sensible: produce standard machines yourself with software, and have a safety engineer accompany critical projects or linked assemblies. That keeps the competence in house without leaving you alone on the difficult cases.
Editions of standards and their harmonised status change continuously. Check standard numbers and editions against the current list in the Official Journal of the EU before applying them. This article is a technical classification and does not replace legal advice.
It leads you through the procedure of EN ISO 12100: it structures hazard identification with hazard catalogues, evaluates risks with a single method such as a risk graph, documents the protective measures following the three-step method and links the residual risks to the instructions for use. The result feeds directly into the technical documentation for CE marking.
For a single simple machine a spreadsheet can be enough. As soon as you have several machines, variants or recurring assessments, software becomes markedly more efficient and safer. It gives you consistent evaluation, reusable hazard lists and complete traceability, which a grown spreadsheet with overwritten cells cannot offer.
The basis is EN ISO 12100, the basic standard for risk assessment and risk reduction. It describes the three-step method: first inherently safe design, then safeguarding, and last information for use. Good software maps this method completely and keeps the state of standards current for Machinery Regulation (EU) 2023/1230.
What matters is full coverage of EN ISO 12100 and the three-step method, maintainable hazard catalogues, a consistent evaluation method such as a risk graph, iterative re-evaluation after every measure, the link between residual risks and the instructions for use, export into the technical documentation and templates at the current state of the standards.
That depends on the tool. Check that templates and references to standards are at the level of Machinery Regulation (EU) 2023/1230. It applies from 20 January 2027 with no transition period and replaces Machinery Directive 2006/42/EC. The risk assessment procedure to EN ISO 12100 stays the same at its core, but some duties and templates change.
No. Software is a tool that structures and speeds up the process. The technical evaluation of the hazards and the choice of protective measures remain an engineering task. For standard machines a guided tool supports the user effectively; for complex assemblies additional expertise is advisable.
Both are possible. For recurring assessments and standard machines you produce the risk assessment yourself with guided software. For complex assemblies, linked systems or when capacity is missing, you outsource it as an engineering service. A combination is often sensible: standard cases yourself, critical projects accompanied.
Has been guiding CE projects in machinery, plant and special purpose engineering for years. That work led to Kaidoc.app, a software for standards-based CE documentation. Through Knutec.de the same work is available as a personal service.
Write me a few lines about your project. You get a first assessment back, free of charge and without obligation.
This article was produced with AI assistance and reviewed for technical accuracy before publication. Editorial responsibility within the meaning of Art. 50(4) of the AI Act (EU) 2024/1689 lies with Heinrich Knutas.
No credit card required. A complete project to try out.