SAR Backlog Calculator

How to use the SAR Backlog Calculator

Enter four numbers: how many new alerts your systems generate each day, how many analysts are currently reviewing alerts, how many alerts one analyst can clear per day, and your current open backlog. The backlog figure is optional. If you leave it blank, the tool will still show whether your daily capacity matches your inflow and what your queue looks like in 30 days assuming it starts at zero.

A few things to keep in mind before you enter your numbers. "Alerts cleared per analyst per day" should reflect completed dispositions, not alerts opened or assigned. If your analysts spend part of their day on SARs, escalations, or other tasks, use a number that reflects alert review time specifically. Teams that track this in their case management system can pull it directly. Teams that do not should start with a conservative estimate and adjust after a week of data.

The "new alerts per day" figure should come from your transaction monitoring system's daily output. These are net-new alerts entering the queue from automated rules or models, not the total number sitting in your existing backlog.

What the result means

The calculator returns four outputs. Daily review capacity tells you your team's theoretical throughput on a normal working day. Net daily change tells you whether your queue is growing, holding steady, or shrinking. A positive number means your backlog increases every day. A negative number means your team is working it down.

Weeks to clear only appears when capacity exceeds inflow. If your net daily change is positive, you get a 30-day projection instead, showing how large the backlog will be a month from now if nothing changes.

That 30-day projection is the number compliance officers should look at first. A backlog that looks manageable today, say 500 open alerts, can become a serious problem by month end if your team is running at a consistent daily deficit. The projection makes that trajectory visible before it becomes an examination concern.

If your weeks-to-clear figure is higher than expected even with a negative net daily change, check whether your spare capacity is realistic. When the gap between inflow and throughput is small, the queue clears slowly, and small fluctuations in analyst availability push that number further out.

Why this matters for compliance teams

Alert backlogs in transaction monitoring are a standing examination focus in AML supervision. A growing, uncontrolled backlog that delays SAR filings is the concrete regulatory risk. The calculator helps you quantify the gap before it becomes a remediation problem.

Compliance teams often discover backlog issues late, when they are already large enough to require a formal plan. The earlier you can show the arithmetic to senior management, the more options remain available. Adjusting alert thresholds, improving false-positive rates, adding analysts, and improving triage efficiency all affect the same equation. Each change has a different cost and lead time, and the calculator lets you model each one by changing a single input.

This tool translates a staffing question into operational terms: not "we need more analysts" but "at current volumes, our backlog will reach X by the end of the month." That framing tends to produce faster decisions from boards and senior leadership than abstract headcount requests.

For teams evaluating AI-assisted triage, FluxForce customers often run the calculator twice, once with current throughput and once with a projected post-automation figure, to produce a concrete before-and-after comparison without building a spreadsheet model from scratch.