JPMorgan and HSBC Embed AI Governance Into Firm-Wide Risk Structures
Source
The Asian BankerWhat happened
According to a report in The Asian Banker, JPMorgan Chase and HSBC have stopped treating AI governance as a separate compliance function. They are instead weaving it into existing firm-wide risk and control structures. Both institutions link AI oversight to model risk management, data governance, conduct risk, and senior management accountability in a single integrated program. A central tool in this approach is a use-case scorecard. It rates each AI application on dimensions including consumer impact, explainability to regulators, and potential systemic relevance. The scorecard creates a tiered review process, with higher-risk applications requiring more intensive oversight before and after deployment. This mirrors the direction signaled by supervisory guidance, including the Interagency Revised Guidance on Model Risk Management (OCC Bulletin 2026-13, SR 26-2). It also aligns with governance benchmarks discussed in coverage of SR 26-2 Forces Banks to Rethink Model Governance From Inventory to Board Oversight.
Why it matters
- ·Regulators examining banks under the Interagency Revised Guidance on Model Risk Management (OCC Bulletin 2026-13, SR 26-2) now have a peer-institution benchmark to compare against. Firms without integrated AI risk structures face a higher bar to demonstrate supervisory adequacy.
- ·The use-case scorecard model makes explainability and consumer impact formal gate criteria, not aspirational principles. Compliance teams that lack a documented classification process for AI applications risk gaps in audit readiness and regulatory examination responses.
- ·Embedding AI governance under senior management accountability raises the stakes for individual executives. If an AI system causes consumer harm or a conduct breach, the accountability trail now runs to named individuals rather than abstract governance committees.
Governance controls affected
What to do now
- ☐Map your current AI governance structure against your existing model risk, data governance, and conduct risk frameworks to identify where AI oversight sits outside those structures.
- ☐Ask the risk team whether each AI application in use has been classified using a documented scorecard or equivalent tool that records consumer impact and explainability criteria.
- ☐Confirm that a named senior executive is accountable for AI governance outcomes, not just a committee or policy document, and that accountability is recorded in governance documentation.
- ☐Review your AI model inventory to determine which applications would qualify as high-risk under a consumer-impact or systemic-relevance standard, and flag any lacking a formal pre-deployment review record.
- ☐Bring the JPMorgan and HSBC integrated model to your next governance committee meeting as a benchmark and ask whether your program structure would satisfy the same supervisory scrutiny.
What to watch next
Banking supervisors are increasing AI-specific examination activity, and peer institutions are setting documented benchmarks that examiners can reference. The Interagency Revised Guidance on Model Risk Management (OCC Bulletin 2026-13, SR 26-2) is already shaping examination expectations. The Financial Stability Board AI in Finance report continues to influence cross-border supervisory thinking. Compliance teams should monitor whether regulators begin explicitly citing integrated governance structures as a condition of satisfactory examination findings. They should also watch whether the scorecard model used by large institutions becomes an informal industry standard that smaller firms are expected to adopt or explain away.
Stay ahead of stories like this
Get developments like this, plus everything else that matters in AI governance. Every Thursday.
Recent issues
- AI systems built to extend your reach are now extending attackers' reach too, and regulators in California and South Korea are making clear that containment failures belong to deployers, not just vendors.8 Oct
- AI agents this week destroyed backups at machine speed, leaked sensitive data without developer approval, and drew federal scrutiny that may extend liability to every enterprise deploying them.1 Oct
Free every Thursday. Unsubscribe anytime.
