AI Use Case Portfolio

How to use this document

• What it is for. This is the register of the organization's demand for AI: every proposal, case under assessment and pilot, with its priority, risk level, state and next decision. It is used to decide what moves forward, what waits and what is rejected, without duplicating the AI system inventory or inventing a prioritization method of its own.
• Who should own it. The AI lead, who keeps it up to date or delegates its upkeep to [RESPONSIBLE FUNCTION] ([OWNER]). Each case has a system owner and a sponsor in management.
• Decisions to take first. Decide where the register will live (spreadsheet, project tool or similar; the tables in Section 10 provide the structure) and the date of the first review. Prioritization weights and thresholds are not decided here: they are set once, in the "AI Impact-Risk Prioritization Matrix."
• How it fits with other documents. Cases come in through the "AI Use Case Proposal Form," are prioritized with the "AI Impact-Risk Prioritization Matrix," are classified with the "AI Risk Classification Matrix" and are approved in the lane set by the "AI Governance Operating Model." When a case moves to pilot it is added to the "AI System Inventory," which from then on is the source of the risk level, owner and review date.
• Fields to complete. Replace the bracketed fields. Rows marked "Example" show how the register is completed: delete them before use.
• Country variants. This document has no country variants. The categories each law sets are reflected in the classification matrix; see "Related regulatory references."
• Review and approval. Have legal and the data protection officer (or the country's equivalent role) validate the screen in Section 6. The AI lead approves these rules (at the standard or reinforced level, the AI committee) and records the approval in "Version history." The register's content is updated continuously and does not require new approval.

AI Use Case Portfolio

Field	Value
Organization	[LEGAL ENTITY NAME]
Register owner	AI lead
Maintained by	[RESPONSIBLE FUNCTION]; [OWNER]
Rules approved by	[APPROVED BY]
Rules approval date	[DATE]
Review frequency	[REVIEW FREQUENCY]
Channel to propose cases	[AI GOVERNANCE EMAIL]

1. Purpose

This portfolio brings together in one place the AI initiatives [ORGANIZATION NAME] wants to assess, pilot or drop. Its aim is to provide visibility, avoid duplication, invest in the initiatives with the best balance between value and risk within the risk appetite (see "AI Risk Appetite Statement") and ensure that none moves forward without the analysis its risk level calls for.

2. Scope

2.1 The register covers:

a) proposals to use AI from any department;
b) cases under assessment and in pilot;
c) cases in production while their benefits are still being measured (their operational record lives in the AI system inventory);
d) rejected or retired cases, with their reason, when the lesson remains useful.

2.2 It covers in-house development as well as buying tools or switching on AI features in software already contracted when they change a process in a significant way. Using tools already authorized by the "Responsible AI Use Policy (Including Generative AI)" for ordinary tasks does not need to go through the portfolio.