Description

A focused course, tailored for you

Regulatory Programme Delivery for Senior PMs

Map every work package to its regulatory obligation, close the audit gap, and stop the steering committee from asking the same question twice.

Your RAID log is up to date. Your milestone tracker is green. And yet every steering committee meeting produces the same question: which regulatory obligation does this deliverable actually satisfy? That question is not a process failure. It is a skills gap in how PMs are trained to connect project delivery artefacts to regulatory obligation structures at a large, cross-border financial institution.

$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

Senior Project Managers at major international banks operate in a space most PM certifications do not cover: the intersection of delivery governance and regulatory compliance. The standard toolkit teaches scope, schedule, and stakeholder management. It does not teach obligation decomposition, traceability from work package to regulatory article, or how to construct a steering committee narrative that satisfies both the programme board and the internal audit function in the same 30 minutes. When the steering committee asks why a deliverable is not mapped to its CRR obligation or why a RAID risk has no regulatory citation, the PM who cannot answer fluently loses credibility with the governance layer and risks the programme being escalated. That situation is not caused by a lack of seniority. It is caused by a missing method.

What you walk away with

Decompose a regulatory obligation set (CRR, MiFID II, DORA, or equivalent) into trackable work packages with clear ownership and evidence artefacts.
Build a RAID log structure that links every risk and issue to its regulatory citation, making audit queries answerable in under two minutes.
Construct a steering committee narrative that answers the 'which obligation does this satisfy' question before anyone has to ask it.
Design a regulatory change traceability matrix that survives both internal audit and external regulator review.
Manage cross-border regulatory conflicts at the programme level, documenting the resolution path and the governance sign-off.
Produce a programme charter where the regulatory scope section is a first-class artefact, not a footnote.

The 12 modules

Module 1. Regulatory Obligation Anatomy for Programme Managers

Regulations are structured at article, sub-article, and technical standard level. This module teaches you to read a regulatory text as a PM, identify the implementation obligations it creates, and classify them by delivery type: process change, system change, reporting change, or governance change. Covers CRR, DORA, and MiFID II from a delivery perspective. Output: a one-page obligation classification template used across every later module.

Module 2. Obligation Decomposition: From Article to Work Package

Translating a regulatory article into deliverable work packages is the foundational skill. This module covers the decomposition method: take a regulatory text, identify the obligations it imposes, break each into discrete work packages, assign an evidence artefact to each. The worked example uses a DORA ICT risk requirement and walks the full decomposition to a RAID entry with regulatory citation, owner, target date, and the specific document that satisfies the obligation on audit day.

Module 3. The Regulatory RAID Log: Structure and Citation Standards

Most RAID logs carry no regulatory citation. When audit asks which obligation a risk relates to, the answer is not in the log. This module redesigns the RAID log to include citation fields as first-class columns: article reference, internal policy, work package owner, and evidence artefact. Includes a template for cross-border programmes with worked examples citing CRR Article 92 and DORA Article 6 in the same log.

Module 4. Traceability Matrix Design for Regulatory Programmes

The traceability matrix is the first document an auditor or regulator requests when reviewing a change programme. This module covers the design from scratch: column structure, how to link obligations to deliverables to evidence artefacts in a way that survives challenge. You will learn the three most common gaps that cause a matrix to fail review and build a template using a DORA readiness programme as the worked example.

Module 5. Programme Charter: The Regulatory Scope Section

Most programme charters describe what the programme delivers but do not state which regulatory obligations it satisfies. This module rewrites the regulatory scope section to include: the regulatory driver by article reference, specific obligations the programme satisfies, what is explicitly out of scope and why, and the governance body that validated the scope. The output is a charter section the regulatory affairs team, programme board, and audit function all accept without separate sign-off conversations.

Module 6. Cross-Border Regulatory Conflict Management

Programmes spanning multiple jurisdictions regularly surface conflicting obligations on the same system or process. This module covers how to identify the conflict, document it formally, escalate through the governance structure, and record the resolution so both regulators can review it independently. The worked example is a DORA ICT third-party risk requirement in conflict with a local outsourcing approval timeline in a non-EU jurisdiction.

Module 7. The Steering Committee Narrative for Regulatory Programmes

Steering committees at regulated banks ask one question above all others: which obligation does each deliverable satisfy, and how do you know it is satisfied? This module builds the narrative template specifically for regulatory programmes, opening with obligation status rather than milestone status. You will learn how to answer the compliance question with a specific evidence-based response and how to close the update in a way that stops the same question recurring next meeting.

Module 8. Internal Audit Engagement During Programme Delivery

Internal audit reviews regulatory programmes at intermediate milestones, not only at close. This module covers how to prepare for a mid-programme audit review: what documentation to have ready, how to brief the audit team on your traceability approach before they ask for it, and how to respond to findings without derailing the programme timeline. You will build a standard audit readiness pack that the audit function can review in a one-hour walkaround.

Module 9. Evidence Artefact Standards for Regulatory Programmes

Not all project documentation counts as regulatory evidence. A meeting minute does not satisfy a record-keeping obligation. This module defines what counts as evidence for each obligation type, how to structure artefacts for non-technical auditors, and how to identify gaps before the audit does. Includes a reference table mapping obligation types to the evidence artefact categories that satisfy them under CRR, DORA, and MiFID II.

