Description

A focused course, tailored for you

Market Risk Model Validation for Regulatory Sign-Off

Build the governance artefacts that get your VaR models through the next independent model review.

Most market risk model validation failures are not model failures. They are documentation failures. The quantitative team builds a clean VaR or Expected Shortfall model, the backtesting passes, and then the independent model review stalls on missing use-case attestation, incomplete scope statements, or a performance monitoring plan that does not tie back to the model risk policy. The model sits in a holding pattern while the desk carries the regulatory risk.

$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

The Basel III/IV transition has raised the bar on what counts as adequate model documentation. APRA, the Fed, ECB, and PRA supervisors now expect a model governance file that connects the model's intended use, its limitations, its validation scope, and its ongoing performance monitoring into a single coherent package before they will accept an independent model review conclusion. For a market risk desk managing VaR, ES, IRC, SVAR, and sensitivity-based approaches under FRTB, that means a separate governance package per model family. The artefacts are not difficult to produce once you understand the structure; the difficulty is knowing which gaps will trigger a request for information and how to close them without rewriting the technical spec.

What you walk away with

Produce a model governance package that meets APRA, Basel, and FRTB documentation standards for VaR, ES, and IRC models.
Write validation scope statements that pre-empt the top five independent model review findings for market risk.
Build a performance monitoring plan that satisfies both the model risk policy and the prudential supervisor's ongoing oversight expectations.
Close model inventory gaps before the next MRC or regulatory review cycle rather than in response to a finding.
Navigate the FRTB internal models approach documentation requirements without relying on external consultants for each submission.

The 12 modules

Module 1. The Regulatory Documentation Stack for Market Risk Models

Map the complete documentation hierarchy a prudential supervisor expects: model risk policy, model inventory entry, use-case attestation, validation report, and ongoing performance plan. Understand which artefact each reviewer reads first and why the sequence matters. By the end of this module you have a documentation checklist tied to the specific regulatory expectations of APRA, Basel Committee guidance, and the UK PRA model risk management principles.

Module 2. Model Inventory Governance: What Belongs in Each Entry

Build a model inventory entry that satisfies an independent model review function and a prudential supervisor simultaneously. Cover model ID, model tier, intended use, material limitations, validation status, and last review date in a format that survives an MRC question. Work through the common inventory gaps that generate findings: missing owner attestation, stale validation dates, and use-case scope creep that was never formally amended.

Module 3. VaR Model Documentation: The Technical Spec and Its Governance Wrapper

Separate the technical specification (methodology, parameters, data inputs) from the governance wrapper (intended use, approved scope, limitation disclosures) that regulators read first. Understand why a technically sound VaR model can still fail documentation review and how to structure the wrapper so that the independent model review team can reach a conclusion without an RFI. Covers historical simulation and parametric approaches under Basel II.5 and the FRTB IMA application.

Module 4. Expected Shortfall Under FRTB: Documentation for the IMA Application

Map the specific documentation requirements for FRTB Internal Models Approach approval: the P&L attribution test documentation, the desk-level model approval scope, the backtesting exception register, and the stressed period selection rationale. Build the governance artefacts the regulator will request during the IMA application review, including the liquidity horizon assignment policy and the non-modellable risk factor treatment record.

Module 5. Validation Scope Statements That Pre-Empt RFIs

Write a validation scope statement that closes the five questions an independent model reviewer asks before opening the technical report: model purpose, validation methodology, scope exclusions, data used, and reviewer independence. Cover the common scope statement failures that generate back-and-forth: circular references to the model spec, scope exclusions without a rationale, and independence declarations that do not meet the model risk policy definition of independent review.

Module 6. Performance Monitoring Plans for VaR and ES

Build a performance monitoring plan that satisfies both internal model risk policy and the prudential supervisor's ongoing oversight expectations. Cover backtesting frequency, exception thresholds, P&L attribution periodicity, and the escalation path when performance degrades. Connect the monitoring plan to the model inventory entry so that a regulator reviewing the inventory can trace the ongoing oversight without requesting additional documentation.

Module 7. IRC and SVAR: Documentation for the Models That Get Less Attention

IRC and Stressed VaR often receive less documentation rigour than the headline VaR model, and that is where independent model reviews find their easiest findings. Build complete governance packages for IRC (credit migration, default correlation, liquidity horizon calibration) and SVAR (stressed period selection, parameter stability through the stress window), including the use-case scope and the performance monitoring approach specific to each model type.

Module 8. Sensitivity-Based Approach Documentation Under FRTB SA

For desks using the standardised approach under FRTB, document the sensitivity calculation methodology, the risk factor mapping to the regulatory classification, and the capital add-on rationale. Cover the desk-level scope determination, the switch between IMA and SA documentation implications, and the ongoing monitoring requirements for SA desks. Build the artefacts that an internal audit function or prudential supervisor will review during a FRTB SA implementation check.

Module 9. Model Risk Policy Alignment: Linking Model Documentation to the Framework

