Practice Compliance

A full collaborative working environment for compliance officers — assembling documentation, creating auditor data packages, engaging with external regulators, and managing the policy landscape that governs AI systems across your organisation.

Evidence

Documentation & Evidence

Every compliance obligation requires evidence. Practice Compliance structures the creation, assembly, and delivery of that evidence — from initial documentation through audit-ready packages.

Documentation Assembly

Annex IV & XI

Structured document creation mapped to Annex IV and XI requirements — section-by-section with collaborative editing, version control, and evidence attachment. Every document section links to the regulatory requirement it satisfies. Evidence files are attached with SHA-256 hashing for integrity verification. No more scattered documents across shared drives.

Auditor Data Packages

PDF/A-3

One-click audit pack generation. All documentation, evidence, approval records, and attestations assembled into a PDF/A-3 archive with a manifest and checksums. The auditor receives a single, self-contained package with cryptographic proof that nothing has been altered since assembly. Reduce audit preparation from weeks to minutes.

External Audit Room

Scoped Access

Scoped, read-only access for external auditors. Time-limited access tokens, permissioned views restricted to the AI systems under review, and full access logging — who viewed what, when, for how long. Auditors see exactly what they need, nothing more. Every access event is recorded in the immutable audit trail.

Regulator Engagement

National Authorities

Structured templates for national authority interaction — registration submissions, notification letters, information request responses, and correspondence tracking. Each template follows the format expected by the relevant authority. Correspondence history is maintained with full version control and approval workflows.

Policy Management

Policy Library & Policy Lab

Policies are the foundation of AI governance. The Policy Library manages your existing policies. The Policy Lab helps you create new ones — with AI-assisted drafting grounded in your regulatory profile.

Policy Library

Governance

Centralised management of AI governance policies, acceptable use policies, data handling policies, and incident response procedures. Every policy is version controlled with full change history. Assigned ownership ensures accountability. Review schedules trigger automated reminders. Attestation tracking records who has read and acknowledged each policy — and who hasn't.

Policy Lab

AI-Assisted

AI-assisted policy creation — draft new policies using templates and regulatory context. The Policy Lab suggests clauses based on your regulatory profile, flags gaps against best practice frameworks, and ensures consistency with existing policies in your library. Output is always a draft for human review — the AI accelerates creation, your compliance team approves.

Operations

Runbook Design

Compliance officers design the operational procedures. Operations personnel execute them. Runbooks bridge the gap — structured, versioned, and regulatory-mapped procedures that flow from compliance to operations.

Runbook Design Studio

Visual editor for creating operational runbooks — step-by-step procedures for AI system monitoring, incident response, scheduled reviews, and maintenance windows. Each step can include regulatory references, escalation triggers, and evidence collection requirements.

Regulatory Mapping

Article 26

Every runbook step maps to the regulatory obligation it fulfils. Article 26 deployer obligations, Article 72 post-market monitoring requirements, and Article 73 incident reporting procedures are embedded in the runbook, not referenced in a separate document.

Version Control & Approval

Audit Trail

Runbooks are version controlled with approval workflows. Changes require sign-off from designated reviewers before becoming the active version. Previous versions are retained for audit purposes. The approval chain is part of the compliance evidence.

Handoff to Operations

Approved runbooks are published to the Practice Operator workspace for execution. Operations personnel follow the procedures designed by compliance — with compliance maintaining ownership of the procedure design. Changes flow from compliance to operations, execution data flows back.