Your AML team passed the training. But how will they make the call?

AML decision readiness is how reliably a financial crime team investigates, reasons and escalates when the correct answer is not obvious: when evidence is incomplete, signals conflict, throughput pressure is real and a pattern does not match a familiar typology. It is different from knowledge. A team can score perfectly on mandatory training and still clear alerts passively, escalate late or carry unverified assumptions into a decision. Readiness is observed behavior under realistic pressure, measured against the team’s own baseline, and it is the layer conventional completion metrics do not reach.

By watching decisions develop rather than grading final answers. RCM ThinkLabs places analysts inside fictional cases where evidence is incomplete and incentives conflict, then records the path each person takes: what they check before acting, which assumptions they test, how they respond when a fact contradicts their working theory, and when they choose to escalate. Because every choice is a move in a modelled game, the record is behavioral evidence rather than self-report, and it is read as team-level patterns, with each person measured against their own starting point.

Because it separates judgment from knowledge. Score judgment with typology quiz content and every miss is ambiguous: a knowledge gap and a judgment gap look identical, so you cannot tell which one to fix. The engine reads how a person decides, independent of what they know, and your training records already certify the knowledge. It also means the instrument arrives proven rather than new. The same measurement ran in production with a mission-critical engineering team at a U.S. defense contractor, and its validity carried over when the content changed to AML, because the behaviors it reads, evidence-seeking, surfacing contradictions, escalation timing, are the same in any domain. And it is what makes a benchmark possible: one taxonomy of 3 vectors, 16 capabilities and 64 microskills reads every cohort on a common scale. A test built only for AML could never tell you how your team compares, because nothing would sit on the other side of the comparison.

No. Mandatory training, institutional policy, transaction-monitoring systems, case management, quality assurance and regulatory reporting all remain in place and are not touched. RCM ThinkLabs adds a behavioral evidence layer on top of them: it shows how consistently people apply what the training delivered once the correct response is debatable. The two answer different questions. Completion records show that information was delivered and recalled. The decision record shows what analysts do with it under ambiguity, which is where operational exposure actually lives.

No. RCM ThinkLabs does not determine whether a suspicious activity report or suspicious transaction report must legally be filed, and it makes no legal or regulatory determinations of any kind. It provides behavioral evidence about how a team investigates and escalates inside fictional scenarios, as an input to institutional oversight and management judgment. Filing decisions, regulatory interpretation and legal review remain entirely with the institution’s own compliance professionals, counsel and governance processes.

A focused diagnostic engagement. The institution selects 10 to 25 analysts, investigators or reviewers from one AML workflow. Each participant completes one scenario-based decision session per business day for 14 business days, with each session taking up to fifteen minutes. The scenarios are fictional, so no live customer or transaction data is required. RCM ThinkLabs records how decisions develop during the sessions, and compliance leadership receives an Executive Decision Risk Map: aggregated team patterns, inconsistencies, blind spots and areas worth targeted follow-up. It is a baseline, not an audit or certification.

An aggregated view of how the team decides across six behaviors: escalation timing and thresholds, evidence-seeking tendencies, assumption testing, responses to contradictory information, red flag sensitivity and consistency under volume pressure. It highlights patterns and distributions rather than ranking individuals, and it names the blind spots that deserve further investigation or reinforcement. It is delivered with a method note and the scoring rubric, written to be attached to an internal report, with access and visibility aligned to the institution’s governance requirements.

No. The baseline runs on fictional scenarios and requires no integration with transaction-monitoring platforms, case-management systems or customer records, and no live customer or transaction data. No personal data beyond a work email is needed. Participants need a browser and up to fifteen minutes on each business day. That separation is deliberate: fictional cases reduce reliance on memorized answers and keep every live decision unaffected, so the baseline can start quickly and sit safely outside production systems.

Up to fifteen minutes per session, one session per business day, for fourteen business days. The sessions are short on purpose. Decision behavior is built and revealed through frequent repetition under realistic pressure, not through occasional long exercises, so the format is a brief daily decision rather than a workshop. Each of the six behaviors is scored from multiple decisions per session, so the baseline produces roughly 190 scored decisions per analyst without pulling anyone away from their queue for meaningful stretches of the day.

Yes. Scenarios are authored against published AML typologies and reviewed for plausibility before a cohort starts, and the decision tensions can be weighted toward the risks that matter most in your environment: escalation under volume pressure, sanctions exposure, reliance on monitoring output, or due diligence narratives that do not add up. The instrument underneath does not change, which is what keeps results comparable over time. During scoping, RCM ThinkLabs confirms the relevant workflow, participant roles, priority decision risks, governance expectations and reporting requirements.

No. RCM ThinkLabs does not determine individual competence, fitness, promotion readiness or employment status, and the findings should never be used as a standalone verdict on a person. No individual scores leave the platform. The reporting emphasizes aggregated team patterns and distributions, each person is measured against their own baseline rather than ranked against colleagues, and the purpose is developmental: to show leadership where reasoning is inconsistent, where escalation drifts and where reinforcement would pay off.

The baseline ends with an executive briefing on the Executive Decision Risk Map: what the team’s decision patterns show, where the priority blind spots are and which areas deserve targeted follow-up. From there, institutions that continue move into RCM ThinkLabs’ standard deployment model: an Initial Operating Capability cycle to establish a full measured baseline across the cohort, then a Full Operating Capability rhythm of two fixed days per week, so decision readiness compounds and leadership keeps a continuous read instead of a one-time snapshot.