ISO 12100 • hazard scenarios • risk reduction • residual risk

Machine Risk Assessment Documentation
from machine limits to residual risk

Safety Software builds machine risk assessment documentation from process data: machine limits, tasks and operations, hazard sources, hazardous situations, hazardous events, risk estimation, risk reduction measures, photos, secondary hazards, residual risk and decision history.

Build your risk assessment documentation See what the report captures
Machine Risk Assessment Documentation

Risk assessment documentation is not just a PDF you generate at the end.

What matters in the real world is whether you can reconstruct the logic: which machine limits were assumed, which tasks and operations were analysed, where the hazard comes from, which hazardous situation and hazardous event were described, how the risk was estimated, and why specific risk reduction measures were selected.

Safety Software keeps all of that in one structured model, and the report is simply a view of the process: it shows decisions, parameters, photos, standards, risk reduction measures, secondary hazards and residual risk.

For teams that want to document risk assessment step by step instead of stitching a report together by hand from multiple sources

What does machine risk assessment documentation capture?

Machine, project and limits
Project name, machine model, reference number, assessment version, assessor, manufacturer, intended use, reasonably foreseeable misuse and the limits of the machine.
ISO 12100 hazard scenarios
Task or operation, hazard source, category, hazard zone, hazardous situation, hazardous event, consequences and visual evidence.
Estimation method and parameters
Selected assessment method, risk category thresholds, HRN/RPN/risk graph/matrix input parameters, and the initial risk result with a decision on whether risk reduction is required.
Risk reduction and residual risk
Risk reduction measures across the three ISO 12100 steps, linked standards or documents, verification method, secondary hazards, iterations and residual risk acceptability.

The report shows the decision path, not just a list of hazards.

The real value is in the links between the data: scenario, estimation, decision, risk reduction measure, verification and residual risk.

What the documentation needs
What Safety Software captures
Machine limits
Intended use, reasonably foreseeable misuse, spatial and time limits, and operating conditions.
A separate project context and assessment scope that hazard scenarios can always link back to.
ISO 12100 scenario
Task, hazard source, hazardous situation, hazardous event and possible consequences.
A structured scenario description so the team can see exactly what was assessed.
Risk estimation
Method, criteria, result, category and the decision on whether risk reduction is needed.
Visible estimation parameters and rationale, instead of just a number dropped into a table.
Risk reduction measures
Inherently safe design, technical or organisational measures, and information for use.
Each risk reduction measure linked to the standard, evidence, verification method and its effect on residual risk.
Residual risk
Acceptability assessment, rationale, secondary hazards and information needed in the instructions.
A final decision with context, change history and material ready for the risk assessment report.
trace:
  actor: Anna K.
  decision: reduction_effective
  subject: feeder zone
  changed_at: 2026-05-12 14:30
Decision history

Who changed the assessment, when, and why?

The report draws on process data: task statuses, risk reduction decisions, changes to risk reduction measures, residual risk iterations, the user making the decision, and the exact time of change.

  • task or operation status change
  • decision on risk reduction effectiveness
  • return to the assessment after a design change or audit
Evidence at scenario level

Photos, standards and verification right next to the risk reduction measure.

For each hazard, you can keep visual evidence, the scenario description, assessment parameters, the applied risk reduction measures, linked standards or documents, and the verification method.

  • photo or description of the hazard zone
  • linked standard or document
  • verification method for the risk reduction measure
protective_measure:
  step: technical_measure
  standard: EN ISO 13857
  verification: safety distance measurement
  evidence: photo_042.jpg
residual_risk:
  category: low
  acceptable: yes
  rationale: guard + cleaning instructions
  user_information: warning_label_required
Residual risk

After risk reduction, what remains is a decision — not just another paragraph.

Safety Software captures residual risk, its acceptability, the rationale, the risk reduction measures, and the information that should go into the instructions or user communication.

  • risk acceptability after reduction
  • rationale for the technical decision
  • information for the operating instructions
Boundary of responsibility

The report supports the manufacturer, but it does not make the decision for them.

Risk assessment documentation in Safety Software does not certify the machine and does not make decisions on the manufacturer’s behalf. It structures the data, parameters, rationale and decision history.

  • the tool structures the process
  • the manufacturer keeps responsibility for the decision
  • the technical conclusion has a traceable context
boundary:
  software_role: documentation_support
  producer_role: final_decision
  output: risk_assessment_report
  certification: not_automatic

Common questions about machine risk assessment documentation

Is this a risk assessment report or the machine’s full technical documentation?
This is the machine risk assessment documentation module. It structures the data needed for the risk assessment report: machine limits, tasks, hazard scenarios, estimation, risk reduction measures, residual risk, photos and decision history. Full machine technical documentation may also include other documents such as schematics, calculations, instructions, declarations, test reports and design documentation.
Does the report cover life-cycle phases and machine limits?
Yes. The process starts with the limits of the machine and the project context. Within the scenarios, you can describe life-cycle tasks, operations, zones, hazard sources and situations that matter to the risk assessment.
Which risk estimation methods does the documentation support?
The report uses the selected risk assessment method, for example HRN, RPN, a risk graph or a matrix. It shows the input parameters, thresholds, result, category and the decision on risk reduction.
Are risk reduction measures presented in line with ISO 12100 logic?
Yes. The documentation separates risk reduction measures into steps: inherently safe design, technical or organisational measures, and information for use. You can also keep linked standards, documents and the verification method alongside each measure.
Does the report show residual risk?
Yes. Residual risk, acceptability, rationale, iterations and user information are part of the documentation. If secondary hazards appear, they can be included in the analysis as well.
Does the module replace the manufacturer’s responsibility?
No. Safety Software structures the data and reports the decision path, but it does not certify the machine and it does not make decisions on the manufacturer’s behalf.
Is the PDF report always available?
PDF report generation depends on permissions and the feature plan. The risk assessment itself remains structured inside the application, and the report is simply an export of the process data.

Stop assembling risk assessment documentation by hand once the project is over.

Build it from the very first machine limit: scenarios, estimation, risk reduction, photos, standards, secondary hazards, residual risk and decision history in one connected process.

Start your risk assessment documentation

The best place to start is one machine and one risk assessment version that the team can run step by step.

Practical articles on risk assessment, machinery directives and compliance — supporting this product page.