vaayaa Inclusive Education
Industrial risk assessment

Quality Assurance and Testing Technology Risk Assessment: Test Integrity, Data and Control Gaps

A worked example of how a quality team identifies, scores and controls risks to test results, test equipment, data records and release decisions in an industrial setting.

Updated November 2026 8 hazards assessed Review every 6 months Highest risk: Critical to Medium
See the Quality Assurance and Testing Technology course

Executive summary

This assessment shows how a quality and testing function can find, rate and control the risks that threaten the accuracy of test results and the confidence placed in released product. Eight hazards were chosen because they are plausible in everyday laboratory and inspection work. Errors in test records, uncalibrated equipment and handover failures are the most likely, while release of non-conforming product and data loss carry the greatest impact. Each hazard is scored before controls and again after existing and added controls. Most risks fall to Medium or Low once the added controls are in place, but non-conforming release stays at Medium because its impact remains serious. The first actions are a stop rule for overdue instruments, a second signature on marginal releases, a tested restore of the test database and a retest pattern review. The site is a teaching example, so every score illustrates method, not a real organization.

Focus area
Quality assurance, testing and inspection technology
Setting
Industrial manufacturing site with an in-house test laboratory and inspection equipment
Method
Five by five likelihood and impact risk register

Scope

This assessment covers the quality assurance and testing function of a manufacturing site, from incoming inspection and in-process testing to final release, calibration, test data records and corrective action. It looks at risks to product conformity, people, equipment, data and the business. It does not cover design validation of any specific product or any regulated medical, aviation or nuclear device. Site size, sector and jurisdiction are assumptions made for teaching.

Context

The site has a quality manager, test engineers, laboratory technicians, production inspectors and an IT administrator who supports the laboratory information system. Test equipment includes bench instruments, automated test rigs and gauges that are calibrated by an external provider. Results are recorded in a laboratory information system, with some spreadsheets used for trend analysis. Customers and an external auditor review quality records periodically. Each risk is scored before controls to show its natural level, then again after existing controls and the added controls proposed here.

Objectives, assets and stakeholders

The objective is to release only conforming product, keep test results accurate and traceable, protect people and customers from unsafe parts, and meet the duties set by customers and any applicable standards. The assets in scope are the test equipment and rigs, the laboratory information system and its stored records, controlled procedures, product batches and the reputation of the quality function. Stakeholders include test technicians, inspectors, production managers, the quality manager, the site manager, customers, external calibration and test suppliers, the external auditor and end users. Every hazard has one owner role, and the quality manager keeps the register current and reports residual ratings to the management review each quarter.

Risk matrix: before and after controls

Each cell shows hazard numbers placed by likelihood and impact. Compare the two grids to see how controls move each hazard.

Before controls

Inherent risk

Risk before controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant		 2
Minor		 3
Moderate		 4
Major		 5
Catastrophic
5 Almost certain
4 Likely Likelihood 4, impact 3, score 12, high: H05 Likelihood 4, impact 4, score 16, high: H01 Likelihood 4, impact 5, score 20, critical: H03
3 Possible Likelihood 3, impact 3, score 9, medium: H06 H08 Likelihood 3, impact 4, score 12, high: H02 H04
2 Unlikely Likelihood 2, impact 5, score 10, high: H07
1 Rare

After controls

Residual risk

Risk after controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant		 2
Minor		 3
Moderate		 4
Major		 5
Catastrophic
5 Almost certain
4 Likely
3 Possible Likelihood 3, impact 2, score 6, medium: H05
2 Unlikely Likelihood 2, impact 2, score 4, low: H06 H08 Likelihood 2, impact 3, score 6, medium: H01 H02 H04 Likelihood 2, impact 4, score 8, medium: H03
1 Rare Likelihood 1, impact 4, score 4, low: H07
  • Low 1 to 4
  • Medium 5 to 9
  • High 10 to 16
  • Critical 17 to 25

Hazard register

A summary first, then the detail for each hazard.

Summary of hazards with scores before and after controls
No.HazardBeforeAfterOwner
H01 Transcription and recording errors in test results 16 High 6 Medium Laboratory supervisor
H02 Out-of-calibration or unverified test equipment 12 High 6 Medium Metrology coordinator
H03 Release of non-conforming product into service 20 Critical 8 Medium Quality manager
H04 Laboratory system outage and loss of test data 12 High 6 Medium IT administrator
H05 Handover failure and inconsistent test procedures 12 High 6 Medium Test engineering lead
H06 Dependence on a single calibration or test service supplier 9 Medium 4 Low Supplier quality engineer
H07 Manipulated test data and financial leakage through rework and scrap 10 High 4 Low Finance business partner
H08 Corrective actions that are not closed or verified 9 Medium 4 Low Quality manager
H01

