AskAjay.ai

The Governance Playbook:
From Principles to Practice

An operational worksheet for translating AI principles into enforceable governance, structured around the Five-Layer Governance Stack and the three risk tiers from Minimum Viable Governance.

5 Layers · 3 Risk Tiers · NIST Layer Map Version 1.3 · Updated 2026-10-04 © AskAjay.ai

Canonical reference: Show Me the Last Time Your AI Principles Changed a Decision

One model, three stages: Assess, days 0 to 90 (the MVG worksheet) → Align, months 3 to 6 → Assure, ongoing. This worksheet covers Align and Assure.

How to Use This Worksheet

  1. Gather your team: AI leadership, legal, risk, and engineering leads. Schedule a 90-minute working session.
  2. Work through each layer in order: Policy → Process → Tooling → People → Assurance. Each layer depends on the ones before it: tooling automates what policy defines and process enforces, and assurance checks all four. Every system should already have its named owner from MVG; if one does not, name it before anything else.
  3. Confirm risk tiers: Each system keeps the tier it got in Minimum Viable Governance. Use the Risk-Tiering section to check it and to tier any new system. Different tiers get different governance intensity.
  4. Run the Anti-Pattern Diagnostic: Honestly assess which governance failures exist in your organization today.
  5. Build your sprint plan: Use the Implementation Sprint Planner to set owners and deadlines for each action item.
  6. Score your readiness: Complete the Governance Readiness Scorecard to track progress over time.
The core premise: AI principles that don't change decisions are decoration. AI governance that changes decisions is infrastructure. This worksheet helps you build the infrastructure.
Brand commitments behind this worksheet

Principles do not govern. Processes do. A signed AI ethics statement is not governance. Governance is who decides, on what evidence, with what consequences for getting it wrong. The five-layer stack (Policy, Process, Tooling, People, Assurance) is the structure that converts principles into operational discipline.

Every layer needs a named owner. Not a committee. Not a department. A named individual with the authority to decide and the accountability to be wrong. Governance without an owner is theatre. The accountability matrix on this worksheet is the discipline that prevents theatre.

Layer 1: The Policy Layer

1
Policy Layer: What You Enforce
Translate abstract principles into specific, testable policy statements. Each policy should be falsifiable: you can objectively determine whether a system complies or not.

Principle-to-Policy Translation

For each principle, write a corresponding testable policy statement.

AI Principle Testable Policy Statement Metric / Threshold Applies to Tier
Fairness
Transparency
Accountability
Safety
Privacy

Policy Falsifiability Check

For each policy statement above, confirm it passes this test:

Can an independent reviewer determine compliance with a yes/no answer?
Is there a specific metric or threshold defined?
Is the enforcement mechanism specified (what happens if violated)?
Is the scope clear (which AI systems does this apply to)?
Layer 1 Checkpoint: You should now have testable policy statements for each of your AI principles, with metrics, thresholds, and clear scope. If a policy can't be tested, it's still a principle. Rewrite it.

Layer 2: The Process Layer

2
Process Layer: How It Flows
Define workflows that enforce policies: review gates, approval chains, escalation paths, and exception procedures. Critical rule: embed into existing development processes, not parallel tracks.

Governance Gate Map

Map each governance gate to its trigger, reviewer, and SLA.

Gate Name Trigger / When Reviewer / Approver SLA (hours/days) Exception Process
Design Review
Data Review
Fairness Review
Pre-Production
Deployment Gate
Post-Launch Review

Escalation Path

System Tier Escalation To Response Time Decision Authority
Low tier
Medium tier
High tier
High tier, most critical systems
Layer 2 Checkpoint: You should now have a governance gate map with named reviewers, SLAs, and exception processes. Every gate must have an owner. If a gate has "the committee" as reviewer, it's a bottleneck. Assign a named individual.

Risk-Tiering Model

