Description

A focused course, tailored for you

Compliance Project Delivery for Banking AVPs

Build the control-design evidence pack, implementation log, and regulator-ready closure artefacts your next supervisory review demands.

The project is closed on paper. The control design was signed off. But the regulator's follow-up letter or the internal audit finding reopens the same gap because the evidence trail between the regulatory requirement, the design decision, and the operating control doesn't hold. This course teaches the layer most compliance project managers skip.

$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

AVPs running compliance projects at large banks sit between two accountability surfaces: the programme office demanding RAG status, and the supervisory or audit function demanding traceable evidence. Most project management training covers the first surface. Almost none covers the second. The result is projects that close in the system but fail at the next examination. The implementation log exists but doesn't map to the regulator's question. The control design rationale is in a slide deck nobody can find. The closure evidence was written for internal sign-off, not for an ECB or FCA examiner who reads it six months later. This course addresses that gap directly: how to structure control-design artefacts, maintain an implementation log that survives examination, and close regulatory findings in a way that holds under follow-up review.

What you walk away with

Write a control-design rationale document that maps cleanly from regulatory requirement through design decision to operating evidence, in a format an ECB, FCA, or internal audit examiner can follow without a briefing.
Build and maintain an implementation log structured for dual readership: programme office RAG status and supervisory evidence trail.
Draft a findings closure pack that does not reopen at the next examination cycle, including root-cause analysis, remediation steps, and evidence of operating effectiveness.
Identify the three most common gaps between project-close artefacts and examiner expectations, and correct them in your current project before the next review.
Deliver a structured status briefing to senior management that doubles as preliminary evidence documentation for the supervision file.

The 12 modules

Module 1. The Examination Evidence Chain

Most compliance project artefacts are written for internal audiences: steering committees, programme boards, first-line sign-off. This module maps the chain an ECB JST examiner or FCA supervisory team actually follows when reviewing a regulatory change project. You will learn the five nodes in that chain (requirement, gap analysis, design decision, implementation evidence, operating effectiveness) and why most project logs break at node three. Includes a blank chain template you annotate against your live project.

Module 2. Reading the Regulatory Ask Precisely

Supervisory expectations are written at a level of abstraction that creates interpretation risk. This module covers how to decompose a regulatory requirement into the specific control attributes an examiner is looking for, using worked examples from FRTB SA-CVA, ECB TRIM, and FCA Consumer Duty implementation. You will practice the decomposition exercise on a requirement from your own current programme and produce a one-page interpretive brief that can accompany your project's gap analysis.

Module 3. Control-Design Rationale Documents That Hold

A control design rationale document is a structured argument: here is the regulatory requirement, here is the risk it targets, here is the control we chose, here is why that design adequately addresses the requirement, and here is how you will know if it stops working. This module walks through the anatomy of a rationale document that satisfies both internal audit and supervisory review, with annotated examples and a blank template for your current project.

Module 4. The Implementation Log as Evidence Asset

Most implementation logs are project management artefacts: dates, owners, RAG statuses, action items. This module teaches you to maintain a parallel evidence layer in the same log: the decisions taken, the options considered and rejected, the approvals obtained, and the evidence of each step being completed. You will restructure an existing project log to carry both layers simultaneously, so the same document serves the programme office and the supervision file without duplication or contradiction.

Module 5. Gap Analysis Documentation for Dual Audiences

The gap analysis is the first artefact an examiner reads and the most frequently challenged. This module covers how to document a gap analysis in a way that is credible to both the risk function (which wants a risk-quantification framing) and the supervisory body (which wants a regulatory-requirement framing). You will produce a gap analysis template that carries both views in a single document, with a worked example from an operational resilience programme and a capital adequacy initiative.

Module 6. Steering Committee Packs That Double as Evidence

Senior management briefings are typically prepared for decision-making, not for examination. But in a well-structured programme, every steering committee pack is also a dated evidence artefact: it records what management knew, when they knew it, what decision they took, and what the basis was. This module shows you how to structure agenda items, decision records, and management information so they serve both purposes. Includes a steering committee pack template with an integrated evidence index.

Module 7. Writing Findings Closure That Stays Closed

A findings closure document is a promise: the gap that was found no longer exists and here is the evidence. This module teaches the four-part closure structure that satisfies both internal audit methodology and supervisory examination: root cause (not just symptoms), remediation steps taken (not planned), operating effectiveness evidence (not design adequacy), and sustainability controls (what prevents recurrence). You will rewrite a past closure document using this structure and identify why it would or would not hold at follow-up review.

Module 8. Managing Regulator Information Requests

When a supervisory body sends an information request during or after an examination, the response is itself an evidence artefact. This module covers how to log, track, and respond to information requests in a way that does not create new evidential gaps: how to scope responses precisely, how to attach supporting documentation in a navigable format, and how to escalate contested requests without creating a correspondence trail that complicates future interactions. Includes a request-tracking template.

Module 9. Operating Effectiveness Evidence vs Design Adequacy

One of the most common causes of reopened findings is conflating design adequacy evidence with operating effectiveness evidence. A control can be well-designed and still fail operating effectiveness testing. This module teaches the difference and shows you how to structure an evidence programme that captures both: control design documentation for the initial examination, and operating effectiveness samples for follow-up review. Worked examples from credit risk controls, conduct risk monitoring, and operational resilience testing.

