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

Technical evaluations

A Technical Evaluation measures AI behaviour against a defined method, dataset and threshold. You run it in your own environment and submit signed results to AIGovernr.

In the app
Project → Understand & Assure → Evaluations

Define the gate

  1. 1Choose Create gate requirement and pick an evaluator from the Evaluator catalog, such as performance, fairness, robustness, privacy or prompt injection.
  2. 2Set the dataset, metric and threshold, and choose Approve new specification version.
  3. 3Choose Queue for external runner, or use CI config to generate a GitHub Actions workflow for your pipeline.

AIGovernr does not execute evaluations itself. Your runner posts an HMAC-signed result, which keeps the result tamper-evident.

Interpret results

  • Each submitted result is stored as evidence and shown in Run history. Choose Check gate to see whether the latest result passes.
  • A failed gate raises a High-severity Finding, linked to a Risk when one is set on the requirement.
  • Use Review nuanced finding and Record attestation when a result needs human judgement.

Last reviewed 2 October 2026

Next stepDPIAA Data Protection Impact Assessment reviews processing that may create a high risk to people's privacy. In AIGovernr each DPIA belongs to one AI System.
Assurance methodsDPIA
On this page
Define the gateInterpret results
Capability status

Check current availability and limitations before relying on a feature.

View matrix