Description

A focused course, tailored for you

The AML Strategy Technology Build Playbook

Turn the AML model-tuning backlog into a quarterly roadmap the BSA Officer signs and the FinCEN exam team reads cleanly.

Your AML technology roadmap reads as a tools list, not a sequenced plan tied to typology coverage, alert effectiveness, and the next BSA/AML risk assessment cycle.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

Inside the AML strategy technology function of a Tier 1 US bank, the work is not buying tools. The tools are already there. Actimize or Mantas runs the transaction monitoring. SAS or homegrown rules sit alongside. The investigators have a case manager. The challenge is governing what those tools do: which typologies the scenarios cover, how the segments were derived and when they were last refreshed, what the threshold settings produce in alerts-per-investigator and effectiveness ratio, which models the second-line validators have signed off on and which still carry findings. Every cycle the BSA Officer needs a roadmap that ties tuning work to the SARs the bank actually filed, to the typologies the FinCEN advisory list flagged, to the geographic and product risk that drove the BSA/AML risk assessment rating. Every cycle the strategy technology team produces a backlog instead. The course turns the backlog into the roadmap.

What you walk away with

A quarterly AML technology roadmap document the BSA Officer signs without rework.
A typology coverage map tied to the bank's actual SAR filings and FinCEN advisory list.
A tuning governance pack that survives second-line model validation review.
An alerts-per-investigator and effectiveness testing dashboard the exam team can read.
A retire/replace decision template for legacy scenarios that no longer drive SARs.

The 12 modules

Module 1. The AML technology landscape inside a Tier 1 US bank

Maps how transaction monitoring, KYC/CDD, sanctions screening, and case management fit together, who owns each tool, where the strategy technology function actually has authority, and where the work hands off to investigations, compliance testing, second-line model validation, and IT operations. Sets the boundary of what this course is for.

Module 2. Reading the BSA/AML risk assessment as the input to the roadmap

Walks the most recent BSA/AML risk assessment as the source document for technology priorities. How geographic, product, customer, and channel risk ratings should translate into typology coverage, segmentation refresh cadence, and threshold tuning decisions. The questions the BSA Officer expects the roadmap to answer.

Module 3. Typology coverage mapping against actual SAR output

The diagnostic that compares which typologies the current scenarios cover against which typologies the bank's filed SARs actually involved over the past four quarters. Surfaces the coverage gaps the second-line testing programme will eventually find and turns them into named scenarios for the roadmap.

Module 4. Segmentation refresh, sequencing, and defending the methodology

When and why to refresh customer segmentation, how to sequence segmentation work ahead of threshold tuning, how to document the statistical methodology so the model validators sign off, and how to handle the segment-population shifts the business will challenge. Includes the worked memo template.

Module 5. Threshold tuning governance and the effectiveness testing pack

Above-the-line and below-the-line testing, the sampling methodology the OCC examiners expect, how to evidence the tuning decision, and how to produce the effectiveness testing pack that pairs with each threshold change. Worked example using a cross-border wires scenario, including the productivity and effectiveness ratios the second-line validators will challenge first.

Module 6. Scenario design and the FinCEN advisory list translation

How to translate a new FinCEN advisory (elder financial exploitation, fentanyl, Russia sanctions evasion typologies, etc.) into a named scenario with logic, data requirements, expected alert volume, and an effectiveness testing plan. The artefact your strategy partner in compliance will accept as a tuning ticket.

Module 7. Model risk governance under SR 11-7 for AML models

What the second-line model risk function expects for AML transaction monitoring scenarios: conceptual soundness, ongoing monitoring, outcomes analysis, and the documentation package that closes a finding. How to scope a model so validators accept the boundary, and how to handle findings without grinding the roadmap to a halt.

Module 8. Alerts-per-investigator, false positive ratio, and the exam narrative

The operational metrics the FinCEN/OCC exam team actually reads, why ratios alone mislead, how to frame productivity and effectiveness together, and how to construct the dashboard the BSA Officer will use in committee. Includes the SAR-to-alert conversion view investigations needs to defend headcount.

Module 9. Investigator workflow changes that pair with each tuning ticket

Every tuning change lands in an investigator's queue. The module covers how to pair scenario changes with case-manager workflow updates, alert disposition rule changes, and quality assurance criteria so investigations does not absorb the change as silent rework. The handoff document template.

Module 10. Retire/replace decisions for legacy scenarios

How to write the case for retiring a scenario that no longer drives SARs, what evidence the BSA Officer needs, how to document the residual risk, and how to sequence retirements alongside new scenario rollout so coverage never dips during the transition. The retire-decision template second-line will approve.

Module 11. Assembling the quarterly roadmap the BSA Officer signs