Module 10. Multi-Regulator Project Mapping

Large compliance projects at global banks often need to satisfy requirements from multiple regulators simultaneously: ECB, FCA, ACPR, FED, or OCC each with their own documentation expectations. This module covers how to map a single project's control design and implementation evidence to multiple regulatory frameworks without maintaining parallel artefact sets. You will produce a multi-regulator mapping matrix that identifies shared evidence, regulator-specific add-ons, and the minimum documentation set that satisfies all jurisdictions simultaneously.

Module 11. The Project Handover to BAU Control Owners

Most compliance project failures in examination are not failures of the project itself but failures of the handover. The project team built the control and documented the design; the BAU control owner inherited it without the evidence context and cannot answer the examiner's questions. This module covers how to structure the handover pack so that the BAU owner can narrate the control's history, locate the evidence trail, and respond to examination questions without escalating back to the original project team.

Module 12. Building Your Personal Examination Readiness Baseline

Practical synthesis. You will audit your current active projects against the examination evidence chain from module one, identify the specific artefact gaps, and produce a remediation plan with owner assignments and target dates. The output is a one-page examination readiness baseline per project: both a self-assessment tool and a status document for your compliance officer. This is the artefact that tells you, before the examiner arrives, which projects will hold and which will not.

How this addresses your situation

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

You are three months from a scheduled ECB thematic review and your implementation log is a project management tool, not an evidence asset.

Internal audit has just issued a finding that you thought was closed eighteen months ago. The root cause is that the closure document described what was planned, not what was done.

Your programme board wants a RAG-status briefing and your supervisory file needs the same information in a completely different format. You are maintaining two parallel document sets and neither is complete.

A new AVP has joined the team and needs to be able to answer examiner questions about a project that closed before they arrived. There is no evidence trail a new team member can navigate without the original project lead present.

What you get with this course

Twelve written course modules covering the full arc from regulatory requirement decomposition through examination-ready project closure.
Downloadable templates for every module: examination evidence chain, control-design rationale, dual-layer implementation log, gap analysis, steering committee evidence pack, findings closure document, multi-regulator mapping matrix, and examination readiness baseline.
Worked examples from regulatory change programmes across capital adequacy, conduct risk, operational resilience, and data governance.
The hand-built implementation playbook: a tailored guide applying this course's methodology to the specific regulatory context and project type relevant to your current programme, delivered alongside course access.

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

Course access and the hand-built implementation playbook are both delivered within 24 hours of purchase.

The twelve modules are self-paced. Most participants complete the core modules relevant to their current project in the first week and use the remaining modules as reference for subsequent projects.

The downloadable templates are available from module one and are designed to be used on live projects from the first session.

Before and after

Before

Compliance projects close in the system but findings reopen at the next examination. The control design rationale is in a slide deck. The implementation log satisfies the programme board but not the examiner. Findings closure documents describe what was planned rather than what was done and evidenced.

After

Every project produces an examination evidence chain from requirement to operating effectiveness. The implementation log serves both the programme board and the supervision file. Findings closure documents are structured to hold under follow-up review. The BAU handover pack means the control owner can answer examination questions without escalating to the original project team.

What happens if you do not address this

Regulatory findings that reopen are expensive: they consume senior management attention, extend the examination timeline, and in some supervisory regimes (ECB, FCA) they elevate the institution's risk profile for future inspections. For the AVP who owned the original project, a reopened finding is a professional credibility problem regardless of whether the underlying control is sound. The gap is almost always in the evidence trail, not in the control itself, and it is entirely preventable.

Who it is for

AVPs and senior compliance project managers at global and regional banks who own the delivery of regulatory change programmes (capital, conduct, operational resilience, data) and are accountable for both internal audit clearance and supervisory examination readiness. You run projects, write control designs, and brief senior management; the piece you have not had formal training on is how to make those artefacts examiner-proof.

Who this is NOT for. Entry-level compliance analysts who do not own project delivery. Consultants who advise rather than implement. Teams working exclusively on AML transaction monitoring where the tooling and evidence patterns differ substantially.

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 4-6 hours across the twelve modules, plus time to apply the templates to your current project. Most participants treat this as working sessions rather than study sessions: they complete a module and immediately apply the template to a live artefact.

Why $199 is the right number

External compliance training programmes typically cover regulatory content (what FRTB requires, what Consumer Duty expects) rather than project delivery methodology (how to document a control design so it holds under examination). Internal training at banks covers the firm's existing methodology, which is the methodology that produced the current evidence gaps. This course covers the layer between: how to structure project artefacts so they satisfy both internal governance and external examination, regardless of the specific regulatory framework.

FAQ

Does this course cover specific regulatory frameworks like FRTB or ECB TRIM?

The course uses worked examples from those frameworks but teaches methodology that applies across frameworks. The hand-built implementation playbook included with your purchase is tailored to the specific regulatory context you are working in.

Is this relevant if my projects are internal audit-driven rather than supervisory examination-driven?

Yes. The evidence chain methodology works for both audiences. Internal audit methodology at most large banks mirrors supervisory examination standards, and the artefact structures taught in this course satisfy both.

How is the implementation playbook tailored?

The playbook is hand-built for your specific regulatory context and project type based on the information provided at purchase. It is not a template with your name inserted; it is a worked application of the course methodology to your situation.

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.