The triage matrix for routing legal work across internal teams, alternative providers, and technology — and the middleware architecture that connects them seamlessly. --- ## The Service Delivery Spectrum Modern legal operations does not rely on a single delivery model. Instead, the entire legal function sits within a spectrum of service delivery options, each optimised for different types of work, complexity levels, and cost profiles. Understanding this spectrum — and being deliberate about where each piece of work sits within it — is foundational to building an efficient, scalable legal function. The spectrum spans from fully automated, self-service delivery at one end to high-touch specialist counsel at the other: **Self-Service (Business Users).** The starting point: empowering business stakeholders to serve themselves for common, low-risk requests without requiring legal involvement. This might include accessing pre-approved template contracts, completing compliance checklists, or submitting standardised legal requests through a self-service portal. Self-service reduces legal team load and accelerates time-to-answer for routine questions. **In-House Legal.** The traditional model: in-house lawyers handling work across all complexity levels. Cost-effective for strategic, high-judgment work and matters requiring deep organisational context. Less cost-effective for routine, high-volume work that could be delivered elsewhere. **Alternative Legal Service Providers (ALSPs).** Specialised providers offering defined services — contract review, due diligence, legal research, compliance support — at fixed or blended hourly rates substantially lower than traditional law firms. ALSPs excel at moderate-complexity, process-driven work. **Managed Legal Services.** Outsourced legal operations, where a service provider takes responsibility for managing a defined legal function — contract management, IP administration, compliance — using a team model, process framework, and technology stack. Typically structured as an extended team integrated into the client organisation’s operations. **Traditional Law Firms.** External counsel for high-complexity, high-risk, bespoke matters requiring specialist expertise, client-specific knowledge, and the leverage to handle large-scale projects (M&A, major litigation, novel regulatory work). **Specialist Boutiques.** Smaller firms or solo practitioners offering deep expertise in niche areas — cryptocurrency regulation, healthcare IP, franchise law — where you need the very best but may not need a full-service firm. This spectrum reflects the unbundling of legal services discussed in Chapter 2 (Legal Ops 3.0). Rather than sending all work to a single law firm or handling everything in-house, modern legal operations is disaggregated: different work types flow to the provider best positioned to deliver them at the optimal cost and quality. The challenge is discipline: deciding, for each piece of work, which point on this spectrum is actually optimal. That decision is the job of the Triage Matrix. ## The Allocation Problem Every piece of legal work that enters the department faces an allocation decision: who should do this? Structured routing enables optimal work allocation, ensuring senior lawyers focus on high-complexity matters, cost-effective providers handle routine work, and capacity is reserved for strategic, high-judgment issues. The Triage Matrix replaces ad hoc allocation with a structured routing system that matches work to the most appropriate — and cost-effective — provider. ## The Triage Matrix ### The Three-Tier Model
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 about the answer (rather than apply a known rule or standard), it is 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* report series) and [Gartner’s legal technology predictions](https://www.gartner.com/en/legal-compliance) confirm that **process-fit** is the single most important predictor of whether a legal technology investment delivers its expected value. 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 a repository of inconsistently formatted PDFs with no metadata will produce unreliable results, eroding user confidence in the system 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 do not adopt the tool despite its technical capability. This results from insufficient WIIFM communication, training, or ongoing reinforcement — all change management factors described in Chapter 5. Successful adoption requires consistent engagement with users 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 delivery that comes from completing the initial scope successfully. ### 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 that scope. Stabilise it. Prove value. Then — and only then — expand. This phased approach demonstrates early wins and builds momentum, accelerating long-term value 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 **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. The Head of Legal Ops, rather than replacing the CLM, deployed a middleware layer using Microsoft Power Automate and a custom Teams bot. The underwriters could now initiate a contract request directly from a Teams message, answer four triage questions, and receive a first draft in their Teams channel within minutes. The middleware handled all interactions with the CLM — template selection, data population, routing for approval — without the underwriters ever seeing the CLM interface. CLM-processed contract volume tripled in three months. The underwriters were using the CLM through their familiar Teams interface; the middleware layer handled the technical complexity behind the scenes. The same underlying platform now delivered value because the user experience aligned with where users actually work. The total cost of the middleware deployment: approximately \$35K in Power Automate licensing and three weeks of configuration effort. 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)