Skip to main content
LLM Squared

What belongs in a community-bank AI inventory?

List the AI your bank uses, why it uses it and who owns each use. Note which records you have and what you still need to check.

Updated .

Begin with the coverage record.

Record which teams and approved sources the review consulted. Include staff-listed use and vendor features that may include AI. Keep unconfirmed features visible rather than treating the list as a complete census.

Separate the use from its evidence.

For each use, record where it runs, data categories, the owner, allowed evidence and the question still open. Keep the source version and approval basis in supporting records. A proposal supplies a reference; it does not establish that a control works.

Assign the next action.

Give each gap an accountable role, a due date and a review trigger. Record who judges evidence sufficient and who accepts the use. Keep the institution decision separate from the prepared inventory.

Sources and applicability.

CSBS AI Supervisory Framework. Source checked October 5, 2026. States decide how to use this framework for state-chartered banks and nonbanks; it creates no new legal obligations.

NCUA AI resources apply to the credit-union route. National banks should use their OCC supervisory route.

Review limits and responsibilities are described in the method. Read the method.

Send the review question.

Tell us the decision, deadline and accountable role.

Book a call