Risk Management
Definition
Risk Management
Risk management is the practice of identifying what could stop a company meeting its goals, judging how serious each threat is, and deciding what to do about it. Risk management is a continuous discipline, not a document, and its output is decisions, not registers.

The discipline is deliberately general. The same four responses apply whether the risk is a currency movement, a ransomware incident or a provider going insolvent.
What changes is the specialism. Enterprise, third-party, operational and security risk are applications of one method to different threat surfaces.
Outsourcing adds a particular wrinkle. Work can be delegated to a provider, but accountability for the outcome stays with the buyer — so the risk moves without the responsibility following it.
Key takeaways
- Risk management identifies, assesses, treats and monitors threats to objectives.
- Four treatments exist: avoid, reduce, transfer and accept.
- Specialisms such as enterprise and third-party risk apply one method to different surfaces.
- Delegating work to a provider never delegates accountability for the outcome.
How it works
The cycle is consistent regardless of domain. Identify what could go wrong, assess likelihood and impact, choose a treatment, assign an owner, then monitor whether the treatment is still working as conditions change.
Assessment produces a ranking rather than a certainty. Likelihood and impact are both estimates — which is why the register is a prioritisation tool rather than a forecast.
Treatment is where the method becomes a decision. Each risk resolves into one of four responses, and naming which one was chosen is what makes the choice auditable later.
| Treatment | What it means | Typical example |
|---|---|---|
| Avoid | Stop doing the thing that creates the risk | Declining to process card data in-house |
| Reduce | Lower likelihood or impact with controls | Multi-factor authentication on privileged access |
| Transfer | Move the financial consequence elsewhere | Insurance, or an indemnity in a contract |
| Accept | Carry it knowingly, with a trigger to revisit | A tolerable single-supplier dependency |
Transfer is the one most often misread. Moving the financial consequence through insurance or an indemnity is a risk transfer strategy, not a way of making the risk itself disappear.
Formal frameworks give the cycle structure.
The National Institute of Standards and Technology published its Risk Management Framework in Special Publication 800-37 Revision 2, dated December 2018, covering categorisation, control selection, authorisation and continuous monitoring.
Continuity planning is the operational counterpart. The United States government’s continuity guidance sets out a six-step process from preparing a team through to testing the plan, which is the step most organisations skip.
International standards codify the same cycle. The International Organization for Standardization publishes ISO 31000, its guidelines for managing risk, which apply to any organisation whatever its sector or size.
Monitoring is what separates the discipline from the paperwork. A register nobody revisits records the risks of the year it was written.
Examples
Risk management becomes concrete when the threat surface is named. The three cases below show the same cycle applied to a supplier, to an operation and to a geography.
A buyer concentrating a critical process with one offshore provider holds a supplier concentration risk. Reduce it with a second delivery site, transfer part of it through contractual remedies, or accept it explicitly with a review trigger.
A contact centre in a typhoon-exposed market carries a continuity risk. The treatment is geographic separation and tested home-working fallback — which is why buyers should ask to see the test results rather than the plan.
A provider holding privileged access to production systems creates a security risk the buyer cannot delegate. Controls sit in access scoping and monitoring, and the obligation to regulators stays with the buyer throughout.

A single-currency pricing arrangement carries financial risk for whichever party absorbs the movement. Naming who carries it in the contract is cheaper than discovering it during a devaluation.
Related terms
Risk management is a method; most glossary entries nearby are applications of it to one threat surface. The distinctions below keep the general discipline separate from its specialisms, which is where most reporting confusion starts.
- Enterprise Risk Management: the single company-wide application of this method, consolidated into one register the board reads.
- Third Party Risk Management: the application covering suppliers, vendors and outsourcing providers.
- Risk Outsourcing: contracting risk and compliance functions themselves to an external specialist.
- Governance Risk Compliance: the combined operating model linking oversight, risk and regulatory obligation.
- Risk Based Approach: the principle of directing effort in proportion to assessed risk.
- Risk Register Template: the standard structure used to record risks, owners and treatments.
FAQ
What is the difference between risk management and enterprise risk management?
Risk management is the general discipline. Enterprise risk management is its company-wide application, consolidating departmental registers into one view for the board.
Can risk be eliminated?
No. It can be avoided, reduced, transferred or accepted, but an organisation that pursued zero risk would have to stop operating.
Does outsourcing transfer risk?
It transfers the work and some financial consequence, not accountability. Regulators and customers continue to hold the buyer responsible for the outcome.
How often should a risk register be reviewed?
At least quarterly, and immediately after any material change such as a new provider, a new market or an incident.
Who should own a risk?
A named individual with the authority to act on it, never a committee or a department.
What makes risk management fail in practice?
Treating the register as the deliverable.
Compare providers and their governance practices through Outsource Accelerator before committing a critical process.







Independent