Brings modules 3 through 10 into one quarterly roadmap document. What gets sequenced where, how to attach typology coverage, tuning, validation, and investigator workflow into one read, how to handle the budget and resourcing conversation, and how to present it to the BSA/AML committee. Worked example end-to-end.

Module 12. Exam evidence and the MRA response posture

How the roadmap reads to an OCC or FinCEN examiner, the evidence package that should sit behind it, how to handle a Matter Requiring Attention or consent order remediation as an input to the next roadmap cycle, and how to keep the roadmap defensible quarter over quarter without burning the team out.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

Module 3 lands when you cannot yet show typology coverage against last year's SAR output.

Module 5 lands when the last threshold tuning evidence pack came back from validation with a finding.

Module 8 lands when the alerts-per-investigator number is the only metric in front of the committee.

Module 11 lands when the BSA Officer has asked for a quarterly roadmap and the team is returning a backlog.

What you get with this course

Twelve written modules covering the full strategy technology roadmap build.
The typology coverage diagnostic spreadsheet keyed to FinCEN advisories.
The threshold tuning evidence pack template second-line validators accept.
The quarterly roadmap document template formatted for the BSA/AML committee.
The hand-built implementation playbook tuned to your bank's tooling and risk profile.
Thirty-day money-back if the course does not deliver what the page promises.

What you will have in hand by Day 1, Week 1, Month 1

Account in the Art of Service learning environment provisioned within 24 hours of purchase.

Hand-built implementation playbook delivered alongside course access, tuned to your tooling and roadmap stage.

All twelve modules accessible from day one, no drip schedule.

Before and after

Before

A growing tuning backlog, a tools-list roadmap, second-line findings that keep coming back, and a BSA Officer asking for a sequenced plan you cannot yet produce.

After

A quarterly roadmap document signed without rework, typology coverage tied to actual SAR output, tuning evidence packs that close validation findings the first time, and an effectiveness dashboard the exam team reads cleanly.

What happens if you do not address this

The next BSA/AML risk assessment cycle closes with the same tools-list roadmap, the second-line testing programme flags the typology coverage gap before you do, and the next exam cycle opens with an MRA the team will spend two quarters remediating instead of building.

Who it is for

AML Strategy Technology lead or senior individual contributor inside a Tier 1 US bank or large regional, accountable for transaction monitoring model governance, tuning, scenario coverage, and the technology roadmap that the BSA Officer signs and the FinCEN/OCC exam team reviews.

Who this is NOT for. Investigators working individual cases, KYC/CDD onboarding technology owners, sanctions screening leads working OFAC matching, or fintech AML founders pre-MTL. The course is specifically about the strategy and technology roadmap for transaction monitoring inside a bank already operating under a BSA/AML programme.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Roughly fifteen to twenty hours of reading across the twelve modules, plus the time to adapt the templates to your bank's specific tooling and roadmap stage. Most strategy technology leads work it across two to three weekends or one full sprint.

Why $199 is the right number

A vendor-led tuning workshop costs more, ties the methodology to one platform, and delivers a slide deck the BSA Officer cannot sign as a roadmap. A Big Four advisory engagement on AML model governance starts in the high five figures and arrives as a maturity assessment, not a tuning ticket your team can execute. Free FFIEC and FinCEN guidance is the rulebook, not the build. This is the build playbook for the strategy technology lead actually doing the work.

FAQ

Is this tied to a specific platform like Actimize or Mantas?

No. The methodology is platform agnostic. The worked examples reference common platforms but the diagnostic, governance, and roadmap templates apply whether the bank runs Actimize, Mantas, SAS, or a hybrid configuration.

Does this cover KYC/CDD or sanctions screening?

Only as adjacent context. The course is specifically about transaction monitoring strategy, tuning, scenario design, and the roadmap that ties it together. KYC/CDD and sanctions screening have separate governance regimes and would be a different course.

What does the hand-built implementation playbook actually contain?

A tailored read of your current tooling, roadmap stage, recent exam findings if shared, and a sequenced set of recommendations for the next two quarters. Built per buyer, delivered alongside course access within 24 hours of purchase.

Is this enough to defend a roadmap to an OCC examiner?

The course produces the artefacts an examiner expects to see: typology coverage, tuning evidence, model validation documentation, effectiveness testing, and the sequenced roadmap. The defence is in how your team executes against those artefacts, but the artefacts are what the exam team reads.

What if my bank is a large regional rather than a Tier 1?

The methodology scales. The Tier 1 framing is because that is where the strategy technology function exists as its own discipline. Large regionals running their own transaction monitoring programme apply the same diagnostics with smaller scenario libraries and tighter resourcing.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.