HomeLibraryServicesCase studiesBlogAbout
consultance.ai
Book a discovery call →

Services

  • AI consulting
  • AI implementation
  • AI agents
  • Workflow automation
  • RAG systems
  • Voice AI
  • Custom AI development
  • All services

Library

  • AI build library
  • Finance AI automation
  • AiToEarn content agent
  • Fincept Terminal
  • ERPNext
  • SEO + GEO Claude skill
  • Claude for Legal
  • Free Claude Code proxy

Resources

  • Case studies
  • Blog
  • Industries
  • Locations
  • Guide: AI for property management
  • Guide: AI for marketing agencies
  • Guide: AI agents vs Zapier
  • AI glossary
  • vs traditional consulting

Company

  • About
  • Book a call
  • Contact
  • Privacy
  • Terms

© 2026 consultance.ai · AI, implemented.

audit → build → deploy

← Libraryconsultance.ai
Book a build call
Finance and data

Bank Model Risk Gap Check

8 prompts that map your model inventory to the new SR 26-2 rule, find the validation gaps, and build an examiner-ready file. For model risk officers, CROs, and validation leads.

Free — runs in your own ClaudeTechnical setup · 4 steps8 ready-to-run prompts
Set it up free — takes 3 minutes ↓Or have us wire it in →
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. 1

    Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. 2

    Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. 3

    Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai ↗
  4. 4

    Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

I want to set this up properly so Claude checks my model risk program against the new SR 26-2 rule on my real inventory, not a one-off chat. Walk me through it step by step, do not skip anything. Treat me like a model risk officer, CRO, or validation lead who has never built a Claude Project and does not write code. Define every term once.

This is NOT a Terminal or coding install. There is nothing to compile. It is a private Claude Project where the model inventory and governance docs live.

## The setup — a private Claude Project
Walk me through ONE step at a time, waiting for me to confirm each:

1. **What I need.** A Claude account on a Team or Enterprise plan so the data stays in my tenant. Pin **Opus 5**. Nothing to install.
2. **Make the workspace.** In Claude, create a new **Project** named for the institution and the review. A Project is a private workspace with its own knowledge other chats cannot see. My inventory and reports stay in my own tenant.
3. **Load the records.** Drop the model inventory, the validation reports, and the model risk governance policy into the Project knowledge. A spreadsheet inventory is fine.
4. **Run the vault.** Run prompt 01, pick the scope (full readiness, one model family, the vendor models, or a quarterly refresh) and where the data is. Then run 02 to 08: map to SR 26-2, find the shift-left gaps, re-grade the tiers, catch the vendor models, the self-check, the remediation plan, and the examiner-ready file.
5. **Gate it.** Treat prompt 06 (the self-check) as a hard stop. A **GATE: FAILED** means the two passes disagree on a gap; reconcile before continuing. This is a first-pass readiness review, not a filing. A named risk officer signs; legal and risk own the final program.

## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, SR 11-7, SR 26-2, model inventory, validation, shift left, model tier, third-party and nth-party model, regulated-decision model, review gate.
- Do NOT tell me a step is "not possible." If I cannot find the Project button, it is in the left sidebar of claude.ai.
- Never paste supervised or confidential data into a public chat. Use a Project with my tenant controls.
- This maps the new rule to my inventory and finds the gaps. It does not validate a model or replace my validation function. Not legal or regulatory advice.

First message: ask me "What is the scope: full SR 26-2 readiness across the inventory, one model family, the vendor models, or a quarterly refresh? And do you have the model inventory and governance policy ready to upload?" Then start step 1.
Step 2 · run it on your data

Step 1 set it up. These 8 prompts do the work.

the vault

The 8 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 8 prompts, numbered, in order · nothing left out.
Click to copy
You are my model risk desk under the new SR 26-2 guidance, acting as four people on every answer: a model validation lead, a Fed examiner, a chief risk officer, and a third-party risk lead.

Ask me and wait:
1. What am I running? (A) full SR 26-2 readiness across the inventory (B) one model or model family (C) the vendor and third-party models (D) a quarterly validation refresh
2. Where is the data? (A) I upload the model inventory, validation reports, and governance policy (B) I paste the inventory (C) the Claude add-in for Excel on the inventory workbook
3. Context: institution size and complexity, number of models, and which are high risk or regulated-decision models?

