# CAPA Backlog Clearance Time Calculator

> Source: https://netray.co/tools/capa-backlog-clearance-time-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Months to clear an open CAPA backlog, average age implied by throughput, and the backlog in 12 months at current rates.

## Category

quality

## Audience

- Quality manager
- Quality director
- Management representative

## Tool

**Kind:** calculator

**Inputs:**

#### Open CAPAs today

**Key:** backlog

**Type:** number

**Default:** 64

**Min:** 0

**Step:** 1

**Unit:** records

#### New CAPAs opened per month

**Key:** new_pm

**Type:** number

**Default:** 14

**Min:** 0

**Step:** 1

**Unit:** records/month

#### CAPAs closed per month

**Key:** closed_pm

**Type:** slider

**Default:** 18

**Min:** 1

**Max:** 60

**Step:** 1

**Unit:** records/month

#### Currently overdue

**Key:** overdue

**Type:** number

**Default:** 21

**Min:** 0

**Step:** 1

**Unit:** records

#### Target cycle time

**Key:** target_days

**Type:** number

**Default:** 90

**Min:** 1

**Step:** 5

**Unit:** days

**Help:** Your procedure target for open to effective close.

**Outputs:**

#### Net burn-down per month

**Key:** net

**Expr:** closed_pm - new_pm

**Format:** number

**Description:** Positive means the backlog is shrinking.

#### Months to clear backlog

**Key:** months_clear

**Expr:** if(gt(net, 0), backlog / net, 0)

**Format:** months

**Primary:** true

**Description:** Shows 0 when closures do not exceed new records, meaning the backlog never clears at this pace.

#### Implied average cycle time

**Key:** cycle_days

**Expr:** backlog / closed_pm * 30.4

**Format:** days

**Description:** Little's law: work in progress divided by throughput.

#### Gap to target cycle time

**Key:** gap_days

**Expr:** cycle_days - target_days

**Format:** days

#### Backlog in 12 months at current rates

**Key:** backlog_12

**Expr:** max(0, backlog - net * 12)

**Format:** integer

**Primary:** true

#### Overdue share of backlog

**Key:** overdue_pct

**Expr:** overdue / max(1, backlog) * 100

**Format:** percent

**Chart:**

#### Backlog in 12 months vs closures per month

**Type:** line

**X:** closed_pm

**From:** 5

**To:** 40

**Steps:** 36

**Series:**

- backlog_12

**Disclaimer:** A planning view based on average rates. Real closure rates vary by CAPA complexity and approval cycles.

## Content

**Intro:** A growing CAPA backlog is one of the first things an auditor or a management review notices. This calculator uses intake and closure rates to show when, or whether, the backlog clears, and what average cycle time your throughput implies.

**Sections:**

#### How to use it

**Body:** Pull three numbers from your quality system for the last quarter: open records, records opened per month and records closed per month. Enter the count of overdue records and your procedure cycle time target. Then move the closure slider to see how much faster you must close to get ahead. Count only CAPA, not every NCR, unless your system treats them as one workflow.

#### The method behind it

**Body:** Net burn-down is closures minus intake. Time to clear is backlog divided by net burn-down, and it only exists if net is positive. Average cycle time uses Little's law: work in progress equals throughput times time in system, so time in system is backlog divided by closure rate. It is an average, so a handful of very old records can hide behind a healthy number.

**Bullets:**

- Net = closed - opened per month
- Months to clear = backlog / net
- Cycle days = backlog / closures per month x 30.4
- Backlog in 12 months = backlog - 12 x net

#### How to read the result

**Body:** If the chart shows the 12 month backlog flat at the current level, you are only treading water. If cycle time is far above your target, the problem is usually approvals and verification of effectiveness, not the investigation itself. Sort the backlog by age and by stage in your system to find where records wait.

#### Common mistakes

**Body:** Closing records faster by lowering the bar on effectiveness checks, which brings repeat issues back as new records. Counting containment-only tickets as CAPA. Ignoring that intake can rise after a supplier or process change, so rerun this tool each month with fresh numbers.

**Cta:** If your CAPA data lives in an ERP quality module or a separate system, we can help build an aging and throughput view that feeds your management review automatically.

**Faq:**

#### What is a healthy CAPA cycle time?

**Answer:** It depends on your procedure and the risk class. Many sites target 60 to 120 days for standard records, with faster targets for safety or customer-escape issues. Use your own documented target.

#### Why does the tool show 0 months to clear?

**Answer:** That means you close fewer records than you open, so the backlog does not clear at current rates. Raise closures or reduce intake by filtering what truly needs a CAPA.

#### Does Little's law apply to CAPA?

**Answer:** As an average over a stable period, yes. It works best when intake and closure are roughly steady. After a spike in new records, the figure lags reality.

#### Should overdue records be handled separately?

**Answer:** Yes. Track them as their own queue with owners and dates. The overdue share shown here helps decide whether to run a focused clean-up sprint.

## Search terms

capa backlog calculator, open capa metrics, capa closure rate, capa cycle time, ncr backlog clearance, quality management review capa metrics, overdue capa reduction, capa throughput

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