RFP Template for Banking
AI Governance RFP Template for Banks with Requirements Aligned to SR 26-2
A defensible AI governance RFP for a bank turns each supervisory expectation into four parts: a requirement statement, a testable vendor question, a named evidence artifact, and a scoring rule. Separate technical requirements, which can be demonstrated, from contractual and procedural requirements, which are verified through documents and legal review. Have compliance confirm each row against the primary text of SR 26-2 before the RFP is issued.
How to use this template
Write every requirement in the RFP as four parts, tied to a supervisory expectation area:
- Requirement: a specific, testable statement.
- Vendor question: a question that asks how the capability works, not whether it exists.
- Required evidence: a demonstration, export, document, or contract term the vendor must supply.
- Scoring rule: defined score levels, set before responses arrive, with a gate or weight.
Label each requirement as technical or as contractual and procedural, because the two types are verified differently.
| Requirement type | How it is verified |
|---|---|
| Technical | Demonstrated by the vendor |
| Contractual and procedural | Documents and legal review |
Requirement matrix
Each row of the matrix carries the same four parts. Use the structure below as the column set for your own requirements.
| Part | Description |
|---|---|
| Requirement | A specific, testable statement tied to a supervisory expectation area. |
| Vendor question | A question that asks how the capability works, not whether it exists. |
| Required evidence | A demonstration, export, document, or contract term the vendor must supply. |
| Scoring rule | Defined score levels, set before responses arrive, with a gate or weight. |
Scoring approach that holds up to review
Label every requirement as a gate or a scored item, and define the score levels for each before responses are received. Approve weights, score definitions, and scorer roles in advance so that scoring can be explained to reviewers afterward.
Ask for evidence that names a specific artifact rather than a general description. For technical requirements, run demonstration scenarios on the bank's own test cases, including a blocked action and its log entry.
Before you issue the RFP
- Compliance has confirmed each requirement against the primary text of SR 26-2 and recorded the citation.
- Every requirement is labeled as a gate or a scored item.
- Evidence requests name a specific artifact, not a general description.
- Demonstration scenarios use the bank's own test cases, including a blocked action and its log entry.
- Weights, score definitions, and scorer roles are approved before responses are received.
- Legal has reviewed the draft contract terms and data handling requirements.