| Stakeholder |
Role |
Responsibility |
Time Commitment |
| \[Name\] |
Project Sponsor |
Strategic direction, budget approval, escalation resolution |
2 hrs/month |
| \[Name\] |
Project Lead |
Day-to-day management, delivery accountability |
\[X\] hrs/week |
| \[Name\] |
Business SME |
Requirements input, UAT, adoption champion |
\[X\] hrs/week |
| \[Name\] |
IT/Technology |
Integration, security review, infrastructure |
\[X\] hrs/week |
| \[Name\] |
Vendor PM |
Platform configuration, training, support |
Per SOW |
### 6. Timeline and Milestones
| Category |
Weight |
Subcriteria |
| **Functional Fit** |
30% |
Core feature coverage, workflow alignment, configurability, reporting capabilities |
| **Integration** |
20% |
API availability, native connectors (CRM, ERP, DMS), middleware compatibility, data export/import |
| **User Experience** |
15% |
Interface design, mobile access, learning curve, self-service capability |
| **Security & Compliance** |
15% |
Data encryption, hosting options (cloud/on-prem/hybrid), SOC 2/ISO 27001, data residency, privacy compliance |
| **Vendor Viability** |
10% |
Company size and funding, customer base, product roadmap, financial stability |
| **Commercial Terms** |
10% |
Pricing model, contract flexibility, implementation costs, ongoing support costs |
### Scoring Scale
| Stakeholder Group |
Key Message (WIIFM) |
Channel |
Timing |
Owner |
Status |
| GC/CLO |
Clearer visibility into function performance; direct reports more engaged; strategic time freed from admin oversight |
One-on-one briefing + monthly metrics report |
Week 1 (pre-launch) + ongoing |
Project Lead |
Scheduled |
| Senior Counsel |
Less administrative overhead; more time to focus on complex matters and team development |
Team meeting + executive summary document |
Week 1 (pre-launch) |
Project Lead |
Scheduled |
| Working-Level Lawyers |
5–8 hours per week reclaimed from admin; faster turnaround on client requests; clearer career visibility |
Hands-on workshop + peer champions |
Weeks 3–4 |
Training Lead |
Scheduled |
| Business Stakeholders |
Faster contract turnaround; real-time visibility into status; reduced chase time |
Business partner briefing + demonstration |
Week 1 (pre-launch) |
Project Lead |
Scheduled |
| IT/Technology |
Visibility into new systems; integration points clear; support model defined |
Technical briefing |
Week 1 (pre-launch) |
IT Lead |
Scheduled |
---
## Tool 2: Adoption Tracker
Track adoption by stakeholder group across the launch timeline. Use RAG (Red/Amber/Green) status to identify groups falling behind target and trigger intervention.
| Role Group |
Training Format |
Duration |
Content Focus |
Facilitator |
Scheduled Date |
Completion Rate |
| Executive/GC |
Executive briefing |
30 min |
Strategic benefits; oversight and governance; adoption expectations |
Project Lead |
Week 1 |
100% |
| Senior Counsel |
Executive briefing + Q&A |
45 min |
How the tool changes their day; team supervision; quality assurance role |
Senior Champion |
Week 1 |
95% |
| Mid-Level Lawyers |
Hands-on workshop |
2.5 hrs |
Live workflow walk-through using their actual contracts; decision-making in the system; peer Q&A |
Training Lead + Peer Champions |
Weeks 3–4 |
85% |
| Junior Lawyers |
Hands-on workshop |
2 hrs |
Core tasks; integration with research/precedent tools; how to escalate complex issues |
Peer Champions |
Week 4 |
92% |
| Paralegals & Support |
Operational training |
1.5 hrs |
Specific operational tasks; data entry standards; reporting obligations |
Operations Manager |
Week 4 |
98% |
| Business Stakeholders |
Demonstration + Q&A |
60 min |
Visibility features; status tracking; communication workflow |
Project Lead |
Week 1 |
75% |
| Remote/Geographic |
Self-paced online module |
1.5 hrs |
Core content + recorded walkthrough; asynchronous Q&A via Slack |
Training Lead |
Available Week 2 |
70% |
| New hires (post-launch) |
Peer coaching |
2 hrs |
One-on-one or small group with peer champion; embedded in onboarding |
Peer Champions |
Ongoing |
TBD |
**Format Guidance:**
- **Executive briefing (30 min):** High-level overview, business case, leadership role, minimal operational detail. Benefit-focused. For C-suite, senior leaders, or stakeholders without daily tool use.
- **Hands-on workshop (2–3 hrs):** Live demonstration using participant work examples; guided practice with real-world scenarios; peer Q&A. Best for regular tool users. Deliver in role-specific groups.
- **Self-paced module (online):** Recorded walkthrough, knowledge checks, downloadable reference guide. For geographically distributed teams, shift workers, or people who learn better alone.
- **Peer coaching (1–2 hrs):** One-on-one or small group with a champion or experienced user. Used for laggards, new hires, or complex use cases. Most personalised; highest coaching intensity.
---
## Tool 4: 30-Day Post-Launch Review Agenda
Schedule a structured review meeting at day 30 of launch to assess adoption progress, identify friction points, and plan interventions for the next phase.
**Meeting Duration:** 60 minutes
| Scenario |
Methodology |
Goal |
Timeline |
Effort |
| A process works but is slow. Incremental improvements have delivered results. |
Lean |
Reduce cycle time by 25–40% by eliminating waste |
3–6 months |
Moderate: mapping, pilot, measurement |
| A process is fundamentally broken or misaligned with business needs. Need radical redesign. |
BPR |
Redesign from first principles. Target: 50–70% cycle time reduction or 10x efficiency gain. |
4–8 months |
High: requires deep analysis, stakeholder alignment, significant change management |
| A process is reasonably designed but inconsistent. Performance varies wildly. |
Six Sigma |
Reduce variation in cycle time, quality, or cost. Goal: 95%+ of instances meet the target. |
2–4 months |
Moderate: data collection, root cause analysis, standardisation |
| You need quick wins while planning larger redesigns. |
Lean |
Early improvements build credibility and fund larger projects |
1–3 months |
Low to moderate |
| You need to scale a process across multiple teams or geographies. |
Lean + Six Sigma |
Remove waste, then standardise to ensure consistency across all instances |
6–12 months |
Moderate to high |
## In the Trenches
> *This example is fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
**The Intake Process That Was Not a Process**
Tom Andersen, Legal Ops Manager at a New Zealand-based technology company, was asked to “digitise the legal intake process.” He assumed this meant building a web form to replace the email-based request system. Before committing to a solution, he decided to map the current process.
What he found was revealing. There was no single intake process. The sales team sent contract requests to the GC’s assistant via email. The product team submitted compliance questions through a Slack channel. The HR team called individual lawyers directly. The finance team forwarded vendor agreements by attaching them to calendar invitations for “quick review meetings.”
In total, there were seven distinct entry points into the legal department, none of them tracked, measured, or documented. The legal team had no visibility into their own queue — they couldn’t answer the basic question: “How many open requests do we currently have?”
Tom spent four weeks mapping each entry point, interviewing the stakeholders who used them, and understanding why each channel had evolved. In several cases, the workaround existed because a previous attempt to centralise intake had been too rigid or too slow, and users had found their own solutions.
This was an excellent candidate for BPR: the current process was broken (fragmented across seven channels), resisted incremental fixes (previous attempts at centralisation had failed), and required fundamental redesign.
His redesign consolidated all seven channels into a single intake portal built on Jira Service Management — but critically, he kept Slack as a supported submission channel (via a Jira integration) because the product team’s adoption of any non-Slack tool was near zero. He built a triage decision tree that categorised requests by type and urgency, auto-assigned them to the appropriate lawyer, and set SLA expectations with the requester.
Within three months, the legal team could see their complete queue for the first time. Average request response time dropped from “somewhere between 2 hours and 2 weeks” (Tom’s characterisation of the previous state) to a measurable 36-hour median.
Once the new intake process was stable, Tom applied Six Sigma principles to reduce variation. He created a complexity rubric so every request was consistently classified. He documented SLAs tied to complexity: routine requests were targeted at 24 hours, standard at 48 hours, complex at 5 business days. He implemented weekly control charts tracking performance against these targets. Variation in response time dropped from ±100% (unpredictable) to ±10% (predictable).
## Checklist
- **Pick your most painful process and shadow it.** Literally follow one real request from submission to completion, documenting every step and every wait state. Do not rely on anyone’s description of how the process works — observe it in action. This single exercise surfaces issues that months of meetings would miss.
- **Count your intake channels.** How many different ways does the business currently submit requests to the legal department? Email, Slack, phone calls, hallway conversations, calendar invitations — count them all. If the number exceeds two, you have a visibility problem that is likely sabotaging your cycle time.
- **Run a waste audit on your longest process.** Pick the process that consumes the most legal team hours (typically contract review, legal intake, or matter opening). Using the eight types of waste above, identify where each type occurs. Colour-code by impact: red for 20+ hours/month, yellow for 5–20 hours/month. Your biggest opportunity lies in the red items.
- **Measure your current state baseline.** Before you improve anything, establish the baseline: What is the current cycle time? What is the defect rate (percentage of work requiring rework)? What is the queue length? These three numbers are your control group. After redesign, these numbers tell you whether you actually improved.
- **Choose your methodology.** Is the process broken (BPR), slow but functional (Lean), or inconsistent (Six Sigma)? Your answer determines your approach. Applying BPR to a Lean problem is overkill; applying Lean to a fundamentally broken process will disappoint.
## Suggested Reading
- [ASQ - What is Six Sigma?](https://asq.org/quality-resources/six-sigma)
- [Lean Enterprise Institute - Lean Lexicon](https://www.lean.org/lexicon-terms/)
- [APQC - Process and Performance Management Resources](https://www.apqc.org/resource-library/resource-listing?f%5B0%5D=topic%3A73)
- [PMI Standards and Guides](https://www.pmi.org/pmbok-guide-standards)
- [NIST - Process Improvement and Quality Resources](https://www.nist.gov/topics/manufacturing/lean-six-sigma)
Source: https://tilt.legal/docs/legal-ops-kit/esg-the-supply-chain
Markdown: https://tilt.legal/docs/legal-ops-kit/esg-the-supply-chain.md
Operationalising ESG obligations through legal infrastructure — embedding environmental, social, and governance requirements into contracts, vendor management, and reporting workflows.
## ESG Is an Operations Problem
Environmental, Social, and Governance (ESG) reporting has migrated from the corporate responsibility team’s annual report to the legal department’s operational mandate. The reason is straightforward: ESG obligations are increasingly codified in legislation, embedded in regulatory frameworks, and enforced through supply chain due diligence requirements. In Australia, the Modern Slavery Act, mandatory climate-related financial disclosures, and evolving supply chain transparency requirements establish ESG compliance as a legal obligation.
The legal function is uniquely positioned to operationalise ESG because the critical enforcement mechanisms — contracts and compliance processes — are already managed by Legal Ops. The challenge is building ESG tracking and reporting into existing legal infrastructure rather than spinning up a parallel compliance universe.
## The Three ESG Domains for Legal Ops
### Environmental: Carbon and Climate
The legal function’s role in environmental ESG centres on three activities:
**Supply chain emissions tracking via contracts.** Scope 3 emissions — those generated by the organisation’s supply chain — require vendor-level data. The mechanism for collecting this data is the vendor contract. Mature organisations in 2026 embed emissions reporting obligations directly in their supply agreements: mandatory annual disclosure of carbon emissions attributable to the engagement, standardised reporting formats, and audit rights to verify reported data.
**Climate-related disclosure compliance.** Australia’s mandatory climate-related financial disclosures (aligned with ISSB standards) require organisations to report on climate risks, governance, strategy, and metrics. The legal function owns the disclosure review process, ensuring that published climate statements are legally defensible and consistent with the organisation’s actual practices.
**Green procurement standards.** Environmental criteria embedded in the procurement and vendor management process (Chapter 7). The RFP evaluation matrix includes environmental sustainability as a scored criterion, and vendor QBRs track environmental performance alongside cost, quality, and responsiveness.
### Social: Modern Slavery and Diversity
**Modern slavery due diligence.** The Australian Modern Slavery Act requires organisations with consolidated revenue above \$100M to produce annual modern slavery statements. The operational requirement: a due diligence process that assesses modern slavery risk across the supply chain, particularly for high-risk categories (manufacturing, agriculture, construction, cleaning, security).
The CLM plays a direct role. Supplier contracts should include modern slavery representations and warranties, supply chain transparency obligations, audit rights, and remediation commitments. The CLM’s obligation tracking capability ensures that these commitments are actively monitored throughout the engagement lifecycle.
**Diversity and inclusion metrics in vendor management.** Tracking and reporting on the diversity profile of external legal providers. Many organisations now include diversity staffing requirements in their Outside Counsel Guidelines: minimum percentages of diverse lawyers staffed on their matters, reporting on diversity metrics at QBRs, and diversity as a weighted criterion in panel selection.
### Governance: Board-Level ESG Oversight
**ESG risk in the corporate governance framework.** The legal function ensures that ESG risks are integrated into the board’s risk oversight responsibilities. This means ESG items appear on the board risk register, ESG performance is reported to the board at defined intervals, and the board’s governance charter reflects ESG oversight obligations.
**Regulatory change management.** The ESG regulatory landscape is evolving rapidly. The legal function’s horizon-scanning capability (Chapter 15) must include ESG-specific regulatory monitoring — tracking new and proposed legislation across the jurisdictions where the organisation operates.
Organisations that embed ESG into existing legal operations infrastructure achieve better efficiency and cost outcomes. The CLM already manages contracts. The vendor programme already runs QBRs. Compliance already monitors regulatory obligations. Adding ESG dimensions to these existing programmes is incremental work — and avoids the expense and inefficiency of parallel compliance systems.
## Operationalising ESG Through the CLM
### The ESG Clause Library
Build an ESG-specific clause library within the CLM’s playbook infrastructure:
| ESG Domain |
Clause Type |
Application |
| **Environmental** |
Emissions reporting obligation |
Vendor agreements above defined threshold |
| **Environmental** |
Carbon offset / reduction commitment |
Strategic supplier agreements |
| **Social** |
Modern slavery representation and warranty |
All supplier agreements |
| **Social** |
Supply chain transparency obligation |
Suppliers in high-risk categories |
| **Social** |
Diversity staffing requirements |
Outside counsel engagement letters |
| **Governance** |
Anti-corruption and bribery commitment |
All third-party agreements |
| **Governance** |
Data protection and privacy obligations |
All agreements involving personal data |
| **Governance** |
ESG audit rights |
Strategic and high-risk supplier agreements |
### Obligation Tracking for ESG
The CLM’s obligation management capability tracks ESG commitments alongside commercial obligations:
- Annual modern slavery statement due dates
- Quarterly emissions reporting deadlines from vendors
- Diversity metric reporting requirements at QBRs
- ESG audit scheduling and follow-up action tracking
- Regulatory filing deadlines for climate-related disclosures
### ESG Analytics
With structured ESG data flowing through the CLM, the legal function can produce ESG-specific analytics:
**Supply chain risk heat map.** Visualise modern slavery and environmental risk across the vendor portfolio, segmented by category, geography, and contract value.
**Compliance coverage.** Track the percentage of eligible contracts that include required ESG clauses. A gap indicates either a template deficiency or an override that should be investigated.
**Vendor ESG performance.** Aggregate vendor-reported ESG data (emissions, diversity metrics, modern slavery compliance) into a portfolio-level scorecard.
## In the Trenches
> *This example is fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
**The Modern Slavery Audit That Changed Procurement**
An Australian resources company was preparing its annual modern slavery statement when the legal team discovered a significant gap: of the company’s 340 active supplier contracts, only 23% contained modern slavery representations or supply chain transparency obligations. The remainder — including several high-risk suppliers in categories such as labour hire, facilities management, and offshore manufacturing — had been contracted before the Modern Slavery Act took effect, and no one had retrofitted the existing agreements.
The Head of Legal Ops initiated a three-month remediation programme. First, she categorised all 340 suppliers by modern slavery risk using AUSTRAC and NGO risk indicators — geography, industry sector, and engagement type. This produced a heat map with 47 suppliers in the “high risk” category.
Second, she worked with the CLM team to build a modern slavery addendum template with the appropriate representations, warranties, audit rights, and remediation commitments. The addendum was designed to be executed as a standalone supplement to the existing agreement — avoiding the complexity and delay of renegotiating the underlying contract.
Third, she prioritised outreach: the 47 high-risk suppliers were contacted first, with a clear message: the addendum was a contractual requirement, not a request, and non-compliance would affect future engagement decisions. Within six weeks, 41 of the 47 had executed the addendum. The remaining six were escalated to procurement for relationship review — and two were ultimately exited from the supplier panel.
The company’s next modern slavery statement included a compliance coverage metric for the first time: 94% of active supplier contracts contained modern slavery obligations, up from 23% the prior year. The board cited this improvement as evidence of the legal team’s operational maturity — and the CFO approved the remaining Legal Ops budget requests without further negotiation.
## Checklist
- **Audit your ESG clause coverage.** Pull a sample of 20 supplier contracts executed in the last 12 months. Check each for modern slavery provisions, data protection clauses, and environmental reporting obligations. Calculate your compliance coverage percentage. Target 80% or higher; template updates deliver systematic compliance gains across your supplier base.
- **Map your modern slavery risk.** List your top 20 vendors by spend. For each, note the industry category, primary geography of operations, and workforce model (direct employees, contractors, subcontractors). Use publicly available risk indicators to classify each as low, medium, or high risk. The high-risk vendors are your immediate due diligence priorities.
- **Add ESG to your next QBR.** For the next Quarterly Business Review with your highest-spend law firm or vendor, add a 10-minute ESG agenda item. Request diversity staffing data for your matters and environmental sustainability information. The act of asking signals that ESG performance is now a managed dimension of the relationship.
- **Review your modern slavery statement timeline.** Confirm the reporting deadline, the data collection requirements, and the internal approval process. Establish clear timelines and approval pathways — this enables reliable and timely compliance with reporting obligations.
## Suggested Reading
- [IFRS S1 - General Requirements for Sustainability-related Disclosures](https://www.ifrs.org/issued-standards/ifrs-sustainability-standards-navigator/ifrs-s1-general-requirements-for-disclosure-of-sustainability-related-financial-information/)
- [IFRS S2 - Climate-related Disclosures](https://www.ifrs.org/issued-standards/ifrs-sustainability-standards-navigator/ifrs-s2-climate-related-disclosures/)
- [Australian Modern Slavery Register](https://modernslaveryregister.gov.au/)
- [Australian Modern Slavery Act 2018 (Cth)](https://www.legislation.gov.au/C2018A00153/latest/text)
- [OECD Due Diligence Guidance for Responsible Business Conduct](https://www.oecd.org/investment/due-diligence-guidance-for-responsible-business-conduct.htm)
Source: https://tilt.legal/docs/legal-ops-kit/from-legal-department-to-legal-operations
Markdown: https://tilt.legal/docs/legal-ops-kit/from-legal-department-to-legal-operations.md
How the legal function evolved from a bundled service model into a diversified, technology-enabled operation — and what that means for how you build and run your team.
## The Unbundling of Legal Services
The legal profession spent decades on a bundled service model: one law firm, one relationship partner, one hourly rate for everything from bet-the-company litigation to routine corporate housekeeping. Organisations that have moved to a diversified delivery model typically report significant cost reductions on routine work, alongside faster turnaround and often higher quality through specialist channels. (The [Thomson Reuters/Georgetown/Oxford](https://www.legalcurrent.com/alternative-legal-services-providers-2023-report-reactions-from-the-legal-industry/) [*Alternative Legal Service Providers*](https://www.legalcurrent.com/alternative-legal-services-providers-2023-report-reactions-from-the-legal-industry/) [report](https://www.legalcurrent.com/alternative-legal-services-providers-2023-report-reactions-from-the-legal-industry/) and the [ACC Chief Legal Officers Survey](https://www.acc.com/resource-library/acc-chief-legal-officers-survey) both document the scale of these savings, with figures commonly in the 30–50% range for high-volume, repeatable work.)
**Unbundling** means decomposing the legal service delivery chain and routing each component to the provider best suited to deliver it. A \$200M acquisition still warrants a top-tier M&A firm. Reviewing 10,000 legacy contracts for GDPR compliance is ideally suited to an ALSP, augmented by AI-driven extraction and classification.
The unbundling spectrum looks like this:
| Work Type |
Optimal Provider |
Cost Profile |
| Strategic advisory, bet-the-company litigation |
Panel law firm (senior partner) |
\$800-\$1,500/hr |
| Specialist regulatory, complex transactions |
Boutique / mid-tier firm |
\$400-\$800/hr |
| High-volume contract review, due diligence |
ALSP + technology |
\$150-\$300/hr (blended) |
| Template generation, first-draft creation |
Agentic AI + legal engineer |
Near-zero marginal cost |
| Self-serve queries, policy lookups |
Knowledge portal / chatbot |
Zero marginal cost |
GCs who get unbundling right reserve senior external counsel for work that genuinely requires their judgment. Routine and high-volume matters get routed to the channel best placed to handle them on cost, speed, and quality. The law firm relationship becomes more focused — and often more productive — as a result.
### From Tribal Knowledge to Institutional Assets
Every legal department has the same problem: critical institutional knowledge locked inside the heads of two or three senior lawyers. The clause language the CEO insisted on in the 2019 distributor agreement. The informal handshake deal with the regulator about reporting timelines. The “we never do that” positions with no written policy basis.
This is **organisational memory**, and converting it into structured, accessible institutional assets is one of the highest-value investments a legal function can make. When critical knowledge lives in systems rather than individual memory, continuity improves, onboarding accelerates, and the organisation builds compounding institutional intelligence.
Legal Ops 3.0 treats knowledge capture as a **core operational discipline**, applied systematically:
- **Playbook codification:** Every negotiation position, fallback, and non-negotiable is documented in a structured playbook that any team member (or AI agent) can reference
- **Decision logging:** Key legal decisions are recorded with their rationale, not just their outcome, creating an institutional precedent register
- **Process documentation:** Workflows are mapped and stored centrally, preserving continuity through personnel changes
- **Data tagging and normalisation:** Contract metadata, clause libraries, and matter data are structured in machine-readable formats
Capturing operational knowledge in structured systems builds institutional resilience and protects the organisation from unplanned personnel transitions.
## The Three Horizons of Legal Ops Maturity
Legal Ops 3.0 didn’t emerge overnight. Understanding the evolutionary path helps leaders assess where their function sits today and what the next investment horizon looks like.
**Legal Ops 1.0 (2010–2018): The Administrative Era.** Legal Ops was project management and financial administration: e-billing, matter management, basic reporting. The legal department was still a collection of individual practitioners supported by administrative staff.
**Legal Ops 2.0 (2018–2024): The Process Era.** The function matured into process engineering, technology selection, and vendor management. CLM platforms gained adoption, data analytics moved from aspirational to partially implemented, and the CLOC and ACC frameworks gave structural guidance. But most organisations still treated Legal Ops as support, not strategy.
**Legal Ops 3.0 (2024–Present): The Intelligence Era.** Defined by three characteristics: **(1)** AI-augmented workflows that go beyond automation to intelligent decision support; **(2)** data liquidity across the legal tech stack, enabling predictive analytics; and **(3)** the legal function operating as a platform the business consumes through self-service interfaces rather than email. The Legal Ops professional here is part strategist, part technologist, part change manager — the “Legal Engineer” archetype explored in Chapter 16.
## In the Trenches
> *This example is fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
**The Template That Saved a Department**
David Park, newly appointed Head of Legal Ops at a 400-person logistics company, faced a stark reality in his first week: a three-lawyer team processing roughly 1,800 contracts per year, every single one handled as a bespoke document. NDAs, service agreements, subcontractor terms — each drafted from scratch or, more accurately, from whichever prior agreement the handling lawyer found first in their email.
David didn’t have budget for a CLM platform. What he had was Microsoft Word, a SharePoint licence the company was already paying for, and the goodwill of one paralegal willing to work on a side project.
Over eight weeks, they audited every contract executed in the prior 12 months, identified the 12 most common agreement types, and built a standardised template for each with clearly marked “negotiable” and “non-negotiable” fields. They created a simple SharePoint site with a decision tree: answer four questions about your deal, and the system directs you to the correct template with pre-populated standard terms.
The result was transformative. Within three months, average handling time per standard contract dropped from 4.5 hours to 45 minutes. Freed from repetitive drafting, the lawyers took on two strategic projects they’d deferred for over a year — including a vendor rationalisation exercise that saved the company \$340K in annual outside counsel spend.
David’s total investment: approximately 120 hours of paralegal time and zero technology spend beyond existing licences. His ROI, measured in recovered lawyer hours alone, exceeded 2,000% in the first year.
## Checklist
- **Audit your organisational memory risk.** Identify three pieces of institutional knowledge in your team that live only in someone’s head. Schedule time this week to document them somewhere shared and searchable — even a simple wiki page is a start.
- **Draft a first-pass Asset Register.** List your team’s top 10 recurring activities. For each, note whether it’s delivered by human effort, technology, or a hybrid. Flag the three with highest volume and lowest complexity — your first digital asset candidates.
- **Quantify your template gap.** Count how many of your top 5 contract types have a current, approved, version-controlled template. If fewer than 5, template creation is your highest-ROI near-term investment.
- **Calculate your “digital asset ratio.”** Estimate what percentage of your function’s total output is generated or supported by reusable digital assets (templates, workflows, automated processes) versus produced from scratch. Set a 12-month target to lift this ratio by 15–20 percentage points.
## Suggested Reading
- [Alternative Legal Service Providers 2023 Report (Thomson Reuters / Georgetown / Oxford)](https://www.legalcurrent.com/alternative-legal-services-providers-2023-report-reactions-from-the-legal-industry/)
- [ACC Chief Legal Officers Survey](https://www.acc.com/resource-library/acc-chief-legal-officers-survey)
- [CLOC Core 12 Competency Framework](https://cloc.org/cloc-core-12/)
- [WorldCC Research and Benchmarking](https://www.worldcc.com/Resources/benchmarks-research)
- [ACC Legal Operations Resources](https://www.acc.com/topics/legal-operations)
Source: https://tilt.legal/docs/legal-ops-kit/how-to-contribute
Markdown: https://tilt.legal/docs/legal-ops-kit/how-to-contribute.md
The Legal Ops Kit is a living document, and the most valuable improvements come from practitioners using it. Corrections, missing examples, *"this didn't work for us"* notes, regional or jurisdiction-specific nuance — all of it makes the kit more useful for the next person landing on a chapter under pressure.
## Suggesting an edit
Every page has an **Edit in Notion** button at the top. Clicking it opens the page in Notion as a publicly readable view, where you can leave inline comments on any paragraph, table, or callout.
The flow:
1. Read the chapter on the site.
2. Click **Edit in Notion** at the top of the page.
3. The page opens in Notion. Scroll to the section you want to comment on.
4. Highlight the text, click the comment icon, and write your suggestion or correction.
5. Submit. Comments reach the editorial team, and approved changes get merged back into the source.
## You'll need a Notion account
Notion requires you to be signed in to comment. If you don't have an account, you can create one free at [notion.so](http://notion.so) — it takes about 30 seconds and works for any Notion-published kit. We don't get access to your workspace; only your name and the comments you leave on these pages.
Prefer not to create a Notion account? Email suggestions directly to [info@tilt.legal](mailto:info@tilt.legal).
## What makes a good contribution
- **Corrections.** Factual errors, broken links, outdated regulation references, stale benchmarks — flag them.
- **Missing examples.** *"We tried this and it broke because…"* examples are gold. Real-world failure modes belong in *In the Trenches* sections — the kit gets stronger every time one's added.
- **Jurisdiction-specific nuance.** The kit leans Australian and UK in places. If a framework lands differently in your region — different regulators, different market norms, different vendor landscape — tell us how.
- **Tool or vendor updates.** The legal tech market shifts fast. Vendor renames, new entrants, deprecated products, and pricing-model changes are all worth flagging.
- **Better checklists.** If a chapter's checklist would be more useful with two extra items or one fewer, say so and explain why.
## What we tend not to merge
- Vendor promotion or marketing copy.
- Personal opinions presented as best practice without supporting reasoning or evidence.
- Edits that materially change a chapter's framing or thesis. Those are conversations, not comments — reach out directly.
## Proposing something bigger
For a substantial change — a new chapter, major restructure, guest *In the Trenches* piece, or new appendix or template — leave a high-level comment on the most relevant page or email [info@tilt.legal](mailto:info@tilt.legal). We're particularly interested in contributions that close gaps: specific industries, smaller in-house teams, the Asia-Pacific market beyond Australia, the buy-side perspective on legal vendors.
Thanks for helping make this kit better.
Source: https://tilt.legal/docs/legal-ops-kit/information-governance-records-management
Markdown: https://tilt.legal/docs/legal-ops-kit/information-governance-records-management.md
Classifying, retaining, and retrieving legal information — the data foundations that enable AI, analytics, and compliance to work reliably.
## What Information Governance Actually Covers
Information Governance (IG) is the framework that defines how an organisation creates, classifies, retains, accesses, and disposes of its information assets. In legal operations, IG is the discipline that connects data quality, regulatory compliance, risk management, and technology enablement into a unified system.
A mature IG function encompasses:
**Classification and access control.** Every piece of legal information — contracts, advice, matter files, communications — has a classification level (public, internal, confidential, privileged) that determines who can access it, how it can be used, and how long it must be kept.
**Records management.** The systematic management of documents and data throughout their lifecycle: creation, active use, retention according to legal and business requirements, and eventual disposition. Legal departments face unique records management obligations — documents may need to be retained for litigation holds, regulatory investigations, or historical precedent long after a matter closes.
**Data quality and normalisation.** The technical foundation that makes every other capability work. Clean, structured, consistently formatted data is the prerequisite for compliance reporting, analytics, and AI-powered systems. Without data quality discipline, legal operations cannot reliably answer questions like “do we have a liability cap with this vendor?” or “what is our total contractual exposure?”.
**Metadata management.** The capture and maintenance of structured information about legal documents — who created it, when, for what purpose, with what classification, binding which parties. Metadata turns a document repository into an analytical asset.
**Integration and interoperability.** The middleware that connects source systems (CLM, matter management, e-billing) into a unified data environment where information flows automatically, consistently, and with appropriate controls.
**Audit and compliance.** The ability to demonstrate, at any point, that information is stored in the right place, classified correctly, accessible only to authorised users, and retained in accordance with legal and regulatory requirements.
Information Governance isn’t compliance theatre or a burden imposed by risk-averse IT functions. It’s the foundational discipline that makes AI deployment reliable, enables confident decision-making through analytics, unlocks the value locked in legacy contracts and matters, and protects the organisation from data breach, regulatory sanction, and litigation risk.
## The Legal Data Landscape
Legal data is disproportionately unstructured, inconsistently formatted, and distributed across systems for reasons that are structural rather than the result of any particular team’s shortcomings:
**Document-centric work product.** The primary output of legal work is documents — contracts, memos, opinions, filings — rich repositories of data embedded in natural language. Contract key terms (value, duration, governing law, liability cap) can be extracted from these documents and structured into queryable database fields through deliberate metadata capture and AI-assisted tools that legal teams are increasingly adopting.
**System fragmentation.** A typical legal department uses 5–8 distinct technology tools (matter management, document management, e-billing, CLM, e-signature, communication, calendar). Each system stores data in its own format, with its own field definitions, and its own identifiers. “Acme Corporation” in the CLM appears as “ACME Corp.” in the e-billing system and “Acme Corp Pty Ltd” in the matter management system. Without middleware and entity resolution, these separate records remain disconnected.
**Historical accumulation.** Legal departments carry decades of legacy data — paper files, scanned PDFs, obsolete matter management exports, departed lawyers’ email archives. This data has institutional value (precedents, historical positions, legacy obligations) and can be unlocked through structured indexing and AI-assisted metadata extraction.
**Data skills gap.** Lawyers are trained to work with text and legal reasoning, not data management. Investing in data literacy across the legal function — through training, tools, and dedicated data roles — unlocks the analytical potential of legal data and aligns legal ops with modern corporate functions.
**Regulatory and evidentiary requirements.** Legal information must often be retained for extended periods to satisfy litigation hold obligations, regulatory requirements, or corporate governance needs. The obligation to produce documents on demand means every piece of legal information may become material evidence. This creates a duty to maintain information in a state where its authenticity, integrity, and chain of custody can be demonstrated.
## Records Management Fundamentals
Records management is the practical discipline of applying retention schedules, managing legal holds, and ensuring documents are disposed of appropriately when their retention period expires.
### Document Retention Schedules
A retention schedule specifies how long each category of document must be kept, and the business or legal rationale for that period. Unlike general business records, legal documents often require extended retention periods.
**Typical retention tiers in legal:**
- **Permanent retention.** Corporate governance records (board minutes, constitutional documents), precedent-setting advice, significant client relationship documentation, and important transactional records (executed contracts of ongoing commercial significance).
- **7+ years.** Contracts with active or recently closed matters, billing and financial records (tax and audit requirements), employment and contractor agreements, litigation files. The “7 years” horizon is driven by statute of limitations for contract claims and tax law.
- **3–5 years.** General matter files, routine correspondence, work-in-progress matter documentation. Retention extends beyond matter close-date to account for potential follow-on disputes or related matters.
- **1–2 years.** Email and temporary communications, draft documents, administrative records, routine scheduling and logistical information.
- **Disposal on closure.** Ephemeral communications, meeting notes without binding content, temporary working documents.
A retention schedule must be:
- **Documented and communicated.** The schedule exists as a reference document, not an implicit assumption. All staff understand why documents are kept and when they can be deleted.
- **Applied consistently.** Automated workflows or checklists ensure documents are classified to the correct retention tier at the point of creation. Metadata in the document management system captures retention classification and triggers disposition processes automatically.
- **Defensible in litigation.** The schedule must reflect genuine business and legal requirements, not arbitrary decisions to minimise storage costs. If a document has been destroyed, discovery requests will ask why it was destroyed and when. A documented, reasonable retention schedule is your defence.
### Legal Hold Management
A legal hold is an instruction to preserve documents and information relevant to anticipated or ongoing litigation, investigation, or regulatory matter. A legal hold overrides normal retention schedules — documents subject to hold must be kept until the hold is released.
**The hold process:**
1. **Identify custodians.** Determine which employees, contractors, and former staff likely hold information relevant to the hold matter. Include people who may have been involved in the underlying events, even if they are no longer in active roles.
2. **Issue hold notices.** Communicate the hold obligation to custodians in writing. The notice must clearly explain what information is subject to hold, the business reason, the consequences of destruction, and instructions for identifying and preserving information (whether it remains in-place or is transferred to a centralised location).
3. **Preserve information.** Custodians suspend their normal deletion practices. Email is not automatically deleted. Documents are not pruned from file servers. If information is stored across multiple systems (local drives, cloud storage, phone backups), all locations are included in the preservation obligation.
4. **Track and verify.** The legal team or records manager tracks which custodians have acknowledged the hold, verifies that information is being preserved, and addresses any gaps (custodians who didn’t receive notice, information in systems not initially identified).
5. **Release and dispose.** When the litigation or investigation concludes, hold notices are released. Custodians resume normal deletion practices. Documents subject to hold but not to ongoing retention schedules are disposed of appropriately.
A well-managed hold process is essential because failure to preserve documents requested in discovery can result in sanctions, adverse inference instructions (the court instructs the jury to presume the destroyed documents would have been unfavourable to the destroying party), or case dismissal. For regulatory investigations, document destruction can itself become a separate violation.
### Disposition Processes
Disposition is the controlled, documented destruction or archival of information when its retention period expires. It’s not “hit delete” — it’s a formal process.
**Sound disposition practice:**
- **Retention status is confirmed.** Before destruction, verify that the document’s retention period has actually expired and no legal hold is active.
- **Destruction is documented.** A disposition schedule or certificate records what was destroyed, when, and why. This creates an audit trail that demonstrates the organisation acted in good faith if destruction is later questioned.
- **Appropriate destruction method.** Documents are destroyed in a manner appropriate to their sensitivity (physical shredding for paper, certified data destruction for digital, certified deletion of secure data for sensitive electronic records).
- **Verification and sign-off.** Destruction is verified by independent personnel and documented with sign-off.
- **Archived materials are retained separately.** Materials of permanent or long-term value (corporate records, significant precedents) may be transferred to an archives function rather than destroyed, with appropriate access controls and metadata maintained.
Organisations that lack a disciplined disposition process tend to accumulate vast volumes of historical data. Beyond the practical problems (storage cost, system performance, backup complexity), this creates discovery risk — “we have everything, we’re not sure what is responsive” is not a safe litigation posture.
## Data Classification
Data classification defines who can access each piece of information and how it can be used. A classification scheme might be:
**Public.** Information intended for external communication. Published guidance, annual reports, press releases. No restriction on access or use.
**Internal.** Information used internally but not confidential. Policies, procedures, unclassified work product. Accessible to employees and contractors; not shared externally without approval.
**Confidential.** Information that would cause business harm if disclosed. Client information, commercial terms, business strategy, financial performance. Restricted to employees with a business need to know. Not shared externally without contractual confidentiality protections.
**Privileged / Legal Hold.** Information protected by legal privilege (solicitor–client privilege, litigation privilege, work product doctrine). Treated with the highest security. Disclosure may waive the privilege, so access is tightly controlled and disclosure practices are carefully managed. Often flagged with a legend (“Privileged and Confidential”) to signal the protection.
### Implementing Classification
Classification is most effective when it is:
**Automatic where possible.** Documents created in certain systems (CLM, matter management) can be auto-classified based on the context where they are created (documents in a litigation matter are confidential and may be privileged; documents in the templates library are internal). Templates can default to appropriate classifications.
**Enforced through workflow.** When documents are uploaded to a repository, classification is a required field. Users cannot proceed without selecting a classification level.
**Visible at point of use.** Classification is displayed prominently on documents so users understand the restrictions. Email headers, document headers, or metadata views show classification status.
**Enforced through access control.** The classification system is integrated with identity and access management. Privileged documents can only be accessed by explicitly authorised staff. Confidential documents are visible only to staff with a relevant business relationship.
**Auditable.** Access to classified documents is logged. If a sensitive document is accessed, the log record shows who accessed it, when, and what they did (viewed, downloaded, printed). Unusual access patterns (a user accessing hundreds of confidential documents outside their normal role) can be flagged for investigation.
### Practical Implementation Steps
1. **Develop a classification policy.** Define the tiers, the criteria for each tier, examples of documents that fall into each category, and the handling rules for each tier.
2. **Apply to existing data.** The challenge is often the legacy corpus. Apply classification to high-value documents first (executed contracts, key advice) and progressively extend to the broader repository. AI-assisted classification can speed this process, though human review is usually required for sensitive materials.
3. **Build classification into workflow.** New documents are classified at creation. Templates default to appropriate classifications. Matter creation or contract uploads trigger classification workflows.
4. **Connect to access control.** The classification system is integrated with the document management system, email, and identity management so that access rules are automatically enforced.
5. **Communicate and train.** Staff understand what each classification tier means, how it affects their work, and how to handle documents they encounter. Training is especially important around privilege — inadvertent disclosure can waive the privilege.
## Data Normalisation: The AI Prerequisite
Data normalisation is the technical foundation that transforms raw, inconsistent data into structured, consistent, analytically usable information. It is the essential prerequisite for AI deployment in legal.
### The Five-Step Normalisation Programme
**Step 1: Entity Resolution.** Establish a single, authoritative naming convention for every entity (client, counterparty, vendor, firm) that appears in your data. Map all variations to the canonical name. This is the prerequisite for any cross-system analysis — you cannot track total spend with a vendor if the vendor has three different names across three systems.
**Step 2: Taxonomy Standardisation.** Define standardised taxonomies for matter types, contract types, practice areas, and work categories. Adopt industry standards where they exist ([UTBMS codes](https://utbms.com/) for billing, [SALI standards](https://www.sali.org/) for matter types, [LEDES standards](https://www.ledes.org/) for e-discovery) and supplement with organisation-specific categories where needed. Apply the taxonomy consistently across all systems.
**Step 3: Metadata Enrichment.** For key data assets — particularly contracts — extract and structure the metadata embedded in document text into queryable, analytically useful fields. Party names, effective dates, expiry dates, contract values, governing law, key obligations, and material terms should exist as structured fields in the CLM or repository. AI-assisted extraction tools accelerate this work for legacy documents; new documents should have metadata captured at the point of creation through structured templates.
**Step 4: Deduplication and Reconciliation.** Identify and resolve duplicate records across systems, creating a single authoritative record for each entity. When the same matter exists in multiple systems with different data, consolidate and reconcile to establish one source of truth. This foundational work enables all downstream analytics and decision support.
**Step 5: Ongoing Governance.** Data normalisation is a continuous capability, not a one-time project. Establish data governance processes that maintain quality on an ongoing basis: defined data owners for each system, automated validation rules that catch quality issues at the point of entry, and periodic audits that verify data integrity.
### Why Normalisation Matters for AI
Data normalisation is the essential foundation for successful AI deployment in legal. Organisations that invest before implementing AI unlock its full potential — outputs reflect the quality of inputs, which means consistent, reliable, actionable results.
A machine learning model trained on inconsistent data (where entity names vary, taxonomies are non-standard, and metadata is missing) will learn to recognise the inconsistencies rather than the underlying patterns. When the model encounters new data, it struggles because the patterns it learned are artefacts of poor data quality, not genuine legal patterns. Conversely, an AI system querying clean, normalised data can focus on the substantive legal patterns and produce reliable, defensible insights.
### The Normalisation Investment
Data normalisation requires investment in time and effort, with returns that compound across all downstream applications. Frame it as an enabling capability that multiplies the value of every subsequent technology investment:
| Normalisation Step |
Typical Effort |
Prerequisite For |
| Entity resolution |
2–4 weeks (one-time), ongoing governance |
Cross-system reporting, vendor analytics, conflict checks |
| Taxonomy standardisation |
4–6 weeks (one-time) |
Matter analytics, benchmarking, trend analysis |
| Metadata enrichment |
2–6 months (for legacy corpus) |
CLM analytics, obligation management, AI-powered review |
| Deduplication |
2–4 weeks per system pair |
Reliable dashboards, accurate financial reporting |
| Ongoing governance |
2–4 hours/week (permanent) |
Sustaining all of the above |
## The Three-Layer Data Architecture
### From Silos to Flow
Data normalisation makes individual systems reliable. The middleware layer makes them **interoperable**. Middleware — the integration technology that connects systems — enables data to flow between systems automatically, eliminating manual re-entry, reducing errors, and creating a unified data environment.
### The Legal Data Flow Architecture
A mature legal data architecture has three layers:
**Source systems.** The individual tools where data originates: CLM (contract data), matter management (matter data), e-billing (spend data), document management (work product), and enterprise systems (CRM, ERP, HR).
**Integration layer.** The middleware that moves data between source systems, applying transformation rules (normalisation, format conversion, entity mapping) in transit. This layer ensures that when a contract is executed in the CLM, the relevant data flows automatically to the CRM (deal closed), the ERP (payment terms activated), and the matter management system (matter status updated).
**Analytics layer.** The data warehouse or business intelligence platform where data from all source systems is consolidated for reporting and analysis. This is where financial performance is analysed, where spend trends are tracked, where cycle time metrics are computed, where legal value is measured, and where AI models are trained on high-quality, integrated legal information.
### The Single Source of Truth
The “single source of truth” is a data architecture where every data element has one authoritative source, and all other systems that consume that data receive it from that source. Contract terms are authoritative in the CLM. Spend data is authoritative in the e-billing system. Matter status is authoritative in the matter management system. The analytics layer reads from all authoritative sources, and the middleware ensures that authoritative data propagates to dependent systems.
When someone asks “what is our total contract exposure with Vendor X?”, the answer comes from one authoritative source, eliminating the confusion that arises from multiple spreadsheets maintained by different people showing conflicting numbers.
## Building the Single Source of Truth
A single source of truth is achieved through:
**Clear authoritative source designation.** For each data category, explicitly designate which system is authoritative. Document it. Communicate it to all staff. When someone asks “where is the definitive data on matter status?” or “what is the contract’s payment term?”, there is one agreed answer, not three competing spreadsheets.
**Middleware that enforces flow.** Once authoritative sources are designated, middleware ensures data flows from the authoritative source to dependent systems automatically, rather than through manual processes. Contract execution in the CLM triggers automatic updates to the CRM, matter management, and billing systems. No manual re-entry. No divergence.
**Integrated analytics.** The analytics layer pulls data from all authoritative sources and integrates it into a unified repository. This enables reporting and analysis that spans systems — total spend with a vendor across matters and jurisdictions, contract exposure against revenue, client profitability accounting for matter cost and contract margin.
**Reconciliation processes.** Periodic reconciliations identify divergence between systems (why is this contract showing different values in the CLM and the e-billing system?) and trigger investigation. Reconciliation is not a once-yearly audit — in a mature data architecture, reconciliations are continuous and automated, flagging anomalies in real time.
## Measuring Information Governance Maturity
Information Governance maturity can be assessed through key metrics that reflect the health of your data, the effectiveness of your processes, and your readiness for advanced applications like AI and analytics.
### Key Information Governance Metrics
**Data coverage percentage.** What proportion of your legal information assets are in structured, queryable systems versus unstructured repositories or offline storage? Target: \>85% of active contracts in CLM; \>80% of matter documents in document management system.
**Metadata completeness percentage.** Of the documents in your repository, what proportion have complete, accurate metadata (parties, dates, values, classification)? For contracts, what proportion have extraction of key commercial terms? Target: \>90% of executed contracts have complete standard metadata; \>75% have extracted commercial terms.
**Records classified percentage.** What proportion of documents in your repository have been assigned a retention classification and access classification? Target: \>95%.
**Policy compliance rate.** Are documents being retained and disposed of in accordance with your retention schedules? Are legal holds being managed correctly? Do audit logs show that access controls are being enforced? Target: \>98% of dispositions compliant with schedules; 100% of legal holds tracked and managed.
**Data quality audit results.** Periodic data quality audits check for consistency (entity names, taxonomy application, metadata accuracy). Sample 100 random records and assess for accuracy. Target: \>95% accuracy on entity resolution; \>90% accuracy on taxonomy application.
**System interoperability.** What proportion of data flows between source systems are automated via middleware versus manual re-entry? Target: \>90% of routine data flows automated.
### Information Governance Maturity Scorecard
| Capability |
Immature (0–25) |
Developing (25–50) |
Managed (50–75) |
Optimised (75–100) |
| **Classification** |
No formal classification; inconsistent naming |
Classification policy defined; partial rollout |
Classified \>75% of documents; consistent application |
\>95% of documents classified; automated enforcement |
| **Retention** |
Retention schedules vague or absent |
Retention schedules defined for major categories |
Schedules documented and \>80% applied |
Automated disposition workflows; \>98% compliance |
| **Legal Hold** |
Holds managed informally; inconsistent |
Processes documented; holds tracked in spreadsheet |
Centralised holds tracking; some automation |
Integrated holds management; automated notifications |
| **Data Quality** |
Multiple entity names for same counterparty; inconsistent metadata |
Entity resolution underway; taxonomy project initiated |
Entity resolution \>80% complete; metadata \>75% structured |
\>95% entity resolution; metadata \>90% complete |
| **Access Control** |
Access based on role only; minimal audit |
Classification linked to access; access logs maintained |
Access controls enforced by system; audit trail complete |
Real-time access monitoring; anomaly detection active |
| **Analytics** |
No integrated reporting; multiple separate reports |
Data warehouse planned; pilot BI tool |
Warehouse with major source systems; dashboards for key metrics |
Integrated analytics across all systems; AI models operational |
Use this scorecard to identify priority improvement areas. If your organisation is at “immature” on Classification, that is a priority — you cannot confidently restrict access to privileged material if documents are not classified. If you are “immature” on Data Quality, that is your blocking issue for AI deployment — clean the data first.
## In the Trenches
> *This example is fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
**The Data Clean-Up That Unlocked AI**
An Australian financial services firm spent \$180,000 on an AI-powered contract analysis tool. The vendor demo was impressive: the tool could extract 47 different data points from a contract, identify risk clauses, and score overall contract risk. The firm’s General Counsel approved the investment based on the compelling demo.
Four weeks into deployment, the results were unusable. The tool was extracting entity names inconsistently (the same counterparty appeared under seven different name variations), misclassifying contract types (because the firm’s naming conventions differed substantially from the tool’s training taxonomy), and misidentifying standard internal clauses as “high risk” due to lack of context about the firm’s approved positions.
The Head of Legal Operations paused the AI deployment and redirected the team to a three-month data normalisation sprint. They resolved entity names across the contract repository (consolidating 2,800 unique entity strings into 940 canonical entities). They standardised contract type classifications. They tagged 200 approved clause variants as “standard” so the AI could distinguish them from genuinely non-standard language.
When the AI tool was reactivated against the normalised data, extraction accuracy jumped from 62% to 94%. Risk scoring became reliable enough to use in production workflows. Contract review was accelerated from an average of 6 hours to 90 minutes per contract. The tool that had been a \$180,000 write-off candidate became the foundation of the firm’s contract analytics capability and directly contributed to a 30% improvement in contract cycle time.
The lesson is universal: the AI worked as designed. The investment delivered value only once the data foundation was cleaned and normalised. Establishing information governance and data quality as foundational capabilities, ahead of advanced technology, unlocks the full potential of every downstream investment.
## Checklist
- **Run an entity resolution check.** Pick your top 10 counterparties by contract volume or spend. Search for each across every system the legal department uses (CLM, matter management, e-billing, DMS, CRM). Count the name variations. If any entity has more than two variations, entity resolution is an immediate priority.
- **Define your authoritative sources.** For each major data category (contracts, matters, spend, work product), designate one system as the authoritative source. Document it. Communicate it. When someone asks “where is the definitive data on X?”, there should be one answer, not three.
- **Audit your retention schedules.** Review your current document retention policy. Does it cover all document types the legal department manages? Are the retention periods documented and justified (compliant with laws, regulatory requirements, business needs)? Are retention classifications actually being applied?
- **Estimate your metadata enrichment backlog.** How many contracts in your repository have structured metadata (party, value, dates, key terms) versus unstructured storage (a PDF with a filename)? The ratio of structured to unstructured is your metadata enrichment gap — and your AI-readiness indicator.
- **Map one end-to-end data flow.** Select a process (e.g., contract execution to revenue recognition) and trace the data from origin to destination. Note every point where data is manually transferred, reformatted, or re-entered. Each manual step is an error risk and a middleware automation candidate.
- **Classify a small sample of documents.** Take 20 documents at random from your repository and assign them a classification (public, internal, confidential, privileged). What fraction of the team would agree with your classifications? If consensus is unclear, your classification criteria need tightening and your team needs training.
## Suggested Reading
- [ARMA - Generally Accepted Recordkeeping Principles](https://www.arma.org/page/principles)
- [ISO 15489-1: Information and Documentation - Records Management](https://www.iso.org/standard/62542.html)
- [NIST Privacy Framework](https://www.nist.gov/privacy-framework)
- [NIST Cybersecurity Framework 2.0](https://www.nist.gov/cyberframework)
- [IAPP - Data Governance Resources](https://iapp.org/resources/topics/data-governance/)
Source: https://tilt.legal/docs/legal-ops-kit/introduction
Markdown: https://tilt.legal/docs/legal-ops-kit/introduction.md
Welcome to the Legal Ops Kit — a practitioner's guide to running a modern legal function as a discipline rather than a craft.
It's for General Counsel, Heads of Legal Operations, legal engineers, ops managers, and senior counsel doing the day-to-day work of making legal departments scale. Whether you're standing up Legal Ops from scratch, modernising a long-established team, or making a CLM stick on its second attempt, the chapters are built to be picked up mid-stream.
Most of it is written from an in-house perspective — that's where the operational mandate sits most cleanly, and where the worked examples come from. But the underlying disciplines (service-delivery design, vendor and panel management, knowledge management, change leadership, legal technology and AI governance, KPIs) translate directly to private practice. If you're running operations inside a law firm, ALSP, or boutique, swap a few terms ("client" for "the business," "practice group" for "in-house team," "matter intake" for "work routing") — the playbooks land the same way.
## What's inside
Six top-level sections, following the arc of building and running a legal operation:
**Part I — Foundations.** Why Legal Ops exists, what the legal function actually does, and how to baseline your current maturity using the CLOC Core 12 and ACC Maturity Model 2.0.
**Part II — Strategy & Operating Model.** Translating a maturity assessment into a funded, sequenced plan, and designing the team structure to deliver it.
**Part III — People & Change.** The human side: leading change through technology adoption, building enduring legal capability, and the toolkit you'll need for both.
**Part IV — Service Delivery & Spend.** The operational core — routing work to the right provider, managing external counsel and ALSPs, controlling spend, designing workflows, and running legal projects and programmes.
**Part V — Platform: Knowledge, Data & Technology.** The enablement layer that makes everything else scale: knowledge management, information governance, KPI design, and the legal technology stack including CLM and AI.
**Resources & Templates.** Working artefacts — project charters, RFP scorecards, KPI dashboards, prompt-engineering playbooks — to copy, adapt, and use directly.
## How to read it
You don't have to read it cover to cover. Each chapter stands alone: a problem framing, the frameworks and decision tools to apply, an *In the Trenches* example from real implementations, a checklist to act on this week, and suggested reading.
Three common entry points:
- **New to Legal Ops?** Start with Part I — it orients you to the function, the modern mandate, and how to honestly assess where you stand today.
- **Building or refreshing a roadmap?** Jump to Part II. Chapter 4 walks through the strategic planning cycle and the Foundation → Acceleration → Intelligence sequencing model.
- **Trying to land a specific change?** Chapter 6 (Leading Change in Legal) and Appendix F (Change Management Toolkit) are the fastest path to making a tool, process, or workflow stick.
## A living kit
Legal Operations is a fast-moving field — especially around AI, Shadow AI governance, and ESG — and this kit evolves with it. If you spot something wrong, missing, or that could be sharper, the *How to Contribute* page explains how to flag it. The most useful improvements come from practitioners using the kit in real work.
Source: https://tilt.legal/docs/legal-ops-kit/leading-change-in-legal
Markdown: https://tilt.legal/docs/legal-ops-kit/leading-change-in-legal.md
Why change management is the decisive factor in Legal Ops success — three proven frameworks, the psychology of lawyer adoption, and a practical four-phase approach to embedding lasting behavioural change.
## Why Change Fails (And How to Prevent It)
Most legal operations initiatives fail not because of bad technology or strategy, but because the people dimension is underinvested. This isn’t a new observation; it’s just a consistently misapplied one. Organisations spend millions on a new CLM, on process redesign, on competitive technology implementation — and a fraction of that on helping their teams actually adopt the change.
The research is consistent. Thomson Reuters’ *Future of Professionals* report (2025) identified adoption and behaviour change as the primary failure mode for legal technology investments. Not feature gaps. Not technical problems. People.
This chapter treats change management as a professional discipline in its own right — not a soft add-on bolted on after the technology decision. How your team responds to change, adopts new tools and processes, and sustains new ways of working determines whether your investment delivers. It’s the decisive difference between success and expensive underperformance.
## Three Frameworks for Understanding Change
Different change management frameworks emphasise different dimensions of the change process. Understanding three complementary approaches — Kotter’s 8-step model, ADKAR, and the People-Process-Technology framework — gives you diagnostic lenses for identifying why adoption stalls and what to do about it.
### Kotter’s 8-Step Model
John Kotter’s seminal research on organisational change identified eight steps that successful change initiatives follow:
**1. Create urgency.** Establish a clear, credible case for why change is necessary. Without genuine urgency, people defer new behaviours, waiting to see if the change will actually stick.
**2. Build a guiding coalition.** Assemble a leadership group that believes in the change and has the credibility to drive it. This coalition is not necessarily the most senior people — it is people who are trusted, respected, and perceived as having “skin in the game.”
**3. Form a strategic vision.** Define a compelling picture of the future after change. This vision should be clear enough to guide decision-making but compelling enough to inspire discretionary effort.
**4. Enlist a volunteer army.** Move beyond the guiding coalition to recruit broader participation. People who choose to support change are more effective advocates than people who feel obligated.
**5. Enable action by removing barriers.** Identify and eliminate the obstacles that prevent new behaviour. Often these are not technical but organisational — policies, processes, or power structures that reward old ways of working.
**6. Generate short-term wins.** Create visible, tangible successes early. These wins build momentum, prove the change is working, and counter the narrative of “this will never stick.”
**7. Sustain acceleration.** Build on early wins rather than declaring victory prematurely. Change requires sustained effort; the risk of backsliding increases if momentum dissipates.
**8. Institute change.** Embed the new way of working into systems, processes, and culture so it becomes “how we do things here” rather than a temporary initiative.
A consistent pattern in legal technology deployments is that organisations skip steps 1, 2, and 8. They move directly to building the technology (step 3), do some training (implicitly addressing step 4), but fail to establish genuine urgency, assemble respected leadership to champion the change, or institutionalise the new way of working. This produces the failure pattern seen repeatedly: initial adoption after launch, followed by gradual drift back to legacy processes as the initiative loses institutional support.
### ADKAR
The ADKAR model, developed by Prosci, provides a diagnostic framework for understanding what is blocking adoption when it stalls. ADKAR is an acronym for the five dimensions required for successful change:
**Awareness** — Do people understand that change is needed? Do they grasp the business case and the consequences of not changing?
**Desire** — Do people want to support the change? Are they motivated to participate, or are they complying reluctantly?
**Knowledge** — Do people know how to change? Do they have the skills, training, and understanding required to work the new way?
**Ability** — Can people demonstrate the new way consistently and independently? Have they moved from knowing to doing?
**Reinforcement** — Are the new behaviours sustained and reinforced, or is there pressure to revert to old ways?
ADKAR’s power is diagnostic. If adoption is stalling at week 6 of a 12-week rollout, the question is not “why aren’t people using the new tool?” but “which ADKAR element is the bottleneck?” An associate who knows precisely what the new CLM does, has attended training, and understands the business case but still sends contracts via email does not have an Awareness or Knowledge gap — she has an Ability or Desire gap. She may lack confidence in the tool under time pressure, or she may lack personal incentive to change. The intervention is different depending on which element is failing.
Map your current adoption initiative against all five ADKAR elements. Where is the bottleneck? Intervene directly at the broken element rather than re-running generic training in hopes it will fix everything.
### The People-Process-Technology (PPT) Framework
The People-Process-Technology framework rests on a simple but profound observation: sustainable organisational change requires alignment across all three pillars. They are interdependent.
**Technology** performs best when it supports well-designed processes. A tool that automates a broken process simply automates the break. Conversely, a well-designed process supported by poor technology creates friction that eventually drives users back to workarounds.
**Processes** perform best when they are intuitive, well-documented, and aligned with how people actually work. A process that ignores human cognition or behaviour will be subverted — people will find workarounds, especially in high-pressure environments.
**People** are the most important pillar to invest in first. Engagement, motivation, training, and behaviour change are the hardest elements to shift and the longest to embed. If you optimise people last, you will have built expensive technology supporting imperfectly designed processes with people who lack either the knowledge or the motivation to use them.
In practice, this means:
1. **Start with people.** Understand the current behaviours, motivations, and blockers. What is the existing workflow that the new process will displace? What do people value about it? What pain points are you solving? If the people dimension is not solved, technology and process redesign alone will fail.
2. **Design process around how people work.** Map the actual workflow, not the ideal workflow. Involve the people doing the work in process design. A process designed by someone who has not done the work in years will miss critical decision points and dependencies.
3. **Choose technology that supports the process.** The technology is a tool, not the change itself. Its job is to make the new process easier, not to impose a predetermined way of working that ignores how the team actually functions.
4. **Reinforce the people pillar continuously.** Long after technology is deployed and processes are documented, behaviour change is still fragile. Reinforcement, recognition, storytelling, and periodic retraining sustain the change and counter the constant pressure to revert.
## The Psychology of Lawyer Adoption
Lawyers as a professional cohort bring specific behavioural characteristics shaped by their education, incentives, and daily work. Understanding these dynamics isn’t about caricature — it’s about designing change strategies that work with how lawyers actually think, leveraging their professional strengths rather than treating their natural instincts as obstacles.
**Risk aversion as professional identity.** Lawyers are trained extensively to identify risk and protect against downside outcomes. They are paid to worry. A new tool or process represents an unknown, and unknowns carry risk. The instinct to question the unfamiliar is not obstruction — it is professional due diligence. A lawyer questioning a new workflow is executing their professional training. Change management strategies that acknowledge this — building in a testing phase, inviting scepticism, designing small-scale pilots — align with rather than resist this professional reflex.
**Expertise-based authority.** The legal profession’s value proposition rests fundamentally on individual expertise. A lawyer’s professional standing is built on depth in their subject matter. A tool that claims to perform work that previously required lawyer judgment challenges the professional’s sense of indispensability. The subconscious response is often: “If a machine can do what I do, what am I worth?” This is not paranoia — it is a rational response to a genuine threat to professional identity. Effective change communication directly addresses this by positioning the tool as elevating the lawyer’s work, freeing them from commodity tasks to focus on judgment-based advisory where their expertise is truly irreplaceable.
**Perfectionism and control.** Legal work product faces external scrutiny — from courts, regulators, counterparties, and boards. The tolerance for error is near zero in many contexts. Ceding control over any part of the work product to a technology introduces a perceived quality risk that many lawyers find challenging. This is not paranoia either — it is professional prudence. Change strategies that build in lawyer oversight, validation, and final sign-off reduce the perceived risk and recognise the lawyer’s legitimate role as the final quality gate.
**Billable hour conditioning.** For lawyers trained in private practice, time spent learning a new tool is time not spent billing. This creates a deeply ingrained habit of optimising for immediate output over long-term efficiency. Even in-house, where billable hours are irrelevant, the psychological habit persists. Time spent in training or learning a new system feels unproductive. Change strategies that account for this — showing time savings concretely, positioning the investment as “reclaiming time,” offering training in small increments rather than marathon sessions — align with how lawyers actually experience their relationship to time.
**Autonomy expectation.** Senior lawyers, particularly partners and general counsel, are accustomed to high autonomy. Standardised processes and mandatory workflows feel like constraints on professional judgment — even when the intent is to free that judgment for higher-value work. Autonomy is a fundamental professional value in law; it is not obstruction. Change strategies that preserve autonomy within guardrails — “we are standardising the routine work so you can exercise independent judgment on the complex work” — are more successful than approaches that attempt to impose standardisation on the entire workflow.
Effective change management accounts for these real psychological and professional dynamics. A change plan that works with these dynamics — rather than against them — dramatically outperforms one that treats adoption as a training problem alone, regardless of how excellent the underlying technology is.
## The WIIFM Principle
### What’s In It For Me?
Every individual asked to change their behaviour — adopt a new tool, follow a new process, report data in a new format — implicitly asks: “What’s in it for me?” If the answer is unclear, unconvincing, or absent, adoption stalls.
The most effective approach is to frame WIIFM at the individual level rather than the organisational level. “This will save the department £500K per year” is a compelling board-level argument. It lands very differently with the associate who needs to spend 45 minutes learning a new system. Individual adoption accelerates when each person sees a personal, tangible benefit.
Effective WIIFM must be **personal and immediate**:
**For senior lawyers (partners, GCs):** Your direct reports work more efficiently, escalating only genuinely complex matters that require your judgment. You spend less time on administrative oversight and more time on the strategic advisory and leadership work you entered the profession to perform. Your matter management metrics improve, giving you clearer insight into your function’s performance.
**For mid-level lawyers (senior associates, counsel):** This reclaims 5–8 hours per week from administrative overhead, redirecting your time to substantive client work where you build your expertise and strengthen client relationships. Your matter management data flows automatically into your cycle time metrics, visibly demonstrating your efficiency — both supporting your case for advancement.
**For junior lawyers:** This embeds the firm’s negotiation positions and standard clause language directly into your workflow, accelerating your professional development. You spend more time on substantive legal analysis and less time on precedent searches or guessing at what the “house way” is on a particular clause.
**For business stakeholders:** You get your contracts faster, with real-time visibility into where every request sits in the queue. You stop spending time chasing legal for updates because the system notifies you automatically.
### Implementing WIIFM
Map every stakeholder group affected by the change. For each group, define the specific, personal benefit they will experience — not the organisational benefit, but what each person gains individually.
Build these benefits into training materials, launch communications, and ongoing reinforcement. When you talk to a partner about the new CLM, lead with “this frees you from administrative work to do strategic work.” When you talk to an associate, lead with “this saves you 6 hours a week.” When you talk to business stakeholders, lead with “you get faster turnaround and visibility.”
Measure adoption by stakeholder group and investigate promptly when any group falls below target. The adoption gap almost always maps to a WIIFM gap. If partners are not directing their teams to use the tool, you do not have a training problem — you have failed to articulate a compelling WIIFM to partners.
## Managing Shadow AI
### The New Governance Challenge
Shadow IT — the use of unapproved technology tools by employees — has been a governance challenge for over a decade. In 2026, Shadow AI has emerged as the more consequential successor. Lawyers and business users are independently adopting generative AI tools — ChatGPT, Claude, Gemini, and a proliferation of legal-specific AI applications — often without organisational approval, oversight, or governance.
The risks are material and distinct from traditional Shadow IT concerns:
**Confidentiality breach.** Lawyers inputting client-privileged information, deal terms, litigation strategy, or sensitive business data into consumer AI tools risk waiving privilege and breaching confidentiality obligations. Most consumer AI tools’ terms of service explicitly permit the provider to use input data for model training, and the data may be exposed to other users or retained indefinitely. This is not a theoretical risk — regulatory bodies including the Law Society of England and Wales have already issued guidance warning against inputting client information into public AI tools.
**Accuracy risk.** AI-generated legal analysis requires validation by a qualified lawyer to ensure accuracy. AI systems can generate confident, plausible assertions that are factually incorrect — hallucinations in the technical literature. When unvalidated output reaches clients, counterparties, or regulators, liability exposure increases significantly. Validated AI use, by contrast, reduces downstream review burden and catches errors before they escape the organisation.
**Regulatory non-compliance.** Jurisdictions including the EU (under the AI Act) and Australia (under evolving AI governance frameworks) are imposing obligations on the use of AI in regulated contexts. Uncontrolled Shadow AI use may inadvertently trigger compliance obligations the organisation is not yet meeting — audit trails, bias testing, or documentation of AI decision-making.
**Data sovereignty.** Consumer AI tools process data on infrastructure that may not comply with the organisation’s data residency requirements or the data protection obligations in its client contracts. An AI system trained in the cloud may not maintain data residency in the countries required by contract.
### The Governed Enablement Framework
Organisational strategy in 2026 must account for AI’s genuine productivity benefits while establishing governance that is pragmatic rather than prohibitive. A blanket prohibition drives adoption underground, making usage invisible and unmanageable. The effective response is a **governed enablement model** that harnesses AI’s benefits within a compliance framework:
**1. Establish an AI Acceptable Use Policy.** Define what AI tools are approved, what data can be input, and what use cases are permitted. The policy should distinguish between consumer-grade tools (restricted or prohibited) and enterprise-grade tools with appropriate security, privacy, and auditability controls (approved for specific use cases). The policy should also clarify what constitutes confidential data and which roles are authorised to use AI on specific data types.
**2. Provide approved alternatives.** If lawyers are using ChatGPT because the organisation has not provided a sanctioned AI tool, the Shadow AI problem is fundamentally a supply problem, not a demand problem. Deploy enterprise AI tools with appropriate security, privacy, and auditability controls. Give people a sanctioned channel that solves their productivity problem. If the official channel is clunky or slow, people will use the faster unsanctioned alternative.
**3. Train on responsible use.** Every legal team member should complete training on AI-specific risks: confidentiality, accuracy validation, bias, and regulatory requirements. This training should be practical and scenario-based — “here is a confidentiality question and here is how you get an answer safely” — rather than abstract. Training should be regularly updated as the technology and regulatory landscape evolves.
**4. Monitor and guide.** Deploy network monitoring to detect the use of unapproved AI tools. Make the response proportionate and constructive. Initial instances are treated as coaching opportunities, not disciplinary events, with escalation reserved for repeated use after training. The goal is sustainable behaviour change through education and accessible approved alternatives, not enforcement through fear.
Shadow AI is actively present in most legal organisations today. Establishing a governed enablement framework now allows your organisation to capture productivity benefits while maintaining risk control and compliance. Organisations that move first in this space are building competitive advantage through responsible, visible, auditable AI integration.
## The Four-Phase Adoption Plan
Most change management failures trace back to insufficient time in the early phases. Organisations rush from decision to launch, missing the foundation-building work that determines whether adoption sticks.
### Phase 1: Awareness (Weeks 1–2)
**Objective:** Establish urgency, answer “why,” and frame the personal benefit.
**What to do:**
- Communicate the change clearly through multiple channels: email, team meetings, intranet, Slack, one-on-ones. Repetition builds clarity.
- Lead with the problem being solved, not the tool. “We are reducing time spent chasing contract status” not “we have a new CLM.”
- Address the implicit “what’s in it for me?” directly. What does each stakeholder group gain?
- Acknowledge the cost of change. “This will require learning something new” is honest. “This will feel disruptive initially but is worth it” is credible.
- Invite questions without defensiveness. Questions are information about what people are concerned about.
**Success criteria:**
- At least 80% of stakeholders can articulate why the change is happening and what benefit they personally will experience.
- Questions and concerns are being surfaced rather than silently harboured.
### Phase 2: Training (Weeks 3–4)
**Objective:** Build knowledge and confidence through role-specific, hands-on training.
**What to do:**
- Deliver differentiated training by role. Senior lawyers get a 30-minute executive briefing focused on strategic benefits and oversight responsibilities. Working-level lawyers get hands-on workshops with their actual work examples. Support staff get operational training on their specific tasks. One-size-fits-all training serves no one well.
- Use live examples. Show a contract they recently worked on. Walk through how the new process would handle it. Make it concrete, not abstract.
- Emphasise the first month post-launch will include intensive support. People are more willing to try something new if they know help is immediately available.
- Record sessions if possible. People will need to rewatch; live sessions are rarely sufficient for retention.
**Success criteria:**
- At least 80% of stakeholders complete training.
- Post-training surveys show confidence in ability to use the new tool/process.
- Role-specific training is differentiated, not generic.
### Phase 3: Supported Launch (Weeks 5–8)
**Objective:** Build competence and confidence through intensive support and rapid problem-solving.
**What to do:**
- Go live with intensive support immediately available. Assign “floor walkers” or digital champions who can answer questions in real time. These are not trainers — they are peers who have learned the tool and are stationed where people work, able to answer quick questions without requiring a formal support ticket.
- Establish a dedicated support channel (Slack, email, or helpdesk) with committed response times — ideally same-day for urgent issues. Fast response during launch is critical; waiting three days for a response creates frustration and drives users back to workarounds.
- Track adoption daily during this phase. You need to see: How many people are logging into the tool? How many are completing tasks? Where are they dropping off? This granularity allows rapid intervention.
- Intervene immediately when usage drops. If a team is not adopting, find out why. Is it a knowledge gap? Is the tool slower than the legacy process? Is there a specific manager not championing it? Intervene before dropoff becomes entrenched.
- Celebrate early wins publicly. “The contracts team is turning around reviews 3 days faster” creates positive momentum.
**Success criteria:**
- At least 60% of target users are actively using the new tool/process by end of week 6.
- Support response times are consistently met.
- Issues are resolved within 24 hours.
- Adoption is accelerating, not stalling.
### Phase 4: Reinforcement (Ongoing)
**Objective:** Sustain behaviour change, counter backsliding, and build the new way of working into standard operations.
**What to do:**
- Publish adoption metrics monthly. Show progress toward targets. Celebrate teams that are adopting successfully. This creates peer pressure to adopt — in a good way.
- Share stories of how the tool saved specific team members time or improved their work. “Sarah used to spend 6 hours per week searching precedent contracts — now she spends 45 minutes. She is using the time to develop new client relationships.” These stories are more persuasive than any metric.
- Address laggards individually. The conversation is “how can we help you?” not “why aren’t you using this?” Laggards often have legitimate blockers — the tool doesn’t work for their specific workflow, they lack confidence, or they have a workaround that still works. Listen and intervene based on what you hear.
- Build the new tool or process into performance reviews and team objectives. What gets measured and rewarded gets done. If adoption is not connected to performance conversation, people infer it is optional.
- Plan for training refreshers at 6 months and 12 months. New team members will need training; people will have forgotten features they have not used. Refreshers are normal and expected.
**Success criteria:**
- At least 80% of target users are consistently using the new tool/process by end of month 4.
- Adoption is sustained above 75% at month 12.
- The new way of working is becoming “how we do things here” rather than “the new tool the organisation is making us use.”
## Change Champions
The four-phase approach is executed more effectively with peer advocates driving adoption from within the team. These are change champions or “floor walkers” — not formal project resources but respected peers who have embraced the change and help others do the same.
### Identifying Champions
The best change champions are:
- **Early adopters.** They grasp the benefit quickly and are naturally curious about new tools.
- **Respected peers.** People listen to them. This is not automatically the most senior person — it is the person whose judgment colleagues trust and whose opinion influences behaviour.
- **Credible teachers.** They can explain concepts clearly and patiently. Some early adopters are enthusiasts who leave people behind; good champions are teachers.
- **Not just managers.** Peer champions are often more influential than managers. A senior associate’s peer adoption influences her more than her director’s mandate.
Identify champions early — even before launch. Involve them in design and testing. They become your stakeholder advisory board and your implementation team.
### What Champions Do
- **Answer questions in real time.** They sit with the team or are on Slack during the supported launch phase, answering quick questions without requiring a formal support ticket.
- **Demonstrate value to peers.** They share their own workflows, showing how they are getting value. Stories from peers are more persuasive than training materials.
- **Surface feedback.** They gather concerns, friction points, and suggestions from the team and feed them back to the project team. They are your early warning system for adoption problems.
- **Model the behaviour.** They use the tool consistently and visibly. They ask their colleagues “how did you do that in the new system?” normalising the new way of working.
### Supporting Champions
- **Recognition.** Acknowledge their contribution explicitly. Recognise them in team meetings and performance conversations.
- **Time allocation.** They need protected time to support peers. If they are expected to do their normal job plus champion a tool, the championing suffers. Budget their time.
- **Access to the project team.** Give champions direct access to the project team for escalations and feedback. They should not be a bottleneck between the team and the project; they should be a conduit.
- **Training-the-trainer support.** Equip them with deeper knowledge than the general user base so they can confidently answer complex questions.
## Measuring Adoption
Adoption isn’t binary — it’s a spectrum. Moving from “zero usage” to “all users expertly using the tool” is a progression, and knowing where you sit on it — and where the blockers are — lets you intervene precisely.
### Key Adoption Metrics
**Tool activation rate:** What percentage of target users have logged into the system? This is the broadest metric — have people even tried? Target: 80% within 2 weeks of launch.
**Active usage rate:** What percentage of target users are using the tool on a daily or weekly basis? This is a better proxy for genuine adoption than activation. A user who logs in once and never returns is activated but not adopting. Track both daily and weekly active users. Target: 60% at 4 weeks, 75% at 8 weeks, 80% at 12 weeks.
**Task completion via new tool vs legacy method:** For specific workflows, track what percentage of work is being done via the new tool vs the old process. This is the truest adoption metric — are people actually doing the work the new way? Target: Varies by workflow, but for a new CLM you might target 50% of contracts managed through CLM at 4 weeks, 80% at 8 weeks, 95% at 12 weeks.
**User satisfaction:** Run a brief survey or use NPS (Net Promoter Score) to gauge satisfaction. “How likely are you to recommend this tool to a colleague?” Satisfaction is a leading indicator of sustained adoption. Dissatisfied users will find workarounds. Target: NPS \>30 by week 8.
**Time-to-competency:** How long does it take a new user to reach independent competency? This is tracked during the supported launch phase. If time-to-competency is very long, training or tool usability is the issue. Target: 80% of users at independent competency by end of week 4.
### Using Metrics to Diagnose and Intervene
Track metrics weekly during the launch phase and monthly thereafter. When a metric falls below target:
- **Low activation (\< 80% logged in by week 2):** People have not even tried. The barrier is likely awareness or motivation. Do a targeted re-communication emphasizing personal benefit. Is there a manager not championing the change? Address it.
- **High activation but low active usage (60% activated, 20% actively using at week 4):** People tried it but did not persist. The barrier is likely knowledge, ability, or perceived value. The tool may be too complex, the training may have missed something, or the tool may be slower than the legacy process for their specific workflow. Investigate actively and intervene based on what you find.
- **Stalled progress (70% active usage at week 6, still 70% at week 10):** You have hit an adoption ceiling. The remaining 30% likely have a specific blocker — technical, workflow-specific, or motivational. You need to understand what it is and intervene on that specific blocker, not just push harder.
- **Low satisfaction (NPS \< 20 at week 8):** The tool may have quality issues, may not support critical workflows, or may feel slower than the alternative. Do not push harder; diagnose the satisfaction problem and fix it.
## In the Trenches
> *This example is fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
**The Tool Nobody Used**
A regional Australian law firm invested £280,000 in a state-of-the-art document automation platform. The technology was excellent — it could produce first drafts of complex commercial agreements in under three minutes, with clause selection guided by an intuitive decision-tree interface. The vendor’s demo was impressive. The managing partner approved the spend enthusiastically.
Twelve months later, adoption was at 11%. The firm’s lawyers were still drafting documents from prior-matter precedents saved on their personal drives.
The post-mortem identified three failures, all on the people pillar. First, the lawyers had not been consulted during the selection process — the tool was perceived as something imposed by management rather than something designed for them. Second, training was a single two-hour session delivered on a Friday afternoon when half the team was in client meetings. Third, and most critically, no one had addressed WIIFM: the senior partners who controlled workflow allocation did not understand how the tool benefited them personally, so they never directed their teams to use it.
The firm hired a Legal Ops consultant who restarted the adoption effort from Phase 1. She conducted individual interviews with every partner to understand their concerns, then redesigned the training programme around role-specific use cases — showing each partner how the tool would reduce their administrative overhead and free their teams for higher-value work. She identified three “champion” lawyers who had experimented with the tool independently and were willing to demonstrate its benefits to peers. She embedded adoption targets into the firm’s quarterly review process.
Within six months, adoption reached 67%. Within twelve months, 84%. The tool’s ROI, which had been negative for the entire first year, turned positive in month 14. More importantly, the partners began actively directing work to the system, asking champions to help laggards adopt, and treating the tool as foundational to the practice.
The lesson was not about the tool. It was about starting with people, not technology.
## Checklist
- **Draft a WIIFM statement for your current or next initiative for each stakeholder group.** Write one paragraph for each group explaining the personal benefit they will experience. If you cannot articulate a compelling personal benefit, the initiative has an adoption problem that no amount of training will fix.
- **Identify three potential change champions in your team.** Look for respected peers who are early adopters and good teachers — not necessarily the most senior people, but the people whose judgment colleagues trust.
- **Assess your Shadow AI exposure.** Ask your IT security team for a list of AI-related domains accessed from the corporate network in the past 90 days. Do you have an AI Acceptable Use Policy? Is it current? Have you published approved alternatives?
- **Choose your change framework.** For your next initiative, decide whether ADKAR, Kotter, or PPT is the best diagnostic lens. Map your current initiative against it. Where are the gaps?
- **Set adoption targets with timelines for your current initiative.** Define what success looks like — activation rate, active usage rate, task completion rate, satisfaction. Schedule a 30-day review to assess progress and intervene if targets are falling short.
## Suggested Reading
- [Kotter’s 8-Step Change Model](https://www.kotterinc.com/8-steps-process-for-leading-change/)
- [Prosci ADKAR Model Overview](https://www.prosci.com/methodology/adkar)
- [Prosci - Change Management Research](https://www.prosci.com/resources)
- [McKinsey - The Influence Model for Change](https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/the-four-building-blocks--of-change)
- [Thomson Reuters - Future of Professionals](https://www.thomsonreuters.com/en/reports/future-of-professionals.html)
Source: https://tilt.legal/docs/legal-ops-kit/legal-technology-stack-clm-ai
Markdown: https://tilt.legal/docs/legal-ops-kit/legal-technology-stack-clm-ai.md
Building and managing the legal tech stack — CLM as core infrastructure, the build vs buy decision, and deploying AI effectively with appropriate governance.
---
## Introduction: Technology as Strategic Infrastructure
Technology in legal operations isn’t a cost centre — it’s strategic infrastructure. Legal teams that digitise contracts, structure data, automate routine workflows, and deploy AI thoughtfully gain significant competitive advantages: faster execution, higher compliance accuracy, better decision-making, and liberation from commoditised work.
This competency spans four domains: the legal technology landscape, CLM as foundational infrastructure, artificial intelligence and its practical deployment, and the governance frameworks that protect privilege, privacy, and security. Mastery here distinguishes mature legal operations from those that treat technology as a support function.
---
## Part 1: The Legal Technology Stack
### The Landscape in 2026
The legal technology ecosystem has matured into distinct categories, each addressing specific operational needs:
**Contract Lifecycle Management (CLM):** The connective hub of modern legal operations. Contracts are digitised, searchable, version-controlled, and integrated with enterprise systems. CLM platforms include Coda, Icertis, Ironclad, and many others, each with different deployment models and specialisations.
**E-Billing & Cost Management:** Tools that capture and analyse legal spend. Time and expense tracking, matter management, and billing analytics enable cost visibility and vendor performance management. Traditional players (Thomson Reuters, Lexis Nexis) and newer entrants (Casepoint, Managed XChange) compete in this space.
**Matter Management & Practice Management:** Systems that manage the lifecycle of individual matters — from intake through closure — including timekeeping, matter profitability, and resource allocation. These tools integrate with accounting and billing systems.
**Document Automation:** Tools that generate documents from templates and data inputs. Used for everything from standard contracts to regulatory filings. Platforms like HotDocs, Kira Automation, and built-in CLM authoring engines dominate.
**Artificial Intelligence & Analytics:** Increasingly embedded in every platform, but also available as standalone tools. AI handles summarisation, extraction, classification, and workflow automation. Vendor landscape ranges from general-purpose AI providers to legal-specific platforms.
**Compliance & Regulatory Intelligence:** Tools that monitor regulatory changes, track compliance obligations, and generate compliance status reports. Critical for in-house teams managing complex regulatory environments.
**Legal Research:** Traditional research platforms (Westlaw, Lexis Nexis) now augmented with AI-powered research assistance and broader integration with matter management systems.
### Maturity Stages of Technology Adoption
Organisations adopt legal technology in a predictable arc, with distinct maturity stages:
**Stage 1: Digitisation.** Documents move from filing cabinets to shared drives. Basic file naming and folder structure. Limited searchability. Advantage: centralised storage. Risk: false sense of order.
**Stage 2: Systematisation.** Technology platform deployed (CLM, matter management, research system). Documents now in a system with structured metadata, version control, and basic search. Workflows begin to be defined in the system rather than via email and spreadsheets.
**Stage 3: Integration.** Systems are connected through middleware or API integrations. Data flows between CLM and CRM, CRM and ERP, ERP and accounting. The enterprise systems talk to each other rather than forcing manual re-keying.
**Stage 4: Intelligence.** Data extracted from systems is analysed. Analytics dashboards provide visibility into contract portfolio composition, deal cycle times, risk patterns, and cost trends. AI tools augment human decision-making.
**Stage 5: Orchestration.** AI systems autonomously execute multi-step workflows. Agents make routing and classification decisions. Human involvement is structured through defined checkpoints rather than happening at every step. The legal function operates as a platform that the business self-serves through defined interfaces.
Most organisations in 2026 sit in Stage 2 or Stage 3. The jump to Stage 4 requires the data normalisation work described in Competency 10 (Data & Analytics). The jump to Stage 5 requires both Stage 4 maturity and the governance frameworks described in Part 5 of this chapter.
### Integration: The Silent Enabler
The single most impactful factor in technology ROI is integration. A CLM that exists in isolation is a faster document management system. A CLM connected to the CRM, ERP, and procurement system is a strategic asset that enables the entire business to make better decisions faster.
Integration challenges are predominantly architectural and organisational, not technical:
**Architectural:** Which systems need to talk to each other? What data needs to flow between them? How frequently? What is the source of truth for each data field? These questions must be answered before any integration work begins. See Competency 10 (Data & Analytics) for detailed guidance on integration architecture.
**Organisational:** Different departments often use different systems and have conflicting data definitions. The finance team’s definition of “contract value” may differ from the sales team’s. Legal systems, financial systems, and procurement systems may have different taxonomies for the same information. Organisational alignment on data definitions is prerequisite to successful integration.
**Operational:** Once integrated, systems require ongoing maintenance. System updates, data quality monitoring, and change management ensure that integrations continue to function correctly. Budget for operational support, not just implementation.
The role of middleware (platforms like Zapier, MuleSoft, or Boomi) or native API integrations is to translate between systems. Middleware abstracts away the technical complexity but does not eliminate the need for clear data specifications and organisational alignment.
---
## Part 2: CLM as Core Infrastructure
### Contracts as the Enterprise Operating System
Contracts are the connective tissue of every commercial enterprise. They define revenue streams, govern supplier relationships, allocate risk, and encode the terms on which the business operates. The strategic potential of contract data is enormous. Organisations that digitise, structure, and make their contract data analytically accessible gain a significant competitive advantage.
The CLM platform, at its most basic, is a repository and workflow tool. At its most mature, it transforms contracts from static legal documents into **living digital assets** — searchable, structured, analytically rich, and integrated with the enterprise systems that depend on contract data to function.
### CLM Maturity Spectrum
| Maturity Level |
Characteristics |
Business Value |
| **Level 1: Static Files** |
Contracts stored as PDFs or Word documents on shared drives. Basic storage with limited accessibility. |
Foundational organisation. Contracts are centralised in a shared location. |
| **Level 2: Repository** |
Centralised storage with basic metadata (party, date, type). Search capability enables contract discovery. |
Findability. The legal team can locate contracts through searchable fields. |
| **Level 3: Workflow** |
Automated approval routing, version control, e-signature integration. Templates and clause libraries available. |
Cycle time reduction. Standardised processes accelerate execution and enhance consistency. |
| **Level 4: Intelligence** |
AI-powered clause extraction, obligation tracking, risk scoring. Analytics dashboards with portfolio-level visibility. |
Decision support. The organisation gains strategic visibility into contract portfolio composition, risk profile, and value. |
| **Level 5: Platform** |
CLM integrated with CRM, ERP, procurement, and compliance systems. Contracts operate as data sources for enterprise decision-making. Self-service interfaces for the business. |
Revenue enablement. Contracts become a strategic asset class, accelerating deals, enforcing compliance, and generating enterprise intelligence. |
Most organisations sit between Levels 2 and 3. The jump to Level 4 requires robust data normalisation. The jump to Level 5 requires the integration architecture and governance frameworks described elsewhere in this competency.
### Digital Playbooks: Embedding Institutional Knowledge
The digital playbook is the mechanism that transforms institutional knowledge about negotiation into a scalable, machine-readable asset. A well-built playbook codifies the organisation’s approved positions, acceptable deviations, and escalation triggers for every material clause type.
### Playbook Architecture
A digital playbook has four layers:
**Layer 1: Standard Position.** The organisation’s preferred clause language for each material term — the starting point for every negotiation. This language appears in the first draft generated from the template.
**Layer 2: Acceptable Deviations.** The range of modifications the organisation will accept without escalation. For a limitation of liability clause, this might be: “Cap at 2x contract value (standard), acceptable down to 1x contract value (deviation), anything below 1x requires Legal Director approval (escalation).”
**Layer 3: Fallback Language.** Pre-approved alternative formulations that can be offered when the standard position is rejected. Having fallback language ready eliminates the delay of drafting new clause language mid-negotiation.
**Layer 4: Escalation Triggers.** The specific conditions under which a deviation must be escalated to senior counsel or the business sponsor. Triggers should be defined in measurable terms (dollar thresholds, counterparty categories, jurisdictional risks) to eliminate ambiguity.
### Playbook Integration with CLM
In a mature CLM deployment, the playbook is embedded directly in the contract authoring and review workflow:
- When a user generates a first draft, the template populates with Layer 1 standard positions
- When a counterparty redline is received, the CLM highlights deviations and maps them against Layer 2 acceptable ranges
- If a deviation falls within acceptable range, the system suggests Layer 3 fallback language automatically
- If a deviation exceeds acceptable range, the system triggers a Layer 4 escalation to the appropriate reviewer
This integration means that a commercial team member — not a lawyer — can manage a standard negotiation within pre-approved parameters. Legal bandwidth is reserved for genuinely non-standard situations. The result: dramatically reduced cycle times for routine agreements and higher-quality deployment of legal judgment where it is actually needed.
The digital playbook is the highest-ROI investment in the CLM ecosystem. A CLM without a playbook is a faster way to manage contracts. A CLM with a playbook is a fundamentally different operating model — one where legal expertise is embedded in the system rather than bottlenecked through individual lawyers.
### CLM Integration: The Enterprise Nervous System
### CRM Integration (Salesforce, HubSpot, Dynamics)
The CRM-CLM integration creates a seamless handoff from sales process to contract execution. The integration points:
**Deal data push.** When a sales opportunity reaches the contract stage, the CRM pushes deal data (customer name, deal value, product/service selection, pricing) to the CLM, which generates a first draft from the appropriate template with fields pre-populated. Zero re-keying, zero data discrepancy.
**Status sync.** Contract status (draft, in negotiation, pending approval, executed) is synced back to the CRM in real time. Sales representatives see contract status without leaving their CRM — eliminating the emails that consume legal team bandwidth.
**Revenue data flow.** Upon execution, the signed contract terms (value, duration, renewal date, pricing tiers) flow from the CLM to the CRM. Sales forecasting now reflects executed contract terms rather than pipeline estimates.
### ERP Integration (SAP, Oracle, NetSuite)
The ERP-CLM integration connects contract terms to financial operations:
**Obligation automation.** Payment terms, milestone schedules, and performance obligations extracted from executed contracts feed directly into the ERP for accounts payable and receivable processing. Manual spreadsheet-based tracking is replaced by system-driven automation.
**Budget alignment.** Contract commitments flow into the financial planning module, enabling real-time visibility into committed versus available budget. The CFO can see total contractual commitment exposure at any point in time.
**Renewal management.** Renewal dates, auto-renewal windows, and termination notice periods trigger automated alerts through both the CLM and ERP, ensuring proactive contract management.
### Procurement Integration
For vendor contracts, the CLM-procurement integration ensures every vendor engagement follows the approved sourcing and contracting process:
**Vendor onboarding.** New vendor requests trigger the contract workflow automatically — due diligence, risk assessment, contract generation, and approval routing happen within a unified process.
**Compliance enforcement.** Procurement cannot issue a purchase order against a vendor without an executed, valid contract in the CLM. This eliminates informal arrangements and ensures every commercial relationship is governed by appropriate terms.
### Legal-as-a-Platform: Compliance-by-Design
### The Platform Model
Legal-as-a-Platform means the legal function operates as an internal service platform that the business consumes through defined interfaces, rather than engaging through ad hoc requests. The CLM is the primary delivery vehicle in the contracting domain.
**Self-service contract generation.** Business users select the appropriate agreement type, answer guided questions, and receive a compliant first draft — without submitting a request to legal. Legal is involved only when the triage system identifies non-standard elements.
**Embedded compliance checks.** Regulatory and policy requirements are coded as automated checks within the CLM workflow. A data processing agreement is automatically required when the contract involves personal data. Sanctions screening is triggered for cross-border transactions. ESG questionnaires are generated for supplier contracts above a defined threshold.
**Audit-ready documentation.** Every contract action — creation, modification, approval, execution — is logged with timestamps, user identities, and decision rationale. When an auditor or regulator asks “who approved this deviation and why?”, the answer is in the system.
### Compliance-by-Design in Practice
The fundamental principle: compliance controls are built into the process at the point of action, not applied as a review layer after the fact. Compliance requirements are embedded in the system’s workflow, ensuring enforcement without requiring business users to manage compliance explicitly.
A practical example: an Australian financial services company subject to AML/CTF requirements builds customer due diligence (CDD) triggers into its client onboarding CLM workflow. When a new client engagement contract is initiated, the system automatically assesses the client against risk criteria, triggers enhanced due diligence for high-risk categories, generates the required CDD documentation, and blocks contract execution until all AML/CTF requirements are satisfied. The commercial team experiences this as part of the normal contracting process — not as a separate compliance burden.
Compliance-by-Design requires ongoing maintenance. Regulatory requirements change, and compliance rules embedded in the CLM must be updated accordingly. Budget for a quarterly regulatory review cycle that audits all embedded compliance checks against current requirements.
---
## Part 3: AI in Legal — The 2026 Landscape
### Generative vs. Agentic AI
Generative AI is table stakes. By 2026, every major legal technology vendor has embedded LLM capabilities into their platform. Document summarisation, clause extraction, first-draft generation, and natural language search are commodity features. The strategic conversation has moved beyond “whether to adopt AI” — the question is *how* to deploy it for maximum operational impact.
The cutting edge has moved to **Agentic AI** — AI systems that do not merely generate content in response to a prompt but autonomously execute multi-step workflows, make routing decisions, interact with external systems, and adapt their approach based on intermediate results.
### Generative AI: The Content Engine
Generative AI takes an input (a prompt, a document, a dataset) and produces an output (a summary, a draft, a classification). The interaction is **single-turn**: human provides input, AI produces output, human evaluates. Every instance requires human initiation and human review.
**Legal applications of generative AI (mature, widely deployed in 2026):**
- **Document summarisation:** Condensing lengthy contracts, judgments, or regulatory filings into structured summaries highlighting key terms, obligations, and risks
- **First-draft generation:** Producing initial drafts of standard agreements, memos, and correspondence based on templates, playbooks, and matter context
- **Clause extraction and classification:** Identifying and categorising specific clauses across a portfolio of contracts for analytics, migration, or compliance review
- **Research assistance:** Synthesising legal research across jurisdictions, identifying relevant precedents, and drafting preliminary legal analysis
- **Translation and localisation:** Converting legal documents between languages with domain-specific accuracy
### Agentic AI: The Workflow Orchestrator
Agentic AI operates autonomously across multiple steps, making decisions at each stage based on predefined rules, contextual data, and intermediate results. The interaction is **multi-turn and autonomous**: human defines the objective and constraints, the AI executes a sequence of actions, and human actively oversees execution at defined checkpoints.
**Legal applications of agentic AI (emerging, high-impact in 2026):**
- **End-to-end NDA processing:** An AI agent receives an incoming NDA, compares it against the organisation’s playbook, classifies it by risk tier, generates redlines for non-standard terms, routes it for the appropriate level of review (or auto-approves if within parameters), and sends the response to the counterparty — with human review only for Amber and Red classifications
- **Regulatory change management:** An agent monitors regulatory sources across defined jurisdictions, identifies changes relevant to the organisation, assesses the impact against existing policies and contracts, generates a preliminary impact report, and routes it to the responsible lawyer
- **Due diligence orchestration:** An agent ingests a data room, classifies documents by type, extracts material terms from each category using specialised extraction models, flags anomalies and risks, compiles a preliminary due diligence report, and identifies items requiring human review
- **Compliance monitoring:** An agent continuously scans contract obligations, regulatory deadlines, and policy requirements, identifies items approaching their due date, escalates overdue items, and generates compliance status reports
### Generative vs. Agentic: The Comparison Matrix
| Dimension |
Generative AI |
Agentic AI |
| **Interaction model** |
Single-turn: prompt → response |
Multi-turn: objective → autonomous execution |
| **Human involvement** |
Required at every step |
Required at defined checkpoints |
| **Decision-making** |
Human decides; AI produces content |
AI decides within parameters; human oversees |
| **Error profile** |
Hallucination in output content |
Incorrect routing, missed edge cases, cascading errors |
| **Data requirement** |
Input document(s) + prompt |
Normalised data ecosystem + integration layer + rules engine |
| **Maturity in legal (2026)** |
Mature, widely deployed |
Emerging, high-potential, requires careful governance |
Agentic AI amplifies both capability and risk. An agent that processes 500 NDAs per month with 98% accuracy also makes 10 errors per month at production speed — errors that propagate downstream if the governance framework does not catch them. The higher the autonomy, the more critical the Human-in-the-Loop (HITL) checkpoints described in Part 5.
### Build vs Buy: Navigating the AI Decision
One of the most consequential decisions legal ops leaders face is whether to build custom AI solutions or purchase off-the-shelf tools. This decision has profound implications for cost, implementation timeline, ongoing maintenance, and your ability to adapt as requirements evolve.
### When to Buy Off-the-Shelf
**Buy when:** The use case is a commodity workflow that most legal operations encounter.
**Examples:** Contract summarisation, basic clause extraction, document classification, first-draft generation from templates, standard research assistance. These are use cases where vendors have invested in building generalised solutions applicable across industries and organisations.
**Advantages:**
- **Speed to deployment.** An off-the-shelf tool is available immediately. You can pilot in weeks, not months.
- **Vendor support and ongoing development.** The vendor invests in improving the tool, adding features, and ensuring it works with your existing systems. You do not carry the burden of maintenance.
- **Lower upfront cost.** Most SaaS tools have per-user or per-transaction pricing, keeping upfront investment modest.
- **Shared risk.** If the vendor’s tool produces an error, you share the liability with the vendor. Custom-built tools carry entirely your risk.
**Considerations:**
- **Customisation constraints.** Off-the-shelf tools are designed for broad applicability, which often means they do not perfectly fit your specific workflows or data structures. You will need to adapt your process to the tool.
- **Data privacy.** Most SaaS tools process your data in the vendor’s cloud environment. Ensure the vendor’s data handling practices and security certifications meet your requirements.
- **Vendor lock-in.** Once you build workflows around a vendor’s tool, switching to an alternative becomes costly. Choose vendors carefully.
- **Cost scalability.** As usage grows, per-user or per-transaction costs can become substantial. Model long-term cost trajectories.
### When to Build Custom AI
**Build when:** The use case involves proprietary workflows, unique data structures, or competitive differentiation that off-the-shelf tools cannot provide.
**Examples:** A customised AI system for drafting your organisation’s proprietary contract forms while enforcing your playbook. A system that integrates with your bespoke ERP system in ways no vendor tool supports. An AI system trained on your historical contracts and negotiation outcomes to predict counterparty responses.
**Advantages:**
- **Perfect fit.** You build precisely what you need, adapted to your workflows, data structures, and business logic.
- **Competitive advantage.** A custom tool that competitors do not have can produce meaningful advantage. If you have proprietary data (historical contracts, negotiation precedents, risk assessments) that is unique, a custom system that leverages that data is defensible.
- **Integration depth.** You can build deep integrations with your existing systems — real-time data flows, two-way updates, embedded workflows. Off-the-shelf tools typically offer integration at the boundary, not deep embedding.
- **Control.** You control the entire system — data handling, security practices, change management. No vendor surprises or forced migrations.
**Considerations:**
- **Higher cost.** Building custom AI requires hiring or contracting data scientists, ML engineers, and legal domain experts. This is expensive.
- **Longer timeline.** Building, testing, and refining a custom AI system typically takes 6-12 months minimum for non-trivial applications.
- **Ongoing maintenance.** You are responsible for maintaining, updating, and improving the system. As underlying AI models evolve (new versions of Claude, GPT, etc.), you must manage upgrades.
- **Risk concentration.** If the system fails or produces poor results, you bear the full consequences. There is no vendor to share liability or provide support.
- **Talent risk.** Custom AI depends on individuals with specialised skills. If key team members leave, knowledge walks out the door.
### The “Configure” Middle Ground
Many organisations find a middle path: purchasing a platform (like a modern CLM or matter management system) and configuring it extensively to fit your workflows, playbooks, and data structures. This approach is neither pure build nor pure buy.
**When to configure:**
- The vendor’s platform is extensible (APIs, no-code/low-code configuration tools, workflow automation).
- Your team has individuals with technical capability (the Legal Engineer role from Part 5) who can configure the platform.
- Your use case requires customisation but not fundamental technology innovation.
**The advantage:** You get much of the customisation benefit of building, at a fraction of the cost and timeline. You retain vendor support and platform development.
**The risk:** Extensive configuration creates dependency on the vendor’s platform roadmap. If your configuration relies on a feature the vendor changes or deprecates, you are exposed. Test this risk early by confirming that the features you rely on are stable and vendor-committed.
### A Decision Framework
| Domain |
Required Competency |
| **Legal** |
Understanding of legal concepts, workflows, privilege, and risk — sufficient to specify requirements and evaluate AI outputs (not necessarily a practising lawyer) |
| **Data** |
Data normalisation, taxonomy design, SQL or equivalent querying, basic statistical literacy — sufficient to prepare and maintain the data foundation AI depends on |
| **Technology** |
API integration concepts, workflow automation (no-code/low-code), CLM and matter management configuration, prompt engineering — sufficient to build and maintain AI-powered workflows |
| **Change Management** |
Stakeholder engagement, training design, adoption measurement — sufficient to drive the behavioural change that technology deployment requires |
| **Project Management** |
Agile methodology, vendor management, budget tracking — sufficient to deliver initiatives on time and within scope |
### Where Legal Engineers Come From
The Legal Engineer does not emerge fully formed. They evolve from one of three pathways:
**Pathway 1: Lawyer → Legal Ops → Legal Engineer.** A practising lawyer who transitions into Legal Ops, develops technology and data skills, and evolves into the bridging role. Strength: deep legal domain expertise. Investment area: deliberate technology skill development.
**Pathway 2: Technologist → Legal Tech → Legal Engineer.** A software engineer, data analyst, or IT professional who specialises in legal technology. Strength: strong technical foundation. Investment area: legal domain knowledge and substantive AI evaluation capability.
**Pathway 3: Paralegal → Legal Ops → Legal Engineer.** A paralegal with process expertise and operational knowledge who develops both legal and technical skills. Strength: deep understanding of how legal work actually flows. Investment area: seniority and strategic influence.
The most effective Legal Ops teams in 2026 include representation from at least two of these pathways, creating complementary skill coverage.
The Legal Engineer is the connective tissue that lets lawyers and technologists work together productively, translating legal requirements into technical specs and technical constraints into legal solutions. Strong Legal Engineer teams produce tools that work both technically and operationally.
---
## Part 6: In the Trenches
> *These examples are fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
### The Agent That Processed 200 NDAs Per Month
A global professional services firm deployed an agentic AI system for NDA processing in early 2025. The agent’s workflow: receive incoming NDA from business development, compare against the firm’s standard NDA playbook, classify as Green (standard — auto-process), Amber (minor deviations — generate redlines and route for junior counsel review), or Red (material issues — escalate to senior counsel).
The first three months revealed an opportunity: the agent classified 12% of NDAs differently than expected — mostly false Greens (NDAs classified as standard that contained non-standard terms). The diagnosis: the playbook data used to train the agent needed enrichment with additional clause variants that counterparties commonly used.
The team invested six weeks in playbook enrichment — adding 85 additional clause variants with their risk classifications. They also added a “confidence threshold” to the agent: if the agent’s classification confidence fell below 85%, the NDA was automatically escalated to Amber regardless of the classification.
After enrichment, misclassification dropped to 2.1%. The agent processed an average of 200 NDAs per month, with 68% classified as Green (auto-processed), 26% as Amber (junior counsel review, average 20 minutes), and 6% as Red (senior counsel review). The firm estimated that the system freed approximately 140 hours of lawyer time per month — time that was redeployed to client-facing advisory work.
The critical success factor was not the AI technology. It was the quality of the playbook data — confirming, once again, that data quality determines AI effectiveness.
### The CLM That Became the Source of Truth
A mid-sized Australian technology company had a contract management problem that was also a revenue recognition problem. Their 3,200 active customer contracts lived in a combination of a legacy document management system, individual lawyers’ email archives, and a physical filing cabinet in the Sydney office (for agreements predating 2015). When the finance team needed to verify contract terms for revenue recognition under AASB 15, they relied on a spreadsheet maintained by a single paralegal — a spreadsheet that was approximately 78% accurate.
The new Head of Legal Ops proposed a CLM implementation with a dual objective: manage the contract lifecycle going forward and, through a migration project, bring all existing contracts into the system with structured metadata.
The migration was the hard part. An ALSP was engaged to review and tag the 3,200 existing contracts — extracting party names, contract values, key dates, governing law, renewal terms, and material obligations into structured fields. AI-assisted extraction handled 70% of the metadata; the remaining 30% required manual review due to non-standard formats.
Six months later, the CLM was live with both a forward-looking workflow (all new contracts originated and managed in the system) and a backward-looking repository (all legacy contracts searchable with structured metadata). The finance team retired the paralegal’s spreadsheet and built their revenue recognition processes directly on CLM data. The accuracy of contract data used for financial reporting went from 78% to 99.2%.
The CFO called it “the single most impactful legal technology investment the company has made” — because it solved problems that transcended traditional legal operations boundaries. It was fundamentally a financial reporting problem, a revenue assurance problem, and an audit risk management issue that demonstrated how contract data serves enterprise-wide decision-making.
### The Privilege Leak
A multinational corporation deployed a generative AI tool for litigation support. The tool was excellent at summarising deposition transcripts, identifying inconsistencies across witness statements, and drafting preliminary legal memoranda. Lawyers on the litigation team adopted it enthusiastically.
Six months into deployment, opposing counsel in a major dispute issued a discovery request that specifically included “all documents and communications generated by or through artificial intelligence systems in connection with this litigation.” The corporation’s outside counsel reviewed the AI system’s data architecture and discovered that the tool — a cloud-hosted SaaS platform — stored all inputs and outputs on shared infrastructure, with the vendor retaining access to the data for “product improvement” purposes. The vendor’s terms of service granted the vendor a licence to use input data for model training.
The opposing counsel’s challenge: by providing privileged litigation strategy materials to a third-party vendor with ongoing access and usage rights, the corporation had potentially waived privilege over those materials. The court’s ruling — delivered after four months of motion practice and USD 850,000 in legal fees — found privilege maintained for the specific documents at issue but signalled that future cases with more explicit vendor data usage might face different outcomes.
The corporation immediately migrated the tool to a private-cloud deployment with contractual terms prohibiting any vendor access to input or output data. They also implemented a mandatory privilege review checkpoint in the AI workflow: before any privileged content is processed through the AI system, a lawyer confirms that the data pipeline maintains privilege protections.
The episode required nearly USD 1 million in direct legal fees and generated a privilege precedent affecting their future litigation strategy. The lesson: governance frameworks must assess both AI tool functionality and data handling to protect privilege throughout the AI lifecycle.
---
## Checklist
**Technology Landscape & Maturity**
- **Assess your technology maturity.** Using the five-stage framework in Part 1, determine where your organisation currently sits across each legal technology category (CLM, matter management, e-billing, AI, etc.). Be specific — you may be Stage 3 for CLM workflow but Stage 1 for analytics. The gap between current and target state defines your investment roadmap.
- **Map your integration priorities.** List the three enterprise systems that most need contract or legal matter data (typically CRM, ERP, and procurement). For each, define the specific data fields that should flow between systems. This mapping is the specification for your middleware or integration project.
**CLM & Digital Playbooks**
- **Assess your CLM maturity level.** Using the five-level framework in Part 2, determine where your organisation currently sits. Gap analysis between current and target state defines your CLM investment roadmap.
- **Identify your top 3 playbook candidates.** Which contract types have the highest negotiation volume and the most predictable deviation patterns? These are your first digital playbook candidates. Start documenting the standard positions, acceptable deviations, and escalation triggers for each.
- **Quantify your compliance-by-design opportunity.** Identify one regulatory requirement that is currently enforced through manual review. Estimate the annual cost of that manual review (hours × rate) and the risk exposure from inconsistent enforcement. This is the business case for embedding that requirement in the CLM workflow.
**AI Strategy & Deployment**
- **Classify your AI readiness.** For your top 5 legal workflows by volume, assess: (1) Is the underlying data normalised and structured? (2) Is there a clear, documented process that the AI would follow? (3) Is there a measurable baseline for current performance? Workflows that answer “yes” to all three are AI-ready. Workflows that require foundation work become clear priority targets.
- **Make your build vs buy decision.** For your top AI use case, determine whether the workflow is commodity (buy), proprietary (build), or partially unique (configure). Use the decision framework in Part 3 to guide your decision.
- **Identify your RAG knowledge base starting point.** What is the most curated, authoritative, and well-maintained corpus of legal documents in your organisation? This — whether it is a playbook, a policy set, a template library, or a contract portfolio — is your RAG knowledge base seed.
- **Select one pilot use case.** Apply the four selection criteria from Part 3: high volume, low risk, measurable baseline, enthusiastic users. Commit to a 90-day pilot with defined evaluation metrics.
- **Establish your error management framework.** For the selected pilot use case, determine: what is the consequence of an AI error? If the consequence is manageable (a summary that needs correction), proceed with appropriate HITL checkpoints. If the consequence is significant (an auto-executed contract with incorrect terms), maintain human review checkpoints across the full cycle until accuracy proves itself reliably.
**AI Governance**
- **Audit your AI tools for privilege risk.** For every AI tool currently in use by the legal team, answer: Does the vendor have access to input data? Does the vendor retain output data? Do the vendor’s terms permit data usage for model training? Document privilege protection status for tools processing confidential content.
- **Draft (or update) your AI governance policy.** The policy should cover: approved tools, prohibited tools, data classification rules, HITL requirements by use case, privacy impact assessment triggers, and incident response procedures. This policy is your highest-priority governance deliverable.
- **Define your HITL checkpoints.** For each AI-powered workflow, specify: who reviews the output, what depth of review is required, what happens when the reviewer identifies an error, and how review outcomes are logged. Document this in an operational procedure that guides daily work.
- **Identify your Legal Engineer candidate.** Look across your legal and legal ops team for the individual who most naturally bridges legal and technical domains. Invest in their development through formal training in data literacy, prompt engineering, or workflow automation, as this role will define the effectiveness of your AI strategy.
## Suggested Reading
- [CLOC Core 12 - Technology Competency](https://cloc.org/cloc-core-12/)
- [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework)
- [OECD AI Principles](https://oecd.ai/en/ai-principles)
- [ISO/IEC 42001 (AI Management System)](https://www.iso.org/standard/81230.html)
- [Stanford HAI - AI Index Report](https://hai.stanford.edu/ai-index)
Source: https://tilt.legal/docs/legal-ops-kit/managing-external-providers
Markdown: https://tilt.legal/docs/legal-ops-kit/managing-external-providers.md
Selecting, onboarding, and managing law firms and legal service providers by performance — RFP methodology, alternative fee arrangements, and the QBR framework for ongoing accountability.
## The Vendor Ecosystem, Redesigned
The relationship between a corporate legal department and its external providers in 2026 bears little resemblance to the gentleman’s-agreement model of a decade ago. The modern legal vendor ecosystem is a managed portfolio of law firms, ALSPs, contract staffing agencies, and technology vendors — each selected, onboarded, measured, and retained (or exited) on demonstrated performance against defined criteria.
This is vendor management, and it’s one of the highest-leverage activities in Legal Operations. External counsel spend typically represents 50–70% of the total legal budget. A 10% efficiency gain there delivers more absolute savings than a 30% gain on any internal operational metric. The tools to achieve it are the modern RFP, alternative fee arrangements, and structured performance reviews.
## The Modern RFP
### Evidence-Based Selection
The modern law firm selection process builds on the traditional credentials presentation with structured, evidence-based evaluation criteria. Where firms were historically selected on the strength of their pitch and the chemistry of the proposed team, the modern RFP adds performance data, pricing transparency, and delivery track records.
The modern RFP is an evidence-based procurement exercise. It evaluates firms on four dimensions:
**1. Capability and Experience.** Demonstrated track record in the specific matter type, jurisdiction, and industry. Assessed through matter case studies, named lawyer CVs, and client references — not firm-level marketing materials.
**2. Pricing and Commercial Terms.** Detailed fee proposals including rate cards, proposed fee arrangement (hourly, fixed, capped, or hybrid), estimated total cost, and assumptions underlying the estimate. The pricing proposal should be structured to enable apples-to-apples comparison across respondents.
**3. Technology and Process.** What technology does the firm use for matter management, document review, and client reporting? What is their approach to process efficiency? In 2026, firms with articulated technology strategies demonstrate commitment to delivery efficiency and create cost advantages for their clients.
**4. Diversity and ESG Commitments.** Staffing diversity metrics, pro bono commitments, and environmental sustainability practices. These have become core procurement requirements, driven by the client organisation’s ESG obligations and supply chain reporting mandates.
### The ALSP Dimension
Alternative Legal Service Providers (ALSPs) have matured from niche outsourcing shops to sophisticated, technology-enabled service platforms. The modern RFP should evaluate ALSPs alongside traditional law firms for appropriate work categories.
| Work Category |
Law Firm Strength |
ALSP Strength |
| Complex litigation strategy |
Deep expertise, partner judgment |
Limited — this is law firm territory |
| High-volume contract review |
Expensive at scale |
Purpose-built for volume, 30-50% cost advantage |
| Regulatory compliance (routine) |
Over-qualified and over-priced |
Process-driven, technology-augmented |
| Legal project management |
Often under-resourced |
Core competency for many ALSPs |
| Document review (discovery) |
Typically outsourced internally to junior associates |
AI-augmented platforms, per-document pricing |
The key principle: the RFP should be **work-type specific**. Issuing a single RFP that asks one firm to handle everything from M&A advisory to NDA processing is the procurement equivalent of asking a cardiothoracic surgeon to also handle your dental work. Both are medical professionals; the specialisation matters.
## Pricing Models: Escaping the Billable Hour
### Why the Billable Hour Persists
The billable hour is the default for a simple reason: it transfers all pricing risk to the client. The firm bills for time spent regardless of outcome, efficiency, or value delivered. Economically rational for the firm. For the client, it creates an incentive dynamic where the firm’s revenue rises when work takes longer — something best addressed through alternative arrangements.
This doesn’t mean firms deliberately work slowly. The pricing model just creates incentives that are neutral toward efficiency and innovation. Alternative Fee Arrangements (AFAs) reorient those incentives to reward both parties for efficiency.
### The AFA Spectrum
| Model |
Structure |
Risk Allocation |
Best For |
| **Hourly (baseline)** |
Rate × hours |
100% client |
Genuinely unpredictable work |
| **Capped fee** |
Hourly up to a maximum |
Shared — client capped, firm absorbs overrun |
Matters with moderate predictability |
| **Fixed fee** |
Set price for defined scope |
100% firm (for defined scope) |
Repeatable, well-scoped matters |
| **Success fee** |
Base + premium on outcome |
Shared — premium tied to result |
Litigation, recovery matters |
| **Portfolio pricing** |
Fixed annual fee for a basket of work |
Shared — volume and mix risk pooled |
High-volume, predictable work streams |
| **Subscription model** |
Monthly retainer for defined services |
Shared — client gets predictability, firm gets revenue stability |
Ongoing advisory relationships |
### Implementing AFAs: Practical Guidance
**Start with data.** AFAs require historical matter cost data to negotiate effectively. When you know your average employment dispute costs \$45K and takes 14 months, you can assess whether a firm’s \$50K fixed-fee proposal is competitive. Chapter 9’s e-billing data provides this foundation.
**Begin with high-volume, predictable work.** Fixed fees work best for matters with well-understood scope and effort profiles. NDAs, standard employment contracts, routine regulatory filings — these are ideal AFA candidates because the historical data provides a reliable cost baseline.
**Protect scope boundaries.** Every AFA must clearly define what’s in scope and what counts as a scope change. Clear definitions prevent ambiguity over whether the third round of negotiation was “included” or “extra.” Define scope in measurable terms: negotiation rounds, document page counts, court appearances.
**Share the data.** The most productive AFA relationships involve transparency from both sides. Share your matter volume forecasts with the firm. Ask them to share their cost assumptions. When both parties operate from the same data, pricing negotiations become collaborative rather than adversarial.
The goal of AFAs is to align incentives so both parties benefit from efficiency, not to extract the lowest possible price from law firms. A fair, well-scoped fixed fee produces a firm that invests in process improvement, because every hour they save drops to their margin. This incentive alignment is the competitive advantage AFAs create over hourly billing.
## Quarterly Business Reviews (QBRs)
### Managing by Performance, Not Pedigree
The QBR is the governance mechanism that turns a law firm relationship from a trust-based arrangement into a performance-managed engagement. QBRs let you manage vendors on demonstrable performance rather than historical inertia, keeping the engagement aligned with client objectives and business value.
### The QBR Scorecard
An effective QBR evaluates performance across five dimensions:
**1. Quality.** Matter outcomes, substantive accuracy, strategic value of advice. This is inherently subjective but can be partially quantified through internal client satisfaction surveys and outcome tracking.
**2. Efficiency.** Average cost per matter type, hours per matter versus budget, and trend over time. Is the firm getting more efficient with experience, or are costs creeping upward?
**3. Responsiveness.** Turnaround times on deliverables, adherence to agreed SLAs, and proactive communication. Measured through matter management system timestamps and internal stakeholder feedback.
**4. Billing Compliance.** Adherence to OCBG rules, accuracy of invoices, timeliness of WIP reporting, and e-billing adoption. Sourced directly from the e-billing platform.
**5. Innovation and Value-Add.** Is the firm proactively suggesting efficiency improvements, sharing market intelligence, providing training, or investing in technology that benefits the engagement? This identifies the strategic partners driving ongoing value creation.
### The QBR Conversation
The QBR should be a structured 60-90 minute meeting, held quarterly, with the firm’s relationship partner and the key matter leads. The agenda:
- **Scorecard review** (20 minutes): Present the data, discuss trends, and identify areas for improvement
- **Pipeline discussion** (15 minutes): Share upcoming work volume and any changes to the relationship scope
- **Innovation agenda** (15 minutes): Discuss process improvements, technology opportunities, and ways to deliver more value
- **Relationship health** (10 minutes): Address any interpersonal or communication issues directly
The most important part of the QBR is **documented follow-up**. Every action item is recorded, assigned an owner, given a deadline, and reviewed at the next QBR. This is what turns the conversation into operational momentum and measurable improvement.
### Panel Rationalisation
QBR data, accumulated over 12-18 months, provides the evidence base for panel rationalisation — the periodic exercise of reviewing the external provider roster and deciding which firms to retain, which to grow, and which to exit.
The data-driven panel review asks three questions for each firm:
- **Are they competitive on cost?** Compare their average cost per matter type against the panel median and against AFA benchmarks.
- **Are they delivering quality?** Review outcome data, satisfaction scores, and quality incident reports.
- **Are they a strategic fit?** Does the firm’s practice mix, geographic coverage, and innovation posture align with the organisation’s forward-looking legal needs?
Firms that score strongly on all three dimensions are candidates for more volume. Weaker performers go on improvement plans or a transition path. Evidence-based decisions provide clear rationale and enable transparent communication with stakeholders.
## In the Trenches
> *This example is fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
**The \$1.2M Panel Reset**
Priya Mehta, Head of Legal Ops at a mid-cap Australian mining company, inherited a panel of 23 law firms — a number that had grown organically over 15 years as successive GCs added their preferred firms without ever removing any. No firm had ever been subjected to a formal performance review. Fee arrangements were exclusively hourly, negotiated (or more accurately, accepted) on a firm-by-firm basis with no benchmarking.
Priya’s first action was to pull 24 months of e-billing data and build a spend heat map. The data revealed that 80% of external spend went to five firms, and the remaining 18 firms collectively handled 20% of the work — most of it in small, sporadic matters. Three of the top-five firms had never been asked to compete for the work they received.
She launched a formal RFP for the company’s four highest-spend practice areas. She required AFA proposals for all repeatable matter types. She evaluated responses using a weighted scorecard covering capability, pricing, technology, and diversity.
The result: the panel was consolidated from 23 firms to 9. Two incumbent firms lost significant allocations to competitors who offered fixed-fee arrangements at 25-30% below historical hourly costs. One new ALSP was added to handle high-volume contract review at 40% below the prior law firm cost.
Total annual savings in the first year: \$1.2M against a prior spend base of \$6.8M — a 17.6% reduction with no degradation in quality (as measured by matter outcome tracking and internal satisfaction surveys). The savings funded the CLM implementation that had been on the wish list for three years.
## Checklist
- **Count your law firms.** How many external firms received payment from your legal department in the last 12 months? If the number is 2–3x what you’d pick if starting from scratch, a panel rationalisation will unlock meaningful efficiency gains.
- **Identify your AFA candidates.** Pull your top 5 matter types by volume. For each, determine whether the scope is predictable enough to support a fixed or capped fee arrangement. High-volume, repeatable work with clear scope boundaries is ideal for cost-effective AFAs.
- **Schedule your first QBR.** Pick your highest-spend firm. Build a one-page scorecard covering the five dimensions above. Present it as a collaborative discussion, not an adversarial review — the goal is to build a performance-managed partnership, not to ambush a supplier.
- **Benchmark one rate.** Select the most common timekeeper role you engage externally (typically a senior associate). Compare the rate you are paying across your top three firms and against published market benchmarks for your jurisdiction and practice area. If you find a 20%+ variance, you have a negotiation opportunity.
## Suggested Reading
- [ACC Value Challenge (Value-Based Legal Services)](https://www.acc.com/valuechallenge)
- [ACC Legal Operations Resources](https://www.acc.com/topics/legal-operations)
- [CLOC Core 12 - Firm and Vendor Management](https://cloc.org/cloc-core-12/)
- [WorldCC Research and Benchmarking](https://www.worldcc.com/Resources/benchmarks-research)
- [Alternative Legal Service Providers 2023 Report (Thomson Reuters / Georgetown / Oxford)](https://www.legalcurrent.com/alternative-legal-services-providers-2023-report-reactions-from-the-legal-industry/)
Source: https://tilt.legal/docs/legal-ops-kit/managing-legal-spend
Markdown: https://tilt.legal/docs/legal-ops-kit/managing-legal-spend.md
Budgeting, forecasting, accruals, and e-billing — the financial disciplines that give the legal function control over its costs and the credibility to invest in transformation.
## The Gatekeeper Competency
Financial management is the gatekeeper competency of Legal Operations. Every other initiative — technology deployment, vendor rationalisation, AI adoption — requires budget. Budget requires trust. Trust requires demonstrating that the legal function can manage its own financial house with the same rigour the finance department expects from any other business unit.
In most enterprises, legal spend ranks among the top five overhead line items, often 0.5% to 1.5% of total revenue. For a \$500M revenue company, that’s \$2.5M to \$7.5M annually — a figure that attracts CFO scrutiny. The Legal Ops leader who can forecast that spend accurately, explain variances, and show cost optimisation over time earns credibility to propose strategic investments. Consistent financial accuracy builds the trust that gets technology roadmaps and new initiatives approved.
## Budgeting and Forecasting
### The Two-Bucket Model
Legal spend divides into two different buckets, each requiring its own forecasting methodology.
**Bucket 1: Internal Headcount.** This is the more predictable of the two — salaries, benefits, training, and allocated overhead for in-house legal staff. It scales stepwise (each new hire is a discrete cost event) and is forecast using standard HR planning models. The key variable is the **work-to-headcount ratio**: how many matters, contracts, or advisory requests can each FTE handle per period? As Legal Ops matures and automation absorbs routine work, this ratio should improve — meaning the function handles more work without proportionally increasing headcount.
**Bucket 2: External Counsel Spend.** This is where forecasting becomes difficult and where most legal budgets break down. External spend is driven by **matter volume** (how many new matters arise), **matter complexity** (how much work each matter requires), and **rate structures** (how much each unit of work costs). All three variables are partially unpredictable — a single unexpected litigation matter can consume 30% of the annual external budget.
### Building a Defensible Forecast
A defensible external spend forecast uses three inputs:
**Historical baseline:** Analyse 24-36 months of prior spend by matter type, firm, and practice area. Identify the recurring “base load” (the spend that occurs every year regardless of business conditions) and the variable “surge load” (the spend driven by unpredictable events like litigation or regulatory investigations).
**Business pipeline intelligence:** Engage with commercial and corporate development to understand the forward pipeline. If the company is planning three acquisitions in Q3, the M&A budget needs to reflect that. If a new product launch requires regulatory approval in four jurisdictions, the compliance budget must account for it. Legal can’t forecast in isolation from business activity.
**Contingency modelling:** Reserve 10–15% of the external spend budget for unforeseeable events. This isn’t padding — it’s actuarial discipline. Present it to the CFO as a risk reserve, not a slush fund, and report quarterly on utilisation. Consistently under-utilised? Reduce it. Consistently exhausted? The base forecast needs recalibration.
The single most effective thing a Legal Ops leader can do for financial credibility is deliver a quarterly variance report before finance asks for one. Show actual vs. forecast, explain the variances, project the year-end landing. CFOs don’t expect perfection — they expect visibility and accountability.
## Accruals Demystified
Accruals require close coordination between legal finance and corporate finance, where precision directly impacts financial reporting quality.
### The Accruals Process
Law firms bill in arrears, often 30–60 days after the work is performed. So at any given month-end, the legal department has consumed services not yet invoiced. Capturing **unbilled work in progress (WIP)** as an accrual ensures the financial statements accurately reflect the company’s legal expenses and liabilities.
For publicly listed companies, accurate accruals strengthen audit outcomes. For all companies, consistent accruals support clean quarterly P&L reporting and build finance’s confidence in legal’s financial discipline.
### The Solution: A Three-Step Accruals Process
**Step 1: Monthly WIP collection.** Establish a monthly cadence where every law firm on the panel submits a WIP report by a defined deadline (typically the 5th business day after month-end). The WIP report should state the total unbilled fees and disbursements for each active matter. Automate this collection through your e-billing platform if possible; otherwise, a standardised spreadsheet template and a firm deadline are the minimum.
**Step 2: Internal matter owner validation.** Each WIP report is reviewed by the internal lawyer responsible for that matter. They confirm the reasonableness of the reported WIP against their understanding of the work performed. This step catches errors, double-counting, and inflated estimates before they enter the financial system.
**Step 3: Finance submission.** The validated accruals are submitted to the finance department by a defined deadline (typically the 8th-10th business day) for inclusion in the monthly close. The submission should include a summary by practice area, a comparison to prior month, and commentary on any significant changes.
### Accruals and the Finance Relationship
Reliable accruals are the single most impactful thing Legal Ops can do to build a constructive relationship with Finance. Consistent, validated accruals delivered on time every month signal operational maturity and build trust for strategic initiatives.
## e-Billing Implementation
### The Case for Automation
Outside Counsel Billing Guidelines (OCBGs) are the contractual framework governing how law firms bill the organisation. Most enterprises have OCBGs that run to 20-40 pages, covering permissible rates, staffing requirements, task-based billing codes, pre-approval thresholds, and approved charge categories (economy airfare, proportionate research hours, business-appropriate meals).
The opportunity: OCBGs require consistent enforcement to deliver value. Manual invoice review — a lawyer or paralegal reading each invoice line by line — captures only a portion of the available optimisations. Automated e-billing enforcement captures significantly more. Industry benchmarks from leading e-billing providers ([Brightflag](https://brightflag.com/), [CounselLink](https://www.lexisnexis.com/en-us/products/counsellink.page), [BusyLamp/Onit](https://www.onit.com/)) and [ACC](https://www.acc.com/resource-library) research consistently show automated enforcement finds an additional 5–10% in savings over manual review alone.
### Implementation Priorities
An e-billing implementation is a data normalisation exercise as much as a technology deployment. The priorities, in sequence:
**1. Standardise billing codes.** Adopt the [UTBMS (Uniform Task-Based Management System)](https://utbms.com/) or [LEDES](https://ledes.org/) codes and require all panel firms to use them. Without standardised codes, spend analytics across firms is impossible.
**2. Digitise rate cards.** Load each firm’s approved rate card into the e-billing system. This enables automated rate compliance checks — flagging any invoice where a timekeeper bills at a rate above their approved level.
**3. Configure OCBG rules.** Translate your billing guidelines into automated validation rules. Common rules include: block charges (line items that bundle multiple tasks into a single entry), minimum time increments, prohibited expense categories, and staffing ratio requirements.
**4. Establish exception workflows.** Not every flagged item is a genuine violation — sometimes the context justifies the charge. Build an exception workflow that routes flagged items to the appropriate internal reviewer for disposition, with clear SLAs for resolution.
**5. Deploy analytics.** Once 6-12 months of clean, coded data flows through the system, activate spend analytics dashboards. The baseline views should cover: total spend by firm, practice area, and matter type; average cost per matter type; rate trends over time; and guideline compliance rates by firm.
| # |
Competency |
Core Question |
| 1 |
Business Intelligence & Analytics |
Can we measure what matters and predict what is coming? |
| 2 |
Financial Management |
Do we control spend, forecast accurately, and demonstrate ROI? |
| 3 |
Firm & Vendor Management |
Are external providers managed by performance, not relationship? |
| 4 |
Information Governance & Records Management |
Is our data classified, retained, and retrievable? |
| 5 |
Knowledge Management |
Can institutional knowledge survive personnel changes? |
| 6 |
Organisation Optimisation & Health |
Is the team structured and skilled for the work it needs to do? |
| 7 |
Practice Operations |
Are day-to-day workflows efficient and consistent? |
| 8 |
Project / Program Management |
Do we execute initiatives on time, on budget, and on scope? |
| 9 |
Service Delivery Models |
Are we routing work to the right provider at the right cost? |
| 10 |
Strategic Planning |
Does the legal function have a multi-year roadmap aligned to business strategy? |
| 11 |
Technology |
Is our tech stack integrated, adopted, and delivering measurable value? |
| 12 |
Training & Development |
Are our people continuously developing relevant skills? |
### The Compounding Value of Data
The most underappreciated aspect of the CLOC Core 12 is the **data thread** that runs through every competency. Financial Management produces spend data. Firm & Vendor Management produces performance data. Practice Operations produces workflow and cycle-time data. Technology produces adoption and utilisation data.
Normalised and connected, these data streams create a **compounding intelligence layer** that enables predictive analytics, automated triage, and evidence-based strategic planning. They let you answer cross-domain questions like: “Which firms deliver the fastest turnaround on our most common matter types at the lowest cost?”
The CLOC Core 12 is best understood as a system map, not a checklist. Technology investments deliver maximum value when paired with Information Governance maturity — this ensures your team can locate and leverage the data your tools produce. Analytics initiatives generate reliable, actionable insights when grounded in Financial Management discipline and clean spend data. Always assess interdependencies before sequencing investments.
### Using the CLOC Framework in Practice
The CLOC Core 12 excels at **macro-level alignment** — ensuring your Legal Ops strategy covers all the necessary bases and identifying which competencies are underdeveloped relative to your organisation’s needs.
A practical deployment approach:
**Step 1: Self-Assessment.** Rate each competency on a 1-5 scale (1 = non-existent, 5 = optimised and data-driven). Be honest. Most legal departments in 2026 average 2.1-2.8 across the twelve areas.
**Step 2: Prioritisation.** Identify the three competencies where improvement would generate the greatest impact on your organisation’s specific pain points. A company scaling rapidly through M&A will prioritise differently than one facing a regulatory compliance deadline.
**Step 3: Interdependency Mapping.** For each priority competency, identify which other competencies must advance in parallel. Technology investments require Training & Development. Analytics requires Information Governance. Vendor Management requires Financial Management data.
**Step 4: Roadmap Construction.** Build a 12-18 month roadmap that sequences investments across the priority competencies and their dependencies. Present this to leadership as a phased business case, not a wish list. The maturity roadmap methodology — sequencing investments across the twelve competencies — is covered in depth in Chapter 4: Building a Legal Ops Strategy.
## The ACC Maturity Model 2.0: The Micro-Diagnostic Tool
The Association of Corporate Counsel (ACC) Legal Operations Maturity Model takes a different approach. Where CLOC provides a broad competency map, the ACC model offers **deep functional benchmarking** within specific operational domains. The 2.0 iteration, updated to reflect the AI era, adds explicit dimensions for innovation management and technology-enabled service delivery.
### The Five Maturity Levels
The ACC model defines five maturity levels that apply across each functional domain:
| Domain |
Level 2 (Basic) |
Level 4 (Advanced) |
| **Financial Management** |
Invoices are tracked manually; spend reports are built quarterly with incomplete data. |
Spend is tracked in real time by matter type, counsel, and vendor; budget forecasting uses predictive models. |
| **Contract Management** |
Contracts are stored in shared drives; review cycles are ad hoc and depend on individuals knowing when review is needed. |
Contracts are centralised with metadata tags; lifecycle workflows are automated; renewal dates trigger alerts automatically. |
| **Vendor/Firm Management** |
Firms are selected on relationship; performance is not tracked systematically. |
Panel is actively managed by performance metrics; quarterly business reviews are data-driven and linked to spend. |
| **Knowledge Management** |
Expertise lives in individuals’ inboxes; playbooks are outdated or non-existent. |
A searchable knowledge base covers recurring matter types; playbooks are updated monthly and consumed via self-serve portal. |
| **Practice Operations** |
Process for high-risk matters is documented; low-risk matters follow no standard workflow. |
All matter types have documented, standardised workflows; cycle times are measured and continuously optimised. |
| **Technology** |
Tools are deployed but adoption is voluntary; teams often revert to legacy systems. |
Multiple systems are integrated; adoption is 80%+; the tech stack generates data that informs decisions. |
| **Talent/Capability** |
Team members learn on the job; no formal training or succession planning exists. |
Capability framework guides hiring and development; team members rotate through multiple functions; skill gaps are identified and addressed proactively. |
### Innovation Management: The 2.0 Addition
The most significant evolution in the ACC Maturity Model 2.0 is the explicit inclusion of **Innovation Management** as a maturity dimension. This reflects the recognition that in 2026, a legal department that is “managed” (Level 3) across traditional operational domains but “ad hoc” (Level 1) on innovation is strategically exposed.
Innovation Management maturity encompasses:
- **Horizon scanning:** Systematically monitoring emerging legal technologies, regulatory changes, and service delivery models
- **Experimentation capability:** The ability to run controlled pilots of new tools or processes without disrupting BAU operations
- **Adoption discipline:** Structured rollout processes that move successful pilots to full deployment with change management support
- **Measurement rigour:** Quantifying the impact of innovations against pre-defined success criteria, and killing initiatives that do not deliver
**Scoring Innovation Management:** To assess your maturity in this dimension, ask three practical questions: (1) Do we systematically monitor the legal tech landscape — are we subscribed to industry briefings, do we track competitor moves, do we attend legal tech conferences? (2) Can we run a pilot without disrupting BAU operations — do we have sandboxed environments, allocated budget, and a lightweight approval process? (3) Have we killed any initiatives that failed to deliver — are we willing to write off failed bets, or do we keep funding tools that don’t land? Organisations with honest “yes” answers to all three are typically at Level 3 or above.
### Running an ACC Assessment
The ACC maturity model delivers maximum value when the assessment itself becomes a diagnostic and alignment opportunity for the team. A well-run assessment surfaces not just maturity scores but the underlying gaps holding progress back.
**Step 1: Assemble the right group.** Select 3–5 people who actually do the operational work — not the General Counsel or executives who are removed from day-to-day execution. A good assessment team includes the Finance Manager (who understands spend and forecasting), the Contract Manager or Senior Counsel (who manages CLM and vendor relationships), the Practice Lead for a major practice area, and the Operations Coordinator or person managing internal processes. These are the people who know exactly where the friction points are.
**Step 2: Score each domain independently first, then compare.** Have each team member score all seven domains independently, using the maturity level definitions as a guide. Do not discuss scores until everyone has submitted. Then walk through each domain and discuss the disagreements. If one person scored Contract Management at Level 3 and another at Level 2, that disagreement is valuable — it exposes a gap between perceived maturity and actual execution.
**Step 3: Identify the specific sub-process holding each domain back.** Do not stop at “e-billing is Level 2.” Ask: why is e-billing Level 2? Is it because billing guidelines are not documented? Because they are documented but not enforced? Because matter coders are not applying them consistently? Because the system does not validate invoice data before submission? Pinpoint the specific sub-process that is preventing progression to Level 3.
**Step 4: Rank the gaps by business impact.** You have identified 10 domains at Level 2 or below. You cannot fix all of them simultaneously. For each gap, ask: if we fixed this, what commercial outcome improves? Contract cycle time reduction? Spend visibility? Risk mitigation? Rank the gaps by the size of the commercial impact, not by ease of fix. A hard problem that generates £2m in value ranks above an easy problem that saves £100k.
**Step 5: Translate top gaps into specific initiatives for the next 90 days.** Take the top two or three gaps and translate each into a concrete initiative with a 90-day horizon. “Improve Financial Management” becomes “Deploy time-tracking tool and train all lawyers on billing coding by end of Q2.” “Improve Contract Management” becomes “Centralise all active contracts into CLM by end of Q2 and document contract review playbook.” Specificity drives execution.
### Deep Functional Benchmarking
The ACC model’s strength is granularity. CLOC provides a broad competency assessment; the ACC model goes deeper to reveal specific maturity by function. A department that scores 3.2 overall has learned almost nothing — that average masks critical gaps that remain invisible. A department that knows its accruals process is Level 2, its e-billing enforcement is Level 3, and its spend analytics is Level 1 has a clear roadmap.
The ACC model works best when it surfaces actionable specificity rather than aggregate scores. Use the assessment to build a functional maturity map — a simple table that shows each domain and its maturity level. Post it in your department. Refer to it in quarterly planning. Use it to explain to finance, procurement, and the business why certain initiatives are sequenced the way they are. “We are deferring the advanced analytics project because spend analytics is Level 1 — we need to fix data quality first. That’s a three-month initiative, and then we can run pilots on the analytics platform.”
## Comparative Matrix: CLOC vs. ACC
The two frameworks are complementary and gain power when used together. Deploy them in tandem to get both strategic clarity and operational precision.
| Dimension |
CLOC Core 12 |
ACC Maturity Model 2.0 |
| **Best for** |
Macro-alignment and strategy |
Micro-diagnostics and benchmarking |
| **Scope** |
Broad — 12 competency areas |
Deep — granular functional assessment |
| **Output** |
Competency map and investment roadmap |
Maturity scores by function and sub-function |
| **Audience** |
C-Suite and board (strategic narrative) |
Legal Ops team and direct reports (execution plan) |
| **Frequency** |
Annual strategic review |
Quarterly or semi-annual operational review |
| **Data requirement** |
Moderate — qualitative assessment sufficient |
High — requires operational data for accurate scoring |
| **AI/Innovation coverage** |
Embedded across competencies (implicit) |
Explicit Innovation Management dimension |
### The Integration Playbook
**Use CLOC for strategic planning conversations.** When presenting to the CEO or board, the CLOC Core 12 provides a comprehensive, easy-to-communicate picture of where the legal function stands and where it needs to go. A radar chart showing maturity across twelve competencies is immediately legible to non-legal executives.
**Use ACC for operational execution.** When building quarterly improvement plans with your Legal Ops team, the ACC model provides the granularity needed to assign specific initiatives to specific gaps. “Move accruals from Level 2 to Level 3 by Q3” is an actionable objective. “Improve Financial Management” is not.
**Synchronise annually.** Once per year, run both assessments. Use the CLOC assessment to validate strategic direction. Use the ACC assessment to calibrate execution priorities. Where they diverge — for example, CLOC suggests Technology is a strength but ACC reveals that adoption rates are at Level 2 — the discrepancy surfaces issues that neither framework alone would catch.
Framework adoption works best when assessment is tightly coupled to action. Assess rigorously, act decisively on findings, then reassess at defined intervals. Keep cycles efficient so team effort translates directly into improvement initiatives and measurable outcomes.
## In the Trenches
> *This example is fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
**The Framework That Exposed the Gap**
Sarah Okonkwo, Head of Legal Ops at a European pharmaceutical company, believed her department’s technology maturity was strong. They had a CLM platform, an e-billing system, and a recently deployed AI document review tool. When she ran a CLOC self-assessment, Technology scored a 4 out of 5.
Then she ran the ACC deep-dive.
The ACC assessment revealed that while the tools were deployed, **adoption** was at Level 2. The CLM was used by 40% of the legal team, with the rest preferring email workflows. The e-billing system held 18 months of untapped data — information that could drive spend optimisation if actively analysed and owned. The AI review tool was underutilised because the team lacked training on where and how to use it.
Sarah’s CLOC score of 4 had masked a critical reality: the technology existed but wasn’t delivering proportional value. She restructured her roadmap to prioritise Training & Development (CLOC competency 12) and change management alongside technology. Within nine months, CLM adoption reached 85%, the e-billing data produced quarterly spend analytics reports, and the AI review tool became integrated into standard due diligence workflows.
The lesson: the ACC model revealed adoption gaps the CLOC strategic assessment had missed — a clear case for combining macro-level strategy with micro-level operational diagnostics.
## Checklist
- **Run a 60-minute CLOC self-assessment with your legal leadership team.** Score each of the 12 competencies on a 1-5 scale. Do this collaboratively — disagreements about scores are more valuable than the scores themselves, because they reveal where perceptions diverge from reality.
- **Select one functional area for an ACC deep-dive.** Choose the area that scored lowest on CLOC, or the area most critical to your current strategic priorities. Use the ACC maturity levels to diagnose specific sub-function gaps.
- **Identify your “Phase 1 blockers.”** Which foundational capabilities (data, documentation, process consistency) are currently absent and blocking progress on higher-value initiatives? These blockers are your immediate priority, regardless of what the strategic roadmap says.
- **Document your interdependencies.** For each planned initiative in the next 6 months, list the one or two capabilities it depends on. If those capabilities are not yet in place, either sequence the initiative later or add the dependency to your current sprint.
## Suggested Reading
- [CLOC Core 12 Competency Framework](https://cloc.org/cloc-core-12/)
- [CLOC Core 12 Maturity Assessment Playbook](https://cloc.org/core-12-maturity-assessment-playbook/)
- [ACC Maturity Model](https://www.acc.com/maturity)
- [ACC Legal Operations Maturity Model 2.0](https://www.acc.com/resource-library/acc-legal-operations-maturity-model-20)
- [ACC Legal Operations Resources](https://www.acc.com/topics/legal-operations)
Source: https://tilt.legal/docs/legal-ops-kit/measuring-what-matters-kpis-data
Markdown: https://tilt.legal/docs/legal-ops-kit/measuring-what-matters-kpis-data.md
The metrics that demonstrate legal’s value to the business — velocity, leakage, risk, and the Cost of Inaction framework for making the investment case to a sceptical CFO.
---
## The Measurement Imperative
A legal function that measures its performance can defend its budget, justify investments, and demonstrate its value. In 2026 the bar has risen: the C-Suite expects legal to report on its operations with the same analytical rigour as sales, marketing, and finance. Clear metrics drive budget decisions.
Choosing the right metrics is critical. The most effective legal departments use a disciplined hierarchy: a small set of **Strategic KPIs** that communicate enterprise value, supported by **Operational Metrics** across nine domains that drive day-to-day performance management. This layered approach converts data into actionable insight.
## The Hierarchy of Metrics: Strategy and Operations
The measurement architecture sits in two distinct layers:
- **The C-Suite layer** (Strategic KPIs): A small, focused set of metrics that answer the boardroom question: What did the legal function’s performance mean for the business?
- **The Operations layer** (Operational Metrics): Nine domains of granular measurement that drive process improvement, resource allocation, and tactical decision-making.
The Strategic KPIs roll up from the Operations layer—but they do not replace it. Both layers are essential.
## Strategic KPIs: The C-Suite Layer
### Beyond Vanity: The Three Strategic KPI Categories
Strategic KPIs answer the question that the C-Suite actually cares about: what did the legal function’s performance mean for the business? Unlike activity metrics (total contracts processed, total matters opened, number of training sessions delivered), Strategic KPIs connect operational effort directly to business outcomes.
### Category 1: Velocity KPIs
Velocity measures how fast the legal function processes work that sits in the enterprise’s critical path. The primary velocity metrics:
**Average Contract Cycle Time.** The elapsed calendar days from first draft to full execution. Segment by contract type (NDA, MSA, SOW, etc.) to avoid the distortion of averaging simple and complex agreements together. Track the trend quarterly: a declining cycle time demonstrates operational improvement; a rising one signals emerging bottlenecks.
**Legal Request Turnaround Time.** The elapsed time from when a business stakeholder submits a request to when they receive a substantive response. This is the metric that most directly shapes the business’s perception of legal’s responsiveness.
**Time-to-Approval.** For matters requiring internal legal approval (new vendor onboarding, policy exceptions, deal approvals), the elapsed time from request to decision. Faster approvals accelerate business momentum across the entire organisation.
### Category 2: Leakage KPIs
Leakage measures unrealised value — commercial outcomes the enterprise could capture with better legal operations processes and systems. Making leakage visible through measurement is the first step toward capturing it.
**Contract Value Leakage.** Revenue available through proactive contract management: timely renewals, reviewed auto-renewal clauses, and enforced pricing escalations. A CLM with obligation management can track this directly; as a starting point, a manual audit of the last 12 months’ expirations provides an initial estimate of the opportunity.
**Billing Leakage.** The additional value recoverable through automated e-billing enforcement versus manual review. E-billing providers and the [ACC](https://www.acc.com/resource-library) consistently report 5–10% additional recovery when billing guidelines are enforced automatically — a direct and measurable return on e-billing investment.
**Compliance Leakage.** The estimated cost of regulatory exposure that proactive compliance monitoring could reduce — penalties, remediation efforts, and business disruption. This metric is retrospective and imprecise, but even a rough estimate demonstrates the value of early intervention to the CFO.
### Category 3: Risk KPIs
Risk metrics quantify the legal function’s effectiveness as a risk management operation. They are inherently forward-looking and require judgment, but they can be structured to provide meaningful signals.
**Open Risk Exposure.** The total estimated financial exposure of all open litigation, regulatory matters, and material contract disputes. Updated quarterly and reported alongside the movement (new matters opened, matters closed, exposure changes).
**Compliance Health Score.** A composite indicator measuring the organisation’s adherence to regulatory obligations, policy review deadlines, and training completion rates. Expressed as a percentage or a traffic-light rating across the key compliance domains.
**Third-Party Risk Score.** A measure of the legal risk associated with the organisation’s vendor and partner portfolio — encompassing contract compliance, data protection obligations, and regulatory alignment.
The power of Strategic KPIs lies in connecting legal performance to business outcomes non-legal executives already understand. When you report that contract cycle time decreased by 8 days this quarter — contributing an estimated \$3.2M in earlier revenue recognition — you’re speaking the CFO’s language. When you report that you processed 847 contracts this quarter, you’re speaking to yourself.
## Operational Metrics: Nine Domains of Performance
The operational layer provides the granularity needed to diagnose bottlenecks, allocate resources, and drive improvement. These nine domains map the full lifecycle and scope of the legal function’s work.
### Domain 1: Business Enablement
The legal function’s role in accelerating commercial outcomes. These metrics measure the speed at which legal removes friction from critical business processes.
| KPI |
Description |
Measurement |
Implication |
| Average contract completion time |
Calendar days from first draft to full execution |
Track by contract type to avoid distortion of simple and complex agreements |
Rising times indicate bottlenecks; declining times indicate operational improvement |
| M&A completion time |
Elapsed time from LOI to closing across legal’s component |
Track by transaction size and complexity |
Directly affects deal velocity and revenue recognition timing |
| Major projects completed |
Count of significant strategic deliverables (e.g., corporate restructure, major policy implementation) |
Whole number per measurement period |
Indicates legal’s capacity for strategic versus operational work |
### Domain 2: Contract Quantity
Volume metrics that establish the scale and reach of the legal function’s work. These should be tracked consistently to establish trends and identify shifts in demand.
| KPI |
Description |
Measurement |
Implication |
| Total contracts processed |
How many contracts the legal department has completed over the measurement period |
Can be leading or lagging indicator; e.g., 500 contracts per quarter |
Total contract / business value enabled by legal |
| Contracts by type |
Volume categorised by contract type |
Commercial, NDA, vendor, complex, simple, by value, or whatever different types your department works on |
Indicates which contract types will benefit most from knowledge management, CLM, automation, process improvement |
| Usage of standard forms and templates |
How many times proforma documents were accessed or adopted by the business |
Can be set as a percentage against the total number of contracts figure |
Quality and accessibility of knowledge and content produced by legal |
### Domain 3: Contract Quality
Risk and governance metrics that measure the quality of legal work and the effectiveness of risk controls embedded in contracts.
| KPI |
Description |
Measurement |
Implication |
| Contract risk score |
How much risk is embedded within executed contracts |
Set risk criteria and score contracts on low / medium / high or a grade from A–D |
Indicates whether standard form contracts need improvement; what factors are contributing to excessive risk |
| Vendor / external contract adoption |
Number of times external (third-party) contracts were adopted over internal templates |
Percentage of total contracts |
Can indicate that internal documents are outdated or not easily accessible |
| Number of negotiation rounds |
How much back-and-forth effort is spent negotiating contract terms |
Time elapsed or whole number of redline cycles |
Optimisation opportunities for contract language, proformas, or negotiation process |
### Domain 4: Legal Spend
Financial accountability metrics that track spending efficiency across the legal function.
| KPI |
Description |
Measurement |
Implication |
| Budget versus actual spend |
Total legal spend against authorised budget |
YTD / Monthly spend vs. YTD / Monthly budget |
Shows how the legal department is managing financial resources |
| Spend by matter type |
Tracking spend across categories (litigation, contracts, corporate secretary, IP, marketing, etc.) |
YTD / Monthly spend by category vs. budget |
Shows if particular matter types are costing more than others; informs alternative service delivery models |
| Legal spend by business unit |
Tracking spend allocation across business units or staff groups |
YTD / Monthly spend by unit vs. budget |
Shows if particular business units are consuming disproportionate resources; informs resource allocation decisions |
### Domain 5: IP / Intangible Assets
Metrics that measure the legal function’s contribution to protecting and building the organisation’s asset base.
| KPI |
Description |
Measurement |
Implication |
| Number of patents, copyrights, trademarks |
Count of IP registrations by category applied for and granted per year |
Whole number for each IP category |
How much of the organisation’s assets are being secured by legal |
| Value of IP |
Financial valuation of registered IP |
Often found on the balance sheet as “intangible assets” |
Helps C-suite understand legal’s contribution to the organisation’s asset pool and balance sheet value |
### Domain 6: Litigation Management
Metrics that measure the organisation’s litigation profile and the legal function’s effectiveness in managing disputes and regulatory risk.
| KPI |
Description |
Measurement |
Implication |
| Number of significant / risky litigation matters |
Count of open matters with material financial exposure |
Number of matters above a threshold (e.g., \$100,000 USD exposure) |
A rough indication of the organisation’s potential liability by business unit. Compare over time to understand trend. |
| Average cost / duration per litigation |
Mean cost and timeline for matters, both as defendant and plaintiff |
Cost per matter / duration per matter |
Informs resource allocation and external counsel strategy |
| Litigation outcome rate |
Percentage of matters settled favourably versus litigated to judgment |
Percentage settled / won; net monetary amount paid or received |
Indicates effectiveness of early case assessment and settlement strategy |
| Fines and regulatory penalties |
Total penalties and fines paid; categorised by type and cause |
Dollar amount / type / frequency |
Trailing indicator of compliance gaps or risk management failures |
### Domain 7: Compliance
Metrics that measure the organisation’s regulatory and policy adherence (typically tracked by legal, though ownership may vary).
| KPI |
Description |
Measurement |
Implication |
| Mandatory training completion rate |
Percentage of required personnel completing mandatory compliance training |
Percentage of completion |
Indicates compliance control effectiveness; rising rates reduce regulatory risk |
| Reporting channels for compliance matters |
Source breakdown of compliance reports and concerns |
Breakdown of reports from hotline, email, other departments |
Indicates whether reporting mechanisms are effective and accessible |
| Potential fees / consequences from non-compliance |
Estimated financial exposure from identified compliance gaps |
Total dollar amount; dollar amount × probability of non-compliance event |
Helps quantify the urgency of particular compliance investments |
| Open versus closed compliance matters |
Count of open, pending, and resolved compliance issues |
Count by status |
Indicates whether the function is keeping pace with emerging issues |
### Domain 8: Legal Operations
Metrics that measure the health and maturity of the legal function itself — its people, projects, and strategic initiatives.
| KPI |
Description |
Measurement |
Implication |
| Progress of strategic projects |
Tracking delivery against milestones for technology implementations, cost savings initiatives, structural changes |
Relevant project KPI (on-time delivery, budget variance, scope adherence) |
Determines whether the team is executing on its strategic roadmap |
| Employee engagement score |
Measure of legal team member satisfaction, engagement, and commitment |
Annual or bi-annual engagement survey; career development conversations |
Assesses team morale, retention risk, buy-in to vision, and cultural health |
### Domain 9: Business Alignment / Client Satisfaction
Metrics that measure how well the legal function is meeting the needs and expectations of its internal stakeholders.
| KPI |
Description |
Measurement |
Implication |
| Internal customer satisfaction |
Satisfaction of business stakeholders who request legal support |
Periodic survey or real-time feedback after each significant interaction |
Indicates which business units are satisfied; reveals service gaps and relationship tensions |
| Turnaround time by matter type |
Elapsed time from request receipt to substantive response, segmented by request category |
Calculate time between receiving and responding to instructions; where legal is in the product delivery path, measure time delay caused by legal |
Areas with higher turnaround times present opportunities for investigation and optimisation through skills development, resource reallocation, process redesign, automation |
---
## The Cost of Inaction (COI) Framework
### Selling Innovation to the Sceptical CFO
Every Legal Ops investment proposal faces the same implicit question from the CFO: “What happens if we do nothing?” If the answer is “things stay roughly the same,” the investment is deprioritised. The **Cost of Inaction** framework reframes this question by quantifying the accumulating cost of maintaining the status quo.
### Building the COI Case
The COI is calculated across three dimensions:
**Direct cost accumulation.** The ongoing spend on manual processes, redundant work, and inefficient vendor arrangements that would be reduced or eliminated by the proposed investment. A manual contract review process that consumes 2,000 lawyer hours per year at a blended cost of \$250/hour represents \$500K in annual direct cost. If a CLM and playbook deployment could reduce this to 800 hours, the COI of not investing is \$300K per year — and it compounds as matter volume grows.
**Opportunity cost.** The value of strategic work that the legal team could perform if operational capacity were freed up. If the GC spends 15 hours per week on contract approvals instead of M&A advisory, the opportunity cost is the value of the M&A work that could be brought in-house — work currently outsourced to external counsel at \$800/hour.
**Risk exposure cost.** The expected cost of risk events that are more likely to occur without the proposed investment. A compliance monitoring system that costs \$150K per year has a COI of the probability-weighted regulatory penalty it would have prevented. If the expected penalty is \$2M and the probability reduction from the tool is estimated at 15%, the risk COI is \$300K per year.
### Presenting the COI
| Tier |
Complexity |
Provider |
Typical Cost |
Examples |
| **Tier 1: Automate** |
Low complexity, high volume, rules-based |
Technology + legal engineer oversight |
Near-zero marginal cost |
NDA generation, standard amendment processing, compliance certificate production |
| **Tier 2: Outsource** |
Moderate complexity, process-driven, benefits from scale |
ALSP + technology augmentation |
\$150–\$300/hr blended |
Due diligence document review, contract migration, regulatory filing preparation, bulk contract analysis |
| **Tier 3: In-House / External Counsel** |
High complexity, high judgment, strategic or bespoke |
In-house team or specialist law firm |
\$400–\$1,500/hr |
M&A advisory, bet-the-company litigation, novel regulatory interpretation, board governance |
### Applying the Matrix
The routing decision is driven by three variables:
**Volume.** High-volume work types are Tier 1 or Tier 2 candidates by definition. Processing 500 NDAs per year through Tier 3 (lawyer review) is an economic absurdity when a playbook-driven template with AI-assisted triage can handle 80% of them at Tier 1.
**Complexity.** Work that requires significant legal judgment, contextual understanding, or creative problem-solving belongs in Tier 3. The test: if a competent lawyer would need to think carefully (rather than apply a known rule or standard), it’s Tier 3 work.
**Risk.** Some low-complexity work carries high consequences if done incorrectly. A routine corporate filing that is missed can trigger regulatory penalties. A standard data processing addendum that contains an error can create GDPR exposure. Risk modulates the tier assignment — high-risk work may require Tier 3 oversight even if the underlying task is Tier 1 in complexity.
### The Triage Decision Flow
For each incoming matter or request:
1. **Classify the work type** against the Triage Matrix categories
2. **Assess complexity** using the judgment test described above
3. **Evaluate risk** — both the probability of error and the consequence of error
4. **Route accordingly** — with clear escalation paths for edge cases
5. **Track and measure** — log the routing decision and, post-completion, assess whether the routing was appropriate
Over time, the triage data itself becomes valuable. Patterns emerge: certain work types initially routed to Tier 3 consistently prove to be Tier 2 candidates. Certain ALSP providers demonstrate quality sufficient to absorb more complex work. The triage system becomes a learning system.
The Triage Matrix is the operational expression of the unbundling strategy described in Chapter 2. It translates the strategic concept of matching work to the optimal provider into a day-to-day routing mechanism that every member of the legal team can apply. Without the Matrix, unbundling is a theory. With it, unbundling is a process.
## Achieving Process-Fit
### The Critical Success Factor
Organisations that invest in process-fit — aligning technology to their actual workflows before deployment — consistently outperform those that skip this step. Research from the [Thomson Reuters Institute](https://www.thomsonreuters.com/en/institute.html) (including their *State of the Legal Market* and *Legal Department Operations Index* series) and [Gartner’s legal technology predictions](https://www.gartner.com/en/legal-compliance) confirm that **process-fit** is the single biggest predictor of whether a legal technology investment delivers.
Process-fit means the technology aligns with how work actually flows through the organisation. A CLM platform should support the approval patterns that exist — whether linear and sequential, or parallel with multiple simultaneous reviewers. An e-billing system succeeds when onboarding is seamless enough that firms prefer the portal to workarounds like paper submission.
### The Five Process-Fit Considerations
**1. Process-technology alignment.** The tool should be designed for a process that matches the organisation’s actual workflow. The most common opportunity: ensuring the contracting process is mapped, standardised, and agreed upon *before* selecting an enterprise CLM. When the technology mirrors the real workflow, adoption follows naturally.
**2. Data quality failure.** The tool requires clean, structured data to function effectively. An AI-powered contract analytics tool fed inconsistently formatted PDFs with no metadata produces unreliable results, eroding user confidence quickly.
**3. Integration failure.** The tool operates in isolation rather than connecting to the systems where users actually work. A matter management system without integration to Outlook and the document management system requires lawyers to work in a separate environment, reducing adoption and productivity.
**4. Adoption failure.** Users don’t adopt the tool despite its technical capability. The cause is usually insufficient WIIFM communication, training, or ongoing reinforcement — the change management factors described in Chapter 5. Successful adoption requires consistent engagement and demonstrated value.
**5. Scope creep failure.** The implementation begins with a focused scope and expands continuously — “since we’re implementing CLM, let’s also add obligation management, AI review, e-signature, and a vendor portal.” Each addition increases complexity and extends timelines, delaying the value that comes from completing the initial scope.
### The Prevention Protocol
**Map the process first.** Complete the process mapping exercise (Chapter 10) for every workflow the technology will touch before signing a vendor contract. The process map becomes the specification for the technology, not the other way around.
**Start with clean data.** Invest in data normalisation before deploying any analytics or AI capability. This is unglamorous work — it involves cleaning spreadsheets, standardising naming conventions, and deduplicating records. It is also the single most important prerequisite for technology success.
**Demand integration.** Evaluate every tool on its integration capabilities as heavily as its features. A tool with 80% of the features you want but native integration with your existing stack will outperform a tool with 100% of the features that operates as an island.
**Phase ruthlessly.** Define the minimum viable deployment: the smallest scope that delivers measurable value. Deploy it. Stabilise it. Prove value. Then — and only then — expand. Phasing creates early wins and builds momentum, accelerating long-term delivery compared to attempting everything at once.
The integration architecture that connects your service delivery providers and tools is covered in Chapter 15: Legal Technology — Stack, CLM & AI.
## In the Trenches
> *This example is fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
**The Integration That Saved the CLM**
A multinational insurance company had invested \$400K in a tier-one CLM platform. Eighteen months after go-live, the underwriting team — the primary user group — preferred their previous process of emailing Word documents to legal, finding the CLM interface less efficient for their workflow.
Rather than replace the CLM, the Head of Legal Ops deployed a middleware layer using Microsoft Power Automate and a custom Teams bot. Underwriters could now initiate a contract request from a Teams message, answer four triage questions, and receive a first draft in their Teams channel within minutes. The middleware handled all CLM interactions — template selection, data population, approval routing — without underwriters ever seeing the CLM interface.
CLM-processed contract volume tripled in three months. Underwriters were using the CLM through their familiar Teams interface; the middleware handled the technical complexity behind the scenes. The same underlying platform now delivered value because the UX aligned with where users actually worked.
Total cost of the middleware deployment: roughly \$35K in Power Automate licensing and three weeks of configuration. The CLM’s ROI turned positive within the quarter, recovering the initial investment and generating ongoing value.
## Checklist
- **Map your current triage practice.** For the last 20 matters that entered the legal department, reconstruct how each was allocated. How many were routed to the optimal tier? How many involved senior lawyers performing Tier 1 or Tier 2 work? The gap between actual and optimal routing is your triage improvement opportunity.
- **Audit your tech stack integration.** List every legal technology tool in use. For each pair of tools, note whether they are integrated (data flows automatically), manually bridged (someone copies data between them), or siloed (no connection). Count the manual bridges — each one is a candidate for middleware automation.
- **Identify your top process-fit risk.** For any technology currently in implementation or planned, answer: has the underlying process been mapped? Is the data clean? Are integrations with adjacent systems defined? If any answer is “no,” pause the implementation and address the gap before proceeding.
- **Explore one middleware option.** If your stack has more than three tools, investigate one middleware platform (Power Automate, Zapier, or a legal-specific option) and identify one data flow that could be automated this quarter.
## Suggested Reading
- [CLOC Core 12 - Service Delivery Models](https://cloc.org/cloc-core-12/)
- [ACC Legal Operations Resources](https://www.acc.com/topics/legal-operations)
- [Alternative Legal Service Providers 2023 Report (Thomson Reuters / Georgetown / Oxford)](https://www.legalcurrent.com/alternative-legal-services-providers-2023-report-reactions-from-the-legal-industry/)
- [WorldCC Research and Benchmarking](https://www.worldcc.com/Resources/benchmarks-research)
- [Corporate Value Associates - Make-or-Buy Framework (Service Delivery)](https://www.corporatevalue.net/en/insights/make-or-buy-how-to-get-it-right)
Source: https://tilt.legal/docs/legal-ops-kit/structuring-your-legal-team
Markdown: https://tilt.legal/docs/legal-ops-kit/structuring-your-legal-team.md
How to design, staff, and evolve your legal team structure — span of control, role design, behavioural change, and building a culture where people embrace rather than resist operational change.
---
## Designing the Legal Operating Model
The structure of a legal function isn’t fixed. For most of the 20th century, law firms and in-house teams ran on a standardised model: hierarchical, closed, internally staffed, built around traditional lawyer roles. That model still exists — but it’s increasingly one option among many.
### From Hierarchy to Hybrid
The evolution of the legal operating model reflects three parallel shifts:
**The technology shift.** Document automation, contract lifecycle management, legal research platforms, and AI-assisted analysis have automated work that previously required lawyer hours. This technology can be built in-house, licenced from specialised vendors, or accessed through managed services providers.
**The demand shift.** In-house legal functions now handle vastly more transactional volume — data requests, privacy reviews, contract reviews — than they did a decade ago, driven by regulatory intensity and digital business velocity. At the same time, strategic legal work has become more sophisticated, requiring deeper subject matter expertise. Organisations struggle to build a single team that’s both responsive to high-volume routine work and excellent at high-value strategic work.
**The talent shift.** The supply of traditional lawyers willing to work in traditional legal roles is constrained in many markets. At the same time, new roles have emerged — legal operations, legal engineering, legal data science — for professionals who bring engineering, data, or operations skills to legal problems. Competition for these hybrid skills is intense.
The response has been the rise of the **hybrid operating model**: a combination of in-house lawyers, legal operations specialists, managed service providers, alternative legal service providers (ALSPs), and technology platforms, each performing work that matches their cost structure and capability profile.
### Role Architecture for the Hybrid Model
A modern legal function typically includes:
**General Counsel (GC) / Head of Legal.** Strategic leadership, board interface, enterprise risk ownership, talent development, and stakeholder relationship management. The GC sets the legal function’s strategy and culture.
**Senior Counsel / Heads of Practice.** Subject matter expert leaders (e.g., head of litigation, head of IP, head of corporate) responsible for legal quality, risk assessment, and managing external counsel relationships within their practice areas.
**Counsel / Senior Associates.** Lawyers handling complex matters, client relationship management, and strategic advisory work. These roles require legal qualification and typically involve judgment calls that balance business, legal, and reputational considerations.
**Legal Operations Manager.** Owns process design, vendor management, matter management systems, budgeting, and reporting. The legal ops manager is the GC’s primary operating partner.
**Legal Engineer / Legal Developer.** Designs and builds custom automation, integrations, and tools. This role typically requires software engineering skills applied to legal workflows. May be in-house or contracted to a specialist firm.
**Paralegals / Technicians.** Support lawyers with research, drafting, document management, and client interaction. Can be in-house, outsourced to managed service providers, or a hybrid.
**Managed Service Providers (MSPs).** Perform high-volume, standardised work: contract review, document review, due diligence, legal research, and compliance monitoring. Typically selected based on cost, quality, speed, and data security.
**Alternative Legal Service Providers (ALSPs).** Specialist firms offering managed services for specific practice areas (e.g., employment law, IP management, litigation support). Differ from traditional counsel by specialising in specific work types at lower cost.
The specific mix depends on the legal function’s size, industry, geography, and risk profile. A highly regulated organisation with high transactional volume and low strategic complexity might optimise toward MSPs and ALSPs, supplemented by a small in-house team. A high-growth technology company might optimise toward in-house counsel supported by technology and fewer managed services.
### Workforce Planning: Matching Skills to Work Types
Not all legal work is equal. The **triage matrix** (detailed in Chapter 7) categorises work into four bands based on complexity and risk:
- **Routine:** Standardised, repetitive, low-risk work (e.g., contract renewal, standard template review)
- **Guideline:** Work that follows established precedent and process, moderate routine, moderate risk (e.g., contract review with decision tree)
- **Discretionary:** Work requiring judgment, subject matter expertise, material business impact (e.g., novel contract negotiation, regulatory strategy)
- **Leadership:** Strategic, enterprise-wide implications, requiring seniority and business acumen (e.g., acquisition strategy, major litigation)
Each band optimises for different resourcing:
**Routine work** is best performed by paralegals, junior staff, or outsourced to MSPs. Cost per unit is low; quality is consistent; training is straightforward. Staffing with senior lawyers is economically inefficient.
**Guideline work** suits mid-level lawyers applying established processes, potentially supported by legal technology. Standardisation matters here — the goal is consistent, reliable output at reasonable cost.
**Discretionary work** requires experienced counsel. This is where senior lawyer judgment adds value. These lawyers should spend their time on this band, not on routine work.
**Leadership work** is GC and senior partner responsibility. Strategic decisions, enterprise risk, client relationships, and business transformation are concentrated here.
Workforce planning means:
1. **Understanding your work profile.** Analyse a representative month of legal work. Categorise every matter, every task, every request into the four bands. What percentage of your team’s time is spent on each?
2. **Comparing against resourcing.** If 40% of your work is routine but your team is 80% lawyers, you have an economic problem. If 30% of your work is discretionary but only 20% of your team capacity is counsel-level, you have a capability problem.
3. **Rebalancing.** Move routine work to appropriate resources — paralegals, technology, or MSPs. Increase counsel capacity if discretionary work is being rushed or junior lawyers are spending excessive time on routine work. Ensure leadership capacity is not consumed by work that could be delegated.
This analysis should be revisited annually. Business changes — acquisitions, new markets, new product launches, regulatory changes — shift the work profile. Workforce strategy must follow.
---
Building the culture and change management discipline to support these structural decisions is covered in Chapter 6: Leading Change in Legal.
---
## Measuring Organisational Health
Organisational health isn’t intuitive. A legal team can appear healthy on the surface — matters delivered on time, client relationships strong, budgets met — while underlying indicators suggest significant stress or capability gaps. Measuring organisational health requires looking beyond output metrics to diagnostic ones.
### Employee Engagement and Satisfaction
Engagement surveys should be conducted annually and track:
- **Clarity of role and expectations.** Do team members understand what they are responsible for and how success is measured?
- **Access to tools and training.** Do team members feel equipped to do their work effectively?
- **Career development.** Do team members see a future within the legal function? Are there pathways to advancement?
- **Manager effectiveness.** Do team members have clear feedback, support, and development conversations with their manager?
- **Psychological safety.** Can team members raise concerns, ask for help, and admit when they need support?
- **Culture fit.** Do team members feel they belong to the team? Are they treated with respect?
A declining engagement score in any category is an early warning. Team members are your most sensitive sensors for organisational health problems — attend to what they’re telling you.
### Retention and Turnover Analysis
Track voluntary turnover by role and tenure. Turnover trends reveal talent problems:
- **High early turnover (within 18 months)** suggests either misalignment between what new hires expected and what they experienced, or a scaling problem during onboarding.
- **High mid-career turnover (3–5 years)** often indicates lack of career progression, limited advancement opportunities, or manager effectiveness issues.
- **Unexpected loss of senior talent** may signal burnout, an unmet aspiration for specific work, or a specific manager dynamic that needs investigation.
Understanding *why* people leave is as important as knowing *that* they leave. Exit interviews should be structured, thoughtful, and separated from the line manager to encourage honesty.
### Skills Gap Analysis
Assess whether the team’s capability matches the work profile and strategic priorities:
- **Subject matter depth.** Do you have sufficient seniority and expertise in your key practice areas?
- **Functional breadth.** Do you have the right mix of lawyers, operations professionals, technologists, and specialists?
- **Emerging capabilities.** Do you have emerging skills for future work — legal data science, AI, legal engineering?
- **Bench strength.** If a key person departs, could someone else step into their role?
Skills gap analysis should inform hiring, development, and succession planning. It’s particularly important in hybrid operating models where capability may be built in-house, outsourced, or acquired through technology.
### Utilisation and Work Distribution
Analyse how the team spends its time:
- **Utilisation by work type.** What percentage of your lawyer capacity is spent on routine, guideline, discretionary, and leadership work?
- **Workload distribution.** Is work distributed equitably, or are specific individuals consistently overloaded?
- **Efficiency trends.** Are cycle times improving? Is the same work taking longer or shorter as you gain familiarity?
- **Capacity buffer.** Do you have sufficient capacity for unexpected work, or are you perpetually at full utilisation?
These metrics should be tracked monthly and reviewed quarterly. Workload imbalances corrode engagement quickly — intervene when you identify them.
---
## In the Trenches
> *This example is fictional and for illustration only. To contribute a real story, see the *[*How to Contribute*](https://app.notion.com/p/3564815eed4f81aa8783fb7a1326814e)* page.*
**The Tool Nobody Used**
A regional Australian law firm invested \$280K in a state-of-the-art document automation platform. The technology was excellent — it could produce first drafts of complex commercial agreements in under three minutes, with clause selection guided by a decision-tree interface. The vendor’s demo was impressive. The managing partner approved the spend enthusiastically.
Twelve months later, adoption was at 11%. The firm’s lawyers were still drafting documents from prior-matter precedents saved on personal drives.
The post-mortem identified three failures, all on the people pillar. First, lawyers hadn’t been consulted during selection — the tool felt imposed by management rather than designed for them. Second, training was a single two-hour session on a Friday afternoon when half the team was in client meetings. Third, and most critically, no one had addressed the WIIFM: the senior partners who controlled workflow allocation didn’t understand how the tool benefited them personally, so they never directed their teams to use it.
The firm hired a Legal Ops consultant who restarted from Phase 1. She interviewed every partner about their concerns, redesigned training around role-specific use cases, and identified three “champion” lawyers who’d experimented with the tool and were willing to demonstrate its benefits to peers. She embedded adoption targets into the firm’s quarterly review process.
Within six months, adoption reached 67%; within twelve months, 84%. The tool’s ROI, negative for the entire first year, turned positive in month 14.
---
## Checklist
- **Audit your operating model.** Map your current resourcing across in-house lawyers, paralegals, legal ops, managed service providers, and technology. Is this the right mix for your work profile and strategy? Would a different combination improve efficiency or capability?
- **Run the triage analysis.** Categorise a representative month of your team’s work into routine, guideline, discretionary, and leadership bands. What percentage of your team’s time is spent on each? Is this aligned with your role architecture and resourcing?
- **Review your health metrics.** Pull your most recent engagement survey results, turnover analysis, and utilisation metrics. Are there red flags? Where are you losing people? Which roles are overloaded? Use these insights to inform your people strategy for the next quarter.
## Suggested Reading
- [CLOC Core 12 Competency Framework](https://cloc.org/cloc-core-12/)
- [ACC Legal Operations Resources](https://www.acc.com/topics/legal-operations)
- [ACC Chief Legal Officers Survey](https://www.acc.com/resource-library/acc-chief-legal-officers-survey)
- [WorldCC Research and Benchmarking](https://www.worldcc.com/Resources/benchmarks-research)
- [Prosci ADKAR Model Overview](https://www.prosci.com/methodology/adkar)
Source: https://tilt.legal/docs/legal-ops-kit/the-legal-function
Markdown: https://tilt.legal/docs/legal-ops-kit/the-legal-function.md
| Q2C Stage |
Legal Intervention |
Velocity Impact |
| **Lead Qualification** |
Sanctions screening, conflict checks |
Delays of 2–5 days if manual |
| **Proposal / RFP** |
Terms validation, pricing approval |
Template availability reduces cycle by 3–7 days |
| **Negotiation** |
Redlining, playbook-guided negotiation |
Playbook adoption reduces rounds by 40% |
| **Approval** |
Authority matrix sign-off, compliance review |
Automated routing saves 2–4 days per deal |
| **Execution** |
E-signature, counterparty verification |
Digital execution eliminates 5–10 day postal delays |
| **Post-Execution** |
Obligation management, renewal tracking |
Proactive renewal capture prevents 5–15% revenue leakage |
Each intervention point is both a risk gate and a velocity lever. A mature legal operation optimises both — adequate risk controls, minimal elapsed time at each gate.
The Q2C Value Chain is your most powerful tool for communicating legal’s commercial impact to the CFO and CEO. When you can show that Legal Ops cut average deal cycle time from 42 days to 28, you’re speaking the C-Suite’s language — and quantifying legal’s direct contribution to revenue acceleration.
## Measuring What Matters
The legal function’s effectiveness can be measured across three strategic dimensions: **Velocity** (how fast legal enables commercial outcomes), **Leakage** (the value the enterprise could capture through better legal operations), and **Efficiency** (the ratio of output to cost over time). Chapter 13 explores these KPIs in depth, along with the Cost of Inaction framework for presenting them to a sceptical CFO and the Legal Value Scorecard for ongoing reporting.
The reframing from cost centre to value centre requires **three data points** that every Legal Ops leader should be able to produce on demand:
**1. Cost Avoidance (Defensive Value):** Quantify the penalties, litigation exposure, and regulatory fines the legal function prevented. Ground this in actual risk events identified, escalated, and mitigated before they crystallised.
**2. Revenue Acceleration (Offensive Value):** Measure the delta in contract cycle time before and after Legal Ops interventions. Multiply the time saved by average deal value and annual deal volume to get a concrete revenue acceleration figure.
**3. Efficiency Gain (Operational Value):** Track matters handled per legal FTE over time. As automation, self-service, and process optimisation take hold, this ratio should rise — meaning legal is scaling output without proportionally scaling cost.
## Checklist
- **Articulate your function’s purpose in one sentence.** Can you explain what your legal department does — and why it exists — in terms a board member would immediately grasp? If the answer relies on jargon or departmental tradition, refine until it maps to the two core propositions: keeping the business within permissible boundaries, and protecting its rights and assets.
- **Map your Q2C touchpoints.** Identify every stage where legal intervention is required in your organisation’s deal cycle. For each touchpoint, record the current average elapsed time and the number of people involved. This is your baseline.
- **Calculate your contract cycle time.** Pull the last 50 executed contracts: date of first draft to date of full execution. Compute the average and standard deviation. If you can’t produce this number, your first priority is a system that tracks it.
- **Identify your top 3 “friction clauses.”** Ask your commercial team which contract terms generate the most back-and-forth during negotiation. These are your candidates for playbook-driven pre-approval — and the fastest path to measurable cycle time reduction.
- **Schedule a 30-minute meeting with your CFO.** Bring one data point: the estimated revenue impact of cutting average contract cycle time by 5 business days. Frame it as an investment conversation with a clear return.
## Suggested Reading
- [CLOC Core 12 Competency Framework](https://cloc.org/cloc-core-12/)
- [ACC Chief Legal Officers Survey](https://www.acc.com/resource-library/acc-chief-legal-officers-survey)
- [WorldCC Research and Benchmarking](https://www.worldcc.com/Resources/benchmarks-research)
- [OECD Principles of Corporate Governance](https://www.oecd.org/corporate/principles-corporate-governance/)
- [Cornell Legal Information Institute (LII) - Wex](https://www.law.cornell.edu/wex)
Source: https://tilt.legal/mobius
Markdown: https://tilt.legal/mobius.md
# Mobius
Mobius is Tilt Legal's purpose-built AI platform for legal work, designed around structured workflows, configurable delivery, and secure operational patterns.
## What Mobius focuses on
- Turning specialised legal work into repeatable workflows
- Combining structured data, guided steps, and reliable outputs
- Supporting enterprise security, governance, and operational discipline
## Domain areas
The Mobius pages describe specific domain patterns and productised workflows built on the platform.
## Mobius Domains
- [Bill Review](/mobius/bill-review.md)
- Review legal bills with structured rules, invoice parsing, parties management, and clear audit-ready output.
- HTML: /mobius/bill-review
- [Workplace Investigations](/mobius/investigations.md)
- Organise evidence, track allegations to findings, and produce procedurally fair reports from one secure Mobius workspace.
- HTML: /mobius/investigations
Source: https://tilt.legal/mobius/bill-review
Markdown: https://tilt.legal/mobius/bill-review.md
# Bill Review
Review legal bills with structured rules, invoice parsing, parties management, and clear audit-ready output.
- Canonical URL: /mobius/bill-review
import {
ArrowRightFromLine,
FileSearch,
Scale,
ShieldCheck,
} from "@tilt-legal/cubitt-icons/ui/outline";
import { BalanceLogo } from "@tilt-legal/cubitt-logos/partners";
|
Before (spreadsheets) |
After (Mobius) |
| **Finance team** |
Manual verification via Excel macros across multiple spreadsheets; each law firm's billing format required separate handling; identifying specific time entries related to billing issues was difficult and time-consuming |
Automated rule-based verification that ingests and normalises varied billing formats, applies Balance's defined rules consistently, accommodates jurisdictional tax differences, and produces clean exports compatible with existing finance systems |
| **Investment managers** |
Navigating multiple spreadsheets to locate analysis; no consolidated view of fee earner rates, role changes or new additions to a case |
Clear, at-a-glance views with fee earner tracking surfaced automatically: fee changes, role updates and new fee earners are centralised and visible without manual coordination |
The solution was designed to mirror existing workflows, minimising disruption and ensuring the team could transition from spreadsheets without losing familiarity.
The rule-based checks are also the foundation for Mobius's AI-powered review capabilities. Structured, normalised data and clearly codified rules give the AI layer a reliable starting point, so its analysis is grounded in the same standards the team already applies manually.
## Security and trust
Balance manages significant private funds and was appropriately careful about vetting Tilt’s security posture before proceeding. Tilt's ISO 27001 certification provided the foundation for that confidence, demonstrating that the infrastructure meets enterprise security standards across data confidentiality, integrity and availability.
Importantly, the Mobius platform allows Balance to access state-of-the-art AI capabilities within an environment built to the security standards their investors and stakeholders expect. For a firm operating across multiple jurisdictions with sensitive financial and case data, this was a critical factor in the decision to partner with Tilt.
## Impact
> Tilt understood what we were actually trying to achieve. Not just the technical requirements, but the commercial logic behind our verification process. The truth is, reviewing legal bills is no fun for anyone. We have built a system with Tilt that makes life easier for our investment managers and funded law firms, and should help with cost recoverability
*— Robert Rothkopf, Balance Legal Capital*