Business Risk Assessment Checklist for Small Businesses

A practical business risk assessment checklist for small businesses: scope assets, score likelihood and impact, run cyber checks, and set a review cadence.

Start with a scoped checklist, not a blank page

Most small businesses do not lack risk awareness; they lack a repeatable way to capture it. A checklist turns risk assessment from an annual panic into a short, evidence-based routine. Use this as a working document. You do not need a large governance platform to start — a spreadsheet and named owners will do.

The goal is not to eliminate risk. It is to identify the risks that could stop the business, decide which ones you are deliberately accepting, and prove you reviewed them.

Step 1: Scope the assessment and list assets

Define the boundary before you score anything. The phrase business risk is too broad to assess in one sitting. Pick a scope: the whole business, a location, a revenue line, or a system that supports critical work.

  • [ ] Name the scope and the decision-maker who will accept the output.
  • [ ] List revenue-critical activities — what must work tomorrow to get paid.
  • [ ] List the systems and data those activities depend on: email, accounting, CRM, payroll, line-of-business app, shared drives, website.
  • [ ] List people dependencies: who holds unique knowledge, approvals, or credentials.
  • [ ] List third parties: suppliers, contractors, IT provider, payment processor, cloud hosting.
  • [ ] Note regulatory or contractual obligations: client data, student records, payment card handling, grant conditions.
  • [ ] Record what is out of scope so the next review does not re-litigate it.

A useful shortcut: follow the money and the data. If a system touches both, it belongs on the list.

Step 2: Score likelihood and impact consistently

Use a simple 1–5 scale for likelihood and impact, then multiply for a risk score. The exact numbers matter less than applying the same definitions every time.

Likelihood: 1 = rare; 3 = could happen in the next 12 months; 5 = expected or already happening.

Impact: 1 = minor inconvenience; 3 = lost revenue or days of disruption; 5 = business-threatening, legal, or safety impact.

  • [ ] Write the scale definitions down before scoring.
  • [ ] Score inherent risk first, before controls, then residual risk after existing controls.
  • [ ] Set thresholds — for example, 1–6 low, 8–12 medium, 15–25 high — and adjust to your appetite.
  • [ ] For high scores, require a named owner and a dated action.
  • [ ] Record the rationale in one sentence; future you will need it.

Avoid false precision. A score is a prioritization tool, not an audit opinion. If a risk feels wrong, check whether the impact definition is too narrow. Reputation, staff safety, and regulatory exposure often deserve a higher impact score than teams first assign.

Step 3: Cyber risk checks

Cyber risk is operational risk with a technical accent. You do not need a security team to ask better questions.

  • [ ] Multi-factor authentication is enforced on email, remote access, admin accounts, and finance systems.
  • [ ] Backups run automatically and a restore has been tested in the last quarter.
  • [ ] Patching is owned by someone and covers operating systems, browsers, and line-of-business apps.
  • [ ] Endpoint protection is installed, monitored, and not silently expiring.
  • [ ] Admin rights are limited; daily work is not done from administrator accounts.
  • [ ] Email filtering and phishing reporting are in place, with a simple report-it route.
  • [ ] Offboarding removes access on the last day, including shared passwords and cloud apps.
  • [ ] Third-party access is inventoried and removed when contracts end.
  • [ ] A one-page incident response plan names who calls whom, including your IT provider and insurer.
  • [ ] Payment change requests have a callback verification step.

For K-12 and public-sector teams, add student or citizen data handling, records retention, and breach notification paths to the same list.

Step 4: Operational and business risk checks

  • [ ] Key-person dependency is documented, with cross-training or a named backup for critical tasks.
  • [ ] Cash flow has a 13-week view and a trigger point for cutting costs or drawing credit.
  • [ ] Supplier concentration is known; single-source suppliers have an alternative or buffer stock.
  • [ ] Customer concentration is known; losing the largest customer is modeled.
  • [ ] Insurance coverage is checked against actual operations, including cyber and business interruption.
  • [ ] Contracts have clear security, availability, and notification obligations.
  • [ ] Facilities risks — power, water, physical access, weather — have a simple continuity plan.
  • [ ] Legal and regulatory changes are reviewed on a schedule, not only after an incident.

Step 5: Assign owners, evidence, and a review cadence

A checklist without owners becomes a wish list.

  • [ ] Every risk has one accountable owner, not a committee.
  • [ ] Every high risk has an action, a due date, and evidence of completion.
  • [ ] The risk register records date raised, last review, score, treatment, and accepted-by.
  • [ ] Reviews happen quarterly for high risks and at least annually for the full register.
  • [ ] Trigger reviews after major changes: new system, new supplier, acquisition, senior departure, incident.
  • [ ] Results are summarized for leadership in one page: top five risks, movement, and overdue actions.

Keep evidence lightweight: a screenshot of MFA settings, a restore test note, a signed contract clause, a meeting note. The point is to show the control exists, not to build an archive.

Make it stick

Run the checklist once on a single scope. Score what you find, assign three owners, and schedule the next review before you close the document. That small loop is more valuable than a perfect framework you never revisit.

Take the free Business Risk Score assessment to get a quick baseline across your operation, then use this checklist to turn the gaps into owned, dated actions.

Ressources liées