# Quality Risk Register Template

> Source: https://netray.co/tools/quality-risk-register-template-excel
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A scored risk register with likelihood, impact, owner, mitigation and status for ISO 9001 risk-based thinking.

## Category

quality

## Audience

- Quality manager
- Project manager
- Operations manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### ID

**Key:** id

**Type:** text

#### Risk description

**Key:** risk

**Type:** text

#### Area

**Key:** area

**Type:** select

**Options:**

- Supplier
- Process
- Product
- Equipment
- People
- Regulatory
- IT / ERP

#### Likelihood (1-5)

**Key:** lik

**Type:** number

#### Impact (1-5)

**Key:** imp

**Type:** number

#### Score

**Key:** score

**Type:** number

**Expr:** lik * imp

**Format:** integer

#### Mitigation / action

**Key:** mitigation

**Type:** text

#### Owner

**Key:** owner

**Type:** text

#### Next review

**Key:** review

**Type:** date

#### Status

**Key:** status

**Type:** select

**Options:**

- Open
- Mitigating
- Accepted
- Closed

**Rows:**

**Id:** R-01

**Risk:** Single source supplier for castings misses delivery

**Area:** Supplier

**Lik:** 3

**Imp:** 5

**Mitigation:** Qualify second source, hold 4 weeks buffer stock

**Owner:** Purchasing

**Review:** 2026-11-30

**Status:** Mitigating

**Id:** R-02

**Risk:** CMM calibration lapses before audit

**Area:** Equipment

**Lik:** 2

**Imp:** 4

**Mitigation:** Calibration due alerts 30 days ahead

**Owner:** Metrology

**Review:** 2026-12-10

**Status:** Open

**Id:** R-03

**Risk:** Operator turnover on night shift

**Area:** People

**Lik:** 4

**Imp:** 3

**Mitigation:** Cross-training matrix and work instructions

**Owner:** Production

**Review:** 2026-12-15

**Status:** Mitigating

**Id:** R-04

**Risk:** ERP routing not updated after process change

**Area:** IT / ERP

**Lik:** 3

**Imp:** 3

**Mitigation:** Link ECN approval to routing update task

**Owner:** Engineering

**Review:** 2027-01-15

**Status:** Open

**Id:** R-05

**Risk:** New customer requirement not flowed to suppliers

**Area:** Regulatory

**Lik:** 2

**Imp:** 4

**Mitigation:** Flow-down checklist on every PO

**Owner:** Quality

**Review:** 2027-01-31

**Status:** Accepted

**Totals:**

#### Highest score

**Key:** score

**Agg:** max

**Format:** integer

#### Average score

**Key:** score

**Agg:** avg

**Format:** decimal

#### Risks logged

**Key:** id

**Agg:** count

**Format:** integer

**Notes:** Use a 5 by 5 matrix: scores of 15 and above are commonly treated as high, 8 to 14 as medium and below 8 as low. Agree these bands with your management team and record them in your procedure.

## Content

**Intro:** A risk register records what could go wrong, how likely and how serious it is, and who is acting on it. This template scores each risk as likelihood times impact so a quality or operations team can rank them, track mitigation and show evidence of risk-based thinking.

**Sections:**

#### How to use the register

**Body:** Add one row per risk. Write the description as an event plus consequence, such as supplier misses delivery causing line stoppage. Rate likelihood and impact from 1 to 5 using definitions your team agrees on, then record the mitigation, an owner and a review date. Update the status as work progresses and re-score after actions are in place. Review the register in management review and after any significant incident, audit finding or change.

**Bullets:**

- Describe cause, event and consequence, not a vague topic
- Give every risk one named owner
- Set a next review date, not only a closed date
- Re-score after mitigation to show the residual risk

#### The scoring method

**Body:** The score is likelihood times impact, giving 1 to 25. A common banding treats 15 or more as high, 8 to 14 as medium and under 8 as low, though you should define your own and keep it consistent. The matrix is simple and easy to explain, but it hides large impact with low likelihood, so flag any impact of 5 for review regardless of score. For safety critical products use FMEA severity scales rather than a generic matrix.

#### Reading the result

**Body:** Sort by score and take the top five to your management review. Compare the highest and average score: a high average suggests widespread weakness, while one outlier suggests a single target. Count accepted risks and check they have a recorded reason and approver. Over time, the aim is to see scores fall as mitigations take effect and new risks appear from changes rather than neglect.

#### Common mistakes and ISO 9001 links

**Body:** ISO 9001:2015 clause 6.1 asks organisations to determine risks and opportunities and plan actions, but does not require a formal risk method or register. A register is a convenient way to show it. Common mistakes are creating a long list once a year, scoring without evidence, and leaving mitigation vague. Link risks to FMEA lines, supplier scorecards and audit findings so the register stays alive instead of being a document written for auditors.

**Cta:** If your risks relate to ERP data such as supplier delivery or quality history, Netray can discuss pulling signals automatically. The register is free and complete as is.

**Faq:**

#### Is a risk register required by ISO 9001?

**Answer:** ISO 9001:2015 requires risk-based thinking and planned actions to address risks and opportunities, but it does not mandate a specific format. A risk register is a common, practical way to document it.

#### How is this different from an FMEA?

**Answer:** An FMEA analyses failure modes of a specific design or process in detail. A risk register is broader, covering supplier, people, regulatory and business risks at a higher level. Many companies use both and link them.

#### What matrix size should I use?

**Answer:** Five by five is common and gives enough resolution. A three by three matrix is quicker but coarse. Whatever you choose, define each level in words so ratings are repeatable.

#### How often should the register be reviewed?

**Answer:** At least in each management review, and monthly for high risks. Also review after incidents, audits, process changes or new customer requirements.

## Search terms

risk register template, risk register template excel, iso 9001 risk register, quality risk register example, risk assessment matrix template, manufacturing risk register, risk log template, likelihood impact risk register

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
