The compliance team is supposed to spot suspicious activity, protect the company, and make sure that the regulators are happy. What about the situation where the bulk of the analyst’s day is devoted to reviewing transactions that prove to be completely normal?
The process becomes repetitive, the backlog does not go away, and even seasoned staff members may wonder whether the job is worth it anymore. At this point, alert fatigue becomes more than just a technical problem. It becomes a retention issue that affects HR, compliance management, and the company at large.
Understanding that connection is the first step toward building a healthier, more sustainable compliance team.
Most of the Queue Is Noise
Pretty much every bank, payment company, crypto platform, and payroll provider runs aml transaction monitoring, which scans payments for anything that looks like laundering or a way around sanctions. Each payment gets checked against rules or a model. Trip a threshold and out pops a signal. That could be an odd amount, a first payment to a high-risk country, a burst of small transfers, or a customer who suddenly looks nothing like their onboarding profile.
Somebody will have to remove it. The analyst opens the profile, scrolls back through the history, looks up the counterparty, and decides if there’s an ordinary explanation. Usually there is. They write two lines saying so and close it. When there isn’t, it goes up to an investigator, and maybe, eventually, becomes a suspicious activity report.
Thresholds are set low on purpose, and it’s easy to see why. Miss a laundering case, and the regulator may come calling with a penalty. Flag a harmless payment, and you’ve cost someone ten minutes. Any firm weighing those two outcomes will over-flag, and a system tuned to over-flag will throw up far more alerts than real cases. Which is a way of saying that a large portion of the analyst’s day is occupied by false alarms.
Picture a payroll provider. Every time a small business pays a contractor in a new country, an alert fires. The first dozen are mildly interesting. By number three hundred, the analyst is pasting the same closing note and trying hard not to miss the one that’s actually different. Staying sharp for something that almost never shows up is tiring in a way that’s hard to explain to outsiders, and it’s what compliance people mean when they talk about alert fatigue.
Why the Best Analysts Leave First
And the pile keeps getting taller. In fiscal year 2025, according to FinCEN’s Year in Review, US institutions filed 4.8 million suspicious activity reports. In fiscal 2022, the figure was 4.3 million. Each report began life as an alert someone looked at. Most alerts never get that far, so the hours behind that 4.8 million are a good deal bigger than the number suggests.
Three reasons make that volume one of resignation.
One is that nothing builds up. Most office work leaves something behind, a finished project or a signed client. A queue just refills overnight. You can have a good day and finish it with as many open alerts as you started with.
One reason is taking the responsibility without having the controls. When you close an alert, it’s your name on the decision, and an examiner might read it years from now. Chances are you had no say in the rule that fired it, and none in this week’s target either. Being answerable for a decision when someone else set its inputs is a hard place to sit for long, and the queue puts people there by design.
The last is the slow drift between the job they were hired for and the job they do. Firms recruit analysts for judgment, often people who’ve done audit or investigations before, and then hand them work that mostly consists of confirming that nothing happened, so every month in the queue widens the gap between the role on the offer letter and the role at the desk. The sharpest people notice first. They also have the most options. So the analysts most likely to catch a real case are often first out the door, and whoever stays gets a longer queue.
What Each Departure Costs
Replacing the lost compliance analyst is far worse than simply having any old job opening. A lot of what they knew was never written down anywhere.
A seasoned analyst knows which corporate clients run payroll through four countries for perfectly good reasons, and which alert scenarios have caught something real in the past. That’s how they clear a routine alert in a few minutes. Their replacement doesn’t know any of it yet. So they go slower. They escalate more, just in case, and all of that lands on the senior investigators’ desks.
Then the backlog starts. Say a team of six loses one person. Five people now cover six people’s queue until the new hire arrives and gets through training, and no new analyst is closing alerts on their own in week one. Overtime creeps up. The same pressure that pushed the first person out starts working on everyone else, and one resignation can turn into two.
Regulators also take notice of this. Examiners look at whether alerts get cleared on time, and a pile of unreviewed ones is a finding all by itself. High turnover in the team that works the queue can end up as a control weakness the firm has to explain.
So the usual cost-of-turnover sum undercounts. Recruiter fees and onboarding hours show up in the budget. What gets overlooked is the months of painstaking effort and the cost incurred by those who remained behind.
Workload Levers HR and Team Leads Control
Some of the fixes do belong to the monitoring team: switching off rules that never catch anything, or feeding in data that settles the common alerts automatically. Worth doing. But much of what would help is related to the way the job is structured, and that’s HR’s field just as much as compliance’s.
First of all, there is the issue of visibility. Alerts per analyst and the average age of open alerts can sit in the monthly report right next to overtime and unused leave. They’re the same early warnings HR already watches when it helps leaders prevent team burnout, just pointed at a team whose stress is otherwise buried in a case management system.
Then mix the work up. Someone who spends every hour in the queue gets no break from the repetition. Give them a day or two on escalated cases, or on checking a colleague’s closures, and they’re finally using the judgment you hired them for. And there is an added bonus: information sharing takes place, which means that when a person leaves, not as much goes with them.
Have the analysts push back against the regulations. The people closing hundreds of identical alerts know exactly which scenarios never produce anything. A quarterly review where their tuning suggestions get adopted, or turned down with a reason, gives them back some control. And the monitoring gets better at the same time.
Look hard at targets. Measure a team only on alerts closed per day, and they’ll close them faster, with thinner notes. That raises regulatory risk and doesn’t do much for morale either. Combining the throughput with the quality rating makes it worth the effort to do it right.
Finally, the task requires a future. Lay out a path from analyst to investigator or scenario owner, and write down what each step takes. Good analysts then have a reason to stick around, and new hires can see that the queue is the first rung of a ladder.
Someone Has to Own the Middle
Alert fatigue lies somewhere between two responsibilities. The compliance department manages the system and its regulatory responsibility. HR owns hiring and job design. Each side tends to assume the other is looking after the people. A simple fix is a monthly sit-down: the compliance lead and the HR business partner put queue data and exit data side by side, and if either keeps climbing, the job gets changed.
If analysts are leaving faster than you can train replacements, the queue is the place to look first. Cutting alert volume will help. But what holds the seasoned employees back is the position where some portion of each week is spent exercising their expertise.
FAQs
1. What is alert fatigue among compliance teams?
Ans: Alert fatigue arises due to the constant review of huge numbers of alerts, which mostly appear to be false and pose no threat. The repetitive nature of such work causes the analyst to suffer from alert fatigue.
2. Why do compliance departments create many false positives?
Ans: Many monitoring systems use very low thresholds to catch any suspicious transactions. This practice reduces regulatory risks but at the same time leads to creating many false positives that have to be closed manually by analysts.
3. What can HR do to mitigate alert fatigue among compliance teams?
Ans: HR can monitor workload indicators, analyze overtime and unused leave, facilitate improved job design, and collaborate with compliance managers to improve staffing and career development of employees. This will help detect burnout risks prior to an employee’s resignation.
4. What metrics can be used to identify alert fatigue prior to resignation of employees?
Ans: The relevant metrics include alerts per analyst, age of open alerts, overtime, unused leave, quality check scores, turnover, and exit interviews. Analysis of these metrics can help detect the problem prior to resignation.