Transcription and recording errors in test results

Technology and data Before 16 After 6

Readings are copied by hand, keyed into the wrong field or saved against the wrong batch, so the record shows a pass or fail that the test did not produce.

Who or what is affected: Quality team, production and customers relying on release records

Causes

Manual copying, long shifts and unclear field formats on test forms.

Consequences

Wrong release decisions, rework, recalled batches and loss of customer confidence.

Existing controls

  • Two technicians sign each handwritten test sheet.
  • Results are entered into the laboratory system with range checks.

Control gaps

Range checks do not catch a value that is plausible but wrong for the batch.

Additional controls

  • Prevent: Capture readings directly from instruments into the laboratory system wherever the equipment allows it.
  • Detect: Run a weekly audit of a random sample of entries against source printouts.
Likelihood 4 x impact 4 before; 2 x 3 after Owner: Laboratory supervisor Target: Within 30 days Early warning: A rise in corrected or amended test entries in a single month.
H02

Out-of-calibration or unverified test equipment

Operational Before 12 After 6

A gauge, meter or automated rig drifts outside tolerance or is used past its calibration date, so measurements look valid but are not reliable.

Who or what is affected: Test engineers, inspectors and downstream customers

Causes

Missed due dates, heavy use of shared instruments and no reference check between cycles.

Consequences

Good parts rejected, bad parts shipped, rework costs and an invalid test history.

Existing controls

  • Equipment carries a calibration label with a due date.
  • An external provider calibrates critical instruments each year.

Control gaps

Overdue dates are checked monthly, so an instrument can be used for weeks after it lapses.

Additional controls

  • Prevent: Lock out any instrument whose calibration is overdue in the equipment tracker.
  • Detect: Run a reference artefact check at the start of each shift and log the result.
Likelihood 3 x impact 4 before; 2 x 3 after Owner: Metrology coordinator Target: Within 45 days Early warning: An instrument with a calibration due date within 14 days and no booked service slot.
H03

Release of non-conforming product into service

Safety Before 20 After 8

A batch that fails a critical characteristic is released because the result was misread, a waiver was granted without authority or the status label was not updated, and the part reaches a user where it could cause harm.

Who or what is affected: End users, installers, operators and the company's reputation

Causes

Time pressure at dispatch, unclear waiver authority and status labels that are easy to miss.

Consequences

Injury or failure in service, recall costs, customer or regulator action and legal claims.

Existing controls

  • Release needs a signed certificate of conformity.
  • Non-conforming items are placed in a marked quarantine area.

Control gaps

Waivers are not limited by value or characteristic, and status checks are not made at dispatch.

Additional controls

  • Prevent: Require a second independent signature for any release where a critical characteristic is marginal.
  • Respond: Recall and quarantine any shipped lot linked to a failed or waived result within one working day.
Likelihood 4 x impact 5 before; 2 x 4 after Owner: Quality manager Target: Within 14 days Early warning: A release signed with a marginal result or a waiver with no named approver.
H04

Laboratory system outage and loss of test data

Technology and data Before 12 After 6

The laboratory information system or its storage fails, is attacked or is corrupted, so test records cannot be retrieved, traceability is broken and tests cannot be repeated.

Who or what is affected: Quality team, auditors and customers requesting records

Causes

Single server, unpatched software and reliance on local instrument files.

Consequences

Lost traceability, halted release, a failed audit and repeated tests.

Existing controls

  • Data is backed up each night to a separate location.
  • Instrument software keeps a local copy of recent results.

Control gaps

Backups are never restored in full, so their reliability is assumed rather than shown.

Additional controls

  • Recover: Test a full restore of the test database each quarter and record the time taken.
  • Respond: Hold a paper contingency form and a named process for manual recording during an outage.
Likelihood 3 x impact 4 before; 2 x 3 after Owner: IT administrator Target: Within 30 days Early warning: A failed nightly backup or a restore test that exceeds its time target.
H05

Handover failure and inconsistent test procedures

People Before 12 After 6

A test is changed, shifted or passed to a new technician without the current method, setup notes or open issues, so the same product is tested differently across shifts.

Who or what is affected: Technicians, shift leads and production planners

Causes

Staff turnover, informal changes to set-up and brief handover notes.

Consequences

