AIGovernrAIGovernrDocs
Ctrl K
Open workspace
Getting started
AIGovernr documentationQuickstartNavigating the appCore conceptsHow everything connects
Workspaces
CompaniesProjectsTeams & responsibilitiesDashboards & assignments
Account & administration
Plans & billingAccess control & rolesAccount securityNotifications
AI systems
AI SystemsRegister an AI SystemAI System classificationAI System Governance planGovernance plan vs PlaybookSystem documentation & testing recordsVendors & dependenciesShadow AI & asset graph
Obligations
Frameworks & obligationsRequirements & tasksGovernance knowledgeRegulatory updates
Assurance
Assure overviewControlsAssurance methodsTechnical evaluationsDPIAEvidence managementISO/IEC 42001 readinessGovernance maturity
Issues & actions
Findings vs risksCorrective actions
Decisions
ApprovalsApproval PoliciesDecision LedgerExceptions & reassessment
Continuous governance
MonitoringIncidentsAgent & MCP governance
Reusable governance
AI governance policiesPolicy templatesPlaybooks
Reporting
Reports, certificates & audit export
Client collaboration
Client portal & engagement
Guides
Run a client governance engagementOperate an AI governance programmeFramework implementation guides
Discovery tools
Website Compliance Scanner
AI assistance
AI Assistant
Developers
Integrations & APIs
Help
Troubleshooting & FAQ
DocsAI systems
AI systems

AI System Governance plan

The Governance plan shows, for one AI System, which frameworks apply, which workspaces are required, and the controls, open work and risks that follow.

In the app
AI System → Governance plan, or Project → Discover & Register → Governance Plans for every system

The plan is built from the frameworks in scope for the project and the system's recorded facts. It updates when an assessment is re-approved or the system's facts change; there is nothing to generate by hand.

What the plan shows

  • Frameworks that apply: the project frameworks relevant to this system.
  • Required workspaces: the assessments the system needs, such as DPIA, bias assessment, human oversight or technical documentation. Each shows Not required, Not started, In progress, Complete or Needs attention.
  • Controls: the controls mapped to the system and their status.
  • Open work and Risks: outstanding tasks and the system's risks.

Work through the plan

  1. 1Open each required workspace that is not complete and finish it.
  2. 2Use Open system assurance to test controls and attach evidence.
  3. 3When the plan is complete, use Request decision with the action Approve governance plan to record formal acceptance.

When it changes

Adding a framework, re-approving an assessment or changing the system's facts updates the plan. Earlier decisions stay in the Decision Ledger, so you can see what was approved before the change.

Last reviewed 2 October 2026

Next stepGovernance plan vs PlaybookA Governance plan shows what applies to one system. A Playbook is a reusable sequence of steps for carrying out a known scenario.
AI System classificationGovernance plan vs Playbook
On this page
What the plan showsWork through the planWhen it changes
Capability status

Check current availability and limitations before relying on a feature.

View matrix