A global investment banking institution required structured methodology documentation for its Fundamental Review of the Trading Book (FRTB) internal model approach — documentation that would be reviewed by banking regulators and needed to satisfy both technical accuracy and regulatory presentation standards that most technical documentation programs were not designed to produce.
100% regulatory acceptance rate across all regulator-facing FRTB methodology documentation submissions
The Fundamental Review of the Trading Book (FRTB) — the Basel Committee's overhaul of market risk capital requirements — creates documentation obligations that differ materially from standard compliance documentation. FRTB internal model approval requires methodology documentation that satisfies both quantitative finance reviewers (who assess model validity) and regulatory examination teams (who assess documentation completeness and governance). Documentation that satisfies one audience without satisfying the other produces regulatory findings that delay or deny model approval.
The institution had internal quantitative finance teams who understood the models and experienced compliance teams who understood regulatory requirements — but no documentation function with the combination of regulatory documentation expertise, quantitative finance literacy, and presentation discipline that FRTB methodology documentation requires. Previous submissions had received findings on documentation completeness rather than model validity — a pattern that indicated a documentation architecture problem rather than a modelling problem.
ELDR developed a documentation architecture for FRTB methodology documentation that addressed the dual-audience problem structurally. The architecture separated model description (technical content for quantitative reviewers), governance documentation (accountability and oversight content for regulatory reviewers), and evidence documentation (the artefacts that demonstrate the model operates as documented) into distinct, cross-referenced document types. This separation allowed each document type to be optimised for its primary audience without requiring each audience to navigate content written for the other.
Documentation was produced through a structured authoring process that began with model documentation templates calibrated to FRTB internal model documentation requirements — each section mapped to specific regulatory expectations. Control narratives for model governance documentation followed NIST 800-53 and FFIEC guidance, producing regulatory-defensible governance documentation aligned with banking examination expectations. Cross-reference architecture ensured that every model claim was traceable to supporting evidence, and every governance claim was traceable to implementing control.
Documentation architecture for regulatory submissions requires design for the specific regulatory audience — not generic documentation standards. FRTB regulators have different documentation expectations from ISO 27001 auditors or SOC 2 examiners; the documentation program must be calibrated to those specific expectations.
Separating technical documentation from governance documentation from evidence documentation allows each to be optimised without compromise. Documentation that tries to serve all audiences simultaneously typically serves none well.
The documentation quality review process matters as much as the documentation production process. A structured review against specific regulatory expectations — not a general quality check — is what produces submissions that achieve regulatory acceptance on first presentation.
ELDR Consulting and ELDR Technology deliver governance documentation programs across federal, financial services, healthcare, and enterprise contexts. Every engagement begins with a discovery conversation.
Schedule Discovery Call →