Every organization manages risk, whether it calls the work risk management or not.

A small business decides whether to rely on one supplier. A nonprofit considers what would happen if a grant ended. A clinic manages patient safety, staffing, privacy, medications, equipment, and technology. A public organization balances service obligations, funding requirements, workforce capacity, and public trust.

Those decisions are often made separately, by different people, at different times.

Enterprise-wide risk management—often shortened to enterprise risk management or ERM—creates a way to see those risks together.

What enterprise-wide risk management means

ERM is a coordinated process for identifying uncertainty that could affect an organization's objectives, evaluating its significance, deciding how to respond, assigning responsibility, and monitoring what changes.

The word enterprise does not mean the organization must be large. It means the view extends across the organization rather than remaining inside one department or specialty.

A useful ERM process may consider:

  • Strategic and financial risk
  • Operations, staffing, succession, and institutional knowledge
  • Legal, contractual, regulatory, and grant requirements
  • Safety, facilities, equipment, chemicals, medications, and controlled items
  • Technology, cybersecurity, privacy, and data availability
  • Vendors, supply chains, insurance, and external partners
  • Service quality, customer or patient experience, and reputation
  • Emerging opportunities that may create both benefit and exposure

The purpose is not to eliminate all risk. Organizations could not operate, grow, innovate, or serve people if every uncertainty had to disappear first.

The purpose is to make risk visible enough that leadership can make informed choices.

ERM and continuity planning are connected—but different

Continuity planning asks how essential work will continue or resume when normal operations are disrupted. It identifies critical functions, dependencies, alternate arrangements, decision authority, communications, vital records, recovery priorities, and the resources required to operate under difficult conditions.

Enterprise risk management asks a broader question:

What could affect our ability to achieve our objectives, and how should we respond before, during, and after that risk develops?

A continuity plan may prepare for a prolonged power outage. ERM also considers the aging electrical system, insurance limits, deferred maintenance, vendor dependencies, cost of replacement, workplace safety, and whether leadership has accepted more exposure than it realizes.

A continuity plan may address how to restore technology after an incident. ERM also considers who owns cybersecurity decisions, which data are most important, whether vendors are adequately managed, and how much technology risk the organization is willing to accept.

Continuity planning is therefore an important risk treatment—but it is not the entire risk-management system.

Frameworks can provide structure without taking over the work

Organizations do not have to invent a risk-management approach from the beginning.

ISO 31000 provides principles, a framework, and a process for identifying, analyzing, evaluating, treating, monitoring, reviewing, recording, and communicating risk. It can be adapted to organizations of any size or sector. ISO 31000 provides guidance; it is not a certifiable standard.

COSO Enterprise Risk Management places greater emphasis on connecting risk with governance, strategy, performance, review, and communication. It can be especially useful for boards, executive teams, finance leaders, and organizations with more formal governance structures.

Neither framework needs to be implemented word for word. A small organization can use the principles without building a program too complicated to maintain.

The most useful starting tool may be a risk register

A risk register is a structured list of risks and the decisions made about them. It can begin in a spreadsheet.

At its most basic, it should record:

  • Objective or function affected: What work, service, commitment, or result could be affected?
  • Risk statement: What might happen, why might it happen, and what could the consequence be?
  • Category: Operational, financial, workforce, compliance, safety, technology, vendor, reputation, or another useful grouping.
  • Likelihood and impact: How plausible is the event, and how serious could the effect be?
  • Existing controls: What is already reducing the likelihood or impact?
  • Risk owner: Who has authority and responsibility to monitor the risk?
  • Planned treatment: Will the organization avoid, reduce, transfer, share, accept, or pursue the risk?
  • Action owner and due date: Who will complete the agreed work, and by when?
  • Residual risk: What exposure remains after the controls or actions?
  • Status and review date: When will leadership reconsider the risk?

The scoring method matters less than consistency. A three-level scale—low, moderate, and high—may be more useful than a complex calculation no one trusts or updates.

Risk looks different in different operating environments

A general risk register should not replace specialized safety, clinical, environmental, privacy, financial, or regulatory processes.

A clinic may need to address patient safety, medication handling, infection prevention, medical equipment, privacy, staffing credentials, referrals, and continuity of care. A laboratory or manufacturer may need chemical inventories, safety data sheets, exposure controls, hazardous-waste practices, process hazards, emergency procedures, maintenance, and management of change.

Federal requirements can become highly specific when covered quantities or activities are involved. OSHA's Process Safety Management standard applies to defined processes involving certain highly hazardous chemicals or specified quantities of flammable materials. EPA's Risk Management Program under 40 CFR Part 68 applies to covered stationary sources using regulated substances above applicable thresholds.

The ERM process should point leadership toward these specialized obligations and qualified professionals. It should not pretend that one universal checklist is sufficient.

IT risk belongs inside the enterprise view

Technology risk is sometimes treated as a technical matter owned entirely by an outside provider or one knowledgeable employee.

But the consequences are organizational.

A failed system can interrupt payroll, scheduling, billing, clinical work, customer communication, grant reporting, purchasing, records access, or regulatory reporting. A vendor incident can expose information the organization remains responsible for protecting. A backup that exists but cannot be restored may provide confidence without providing recovery.

An enterprise risk register should therefore identify the organization's major technology and data risks, while a separate IT risk-management plan provides the necessary detail about systems, safeguards, incidents, recovery, vendors, and accountability.

Keep the process connected to decisions

A risk register that is completed once and stored away is not risk management.

Risk information becomes useful when it is considered during budgeting, contracting, hiring, technology purchases, service changes, grant planning, facility decisions, and board or leadership review.

A small organization might review its highest risks quarterly and the full register annually. It should also update the register when a significant incident, leadership transition, new contract, system change, regulatory development, or expansion changes the operating environment.

The review should end with decisions:

What changed?

Which risks now require action?

Who owns the next step?

What exposure is leadership choosing to accept?

When will the decision be reviewed?

BERIDIAN helps organizations turn scattered concerns into a practical, maintainable view of risk. That can include defining risk categories, building a right-sized register, clarifying ownership, connecting risk decisions to continuity and operational planning, and creating a review process leadership can actually use.

Good risk management does not make uncertainty disappear. It makes important uncertainty easier to see, discuss, assign, and act on.

Next in this series: IT Risk Is Organizational Risk: Building a Practical Technology Risk Management Plan.

Sources and Further Reading

  1. International Organization for Standardization. ISO 31000:2018, Risk management—Guidelines.
  2. Committee of Sponsoring Organizations of the Treadway Commission. Enterprise Risk Management resources.
  3. Federal Emergency Management Agency. Continuity Guidance Circular, 2024 update.
  4. Occupational Safety and Health Administration. 29 CFR 1910.119, Process Safety Management of Highly Hazardous Chemicals.
  5. U.S. Environmental Protection Agency. Risk Management Program under Clean Air Act Section 112(r) and 40 CFR Part 68.

This article provides general operational information and is not legal, regulatory, clinical, environmental, cybersecurity, accounting, or insurance advice. Organizations should confirm the requirements applicable to their activities, industry, contracts, and jurisdiction with the appropriate professional or regulatory authority.