Skip to content
AI Policy Generator

Procedures and protocols · Procedure · Operations

Model Explainability (XAI) Procedure

Defines which explainability techniques to use by model type and audience, how to document them and how to turn them into plain-language explanations.

GROU LLC · built on AI Business Core, by Vreinn · · How we verify sources

Who it helps

Teams building models whose decisions are explained to customers, auditors or regulators.

Who uses it
Data science, product, risk and customer service
Usual owner
Data science
Formats
DOCX, PDF
Languages
Español, English
Approximate length
4 pages
Length
Standard. A complete policy, procedure, plan or guide, with roles, deadlines and evidence.
Document type
Procedures and protocols. Concrete steps for a task: who does what, in what order, by when and what gets recorded.
Document code
APG-OPS-004. APG is the AI Policy Generator collection, OPS the area (Operations) and the number identifies the document. Use it to cite the document in your document system.

Preview

Excerpt generated from the document: the "How to use this document" section, the title and the first two sections, plus the full table of contents. The rest of the text is not shown.

APG-OPS-004 · Version 1.1.0 · sources as of November 4, 2026

How to use this document

  • What it is for. This is a base technical procedure to decide which explainability techniques to use by model type, how to validate and document them, and which technical outputs (main factors, reason codes, counterfactuals) to hand to those who explain decisions to people, and to reviewers, auditors and authorities. It does not govern how requests for explanation from people are handled: that belongs to the "AI Transparency and User Explanation Policy."
  • Who should own it. Usually the data science technical team, on behalf of system owners and coordinated by the AI lead. Enter the function in [RESPONSIBLE FUNCTION] and the person in [OWNER].
  • Decisions to take first. Before adopting it, decide how you classify your systems by explainability level (Section 4), which technical tools the team uses, who reviews the reason code texts (Section 9) and what information you treat as a trade secret (Section 12).
  • Fields to complete. Replace the bracketed fields, such as [ORGANIZATION NAME], [AI COMMITTEE], [REVIEW FREQUENCY] and [COMPLETE], and prepare an explainability sheet (aid E) for each level E2 or E3 system.
  • Country variants. This document has no country variants. The minimum content and deadlines for explanations given to people differ by law; they are handled in the "AI Transparency and User Explanation Policy" and the "Automated Decision Review Procedure," which contains the country variants.
  • Review. Ask legal and the data protection officer to review the reason code texts and the handling of trade secrets, and the AI lead to validate the level classification.
  • Approval and publication. Have it approved by [AI COMMITTEE] or data leadership, record the approval in "Version history" and share it with data science teams and system owners.

Model Explainability (XAI) Procedure

Field Value
Organization [LEGAL ENTITY NAME]
Owning function [RESPONSIBLE FUNCTION]
Procedure owner [OWNER]
Approved by [APPROVED BY]
Effective date [DATE]
Review frequency [REVIEW FREQUENCY]

1. Purpose

1.1 This procedure sets out how [ORGANIZATION NAME] selects, applies, validates and documents explainability mechanisms for its AI systems, and how it turns their results into useful explanations for each audience.

1.2 Its aim is that the organization can explain, where appropriate, what each system does, why it produced a given result, how it is controlled and what the affected person can do, without claiming more than the technique can support.

2. Scope

2.1 It applies to AI systems developed, fine-tuned or integrated by the organization whose outputs:

a) are used to make or support decisions about people;
b) must be justified to clients, auditors, supervisors or authorities;
c) feed regulated processes, such as creditworthiness assessment, insurance, hiring or workforce management.

2.2 For third-party systems, the organization obtains from the vendor the information needed to apply this procedure, or uses techniques that do not require access to the inside of the model.

Full table of contents of the document:

  • 1. Purpose
  • 2. Scope
  • 3. Definitions
  • 4. Proportionality: explainability levels
  • 5. Audiences and types of explanation
  • 6. Selecting techniques
  • 7. Reasons for unfavorable results
  • 8. Validating explanations
  • 9. Hand-off to explanations for people
  • 10. Documentation
  • 11. Explainability fields in the decision log
  • 12. Trade secrets and security
  • 13. Monitoring and limitations
  • 14. Review of the procedure
  • Implementation aids
  • Related regulatory references
  • Version history

Rules in the registry whose obligations relate to this base document, based on our reading of the sources. It does not mean they apply to you.

Argentina

Brazil

Chile

Ecuador

Spain

European Union

Mexico

Peru

United States (federal)

California

Colorado

Kits that include this document

Includes 7 documents

Credit and Insurance Kit

Model risk with inventory and materiality, adverse-decision explanation letters, human review, a decision log, technical model documentation and the EU AI Act Art. 26 checklist for high-risk systems.

USD 139USD 253

Complete kit · available to buy

Includes 91 documents

Complete pack

Every sellable template in the catalog in a single pack: base policies, procedures, registers, notices and matrices to adapt with your own team, at a flat price below the sum of the individual documents.

USD 297USD 3393

Complete kit · available to buy

What AI Policy Generator is and how it works