Not every AI application requires the same governance intensity. Classify each application by risk tier, using the same three tiers as Minimum Viable Governance, so a system keeps the tier it got in its first 90 days. These are internal tiers. They sit alongside the EU AI Act's legal categories and do not replace them: record the Act classification separately in the inventory below. Practices the Act prohibits, such as social scoring (Article 5), are not a tier at all.
High: Affects a person's rights, safety, money or job, such as credit, hiring, pricing and eligibility. A VP or a named executive approves. Reviewed monthly. The most critical (clinical, justice, safety) also get an external audit.
Medium: Shapes business decisions or customer experience, such as forecasting, process automation and customer chatbots. The AI lead approves. Reviewed quarterly.
Low: An internal tool with no consequential output. The team self-certifies. Reviewed yearly.

AI System Risk Inventory

AI System Owner Decisions Influenced Risk Tier EU AI Act Classification Governance Status

Risk Tier Decision Criteria

For each system, evaluate these factors to assign a tier:

Does the system make or influence decisions about individuals?
Could system failure cause financial harm exceeding $100K?
Does the system process data from protected populations?
Is the system subject to specific regulatory requirements?
Could system failure cause reputational damage visible to customers?
Does the system operate autonomously without human oversight?

Layer 3: The Tooling Layer

3
Tooling Layer: How It's Automated
Automate policy enforcement through technical controls, once the policies and gates exist. A tool automates a policy; it cannot write one.

Automation Coverage Assessment

Governance Function Current State Target Tool / Platform Priority Timeline
Bias / Fairness Testing
Model Card Generation
Drift Monitoring
Explainability Reporting
Data Lineage Tracking
CI/CD Gate Enforcement
Incident Alerting
Audit Trail / Logging
Layer 3 Checkpoint: You should now have an automation coverage map. Prioritise: (1) CI/CD gate enforcement for high-tier systems, (2) drift monitoring for production models, (3) audit trail for all deployed systems.

Layer 4: The People Layer

4
People Layer: Who Decides
Every governance decision should have a single named accountable individual, not a committee. Committees advise; individuals decide.

Accountability Matrix (RACI)

Governance Activity Responsible (Does) Accountable (Owns) Consulted Informed
Policy Creation
Risk Tier Classification
Fairness Review
Deployment Approval
Incident Response
Regulatory Compliance
External Audit
Governance Framework Review

Key Leadership Roles

Role Named Individual Decision Authority Escalation To
Chief AI Officer / AI Lead
AI Governance Owner
AI Ethics Lead
Legal / Compliance Lead
Executive Sponsor

Layer 5: The Assurance Layer

5
Assurance Layer: How You Know It Works
Governance should have its own KPIs, reviewed at the executive level. Without assurance, you're trusting the system to police itself.

Governance KPI Dashboard

Category KPI Current Value Target Review Cadence Owner
PreventionDeployments caught pre-production
PreventionEstimated cost avoidance ($)
EfficiencyAvg. time to governed deployment
Efficiency% reviews within SLA
Compliance% AI systems with documentation
ComplianceShadow AI exposure count
TrustStakeholder confidence score
TrustGovernance maturity score

Audit & Review Schedule

Review Type Frequency Scope Reviewer Next Scheduled
Governance Framework ReviewQuarterly
Model Performance ReviewMonthly
Regulatory Alignment CheckQuarterly
External AuditAnnual
Executive Governance ReportQuarterly
Layer 5 Checkpoint: You should now have governance KPIs with owners and targets, plus a scheduled audit cadence. If governance doesn't have its own OKRs reviewed at the executive level, it won't survive the next budget cycle.

Anti-Pattern Diagnostic

Honestly assess whether each anti-pattern exists in your organization. Check the box if you recognize the symptom.

