What belongs in a community-bank AI inventory?

Begin with the coverage record.

Record which teams and approved sources the review consulted. Include staff-declared 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, permitted 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.

A review prepares a file. It does not certify compliance, give a legal opinion or connect to a core.

Inspect the review file.

Read a complete illustrative engagement. See the two-week inventory review.

Send the review question.

Tell us the decision, deadline and accountable role. A person will reply within one business day.