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 filters
26 Modules
STR-02
AI Strategy Canvas
Facilitated canvas to define legal’s AI vision, ambition, ROAI targets, and augmentation roadmap.
Module
4–8 hour facilitated workshop plus 2-week stakeholder sign-off cycle
View →
STR-03
Risk Matrix — Use Case × Risk Taxonomy 2026 × Likelihood
Systematic risk-scoring framework for AI legal use cases aligned to Risk Taxonomy 2026.
Methodology
3–6 hours per use case; 2–3 days for full portfolio review
View →
STR-07
AI Task Force Charter
Stand up the AI governance body that owns strategy, AI BoM oversight, and DPS production for the legal department.
Module
Initial setup 90 days; ongoing 2–4 hours/month per core member plus quarterly reviews.
View →
SUS-05
Annual AI Audit Methodology
The canonical annual governance audit instrument for deployed legal AI — validates compliance, bias, and performance across all active AI systems and produces the DPS annual evidence refresh.
Module
6 weeks per annual cycle (1 week planning, 3 weeks assessment, 1 week analysis, 1 week reporting)
View →
SUS-10
Capability Portfolio Architecture
Every AI capability the function operates, classified by Lifecycle stage — the GC's situational awareness at a glance and the portfolio input for the Defensibility Posture Statement.
Module
2 hours first run; 30 minutes quarterly refresh
View →
TAL-01
AI Literacy Curriculum Architecture
Canonical training framework to build Defensible AI competency across all legal department roles.
Module
Foundational rollout: ~42 hours total across all tracks; ongoing: 4–8 hours per role annually for refresh and new tools.
View →
USE-01
Use Case Prioritization Methodology
The strategic use case selection instrument that evaluates AI opportunities across five dimensions including Risk Taxonomy 2026, gates vendor adoption via AI BoM, and connects the deployed portfolio to DPS Adoption lens evidence.
Module
4–6 hours initial workshop; 2–3 hours per quarterly refresh
View →
USE-02
Pilot Program Design
The canonical AI pilot execution instrument that structures three-phase deployments with Risk Taxonomy 2026 monitoring, AI BoM gating, and Phase 3 DPS evidence production feeding STR-08 ROAI tracking.
Module
90–180 days per pilot (2–4 weeks planning; 6–12 weeks implementation; 2–4 weeks evaluation)
View →
USE-03
Baseline Metrics Methodology
Establishes pre-implementation performance benchmarks across four measurement dimensions to enable objective ROAI demonstration and AI optimisation for legal departments.
Methodology
Approx. 18-week baseline sprint per engagement; re-baseline on major process or organisational change.
View →
VAL-01
ROAI Matrix Framework
Measure and demonstrate the return on AI investment across four value dimensions — operational, financial, cultural, and strategic — with direct linkage to the DPS Defensibility lens.
Module
Initial setup 2–4 weeks; 1–2 days per quarter for updates and reporting
View →
VEN-01
Vendor Evaluation Operating Methodology
Operates the canonical pre-procurement vendor evaluation methodology, gating Legal AI tools through Pass/Fail controls and five-dimension weighted scoring against Risk Taxonomy 2026.
Module
12-week evaluation cycle per vendor engagement, with 2–4 hours per week from core team
View →
VEN-02
Vendor RFP Methodology
Structured RFP template for procuring legal AI solutions with defensible, risk-aware evaluation.
Module
2–4 weeks to draft and issue; 4–8 weeks for full RFP cycle depending on complexity.
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