Inconsistent results, wasted test time, false failures and missed defects.

Existing controls

  • Test procedures are stored in a controlled document folder.
  • Shift handover notes are written at the end of each shift.

Control gaps

Procedure revisions are not compared against the sheets used at the bench.

Additional controls

  • Prevent: Require a sign-off that the incoming technician has read the current procedure revision before testing.
  • Detect: Compare results from the same part across shifts each week and investigate any gaps.
Likelihood 4 x impact 3 before; 3 x 2 after Owner: Test engineering lead Target: Within 60 days Early warning: Two shifts producing different results for the same part and test.
H06

Dependence on a single calibration or test service supplier

Supplier Before 9 After 4

One external provider performs calibration, specialist testing or spare parts for critical rigs, and a delay, quality lapse or insolvency stops testing or undermines the validity of past results.

Who or what is affected: Production, customers and the quality team

Causes

Single source contracts, limited local options and long lead times for specialist parts.

Consequences

Idle test capacity, late shipments and doubt over past results from a lapsed certificate.

Existing controls

  • Supplier certificates are checked on receipt.
  • An annual review of the provider covers turnaround and accreditation status.

Control gaps

Certificate validity is checked on receipt only, not monitored until it expires.

Additional controls

  • Prevent: Qualify a second calibration provider and agree a turnaround standard in writing.
  • Respond: Keep a list of approved alternative providers and a stock of spare critical gauges.
Likelihood 3 x impact 3 before; 2 x 2 after Owner: Supplier quality engineer Target: Within 90 days Early warning: A calibration turnaround that exceeds the agreed time for a second month.
H07

Manipulated test data and financial leakage through rework and scrap

Financial Before 10 After 4

Results are adjusted, retested until they pass or selectively excluded to avoid scrap or meet a bonus target, which hides real defects and spreads cost through rework, warranty claims and write-offs.

Who or what is affected: Finance team, managers, customers and staff who report results

Causes

Pressure on output targets, bonus links to yield and weak review of changes.

Consequences

Hidden defects, warranty losses, write-offs, legal exposure and loss of trust.

Existing controls

  • Changes to a recorded result need a reason code and an approver.
  • Scrap and rework costs are reported monthly to the site manager.

Control gaps

Reason codes are free text, and no one compares retest rates with defect returns.

Additional controls

  • Detect: Analyse retest counts and result changes by operator and shift each month.
  • Respond: Investigate any pattern of retests that end in a pass and report it to the quality manager.
Likelihood 2 x impact 5 before; 1 x 4 after Owner: Finance business partner Target: Within 60 days Early warning: Retest rates that rise while field returns stay flat, or repeated changes to the same result.
H08

Corrective actions that are not closed or verified

Operational Before 9 After 4

Nonconformances are logged and a fix is agreed, but the action is delayed, given to the wrong owner or closed without evidence, so the same defect returns and the root cause stays in place.

Who or what is affected: Production, the quality team and customers affected by recurring defects

Causes

Heavy workload, vague root cause analysis and actions closed by memo rather than by evidence.

Consequences

Recurring defects, customer complaints, repeated rework and a weak audit record.

Existing controls

  • Each nonconformance is logged with an owner and a due date.
  • Open actions are reviewed at the monthly quality meeting.

Control gaps

Closure does not require evidence, and effectiveness checks are not scheduled.

Additional controls

  • Respond: Escalate any action open beyond its due date to the site manager at the next meeting.
  • Recover: Verify each closed action by re-testing the affected process and recording the evidence.
Likelihood 3 x impact 3 before; 2 x 2 after Owner: Quality manager Target: Within 30 days Early warning: Actions open past their due date or closed with no verification record.

Rating method and evaluation

Each hazard is rated on two five-point scales. Likelihood runs from 1, rare, to 5, almost certain, and impact runs from 1, minor, to 5, severe. Multiplying the two gives a score from 1 to 25 that falls into one of four bands: Low from 1 to 4, Medium from 5 to 9, High from 10 to 16 and Critical from 17 to 25. Critical scores need immediate action and senior sign off, High scores need a dated plan owned by a named role, Medium scores need routine controls with a review, and Low scores are accepted and watched. Inherent risk is the score before any controls. Residual risk is the score after the existing and additional controls are in place, and it must never be higher than the inherent score. If inherent risk is 10 or more, the residual score must be lower. Impact is judged on product conformity, people safety, cost, schedule, legal exposure and trust, and a hazard is not rated down only because it has not happened yet. The ratings are challenged by the people who run the tests, by a second assessor who did not score the hazard, and by the quality manager at the monthly review. Any change must cite evidence such as a calibration record, a restore test or a sample audit. Ratings are also reviewed whenever a monitoring indicator reaches its escalation point.