The Paper Tiger
Governance documents exist but have never blocked a deployment or changed a decision.
The Bottleneck Board
A single committee reviews all AI applications. Teams bypass governance because it's too slow.
The One-Size-Fits-All
Internal dashboards and customer-facing credit models get the same governance treatment.
The Measurement Mismatch
Employees are told to be responsible but are measured only on speed and productivity.
The Set-and-Forget
Governance framework hasn't been updated in 6+ months despite regulatory and technology changes.

Count of anti-patterns present: _____ / 5

0 = Mature governance. 1–2 = Address during next review cycle. 3+ = Governance requires immediate structural intervention.

Governance Readiness Scorecard

Rate your organization's current state for each governance layer.

Layer 1: Policy
Not Started
In Progress
Complete
Layer 2: Process
Not Started
In Progress
Complete
Layer 3: Tooling
Not Started
In Progress
Complete
Layer 4: People
Not Started
In Progress
Complete
Layer 5: Assurance
Not Started
In Progress
Complete
Risk Tiering Applied
Not Started
In Progress
Complete
Anti-Patterns Addressed
Not Started
In Progress
Complete

The Five Layers Against the NIST AI RMF

MVG's documents answer 12 of the 72 subcategories in NIST AI 100-1 (AI RMF 1.0). Align and Assure map the other 60. Each subcategory is listed once, under the layer that does most of the work; many touch more than one.

Layer Starts with, from MVG Added in Align and Assure
PolicyAI system inventory (GOVERN 1.6); governance charter (GOVERN 1.4)GOVERN 1.1, 1.2, 1.3, 6.1; MAP 1.3, 1.5, 1.6, 3.3
ProcessContext and impact record (MAP 1.1); risk register (MAP 5.1, MANAGE 1.2); deployment gate (MANAGE 1.1); escalation and incident procedure (MANAGE 4.1, 4.3)GOVERN 1.7, 4.2, 6.2; MAP 1.4, 2.1, 3.1, 3.2, 4.1, 4.2; MEASURE 2.2, 3.3; MANAGE 1.3, 1.4, 2.1, 2.3, 3.1
ToolingBaselines and thresholds (MEASURE 1.1); production monitoring (MEASURE 2.4)GOVERN 4.3; MAP 2.2, 2.3; MEASURE 2.1, 2.3, 2.5, 2.6, 2.7, 2.9, 2.10, 2.11, 2.12, 3.1; MANAGE 2.2, 3.2
PeopleAccountability matrix (GOVERN 2.1); authority to pause (MANAGE 2.4)GOVERN 2.2, 2.3, 3.1, 3.2, 4.1; MAP 1.2, 3.4, 3.5
AssuranceThe next review date, set at the deployment gate (no MVG subcategory)GOVERN 1.5, 5.1, 5.2; MAP 5.2; MEASURE 1.2, 1.3, 2.8, 2.13, 3.2, 4.1, 4.2, 4.3; MANAGE 4.2

Source: NIST AI 100-1, January 2023, Tables 1 to 4. The canonical article gives a short description of each group.

Implementation Sprint Planner

Use this planner to assign owners and deadlines for the Align stage. Recommended timeline: 13 weeks, weeks 14 to 26 (months 3 to 6), picking up where the MVG worksheet's 13-week planner ends.

Weeks 14–15
Complete Policy Layer (principle-to-policy translations)
Owner: ____________
Carry over the MVG inventory and charter as the first Policy entries
Owner: ____________
Check every system still has its named MVG owner, starting with the high tier
Owner: ____________
Weeks 16–17
Confirm each system's MVG risk tier; tier any new system
Owner: ____________
Run policy falsifiability checks
Owner: ____________
Design governance gate map (Process Layer)
Owner: ____________
Define escalation paths by severity
Owner: ____________
Weeks 18–19
Complete tooling assessment and prioritization
Owner: ____________
Implement CI/CD gates for high-tier systems
Owner: ____________
Set up drift monitoring for production models
Owner: ____________
Weeks 20–21
Complete accountability matrix (RACI)
Owner: ____________
Extend owners into full roles and decision rights
Owner: ____________
Conduct anti-pattern diagnostic
Owner: ____________
Weeks 22–23
Set governance KPIs with targets
Owner: ____________
Establish audit and review schedule
Owner: ____________
Schedule first executive governance report
Owner: ____________
Weeks 24–26
Complete readiness scorecard assessment
Owner: ____________
Address highest-priority anti-patterns
Owner: ____________
Present governance framework to executive team
Owner: ____________
Month 6 on
Assure: keep reviewing each system on its tier's cadence (high monthly, medium quarterly, low yearly). Reviews began at each system's MVG review date, during Align.
Owner: ____________
Feed audit findings, incidents and rule changes back into the Policy layer
Owner: ____________

