Description

A focused course, tailored for you

The Bank MRM Validation File the Examiner Signs Off

A working validation file pack for SR 11-7 model risk, built so the next examiner walkthrough closes with no open findings.

Your validation file has to answer the examiner walkthrough end to end, on one set of numbers, with the AI/ML extension section already filled in. Most files can't.

$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

Model Risk Management specialists at large US banks carry a file per model and a relationship per model owner. The validation file is the artefact the examiner reads cover to cover during a targeted exam or horizontal review, and it is also the artefact internal audit pulls for their annual MRM review. When the inventory entry, the validation memo, the ongoing performance monitoring log, and the vendor attestations don't reconcile to the same model version and the same data cut, the examiner finds the gap inside five minutes. The AI/ML extension makes it harder: champion-challenger frames have to handle a model that retrains, drift monitoring has to be defined on inputs the team didn't choose, and the conceptual soundness section has to defend a model the vendor won't fully document. This course rebuilds the validation file as one reconciled pack, with a section structure that survives both the examiner walkthrough and the audit pull, and with the AI/ML extension wired in as a first-class part of the file, not an appendix.

What you walk away with

Rebuild the validation file as one reconciled pack across inventory, memo, OPM, and attestations.
Walk an examiner through champion-challenger results with the AI/ML extension already wired in.
Close the gap between conceptual soundness write-up and the model owner's actual implementation.
Stand up ongoing performance monitoring thresholds that survive a breach, not just a green dashboard.
Defend vendor model attestations when the vendor refuses to share full documentation.

The 12 modules

Module 1. The validation file as one reconciled pack

Open with the structure: one file, one model version, one data cut, every section reconciled. Walk through the inventory entry that ties to the memo, the memo that ties to OPM, the OPM that ties to vendor attestations. Build the table of contents the examiner reads first and the audit team pulls from. Set the standard for every later module.

Module 2. SR 11-7 conceptual soundness, written for the walkthrough

The conceptual soundness section is the one the examiner reads aloud. Rewrite it from the inside out: the business purpose in the model owner's own words, the theoretical basis with sources cited, the limitations stated plainly, and the assumptions the model breaks under. Include the diagram every MRM file needs and most do not have.

Module 3. Data integrity log and lineage from source to score

Examiners ask where the training data came from, how it was filtered, what was excluded, and how production scoring data is held to the same standard. Build the data integrity log as a live artefact: source system, extraction date, transformations, exclusion rules, and the reconciliation that proves the production scoring pipeline matches the training pipeline assumption set.

Module 4. Benchmarking against a real challenger

A benchmark model only counts if it is independent, sourced from a different methodology, and run on the same data cut. Build two challengers per validation: one simpler model and one alternative method. Document the divergence by segment, write up why the champion wins where it wins, and capture the segments where the challenger would have been picked instead.

Module 5. Ongoing performance monitoring that triggers, not decorates

OPM thresholds that never breach are decorative. Set thresholds at levels that will trigger inside the next four quarters under realistic data drift. Define the breach playbook before the breach: who is paged, what the model owner has to file, what the validation team re-runs, and how the breach record lands back in the file as a new section the next examiner reads.

Module 6. Vendor model attestations when the vendor pushes back

Vendor models put the validation team in a documentation gap the vendor controls. Build the attestation pack you can defend: signed vendor responses to the SR 11-7 questionnaire, your own conceptual soundness write-up of the vendor's documentation, the independent challenger you built without vendor data, and the residual risk write-up the model owner accepts in writing.

Module 7. AI and machine learning model extension to the file

The AI/ML extension is not an appendix. Rebuild conceptual soundness for a model that retrains, OPM for a model whose inputs drift faster than the validation cycle, and challenger benchmarking for a model the developer does not fully explain. Add the interpretability section the examiner now expects: feature attributions, fairness slices, and stability across retrains, with audit-ready snapshots.

Module 8. Documentation the model owner will actually sign

Most validation memos sit on a SharePoint nobody reads until the exam. Rewrite the memo so the model owner reads it before they sign. Use a structure that surfaces the limitations they will be asked about, the assumptions they own, and the conditions under which they have to flag a re-validation. Get the sign-off that is defensible if the model later breaks.

Module 9. Internal audit pull and the file that survives it

Internal audit pulls the validation file once a year and rates the MRM function on it. Build the file to pass an audit pull cold: complete chain of evidence, no orphan references, every limitation traceable to a mitigation, every assumption traceable to a sensitivity test. Capture the audit findings that recur across MRM functions and the file changes that make them go away.

