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
DocsContinuous governance
Continuous governance

Monitoring

Governance does not end at approval. Monitoring checks runtime signals against thresholds and reopens governance work when a decision may no longer be valid.

In the app
Project → Decide & Operate → Monitoring (tabs: Runtime Inbox, Web Scan, AI Plans)

Runtime monitoring

  1. 1Create a signal source and save its ingestion key. The key is shown once.
  2. 2Send signals from your system to the runtime signals API with the key. See Integrations & APIs.
  3. 3Set a threshold for each signal.
  4. 4When a threshold is breached, AIGovernr records a material change, an impact assessment, a reassessment case and an incident, and can pause affected decisions.
  5. 5Handle the breach in Runtime Inbox: Acknowledge, Start investigation, then Resolve with evidence.

Other monitoring

  • AI Plans: per-system monitoring plans with KPIs, alert rules and review frequency. They document what to watch; signals still come from runtime monitoring.
  • Web Scan: scheduled re-scans of the project's website.

What triggers reassessment

  • Runtime threshold breaches.
  • Validated vendor material changes.
  • Regulatory updates marked Action required.
  • Decision expiry, stale evidence, or a change of risk tier.

Last reviewed 2 October 2026

Next stepIncidentsRecord AI incidents, track regulatory notification deadlines, and connect the incident to the corrective actions and reassessments it causes.
Exceptions & reassessmentIncidents
On this page
Runtime monitoringOther monitoringWhat triggers reassessment
Capability status

Check current availability and limitations before relying on a feature.

View matrix