Notes & Action Items

Glossary

Definitions used throughout this worksheet. These align with the canonical methodology article.

Five-Layer Governance Stack. Policy → Process → Tooling → People → Assurance. The five operational layers that together convert AI principles into enforceable governance. Skipping any layer creates a gap that compounds.

Risk Tier. High, Medium and Low, the same three tiers as Minimum Viable Governance. High affects a person's rights, safety, money or job; Medium shapes business decisions or customer experience; Low is an internal tool with no consequential output. Higher tiers get more senior approval and more frequent review. Internal tiers, separate from legal classifications such as the EU AI Act's.

Assess, Align, Assure. One model in three stages. Assess (days 0 to 90) is Minimum Viable Governance. Align (months 3 to 6) builds each MVG document out into its layer. Assure (ongoing) runs the Assurance layer: reviews on each tier's cadence, with findings fed back into Policy.

Falsifiable Policy. A policy that specifies measurable, auditable conditions for compliance. “Be fair” is not falsifiable. “True and false positive rates within five percentage points across legally protected groups, tested before release and monitored monthly” is.

Anti-Pattern. A common governance failure mode that looks like governance but does not function as governance. The five named anti-patterns: Paper Tiger, Bottleneck Board, One-Size-Fits-All, Measurement Mismatch, Set-and-Forget.

RACI (Responsible / Accountable / Consulted / Informed). The accountability matrix for governance decisions. Each AI lifecycle event must have exactly one Accountable party. Multiple Accountables is the same as zero Accountables.

Governance Gate. A mandatory checkpoint in the AI lifecycle (deployment approval, model retirement, incident response) where governance criteria must be met before proceeding. Skipping a gate accumulates governance debt.

SLA (Service Level Agreement) for Governance. A defined response time for governance decisions, for example deployment approval within 5 business days, incident response within 1 hour for P1. Without SLAs, governance becomes the bottleneck the business routes around.

EU AI Act Penalty Tiers (Article 99). Up to €35M or 7% of worldwide annual turnover for prohibited practices (Art. 99(3)); up to €15M or 3% for breaches of operator obligations, including providers' high-risk duties, deployers' duties under Article 26 and the Article 50 transparency duties (Art. 99(4)); up to €7.5M or 1% for supplying incorrect, incomplete or misleading information to notified bodies or national competent authorities in reply to a request (Art. 99(5)). For companies, whichever is higher; for SMEs, whichever is lower (Art. 99(6)); for small mid-caps, whichever is lower for the 99(4) and 99(5) fines (Art. 99(6a), added by Regulation (EU) 2026/1744). Calibrate the assurance layer to these exposures.

Evidence Base

This worksheet is the operational layer of a published, sourced framework. The methodology, anti-pattern analysis, and external citations live in the canonical article below.

Canonical article: Show Me the Last Time Your AI Principles Changed a Decision: the five-layer stack, the three risk tiers shared with MVG, the NIST layer map and the five failure patterns, with sources.

Companion frameworks:

Key external sources: EU AI Act, consolidated text (AI Act Service Desk) · Regulation (EU) 2026/1744 · NIST AI 100-1 (AI RMF 1.0) · Fairlearn · AI Fairness 360