Module 10. Champion replacement, retirement, and the file that follows

When a model is replaced or retired, the file does not stop. Walk through the retirement memo, the replacement validation that explicitly compares to the retired champion, and the inventory transition that keeps prior decisions traceable. Build the retirement section the examiner reviews when they ask why a prior decision was reversed.

Module 11. Inventory reconciliation across business lines

Most bank MRM inventories disagree with the line of business inventory and with the model owner inventory. Build the quarterly reconciliation that surfaces the gap before the examiner does: every line-of-business model lookup, every model owner attestation, every retired model still in production somewhere, and the closure log that resolves each gap with a dated decision.

Module 12. The examiner walkthrough rehearsal

Run the walkthrough before the examiner does. The model owner answers the same questions the examiner will ask, in the same order, against the same file. Capture the questions that produced a stumble, the questions that produced a contradiction across sections, and the file edits that close each gap. Land the file in the state where the real walkthrough closes with no open findings.

How this addresses your situation

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

You are reading a validation memo that no longer matches the OPM dashboard.

The examiner asked why the challenger result diverged from the champion in one segment.

Internal audit pulled the file and the inventory entry points to a model version you retired.

The model owner pushed back on a limitation the validation memo states as fact.

What you get with this course

Twelve written modules in the Art of Service learning environment.
A downloadable validation file pack template with every section pre-structured.
Worked examples for the AI/ML extension, vendor attestation, and OPM breach log sections.
A hand-built implementation playbook tailored to your model inventory and review cadence.
Thirty-day full refund if the file pack does not stand up to your next examiner walkthrough.

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

Within 24 hours: account provisioned, file pack template downloaded, implementation playbook delivered.

Week one: modules 1 to 3 walked, validation file table of contents rebuilt against the template.

Week two: modules 4 to 7 walked, AI/ML extension drafted for one live model in your inventory.

Week three: modules 8 to 10 walked, internal audit pull rehearsed against the rebuilt file.

Week four: modules 11 and 12 walked, examiner walkthrough rehearsal run with the model owner.

Before and after

Before

The validation file is three folders that don't reconcile. The examiner walkthrough surfaces the gap inside five minutes. The AI/ML extension is an appendix nobody believes.

After

The validation file is one reconciled pack. The walkthrough rehearsal already closed every question the examiner will ask. The AI/ML extension is a first-class part of the file.

What happens if you do not address this

The next horizontal exam or targeted MRM review will land on the file you have today. The gap between the validation memo and the OPM log surfaces inside the first session. The finding lands in the MRM function rating, the function rating lands in the supervisory letter, and the supervisory letter lands in the next round of internal hiring and budget conversations.

Who it is for

Built for MRM Specialists, Senior MRM Analysts, and Validation Leads inside large US bank holding company MRM functions. Useful whether you sit in second-line MRM, first-line model development with validation responsibilities, or the audit team that pulls the file every year. Most useful if you carry between four and twenty validations a year and at least one of them is an AI or machine learning model.

Who this is NOT for. Not for academic statisticians without a regulated-bank MRM file to defend. Not for vendor sales engineers selling model risk platforms. Not for first-line model developers who do not own any validation deliverable. Not for SR 11-7 newcomers who have not yet read the supervisory letter; this course assumes you have.

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 four to six hours per module if you work through it with a live validation file open alongside. Total course commitment of 60 to 80 hours across four weeks, less if you are rebuilding fewer than five files.

Why $199 is the right number

The MRM trade body courses cover SR 11-7 at the supervisory letter level and stop before the file. The Big4 advisory engagements rebuild your file once for a fee in the six figures and leave when the project closes. Internal training repeats the policy. This course gives you the file pack and the rehearsal so the rebuild stays yours.

FAQ

Does this assume I already know SR 11-7?

Yes. The course assumes you have read the supervisory letter and have at least one validation file in production. The modules rebuild the file; they do not teach the letter.

What if my bank uses a model risk platform?

The file pack template maps to the standard platform sections (inventory, validation memo, OPM, attestations). The platform stores it; the course rebuilds what is stored.

Is the AI/ML extension specific to a method?

No. The extension is structural: how the file changes for any model that retrains, drifts, or comes from a vendor that does not fully document. Applies to gradient boosting, neural network, and generative model cases alike.

What if my next exam is sooner than four weeks?

The implementation playbook is sequenced so weeks one and two close the highest-risk sections first. You can compress to two weeks at the cost of skipping the rehearsal in module 12.

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.