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
DocsAssurance
Assurance

Controls

A Control is a practical, recurring measure that meets requirements or reduces risk. You build it, test it, and keep evidence that it works.

In the app
Project → Understand & Assure → Controls

Example

Requirement: high-risk AI systems need effective human oversight. Control: every high-impact AI recommendation is reviewed by a person before it is acted on.

Control lifecycle

  1. 1Choose New Control, or add one from the Control Library, and link the requirements it covers.
  2. 2Assign an owner and build it. The control moves through Build, Ready to test, Test and Passed.
  3. 3Choose Request evidence or Add evidence to collect proof.
  4. 4Choose Run control test and record Pass, Fail or Not applicable, with the evidence you reviewed.
  5. 5A Fail raises a linked Finding automatically. Choose Remediate to start a corrective action, then Retest when it is fixed.

What a control is not

  • It is not the requirement; it is how you meet it.
  • It is not the one-off task used to build it.
  • It is not the test used to check it.

Last reviewed 2 October 2026

Next stepAssurance methodsDifferent questions need different methods. Several methods can support the same decision.
Assure overviewAssurance methods
On this page
ExampleControl lifecycleWhat a control is not
Capability status

Check current availability and limitations before relying on a feature.

View matrix