Lizzard Solutions

IT Risk Assessment Template for Small Business (5x5 Matrix)

· Lizzard Solutions
CybersecurityRisk AssessmentTemplatesSmall BusinessIT Management

By Nemanja Vukmirović, Lizzard Solutions. Last updated 19 November 2026.

You know your business has IT risks, but the list feels endless: phishing, ransomware, lost laptops, a vendor breach. Without a way to rank them, you either spend on the wrong things or put the whole topic off.

This IT risk assessment template gives you a one-page method: a simple 1 to 5 scoring scale, a risk register you can copy into a spreadsheet, and a worked example for a 10-person office. You can finish a first version in an afternoon.

TL;DR

  • Score each risk by likelihood (1-5) and impact (1-5). Multiply them to get a score from 1 to 25 and fix the highest scores first.
  • For every risk, pick one treatment: reduce, transfer, avoid or accept, and give it an owner and a deadline.
  • Review the register every six months and after any incident, new system or new vendor.

What is an IT risk assessment?

An IT risk assessment is a structured review of what could go wrong with your systems and data, how likely each event is, and how much damage it would cause. The result is a ranked list of risks with an agreed action, owner and deadline for each one.

Large frameworks such as NIST SP 800-30, the US guide for conducting risk assessments use the same core idea: risk is a combination of likelihood and impact. A small business does not need the full method, just a consistent scale and the discipline to act on the results.

It also supports legal duties. Under Article 32 of the GDPR, organisations that process personal data must apply security measures appropriate to the risk, which is hard to show without a written assessment.


Step 1: list what you need to protect

Start with assets, not threats. Write down the systems and data the business cannot work without: email, accounting software, client files, the website, laptops and phones, cloud apps and the people with admin access.

If you already keep an inventory, use it. If not, our IT asset inventory template gives you the columns to fill in first.

Action for today: list your 10 most important systems and data sets, with one owner for each.


Step 2: score likelihood and impact (the 5x5 scale)

For each asset, ask what could realistically go wrong. Then rate every risk on two scales. Use the same definitions every time, or the scores will not be comparable:

ScoreLikelihoodImpact
1Very unlikely in the next 3 yearsMinor annoyance, fixed in an hour
2Could happen once in 3 yearsSome work lost, fixed within a day
3Could happen about once a yearSeveral days of disruption or a small cost
4Likely several times a yearLost clients, serious cost or data exposure
5Almost certain, or already happeningBusiness stops, legal or reputational damage

Multiply the two numbers. 15-25 is critical (act this month), 10-14 high (act this quarter), 5-9 medium (plan it) and 1-4 low (usually accept and monitor).

Tip

Score likelihood with whoever runs IT day to day, and impact with the owner or manager. People who own the money judge impact more realistically than the people who own the servers.


Step 3: fill in the risk register

The register is the actual template. One row per risk, with these columns: Risk, Asset, Likelihood, Impact, Score, Treatment, Owner, Deadline, Status. Here is a worked example for a 10-person accounting office. The scores are illustrative estimates, not measured data.

RiskAssetLIScoreTreatmentOwner
Phishing email leads to a hijacked email accountEmail, client data4416 (Critical)Reduce: MFA on all accounts, phishing awareness sessionOwner
Ransomware encrypts the shared file serverAccounting files3515 (Critical)Reduce: offline and cloud backups, tested restoreIT partner
Former employee still has access to systemsEmail, cloud apps3412 (High)Reduce: offboarding checklist, quarterly access reviewOffice manager
Laptop is lost or stolenLaptops339 (Medium)Reduce: full-disk encryption, remote wipeIT partner
Software vendor suffers a data breachClient data at vendor248 (Medium)Transfer and reduce: contract clauses, vendor questionnaireOwner
Company website is defaced or goes downWebsite236 (Medium)Reduce: updates, uptime monitoring; Accept the restWeb agency

Notice that the top risks are the cheapest to fix. Multi-factor authentication and tested backups cost little but move two of the highest rows down significantly.

Action for today: copy the columns into a spreadsheet and add at least the six example risks, scored for your own business.


Step 4: choose a treatment for each risk

Every risk gets exactly one main decision:

  • Reduce: add a control that lowers likelihood or impact, such as MFA, backups or encryption. This is the default for high and critical risks.
  • Transfer: shift part of the cost to someone else through cyber insurance or contract terms with a vendor.
  • Avoid: stop the risky activity, for example retire an old server nobody maintains.
  • Accept: consciously live with a low risk. Write down who accepted it and why.

After the treatment, re-score the risk. That second score, the residual risk, is what you report to the owner. ENISA's risk management resources describe the same treat-and-review cycle in more detail.


Step 5: assign owners, deadlines and a review date

A register without names becomes a document nobody opens. Every row needs one person and one date. Keep the list short enough that the owner reads it in five minutes.

  • Review every six months, and immediately after an incident, a new system or a new vendor.
  • Link each critical risk to a response in your incident response plan, so people know what to do when it happens.
  • Track status (open, in progress, done) in the same sheet, not in email threads.

Action for today: put a recurring six-month reminder in the calendar called "IT risk review".


Common mistakes in small business risk assessments

  • Listing threats without assets. "Hackers" is not a risk. "Phishing leads to a hijacked email account with client data" is.
  • Scoring everything a 5. If every risk is critical, nothing is. Use the scale definitions above.
  • Ignoring people and vendors. Former staff and third-party tools appear in many incidents. Use the UK NCSC Small Business Guide as a checklist of everyday basics.
  • Doing it once. New apps, staff and vendors change the picture every few months.

For the broader picture, read our cybersecurity guide for small businesses.


FAQ

How often should a small business do an IT risk assessment?

At least once a year, and ideally every six months. Also update it after a security incident, when you add an important system or vendor, or when the business changes significantly, such as remote work or a new office. A quick review of an existing register usually takes about an hour.

What is the difference between a risk assessment and a security audit?

A risk assessment ranks what could go wrong and decides what to do about it. A security audit checks whether specific controls are actually in place and working. Most businesses start with the risk assessment, then audit the controls protecting their highest risks.

Do I need special software for an IT risk assessment?

No. A spreadsheet with the register columns from this template is enough for most small businesses. Dedicated governance tools make sense once you manage many systems, have compliance audits or need to report to clients and regulators regularly.

Who should take part in the assessment?

The owner or manager, whoever runs IT internally or externally, and one person from each key team, such as finance or sales. The owner judges business impact, the IT person judges likelihood, and team members spot everyday risks others miss.

Want to know where your website stands? Run our free website security check or see our IT consulting and cybersecurity services.

Get your IT risks ranked in one session

Send us your list of systems. We will help you score the risks, choose practical fixes and leave you with a register your team can keep up to date. Book a free consultation.

Book a free consultation