Case study · Financial services

A tier 1 bank rebuilt its MiFID II competence program from the framework up.

After a supervisory thematic review flagged evidence gaps, a tier 1 European bank headquartered in Portugal stopped rewriting modules and started rewriting the underlying structure. The library came second.

Chapter 01
The situation

A library that had accumulated like sediment.

The institution, a tier 1 bank headquartered in Portugal with a nationwide branch network of staff who give investment advice and information to clients, had spent close to seven years maintaining its MiFID II knowledge and competence training through successive cohorts of external contractors. Each cohort inherited the last, extended what was there, and moved on. No cohort had ever authored a framework. There was no framework. There was a library of modules that had accumulated the way sediment accumulates.

The drift was invisible until it was not. A thematic review by the CMVM, the Portuguese securities market supervisor, on investment advice and staff competence asked the questions that a structured program is built to answer. How do you know your training covers this particular knowledge requirement. Where is the evidence that this cohort met that obligation. Which module was updated after this regulatory change, and when. Answers took weeks to assemble. In several cases they could not be assembled at all.

The finding was not a fine. It was a request for a remediation plan, delivered against a calendar. That request became the mandate for a different kind of platform, and, as it turned out, a different way of thinking about the program entirely.

The temptation, presented with a finding of coverage gaps, is to write more content faster. The head of conduct training resisted it. Faster authoring against an unnamed structure would produce the same problem in a shorter cycle.

Chapter 02
The framework work

Structure the subject before rewriting a line.

The engagement began by ignoring the existing library entirely. The Foundry ingested the sources that actually governed the program: the ESMA guidelines on knowledge and competence under MiFID II as applied by the CMVM, the bank’s own authorization conditions, product disclosure requirements, and the internal conduct policy that sat above all of it. From those sources it proposed a framework of concept nodes, prerequisite chains, and assessment definitions. A single object the bank’s subject matter experts could review and revise.

Three working sessions later, the framework was signed. Nothing downstream of that signature was permitted to run against an unapproved structure. This is the discipline the platform is built around, where the framework comes first. Structure governs content, not the other way around.

“For the first time we could name what was missing in the regulator’s own language, rather than in ours. That single change reset the conversation with the supervisor.”
Head of conduct training, tier 1 European bank

Only then did the platform look at the seven year library. The approved framework was compared against each existing module. Coverage was quantified. Where the framework was met, where it was met twice under different names, and where a clause implied coverage that had never been written. Regeneration then proceeded module by module under a two reviewer approval gate, with each regenerated element carrying a Foundry Hash back to the framework node it satisfied and to the source clause behind it. Each artifact was traceable, by design, to the obligation that made it necessary.

Chapter 03
The outcome

Cycle time down. Coverage complete. Evidence on tap.

The program completed regeneration inside the remediation window agreed with the regulator, without expanding the authoring team. Author cycle time fell against the previous contractor baseline. Requirement coverage against the approved framework reached parity before regeneration was declared complete. Evidence packs that had previously been assembled by hand in the weeks before an audit became an artifact produced at generation time.

More consequentially, the institution now owned a framework object. Contractor rotation stopped being an integrity risk, because contractors were no longer the source of truth. The framework was.

0%
reduction in author cycle time against the contractor baseline
0%
framework coverage of the approved MiFID II competence requirement set
0 hrs
to generate an evidence pack ready for the regulator (previously weeks)

Illustrative outcomes drawn from typical engagement patterns. Specific program figures shared under NDA on request.

Chapter 04
What it means

What this shows about remediation that begins with the framework.

The instinct after a thematic finding is to write faster. The instinct is wrong. Coverage gaps and evidence gaps are almost never authoring problems. They are structural problems that surface at the authoring layer. Writing more content against an unnamed framework produces the same gap on a shorter cycle.

The alternative (build the framework from source, sign it, then regenerate against it) is slower for the first fortnight and materially faster for every fortnight after. It also produces something the previous state could not: a program whose evidence is a report, not a project.

Any regulated firm sitting inside a remediation calendar, whether the supervisor is the CMVM, FINRA, the Japan FSA, or ASIC, or wanting to avoid the next one, is looking at the same question. Not who authored the last module. Who authors the framework the modules answer to.

For your organization

Bring the subject. Leave with the framework.

A 45-minute working session with our team on a real subject or program you own. You keep the framework the Foundry produces.