Module 10. Regulatory Programme Reporting: The Monthly Status Pack

The monthly status pack serves three audiences: the programme board wants milestone and budget status, regulatory affairs wants obligation coverage status, risk management wants RAID status by citation. This module builds one reporting structure that serves all three without producing three documents. You will structure a single pack with an obligation coverage section, a RAID section with regulatory citation, and milestones tied to obligation delivery rather than work package completion.

Module 11. Programme Closure and Regulatory Sign-Off

Closing a regulatory programme requires a different checklist than standard delivery. Closure artefacts must show every obligation was satisfied, evidence artefacts are stored and accessible, and residual risks have been handed to the business with regulatory citations attached. This module builds the closure checklist, the evidence handover pack, and the governance sign-off record. Covers the specific situation where an obligation is satisfied in principle but formal regulator acknowledgement has not yet arrived.

Module 12. Building Your Obligation Mapping Practice

The final module turns the full method into a repeatable practice. You will build a personal template library: RAID structure with citation fields, traceability matrix, steering committee narrative, and charter regulatory scope section. The module also covers how to brief junior PMs and business analysts on the obligation mapping approach so quality does not depend on your personal presence at every governance meeting. Output: a ready-to-use toolkit for your next regulatory programme.

How this addresses your situation

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

Steering committee asks which obligation a deliverable satisfies and nobody has the answer: Modules 2, 7, and 10 address this directly.

Internal audit arrives mid-programme and finds the RAID log has no regulatory citations: Modules 3, 4, and 8 cover this.

Cross-border regulatory conflict surfaces that the programme charter did not anticipate: Module 6 covers identification, escalation, and documented resolution.

Programme closure is blocked because regulatory affairs cannot confirm obligation coverage: Modules 9 and 11 cover evidence standards and closure artefacts.

What you get with this course

12 written modules with worked examples drawn from CRR, DORA, and MiFID II regulatory structures
Obligation decomposition template with regulatory citation fields
Regulatory RAID log template with worked example
Regulatory change traceability matrix template
Programme charter regulatory scope section template
Steering committee narrative template for regulatory programmes
Internal audit readiness pack template
Monthly status pack structure for regulatory programmes
Programme closure checklist and evidence handover pack
Hand-built implementation playbook tailored to your current programme 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

Before

Steering committee meeting ends with a new AOB item: map the Q3 deliverables to their regulatory obligations before the next governance forum. You spend the following week reconstructing the mapping from email chains and meeting notes, knowing the audit function will ask the same question in six weeks.

After

You open every steering committee update with an obligation coverage section. Every RAID item has a regulatory citation. When internal audit arrives, the traceability matrix is ready. The steering committee stops asking which obligation the programme satisfies because the answer is on slide one.

What happens if you do not address this

Regulatory programmes without obligation traceability fail internal audit reviews, trigger escalations to the CRO, and create personal accountability exposure for the programme manager when the regulator asks why a specific obligation was not tracked. At a major international bank, that exposure is both reputational and career-limiting.

Who it is for

You are a Senior Project Manager at a major international bank, running regulatory change, transformation, or compliance programmes. You have delivered complex projects before. You are comfortable with RAID management, stakeholder communication, and milestone tracking. What you have not had formal training on is how to structure the regulatory obligation layer of a programme so that it satisfies the internal audit function, the regulatory affairs team, and the steering committee simultaneously. You are accountable for a programme where the answer to 'which work package satisfies which regulatory obligation' needs to be defensible on paper.

Who this is NOT for. Project managers working in non-regulated industries, or PMs whose programmes carry no direct regulatory obligation mapping requirement. Also not for those who already have a formalised obligation traceability method and just need tooling.

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. Each module is structured to be readable in under 40 minutes with the templates worked through alongside.

Why $199 is the right number

Regulatory change management courses from major providers cover the regulatory landscape at a high level. They do not cover the programme delivery method for tracing obligations to work packages and defending that tracing in a governance forum. PRINCE2 and PMP certifications cover delivery methodology with no regulatory obligation layer. This course covers the gap between those two bodies of knowledge.

FAQ

Does this course cover specific regulations in detail?

Yes. The worked examples use CRR, DORA, and MiFID II structures. The method applies to any regulatory framework that creates specific implementation obligations, including PSD2, EMIR, and national transpositions of EU directives.

Is this applicable outside the EU regulatory environment?

Yes. The obligation decomposition and traceability method works with any regulatory framework that can be decomposed to article-level implementation requirements. Examples from UK FCA, Hong Kong SFC, and MAS regulations are included in the templates.

What if my current programme is already underway?

The course is structured so that modules 3, 4, and 8 can be applied immediately to a programme in flight. You do not need to restart the programme to add obligation traceability to an existing RAID log and traceability matrix.

How does the implementation playbook differ from the course modules?

The course modules teach the method with worked examples from representative regulatory programmes. The implementation playbook is built for your specific situation: your current regulatory framework, your governance structure, and the specific gaps you are facing. It is a practical tool, not a second pass through the theory.

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.