Risk register or ERM: what a small team needs

The two are not alternatives. A risk register is one part of enterprise risk management. The useful question is how much of the rest you need yet.

A risk register is a list of the things that could hurt the business, each rated, owned and tracked. Enterprise risk management (ERM) is the practice of deciding how much risk you will accept and checking, on a regular rhythm, that you are inside it. A startup can have the first for years before it needs much of the second, but five small habits close most of the gap.

What each one is

A risk registerEnterprise risk management
What it is A list of risks with a rating, an owner and what you are doing about each The whole routine: finding risks, rating them the same way, deciding what to accept, acting, and reporting to the people who run the business
Who it is for Anyone, from one founder up A business where leaders need one consistent picture of risk across teams
What it answers What could go wrong, and who is dealing with it Is our total risk acceptable, and is it moving the right way
What it needs A list and someone who keeps it up to date A shared rating scale, an agreed appetite, named owners, a review rhythm and a way to report

When a register is enough

A small team with a handful of risks, one person who owns them, and nobody outside the company asking to see them. Keep it in one place, review it on a fixed day each month, and give every risk a named owner. Most startups are here for a long time, and that is fine.

The five things to add before you need "ERM"

  1. One rating scale. Use the same likelihood and impact scale for every risk, so a High in finance means the same as a High in operations.
  2. An owner for each risk. A name, not a team. A risk with no owner is not being managed.
  3. Controls, tested. List what you actually do about each risk, and check now and then that it still works. A control nobody has tested is a hope.
  4. An appetite. Decide in advance how much risk is too much, so the register has something to be measured against.
  5. A review rhythm. A fixed monthly or quarterly slot, with one page for whoever leads the company.

With those five in place, a register is doing the working job of ERM for a small company.

Signs you need more than a register

Where this guide stops

This is general guidance for a small business, not advice on what any regulator requires. A bank, insurer or other regulated firm has prescribed requirements that go well beyond five habits. For a full approach to the subject, ISO 31000 sets out principles, a framework and a process for any size of organisation, and the COSO framework has been widely adopted.

How Vetrail fits

Vetrail's free register gives a small team the five habits above in one place: one rating scale, an owner and a date for each treatment, controls that come back for testing, an appetite shown against the register, and a next-review date on each risk. It also records incidents and what they cost. It does not track key risk indicators. See the free ERM and ORM options for a small team for how it compares with the alternatives, or look at how the register works.

Start free  or take the free risk assessment first

Questions

Is ERM only for big companies?
The full machinery is, but the idea is not. A small team can run the core of it with a register, an appetite and a review slot.

What is the difference between ERM and operational risk management?
Operational risk is the risk of loss from processes, people, systems and outside events. ERM is wider and also covers strategic and financial risk. A small business often starts with the operational register and grows outward.

Do I need ISO 31000 or COSO?
Neither is required for a small company, and ISO 31000 is not a standard you can be certified against. They are useful references once you want a more formal approach.

Sources

Vetrail is not affiliated with ISO or COSO. Last checked 22 October 2026.

Related