A focused course, tailored for you
Risk Management Regulatory Submissions Playbook
Turn stress-test outputs and model results into APRA-ready narrative submissions that pass first review.
Your quantitative risk work is solid. The model output is defensible. But the APRA submission, the Basel capital narrative, and the risk committee pack each demand a specific document structure and framing that no modelling course ever taught you. The result: a completed stress test that still needs three rounds of reviewer comments before it is acceptable.
Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.
Why this course
Risk Associates at investment banks and asset managers spend weeks on model calibration, scenario design, and output validation. Then the submission draft lands on a senior reviewer's desk and comes back with structural comments that have nothing to do with the numbers. The regulator wants narrative linkage between the scenario assumptions, the stressed P&L, and the management action framework. The risk committee wants the same output presented as a capital adequacy story with explicit appetite breach triggers. Neither format is documented anywhere in the team's internal process. Junior Associates learn it by trial and error across multiple review cycles, absorbing comments, re-drafting, and losing weeks of productive time. This course removes that trial-and-error period by teaching the submission architecture directly.
What you walk away with
- Structure an APRA stress-test submission narrative that links scenario assumptions to stressed financial outcomes without triggering reviewer re-drafts.
- Build a Basel capital adequacy document that connects RWA sensitivity to management action triggers in the format regulators actually mark against.
- Write a risk committee pack that translates model output into board-level language, covering appetite breach, management response, and capital adequacy in a single coherent read.
- Produce an ICAAP chapter that satisfies the internal audit trail requirement and the external regulator review in the same document.
- Design a reusable submission template for your team that cuts the first-draft-to-acceptable-draft cycle from weeks to days.
- Identify the three structural failure patterns that cause submissions to come back with regulator comments, and build checklists to catch them before submission.
The 12 modules
How this addresses your situation
Specific modules that map to what you said you are dealing with.
What you get with this course
- 12 written modules covering the full APRA stress-test and Basel capital submission architecture
- Downloadable templates: scenario narrative scaffold, capital adequacy document, ICAAP chapter template, risk committee pack format, submission documentation control checklist, pre-send self-audit checklist
- Assumption log template and management action register
- RFI response template and internal coordination protocol
- Hand-built implementation playbook tailored to your submission type and regulatory context, delivered alongside course access
What you will have in hand by Day 1, Week 1, Month 1
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
Before and after
Stress-test output is complete but the submission narrative takes three or four review cycles before APRA or internal reviewers accept it. Each cycle costs weeks and the structural comments keep coming back because the document architecture is not right, not the numbers.
You draft the submission narrative once, using the correct APRA structure, with the appetite linkage, management action overlay, and capital narrative in the right sequence. The first reviewer sees a complete document and the feedback is substantive rather than structural. Future submissions reuse the template kit and take days to first draft.
What happens if you do not address this
Each review cycle that comes back with structural comments is a week of rework and a signal to senior reviewers that the submission function needs more oversight. Associates who learn the submission architecture early move into senior risk roles faster because they can draft without supervision. Those who do not stay on the review-and-revise loop longer than necessary.
Who it is for
You are a Risk Associate or Analyst at an investment bank, asset manager, or financial services firm. You have a quantitative background and you are comfortable with the modelling side of the work. The gap you are running into is the documentation layer: how APRA expects a stress-test narrative to be structured, how Basel capital submissions link scenario output to RWA impact, how a risk committee pack translates model results into governance-ready language. You are producing strong analytical work but losing time to reviewer comments that are structural rather than technical.
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. Approximately 6-8 hours across the 12 modules, self-paced. Most participants work through the core submission modules (1-7) in a single focused session and return to the template-building and self-audit modules (11-12) before their next submission deadline.
Why $199 is the right number
Internal training on submission writing typically does not exist at the Associate level. Regulatory consultants who review submissions charge by the hour and do not leave you with a transferable skill. Generic risk management courses cover modelling methodology, not submission narrative architecture. This course fills the specific gap between model output and regulator-accepted documentation.
FAQ
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.