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
44 Modules
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 →
MAT-06
Board AI Reporting Architecture
Provides the structured report framework for presenting AI governance performance, risk posture, and maturity progression to the Board or Governing Partners.
Module
Report preparation: 2–4 days per quarterly cycle; 5–7 days for first report; 5–10 days for annual report.
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 →
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-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-01
Vendor Performance Review Cycle
Evaluate AI vendor performance quarterly across five weighted dimensions with Risk Taxonomy 2026 mapping and Agentic Tier governance checks.
Module
3–4 hours per vendor per quarter once established
View →
SUS-03
AI Market Scan Radar
Systematically monitor the evolving legal AI market quarterly — tracking vendor developments, funding events, and emerging technology innovations — with Risk Taxonomy 2026 vendor risk assessment and Agentic Tier evaluation criteria for Level 4 tool announcements.
Module
Quarterly scan cycle: 4–6 hours for structured analysis; monthly trend monitoring: 1–2 hours
View →
SUS-04
Vendor Exit Methodology
Plan and execute legal AI vendor exits — from lock-in risk assessment through data migration and contract termination — with Risk Taxonomy 2026 exit trigger classification and Agentic Tier shutdown protocol for Level 4 tools.
Module
Annual review: 4–6 hours per vendor; triggered exit execution: 8–20 weeks depending on integration complexity
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-06
Technology Sunsetting Plan
Formalises how legal teams retire AI and legacy tools in a defensible, low-risk way.
Module
Typical engagement: 12–24 weeks end-to-end, depending on system criticality and data volume.
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 →
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