Likelihood, impact and rating bands

Likelihood

  • 5 Almost certain: Expected to happen in most circumstances.
  • 4 Likely: Will probably happen in many circumstances.
  • 3 Possible: Could happen at some time.
  • 2 Unlikely: Not expected, but it could happen.
  • 1 Rare: Only in exceptional circumstances.

Impact

  • 1 Insignificant: No lasting effect. Handled within routine work.
  • 2 Minor: Small effect that is quickly corrected.
  • 3 Moderate: Noticeable effect that needs managed effort to correct.
  • 4 Major: Serious effect on people, delivery or reputation.
  • 5 Catastrophic: Severe or lasting effect that threatens the whole activity.

Bands (likelihood x impact)

  • Low (1 to 4): Accept and monitor.
  • Medium (5 to 9): Manage with routine controls.
  • High (10 to 16): Senior attention and a treatment plan.
  • Critical (17 to 25): Act first. Do not proceed until reduced.

Monitoring, escalation and review

Review this assessment every 6 months, and sooner when an indicator below reaches its threshold.

Early-warning indicators and escalation thresholds
Indicator to watchEscalate when
Calibration items overdue or due within 14 days with no booked service.Escalate to the metrology coordinator at once, and to the quality manager if any instrument is still overdue after 7 days.
Corrected or amended test entries per month, and releases with a marginal result or waiver.Escalate to the laboratory supervisor when corrections rise above the agreed monthly level, and to the quality manager for any marginal release.
Backup failures or restore tests that exceed the agreed time.Escalate to the IT administrator the same day, and to the site manager if a restore is not proven within 5 working days.
Results for the same part and test that differ between shifts.Escalate to the test engineering lead when two shifts disagree on one part, and hold release until the difference is investigated.
Corrective actions open past their due date or closed without verification evidence.Escalate to the site manager when any action is more than 14 days late, and to the management review if more than three are overdue.

Contingency arrangements

If a suspect release is found, the quality manager places all linked lots on hold, informs the site manager and starts a traceability search. If the test database fails, the IT administrator restores the latest verified backup while technicians use the paper contingency form, and each manual record is entered once the system returns. If an instrument is found out of calibration, its results since the last good check are reviewed and affected parts are held. Customers and regulators are informed through the quality manager, and legal advice is sought where duties apply.

Prioritized action plan

  1. Hold release of any marginal result to a second independent signature and limit waiver authority, owner quality manager, within 14 days.
  2. Stop use of any instrument with overdue calibration and publish a tracker with 14 day alerts, owner metrology coordinator, within 30 days.
  3. Restore a full copy of the test database and record the time taken, owner IT administrator, within 30 days.
  4. Analyse retest and result change patterns by shift each month, owner finance business partner, within 60 days.
  5. Qualify a second calibration provider and agree turnaround in writing, owner supplier quality engineer, within 90 days.

Conclusion

Reliable quality depends on a few steady habits: calibrated equipment, direct recording of results, controlled handovers, verified corrective actions and a tested backup. The highest scores sit with non-conforming release and data loss, and the added controls bring each one down to a lower residual band. Treat the register as a living record, review it every six months or sooner after a serious event, and seek qualified engineering and legal advice for any real standard, product or customer obligation.

Assumptions and limitations

Assumptions

  • The site produces components for industrial customers under a documented quality management system that is audited externally each year.
  • Test equipment is calibrated by a third party, and records are kept in a laboratory information system on managed computers.
  • Jurisdiction and applicable standards are not specified, so legal duties are described in general terms only.

Limitations

  • The scores are examples for learning and do not describe any real site, product or audit.
  • Testing and product standards differ by sector and country and change over time, so specialist review is needed.
  • This is educational content and does not replace a formal site-specific risk assessment or licensed engineering advice.

Related frameworks to study

  • Risk register with likelihood and impact scoring
  • Hierarchy of controls
  • Plan, do, check, act improvement cycle

Industrial Risk Assessment

China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.

For Learning Reference Only: This assessment demonstrates how risk assessment principles are applied in a practical setting, providing a useful reference for learning and understanding. Actual assessments may be adapted to suit specific site conditions and circumstances.

Keep learning

Study the subject behind this assessment.

Quality Assurance and Testing Technology course Read the best practices for this course

More Industrial risk assessments

Hourly Active: 39,499 Learners