Home → Module Library
The operational capability layer of the Legal AI OS.
Modules are the institutional artefacts a legal function runs to advance maturity, produce Defensibility evidence, and operate on canonical ground in front of a regulator or a board. Anchored across the 8 Pillars and 6 Operating Layers. Methodology-versioned. Editorially independent.
PILLAR
AUDIENCE
+ More filters– Fewer filters1 active
45 Modules
GOV-02
AI Use Policy
Define what AI use is permitted, prohibited, and supervised across the legal department — the operational policy that makes AI governance real.
Module
Initial deployment 2–4 weeks; 1 day for annual review
View →
GOV-03
AI Risk Register
Apply the Risk Taxonomy 2026 to identify, score, and mitigate AI risks across nine canonical classes — the register that makes your governance defensible.
Module
Initial setup 4–6 weeks; 2–4 hours per quarterly review cycle
View →
GOV-04
Bias Testing & Monitoring Methodology
Pre-deployment bias test and continuous fairness monitoring checklist for legal AI systems
Module
Pre-deployment testing: 2–4 weeks per AI system; continuous monitoring: ongoing; quarterly audit: 1–2 days
View →
GOV-09
AI Evaluation Harness Specification
Specifies the standardised evaluation methodology, test suites, and pass thresholds for all AI tools before deployment and during ongoing operation.
Module
Initial evaluation 3–5 business days per tool (Tiers 0–2); 7–10 business days for Tier 3–4 including agentic supplement. Ongoing monitoring is continuous.
View →
GOV-10
AI Lifecycle Operating Manual
Maps the complete AI tool lifecycle from identification through retirement, integrating every governance module into a single coherent operational sequence.
Module
Stage 1–4 (Tiers 0–2): 2–5 business days per tool. Stage 1–4 (Tiers 3–4): 5–10 business days. Stage 5–6: Ongoing. Stage 7 standard: 2–4 weeks. Stage 7 emergency: 24–72 hours active response.
View →
GOV-11
AI Incident Disclosure Standard
Governs the organisation's obligations and procedures for disclosing AI incidents to clients, regulators, and professional bodies.
Module
Disclosure decision: 4–8 hours per incident; regulator notification preparation: 1–3 business days; client disclosure drafting: 1 business day per affected client.
View →
GOV-15
Governance Operating Cadence
Committee calendar mapped to AI Lifecycle stages — Concept intake through Sunset closure — with standing agenda, quorum, and gate evidence requirements.
Module
One-time setup 3 hours; standing committee meetings 60–90 minutes per cadence
View →
INS-01
AI Liability & Insurance Posture
Assess professional liability exposure, insurance coverage gaps, and vendor indemnification adequacy for AI tools across the Risk Taxonomy 2026 nine-class framework.
Module
1–2 days initial per tool; 2–4 hours per tool at renewal or quarterly review
View →
MAT-01
Maturity Grid
The canonical Year-1 maturity instrument — plots organisational Adoption against AI Sophistication on a 5×4 grid to produce a defensible quarterly position and Maturity Stack-linked progression evidence.
Module
1–2 days for baseline; 0.5 day per quarterly review; 1 day annual strategic refresh
View →
MAT-02
Legal AI Readiness Baseline
The canonical 8-pillar readiness diagnostic that captures baseline maturity across all Legal AI OS transformation dimensions and maps current position to the MAT-01 2D maturity grid.
Module
1–2 days for full baseline; 0.5 day for quarterly review; 1 day for annual re-baseline
View →
MAT-03
Maturity Gap Analysis
Structured 6-step gap analysis to map current vs. target Legal AI maturity, risk exposure, and roadmap.
Module
2–4 days for baseline; 1 day for quarterly and annual refreshes
View →
MEA-07
ROAI Telemetry
Tracks and visualises ROAI across four value dimensions — operational, financial, client, and strategic — to justify and optimise AI investment in legal departments.
Module
Initial build 12 weeks; then continuous operation with weekly, monthly, and quarterly review cycles
View →
Advisory
The full operating system in one Programme.
Programme Design and Strategic Retainer engagements operate the canonical Module sequence end-to-end — Defensibility evidence produced, Maturity progression evidenced quarterly, methodology version pinned. The Module Library is the artefact; the engagement is the operating posture.
View Engagement Models