Skip to content
Log in DE Arrange a meeting

Knowledge · Risk acceptance

What is residual risk, and who decides whether to accept it?

Residual risk remains despite protective measures. Who may assess and accept it, where the limits lie and why documentation matters.

Updated: · MOVETOS

Residual risk is the risk that remains after protective measures have been implemented and taken into account. Even carefully planned security measures cannot rule out every hazard completely. Assessing residual risk is therefore an essential part of security management.

How does residual risk arise?

At an event, technical systems, security staff and organisational procedures can, for example, reduce the risk of dangerous crowding. A remaining risk from unexpected crowd movements or simultaneous disruptions cannot be ruled out in principle.

In industry and critical infrastructure, too, certain failure scenarios can remain despite backup power, access protection and emergency planning.

Who may accept a residual risk?

The decision depends on the legal requirements, the responsibilities and the defined decision-making authority.

Responsible partyTask
Specialist planners and expertsInvestigate and assess risks and recommend measures
Operators or organisersAssess remaining risks and make decisions within their own area of responsibility
AuthoritiesMonitor legal requirements and issue permits or orders within their competence

Not every residual risk may be accepted. Legally required protective measures, binding limit values and official conditions cannot be set aside by a business decision.

Why does documentation matter?

The risk assessment should record in a traceable way which hazards were identified, which measures are planned, which risks remain and on what basis decisions were made.

It should also define when a new assessment is required, for example when visitor numbers change, new hazards arise or safety-relevant functions fail.

Accepting risk does not mean handing off responsibility. It means consciously assessing remaining risks within the legal limits, justifying decisions and monitoring the conditions on which they rest.

A decision to accept a residual risk is only possible within applicable legal duties, official requirements and actual decision-making authority. A blanket legal “release from liability” through documentation does not exist.

Legal bases (Germany)

Legal sourceMeaning / scope
ArbSchG §§ 3–6Employer duties, principles of hazard avoidance, risk assessment and documentation; no free acceptance of inadequate protective measures.
BetrSichV §§ 3–4Risk assessment and protective measures for work equipment; remaining hazards are to be handled as the rules require.
ArbStättV §§ 3a, 4Safety and health protection in workplaces; observe the specifying technical rules (ASR).
BGB § 823 para. 1Possible liability for damages where duties of care are breached through fault; assessed case by case.
StGB §§ 222, 229Negligent homicide or bodily harm where all elements of the offence are met; not every realised risk is a criminal offence.
State assembly venue ordinances (e.g. BayVStättV §§ 38, 43)Operator responsibility and, where applicable, a security concept; applicability depends on the venue and state law.
KRITIS-Dachgesetz §§ 12–13Risk analysis and resilience measures for covered operators; check scope of application and the staggered start of obligations.

Technical standards and orientation

  • DIN ISO 31000: guidelines on risk management, including the assessment and treatment of risks.
  • DIN EN IEC 31010: methods for risk assessment.
  • BSI Standard 200-3: risk analysis based on IT baseline protection.

These documents are not generally legally binding merely because they exist; their binding nature can arise from specialist law, contracts or official conditions.

Editorial note: Risk acceptance is to be separated from the technical risk analysis. Specialist planners can prepare a decision; competent operators or responsible persons must decide within their authority. Authorities decide within their statutory competence. Acceptance criteria, residual risks, measures, responsibilities and triggers for reassessment should be documented in a traceable way.

Read more: Binding requirements and professional assessment in event security, Organiser responsibility when contractors take on security tasks, Commissioning safety planning: which competences are needed for which tasks, Germany’s KRITIS Umbrella Act: physical protection explained and Security decisions to settle before requesting quotations.

Context: research as of 19 November 2026. Editorial overview; the provisions and standards named have not been checked against the original texts. Their binding force and currency must be checked for the individual project; state law in the relevant state legal portal. General guidance, not legal advice.

Sources

  1. ArbSchG §§ 3–6, BetrSichV §§ 3–4, ArbStättV §§ 3a, 4, BGB § 823 para. 1, StGB §§ 222, 229 (www.gesetze-im-internet.de; German law). State law (e.g. BayVStättV §§ 38, 43) in the relevant state legal portal.
  2. KRITIS-Dachgesetz §§ 12–13 (German law): check scope of application and the staggered start of obligations.
  3. DIN ISO 31000 and DIN EN IEC 31010 (via DIN Media); BSI Standard 200-3 (www.bsi.bund.de).

Read on

Events, companies or critical infrastructure: we will show you how MOVETOS OPS does this in practice.