Every governance artefact must reference back to the model risk policy in a traceable way. Map how validation scope statements, performance monitoring plans, and inventory entries connect to the policy's tier definitions, review frequency requirements, and escalation thresholds. Build a linkage matrix that lets you demonstrate policy compliance to an MRC or prudential supervisor without searching across multiple documents. Cover the common alignment gaps that audit functions find during model risk framework reviews.

Module 10. Preparing for the Independent Model Review: The Pre-Review Package

Assemble the pre-review package that allows an independent model review function to reach a conclusion within the agreed timeline. Cover the index structure, the version control approach for technical specs and governance wrappers, the pre-submission self-assessment against the validation scope, and the open issues register that pre-discloses known limitations. Build the package in a format that reduces RFI volume and demonstrates governance maturity to the reviewer.

Module 11. Responding to Model Review Findings and Closing the Loop

When a model review generates findings, the documentation response is as important as the remediation action. Build the finding response artefact: the finding description, the root cause, the agreed action, the responsible owner, and the target close date. Understand how to distinguish a documentation finding from a model finding in the response so that the remediation scope is accurate. Cover the finding closure process and the updated governance artefact that a reviewer will need to confirm close-out.

Module 12. The Model Governance File: Assembling the Complete Package

Combine all the artefacts from the preceding modules into a model governance file structure that works for both internal model risk oversight and external regulatory review. Cover the file naming convention, the version history, the cross-reference index, and the attestation sign-off process. Build a governance file template that you can apply across your model inventory with minimum adaptation per model, giving you a repeatable process rather than a one-off documentation effort for each review cycle.

How this addresses your situation

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

Model documentation fails independent review: Modules 1, 3, 5, 10 address the specific gaps that cause IMR stalls without remediating the underlying model.

FRTB IMA application documentation under preparation: Modules 4, 6, 8 cover the artefacts the regulator will request during the application review.

Model inventory has stale or thin entries: Modules 2, 9, 12 build the inventory governance structure and the policy linkage that audit functions check.

Regulatory finding on model documentation: Modules 11, 7, 5 address the response artefact, the closure process, and the pre-emption of recurrence.

What you get with this course

12 written modules covering the complete model governance documentation cycle for market risk
Downloadable templates: model inventory entry, validation scope statement, performance monitoring plan, pre-review package index, finding response artefact, model governance file structure
Worked examples for VaR, ES, IRC, SVAR, and FRTB SA documentation
Hand-built implementation playbook delivered alongside course access, covering your specific model family and regulatory context

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

Course access and hand-built implementation playbook delivered within 24 hours of purchase

Before and after

Before

Model documentation is produced reactively, each IMR generates RFIs, and the governance file exists as a collection of separate documents with no consistent structure or policy linkage.

After

A repeatable documentation process produces complete governance packages before the independent model review begins, reducing RFI cycles and demonstrating model risk maturity to both internal audit and the prudential supervisor.

What happens if you do not address this

Thin model documentation does not stop regulators from approving your models; it delays them and generates findings that follow the model in its inventory entry. In an FRTB IMA application cycle, documentation gaps can defer approval by months and require consultants to close. The cost of a documentation remediation project is higher than building the process correctly from the start.

Who it is for

Market risk professionals responsible for model governance, validation, or the model risk framework at a bank or asset manager. You own at least part of the model inventory, you interface with the independent model review function, and you are the person who gets the RFI from the regulator or the MRC finding from internal audit. You understand VaR and ES; what you need is a repeatable documentation process that survives regulatory scrutiny.

Who this is NOT for. Front-office traders who do not touch model governance. Quant developers who produce models but hand them off to a model risk function. Risk technology teams building the system rather than governing the output.

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. Each module takes 25-40 minutes to read and apply. Most participants complete the core modules relevant to their immediate review cycle in the first week and work through the remainder over the following month.

Why $199 is the right number

An external model documentation consultant charges $1,500-$3,000 per model for a governance package review and remediation engagement. The course delivers the process and templates to build every artefact internally, across the entire model inventory, without a per-model fee.

FAQ

Does this cover APRA-specific documentation requirements or is it generic Basel?

Module 1 maps the documentation hierarchy against APRA, Basel Committee guidance, and PRA model risk management principles in parallel, so you can identify which requirements apply to your regulatory context. The templates are built to satisfy the most stringent set of requirements across those three, with annotation on where APRA diverges from the Basel baseline.

My desk uses the FRTB standardised approach, not IMA. Is this still relevant?

Modules 8 and parts of Module 4 specifically address SA documentation. The governance framework modules (1, 2, 9, 12) and the validation scope and performance monitoring modules (5, 6) apply equally to SA and IMA desks.

What does the hand-built implementation playbook cover?

The playbook is built for your specific situation: your model family, your regulatory context, and the gaps most likely to appear in your next review cycle. It arrives within 24 hours alongside course access.

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.