toolbox
Home / Legal, Safety & Compliance / AML Monitoring Review Capacity Estimator

AML Monitoring Review Capacity Estimator

The AML Monitoring Review Capacity Estimator estimates how many alerts or cases a compliance team can review within a chosen work period. It converts staffing, productive hours, average handling time, and an explicit utilization assumption into an operational throughput estimate, then compares that capacity with the current workload. This is useful for compliance managers planning queues, staffing coverage, service levels, or remediation work. The result is an operations estimate rather than a regulatory staffing requirement; actual review depth should reflect risk, case complexity, escalation needs, and internal policy. For U.S. banking organizations, FFIEC BSA/AML guidance emphasizes risk-based monitoring and testing rather than a single mandated review-volume ratio.

Inputs

hr
days
min
%
cases
Result
—
calculated result
Daily capacity—
Period capacity—
Capacity minus workload—
Estimated days to clear workload—

1. Set team size. Enter the number of reviewers assigned to this queue during the period.

2. Enter productive time. Use hours actually available for review work after meetings, training, and other duties.

3. Define the planning period. Enter the number of workdays you want to model.

4. Estimate handling time. Use a representative average minutes-per-review figure for the case mix you expect.

5. Apply utilization. Keep a buffer for unavoidable idle time, escalations, quality checks, and workflow friction.

6. Compare with workload. Enter the current or forecast queue and review the capacity gap and estimated clearance time.

Core throughput model:

Period capacity = Reviewers × Productive hours/day × Workdays × 60 ÷ Minutes per review × Utilization rate

Daily capacity uses one workday. Capacity gap equals period capacity minus workload. Estimated days to clear the workload equals workload divided by daily capacity.

The utilization percentage is entered as a percent and converted to a decimal in the calculation. This model assumes average handling time and staffing are reasonably stable across the modeled period; higher-risk or escalated reviews may require separate capacity assumptions.

What the result means

Use the result as a planning estimate based on the assumptions entered. Revisit the inputs when workload, legal scope, risk profile, staffing, or cost conditions change.

This tool provides general planning information and does not replace legal advice, a regulator-specific methodology, or an organization’s approved compliance procedures.

Given: 10 AML reviewers, 5.5 productive hours per day, 20 workdays, 22 minutes per alert, 80% utilization, and an opening queue of 9,500 alerts.

Calculation: Daily capacity = 10 × 5.5 × 60 ÷ 22 × 0.80 = 120 reviews/day. Period capacity = 120 × 20 = 2,400. Capacity gap = 2,400 − 9,500 = −7,100. Clearance time = 9,500 ÷ 120 ≈ 79.2 workdays.

Result: The scenario supports about 2,400 AML reviews in the month, leaving a 7,100-alert shortfall against the opening queue if no new alerts arrive.

How should AML alert complexity affect the capacity estimate?

If alert types have materially different investigation effort, model separate queues or use a weighted handling time based on recent production data. A single average can hide the staffing effect of high-risk or escalation-heavy alerts.

Does FFIEC prescribe a fixed number of AML alerts per reviewer?

No. FFIEC guidance is risk-focused and does not establish one universal reviewer-to-alert ratio. Staffing should support the institution’s monitoring, investigation, escalation, and reporting processes at the risk level involved.

Should quality-assurance time be included in review minutes?

Include it if QA is routinely part of the same reviewer workflow. If QA is performed by a separate team, model that team separately so the primary review capacity is not overstated or double-counted.

How should incoming alerts be handled in a backlog model?

The workload field is a point-in-time queue. To plan a continuing operation, add expected inflow to the workload for the period or compare period capacity with forecast new alerts plus the opening backlog.

What does a negative capacity gap mean?

It means the modeled team cannot complete the entered workload within the selected period under the current assumptions. It is a planning signal to test staffing, productivity, segmentation, or scheduling scenarios—not proof that the AML program is inadequate.