Confirm the setup, then wait for my files. On every answer: cite the SR 26-2 expectation, the model or control it applies to, and the gap. Flag anything you cannot tie to my data. End with: "First pass readiness review, not a filing. A named risk officer signs."
Click to copy
Using the data from prompt 01, map every model to the SR 26-2 expectations: governance, development standards, validation, ongoing monitoring, and use. For each model, mark which expectations are met, partial, or missing. Scale the rigor to the model's risk and complexity, as the rule now allows. Output the coverage matrix. First pass only; a named risk officer signs.
Click to copy
SR 26-2 pushes risk controls to day one of the model lifecycle. Find where my current process bolts controls on late instead of at the start: requirements, data quality, development review, and pre-deployment validation. List each gap, the lifecycle stage it belongs in, and the control to add. First pass only; a named human owns the fix.
Click to copy
Re-grade every model to its risk tier under the new profile-based approach. Flag models that were under-tiered (too little oversight for their risk) and over-tiered (wasted effort on low-risk models). Give the recommended tier, the reason, and the oversight each tier now requires. First pass only; a named human confirms.
Click to copy
List every vendor, third-party, and embedded model you can find in my data, including the ones outside the formal inventory. For each: the owner, the validation status, the data it touches, and the nth-party exposure (the vendor's own models). Flag the ones with no validation and no owner. First pass only; a named human owns third-party risk.
Click to copy
Independently re-derive the gap list WITHOUT reusing your earlier work. Re-read the inventory and the SR 26-2 expectations fresh, and list the missing and partial controls again. Compare to prompts 02 and 03. If the two passes disagree on any material gap, output "GATE: FAILED" with the discrepancy and reconcile it before continuing. If they agree, output "GATE: PASSED" and the confirmed gap list. Show the re-derivation.
Click to copy
Only if prompt 06 returned GATE: PASSED. Build the remediation plan: each gap, the SR 26-2 expectation it closes, the owner, the effort, and the priority by risk. Sequence the high-risk and regulated-decision models first. Output the plan as a table a CRO can take to the committee. First pass only; a named risk officer signs.
Click to copy
Assemble the examiner-ready summary: the inventory coverage, the open gaps, the remediation plan with dates and owners, and the governance structure that owns model risk. Write it so an examiner can see the institution knows its gaps and is closing them. First pass only; legal and risk own the final file.

Got the prompts. Want them wired into your actual stack? We map that on a free AI audit.

Book the free audit

Rent it forever, or own it once.

8 prompts that map your model inventory to the new SR 26-2 rule, find the validation gaps, and build an examiner-ready file

Path A · free

You just did it

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts ↑
Path B · done with you

We wire it into your business

We would deliver a private model risk workspace: the prompts loaded into your Claude tenant, a connector to your model inventory system, the SR 26-2 mapping and self-check wired as standing controls, and a remediation tracker your CRO can take to the committee and your examiner will accept. Done with you, then handed over so you own it.

Book a build call →
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Prompt set authored by consultance.ai. SR 26-2 and the Fed, FDIC, and OCC are referenced as the public April 17, 2026 supervisory guidance, no affiliation implied. Your inventory stays in your own Claude tenant; we never see it. This is a first-pass readiness review, not a regulatory filing; a named risk officer signs and legal and risk own the program. Not legal or regulatory advice.

Want this running in your business, not just your laptop? We build it and hand you the keys.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

the newsletter

AI news worth opening.

The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.

100% freeNo paywall, everUnsubscribe anytime

More like this

Other builds worth a weekend

All repos →
Finance and data

Free Portfolio Quant Research Desk

For family offices and serious individual investors: run a portfolio backtest, tax loss harvesting, and model risk checks on your own holdings, locally, in your own Claude. Replaces the $250k quant seat you would otherwise hire.

Setup guide →
Finance and data

Private Equity Deal Sourcing Playbook

For lower and mid market private equity origination teams: turn one mandate into a ranked, owner verified proprietary deal flow pipeline. Six Claude agents with Exa and Scrapling replace a rented deal sourcing subscription.

Setup guide →
Finance and data

Free Jira Alternative for Deal Teams

For PE deal teams and IC members still tracking a live process on a sprint board: a self hosted deal tracker your Claude can write to, plus 10 prompts that move a workstream only when the document actually lands.

Setup guide →
Get the free kitBook a call

Forward this to whoever owns the workflow.

The person drowning in this every week is the one who'll actually want it.

Forward by email
in one line

What is Bank Model Risk Gap Check?

Bank Model Risk Gap Check is a finance and data build in the consultance.ai AI Build Library. 8 prompts that map your model inventory to the new SR 26-2 rule, find the validation gaps, and build an examiner-ready file. For model risk officers, CROs, and validation leads. It fits bank model risk officers, CROs, model validation leads, and risk advisory teams in scope for SR 26-2. Setup difficulty is Technical, with 4 plain-English steps.

What does Bank Model Risk Gap Check do?

8 prompts that map your model inventory to the new SR 26-2 rule, find the validation gaps, and build an examiner-ready file. For model risk officers, CROs, and validation leads.

Who is Bank Model Risk Gap Check for?

It fits bank model risk officers, CROs, model validation leads, and risk advisory teams in scope for SR 26-2.

How hard is Bank Model Risk Gap Check to set up?

Technical to set up — one guided setup instruction covering 4 plain-English steps, plus 8 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

We would deliver a private model risk workspace: the prompts loaded into your Claude tenant, a connector to your model inventory system, the SR 26-2 mapping and self-check wired as standing controls, and a remediation tracker your CRO can take to the committee and your examiner will accept. Done with you, then handed over so you own it.

What are the licensing terms?

Prompt set authored by consultance.ai. SR 26-2 and the Fed, FDIC, and OCC are referenced as the public April 17, 2026 supervisory guidance, no affiliation implied. Your inventory stays in your own Claude tenant; we never see it. This is a first-pass readiness review, not a regulatory filing; a named risk officer signs and legal and risk own the program. Not legal or regulatory advice.

Want this built into your workflow?

Bank Model Risk Gap Check is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book your free AI audit