# Medical Device Complaint Rate Trending Calculator

> Source: https://netray.co/tools/medical-device-complaint-rate-trending-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Calculates complaints per 1,000 units, compares against a baseline, and flags a statistical signal using a Poisson upper control limit.

## Category

quality

## Industry

Medical Devices

## Audience

- Complaint handling lead
- Quality engineer
- Post-market surveillance

## Tool

**Kind:** calculator

**Inputs:**

#### Units shipped in period

**Key:** units

**Type:** number

**Default:** 24000

**Min:** 1

**Step:** 500

**Unit:** units

#### Complaints received in period

**Key:** complaints

**Type:** slider

**Default:** 21

**Min:** 0

**Max:** 100

**Step:** 1

**Unit:** complaints

#### Baseline complaint rate

**Key:** baseline

**Type:** number

**Default:** 0.6

**Min:** 0

**Step:** 0.05

**Unit:** per 1,000 units

**Help:** From the prior 12 months or from your risk file's expected rate.

#### Control limit width

**Key:** sigma

**Type:** select

**Default:** 3

**Options:**

##### 2 sigma (alert)

**Value:** 2

##### 3 sigma (action)

**Value:** 3

**Outputs:**

#### Complaint rate per 1,000 units

**Key:** rate

**Expr:** complaints / units * 1000

**Format:** decimal

**Primary:** true

#### Expected complaints at baseline

**Key:** expected

**Expr:** baseline * units / 1000

**Format:** decimal

#### Upper control limit (count)

**Key:** ucl

**Expr:** expected + sigma * sqrt(expected)

**Format:** decimal

**Description:** Poisson approximation: mean plus sigma times the square root of the mean.

#### Signal (1 = above limit)

**Key:** signal

**Expr:** if(gt(complaints, ucl), 1, 0)

**Format:** integer

**Primary:** true

#### Change versus baseline

**Key:** pct_over

**Expr:** if(gt(expected, 0), (complaints - expected) / expected * 100, 0)

**Format:** percent

**Chart:**

#### Complaint rate and limit as complaints vary

**Type:** line

**X:** complaints

**From:** 0

**To:** 60

**Steps:** 31

**Series:**

- rate

**Disclaimer:** A statistical signal is a trigger for investigation, not proof of a defect. Reportability decisions for any individual complaint follow your regulatory procedures and are independent of trend results.

## Content

**Intro:** Complaint trending is a routine input to management review, CAPA and post-market surveillance. This calculator turns raw complaint counts and units shipped into a rate per 1,000 units and tells you whether the period is above a statistical control limit.

**Sections:**

#### How to use it

**Body:** Enter units shipped and complaints received for the same period, then the baseline rate you expect. The tool returns the rate per 1,000 units, the expected count and an upper control limit. A signal value of 1 means the count is above the limit and the trend should be investigated. Use a 2 sigma limit for early alerts and 3 sigma for action triggers, and document the choice in your trending procedure.

#### The statistics

**Body:** Complaint counts are rare events and behave roughly like a Poisson process with mean equal to the baseline rate times units. The standard deviation is the square root of the mean, giving an upper limit of mean plus k times sqrt(mean), the same logic as a c chart. For small expected counts below about five, the normal approximation is weak, so review borderline results manually.

**Bullets:**

- Rate = complaints / units x 1,000
- Expected = baseline x units / 1,000
- UCL = expected + k x sqrt(expected)

#### Common mistakes

**Body:** Using shipments from a different period than the complaints misstates the rate because devices fail with a delay after distribution. Mixing product families with different use environments hides signals. Counting duplicate complaints about the same event inflates the rate, and counting only investigated complaints deflates it. Trend by failure mode and by lot as well as in total, since a lot-specific problem can disappear in a family-level average.

**Cta:** If complaints are logged in one system and shipments in your ERP, we can help review how to produce this trend automatically.

**Faq:**

#### What denominator should I use?

**Answer:** Use units distributed in a comparable period, or better, units in service if you can estimate them. Match complaints to the right product family and time window, and state the choice in your trending procedure.

#### Does a signal mean a CAPA is required?

**Answer:** Not automatically. It means the trend needs review. Your procedure should define how signals are evaluated, for example by checking for clusters, lots and failure modes, and when a CAPA or health hazard evaluation is opened.

#### Is Poisson suitable for low volumes?

**Answer:** It is a reasonable model for rare independent events, but with expected counts under five the approximation is rough. Use exact Poisson limits in a statistics package or review the trend by judgement alongside the numbers.

#### How often should I trend?

**Answer:** Monthly or quarterly is common, with additional reviews after launches or design changes. The frequency should be risk-based and stated in your post-market surveillance plan.

## Search terms

complaint rate calculator, complaints per 1000 units, medical device complaint trending, post market surveillance trending, Poisson control limit complaints, complaint rate baseline, c chart complaints, device complaint signal detection

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