First page of the Model Development Documentation TemplateWord document preview

Model risk management (SR 26-2)

Model Development Documentation Template

Model documentation template in Word: a filled bank example covering purpose, data, method, assumptions, testing, limitations, monitoring plan and version history.

Word document · 41 KB Built on free official texts

3 free downloads per account. Just your email and a 6-digit code.

Need more than 3? Every template for $249, once. Lifetime access, including the templates we add later. See pricing

About this template

Model development documentation explains what a model is for, which data and method it uses, which assumptions it rests on, how it was tested and where it should not be relied on. Validators need it to challenge the model, users need it to understand its limits, and examiners ask for it. It is due before a new model or a redeveloped version is submitted for validation.

This template is a complete worked document for the deposit decay model of an invented community bank. It covers business context and user input, data with quality checks, the method and its results, key assumptions with sensitivity, out-of-time and out-of-sample testing, limitations with compensating controls, implementation, a monitoring plan and version history, following the April 2026 interagency Supervisory Guidance on Model Risk Management (SR 26-2).

Who it is for

The model developer or owner at a bank who must hand validators and examiners a development document that explains what the model does and why it was built that way.

What is inside

  • 11 numbered sections from purpose and scope to version history
  • Worked example: a non-maturity deposit decay model of an invented USD 1.2 billion bank
  • Data table with 4 data sets, periods, record counts and quality checks
  • Results table with decay rates and average life for 4 deposit segments
  • Assumptions table with basis and sensitivity for 4 key assumptions
  • Developmental testing table with out-of-time and out-of-sample results, including a failed test
  • Monitoring plan table with 4 metrics, thresholds and actions, plus a version history table
  • Follows the development and documentation points in the April 2026 interagency guidance (SR 26-2)

How to use it

Replace the worked deposit model with your own model one section at a time, keeping every assumption in the table with its basis and sensitivity.

Files

  • DOCXmodel-development-documentation-template.docx41 KB

Opens in Microsoft Word or Excel, Google Docs or Sheets, and LibreOffice. Built on free, official texts that anyone can read: laws, regulations, standards and guidance published by public bodies. A template to adapt, not legal, tax or accounting advice.

Questions about this template

What should model documentation include?

A clear statement of purpose and intended use, the data and its quality checks, the method and why it was chosen, key assumptions with their basis and sensitivity, developmental testing, limitations, implementation controls and a monitoring plan. The April 2026 interagency guidance links good documentation to continuity and to tracking findings and remediation.

What kind of testing belongs in a development document?

The interagency guidance mentions out-of-sample and out-of-time testing, comparison with alternative assumptions and methods, and a critical look at data quality and relevance. Rigor should match the model's complexity and materiality. Record failed tests too, with the response, as this example does for one deposit segment.

Who writes model documentation?

Usually the developer, with input from the model owner and from users, who know the business context and the decisions the output supports. The validator reviews the document but should not write it, because that would weaken independent challenge. The owner signs it off before it goes to Model Risk Management for validation.