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
DocsWorkspaces
Workspaces

Projects

A Project is the workspace for one engagement or programme. It contains AI Systems, their evidence and decisions, and the people working on them. It is not itself the governed AI System.

In the app
All Projects → New Client Audit
Who can use it
Every plan; the number of active projects depends on your plan.

Create a project

  1. 1Client & programme: enter the client name, programme name, industry, company size and regions, and choose the engagement type.
  2. 2AI in use: list each AI System with its name and what it does, and mark whether it is customer-facing, uses personal data, informs decisions about people or is generative AI. You can skip this step with I'll register systems later.
  3. 3Frameworks: review the recommended frameworks and add or remove any.
  4. 4Review & launch: optionally open a client portal or run a website scan, then choose Create project.

Engagement types

  • Readiness assessment: find the gaps against each framework and agree a plan.
  • Implementation programme: build and evidence the controls with the client's owners.
  • Certification preparation: get the management system ready for an external audit.
  • Continuous assurance: keep controls tested and reviews on schedule over time.

What a project holds

  • AI Systems, vendors, framework assessments, controls, tasks, evidence and policies.
  • Findings, risks, corrective actions, approvals, exceptions, monitoring and incidents.
  • Team members and their roles, the client portal, reports, certificates and the audit trail.

Creating a project opens Framework Assessments, because each selected framework starts as a self-assessment there.

Last reviewed 2 October 2026

Next stepTeams & responsibilitiesInvite people to a project, give them a role, and make ownership explicit with RACI assignments on the records that matter.
CompaniesTeams & responsibilities
On this page
Create a projectEngagement typesWhat a project holds
Capability status

Check current availability and limitations before relying on a feature.

View matrix