The Matter Lifecycle as Organising Principle
A position paper on law firm transformation. June 2025.
Law firm transformation programmes routinely fail to deliver the operational improvement they promise. The reasons are well-documented, consistent across engagements, and largely preventable. This paper argues that the most fundamental of them — the structural error from which the others follow — is designing a Target Operating Model without organising it around the matter lifecycle.
This is not a niche implementation mistake. It is the mistake the industry makes systematically, because the consultants, vendors, and programme teams involved have not been clear, in advance, about what kind of organisation a law firm is and what a TOM actually requires of one.
Two misunderstandings drive most of the damage. The first is about the firm: law firms are understood as professional services organisations that happen to use matters as an administrative unit, when the correct description is that a law firm is a matter processing firm — an organisation whose entire commercial, operational, and regulatory structure is built around matters moving through a lifecycle. The second is about the TOM: most programmes described as TOM programmes are technology implementation programmes with operational language wrapped around them.
Correct both misunderstandings and the matter lifecycle as the organising principle of the TOM follows as a logical conclusion, not an architectural preference.
What a Law Firm Actually Is
A law firm is a matter processing firm. This is not a metaphor. It is a structural description with direct implications for how a law firm should be organised, measured, and transformed.
Revenue is denominated entirely in matters. Every pound, euro, and dollar a law firm earns is earned on a matter. Not on a department, not on a function, not on a system. The matter is the unit of commercial output. This is true whether the firm bills by the hour, by fixed fee, by milestone, or by outcome. The billing model changes; the matter as the unit does not.
Every function exists in relation to a matter.
| Function | What it actually does |
|---|---|
| Business Development | Originates matters |
| Conflicts and Risk | Qualifies matters before they open |
| Compliance / AML | Clears matters for instruction |
| Finance | Tracks matter economics; collects matter revenue |
| HR / Resourcing | Assigns people to matters |
| Knowledge Management | Captures and reuses what was learned on prior matters |
| IT | Provides the systems through which matters are managed |
| Partners | Own, supervise, and are accountable for matters |
No function exists independently of this. A finance team with no matters to bill is not a law firm finance team. An IT system that does not serve matter delivery has no purpose in the firm.
The industry has reached the same conclusion from multiple directions. CLOC — the Corporate Legal Operations Consortium — defines matter lifecycle management as “the best practice process by which in-house legal practitioners, acting alone or together with their outside counsel, effectively and efficiently project manage a legal matter from start to finish.” The definition is scoped to in-house legal teams but the principle is identical from the law firm side: the matter is what is being managed, and everything else is in service of that.
Professional regulation enforces it. Law firms do not merely choose to organise around matters — they are required to. Regulatory obligations attach to matters: conflicts of interest must be checked per matter, AML/KYC assessments are conducted per matter, engagement letters are issued per matter, time records are maintained per matter, and files must be archived per matter. In the EU, WWFT (the Dutch AML implementation) and the incoming AMLR — applying from 10 July 2027 — impose mandatory process requirements that are matter-specific. A law firm that cannot account for the status and history of each matter is not just operationally weak. It is non-compliant.
A law firm is not a professional services firm that happens to use matters as an administrative convenience. The matter is the firm’s fundamental unit of value creation, commercial accountability, regulatory compliance, and operational management.
Sources
- CLOC / Morgan Lewis, Matter Life Cycle Management (MLM) for Legal Teams, August 2022.
- WWFT (Wet ter voorkoming van witwassen en financieren van terrorisme) — Dutch primary AML legislation.
- EU AML Regulation (AMLR), applying from 10 July 2027.
What a Target Operating Model Is — and Isn’t
“Target Operating Model” is consulting language. When a law firm uses the term, someone with a transformation background framed the problem — and that framing carries assumptions worth examining before they harden into programme design.
A Target Operating Model is a blueprint for how an organisation will deliver value in its future state. It is not a technology roadmap. It is not a project plan. It is not a list of systems to be implemented.
The most structurally rigorous published framework is KPMG’s six-layer model:
| Layer | What it defines |
|---|---|
| Process | How work gets done — end to end |
| People | Who does the work, with what skills, in what roles |
| Service Delivery Model | Who does what work, where, and at what cost point |
| Technology | The systems that enable the above |
| Performance Insights | How the organisation measures whether it is working |
| Governance | How decisions are made and accountability is held |
Technology is layer four. It enables the three layers above it and is measured by the two layers below it. A programme that starts with technology selection has skipped three layers of design — and will spend the rest of its life trying to reverse-engineer an operating model that fits the technology chosen.
What most law firm “TOM” programmes actually are
Most law firm transformation programmes described as TOM programmes are technology implementation programmes with operational language wrapped around them. The tell is in the sequence of decisions:
(1) A platform is selected — often for relationship, commercial, or political reasons (2) An implementation partner is engaged whose practice is built on that platform (3) An operating model is defined that accommodates the platform’s architecture (4) The programme is branded as a TOM transformation
This is not a TOM. It is a technology programme with a TOM label. The operating model in step (3) is not designed — it is reverse-engineered to justify a decision already made in step (1).
The difference between a TOM-led and a technology-led programme is not academic. It determines what questions get asked, in what order, and by whom:
Technology-led: Which platform should we select? What can it do? How do we configure it for our firm?
TOM-led: How should work flow through this firm? Who should do which parts of it? How will we know if it is working? Which technology best enables that model?
The second set of questions produces a specification. The first produces a vendor selection.
For law firms specifically, the service delivery model layer — who does what work, at what cost point — is where the most consequential decisions sit in 2026. The arrival of AI and fixed-fee pricing pressure means the answer to “who does this work” is genuinely open in a way it was not five years ago. A TOM that does not address this layer is not a TOM for 2026.
Sources
- KPMG, Target Operating Model — Powered Enterprise, 2024.
- McKinsey, Operating model transformations: Not all elements are created equal.
- Legal Evolution (Bill Henderson), The 2026 Burning Issues Confronting Firm Leaders, December 2025.
The Matter Lifecycle as Organising Principle
If a law firm is a matter processing firm, then the matter lifecycle — the sequence of stages through which every matter passes from origination to closure — is the coordinate system within which all law firm operations take place. Every process, system, role, and integration point in the firm has a location in that coordinate system. The TOM design question is not “what should our systems do” but “what does the lifecycle require at each stage, and what is the best way to provide it.”
The canonical stages
| Stage | What happens | Primary obligation |
|---|---|---|
| 1. Business Development | Relationship management, pitch, opportunity tracking | Commercial |
| 2. Conflict Check | Search against existing client/matter database; sanctions screening | Professional conduct — mandatory |
| 3. Intake / AML | Instruction capture, identity verification, AML/KYC/CDD, risk scoring, engagement letter | Regulatory — mandatory human review |
| 4. Matter Opening | Matter record creation; rate assignment; team configuration; ethical walls | Operational |
| 5. Active Delivery | Time entry, document management, task tracking, budget monitoring, interim billing | Operational and commercial |
| 6. Pre-Bill and Billing | Time review, narrative checking, billing guideline compliance, invoice production, collections | Commercial |
| 7. Matter Closure | File closure, document archival, lessons learned, precedent capture, client feedback | Operational |
This sequence is not a design choice. It is the structure imposed by the nature of legal work, professional regulation, and commercial reality. A firm cannot bill before it has opened a matter. It cannot open a matter before it has cleared conflicts and AML. The sequence is locked.
The gates that cannot be automated away
Two stages contain mandatory human gates — not as a matter of operational preference but as a matter of law.
Stage 2 — Conflicts: The conflict of interest check is a professional conduct requirement in every jurisdiction. While the search itself can be automated and AI-assisted, the decision — whether a conflict exists and what to do about it — must be made by a qualified lawyer. No system can make that decision.
Stage 3 — AML/KYC: Under WWFT and the incoming AMLR (from 10 July 2027), a designated responsible person must make a formal, documented, auditable risk assessment before a matter can proceed. The assessment can be informed by automated risk scoring and integrated sanctions screening. The decision is human. This gate is permanent, not transitional.
STP — Straight-Through Processing — has a hard ceiling at these two stages. Any programme that claims full-lifecycle STP has either misunderstood the regulation or is misdefining STP.
The gap in the literature
The matter lifecycle as the organising principle of a law firm TOM is not a named, published framework. CLOC’s Matter Lifecycle Management standard addresses project management within a matter. Vendor platforms describe themselves as covering “the full lifecycle from intake to billing.” No published document makes the argument that the matter lifecycle should be the primary organising principle of the entire TOM — that it should precede and govern system selection, process design, role definition, and integration architecture.
This is a gap. The industry talks extensively about matter lifecycle management as an operational discipline. It does not yet talk about the matter lifecycle as an architectural principle — the frame within which TOM design decisions are made and evaluated.
The conclusion
If the matter lifecycle is the coordinate system within which all law firm operations take place, then a TOM designed without explicit reference to the lifecycle is not designed at all. It is a set of functional plans — technology, process, people — developed in parallel and hoped to cohere at implementation. They will not cohere. They will meet at the integration points and find they were designed for different versions of the same firm.
Sources
- CLOC / Morgan Lewis, Matter Life Cycle Management, August 2022.
- WWFT. EU AML Regulation (AMLR), applying from 10 July 2027.
Technology’s Role: Enabler, Not Architect
Technology does not design a TOM. It enables one. In practice this distinction is consistently reversed — because the commercial structure of the legal technology market makes reversal easy. Platforms are sold with transformation language. Implementation partners are retained whose practice credentials depend on a specific platform. The operating model discussion happens after the contract is signed.
The orchestration question
Every major legal technology vendor currently claims, or is moving toward claiming, that their platform can orchestrate the full matter lifecycle. The claim requires scrutiny.
Orchestration — in the technical sense — means a system that directs the behaviour of other systems: triggering actions, routing decisions, enforcing rules, and maintaining state across the lifecycle regardless of which downstream system handles the work. What most legal platforms provide is application-level workflow: a system that manages work within its own domain and passes a handoff signal to the next system when its portion is complete.
No single platform currently available in the law firm market orchestrates the full matter lifecycle across a firm’s complete technology stack. The platforms that cover the most ground orchestrate the matter workflow layer well. They do not orchestrate the financial system, the HRM system, the document management system, or the intelligence layer.
What technology cannot do
Technology cannot define the matter lifecycle. It can only reflect a lifecycle defined elsewhere — in process design, role definition, and governance decisions. A system configured against an undefined or assumed lifecycle will automate the confusion, not resolve it.
Technology cannot own compliance. Systems inform compliance decisions. The decision itself must be made by a qualified person. Every compliance gate in the matter lifecycle is a human gate.
Technology cannot drive adoption. A system that fee earners do not use does not improve the matter lifecycle. It creates a parallel process alongside the one that actually operates.
The practical implication
The integration architecture — how data and decisions pass between systems across the lifecycle — is the most important and most consistently under-resourced element of a law firm technology programme. It is where the matter lifecycle either flows or fragments. Investing in it deliberately, with clear data ownership, defined handoff criteria, and explicit integration standards, is the architectural decision that determines whether the TOM works in practice or only on paper.
Sources
- Thomson Reuters Institute, 2025 Report on the State of the US Legal Market, January 2025.
The Argument
A law firm is a matter processing firm. Every function, every system, every compliance obligation, and every commercial metric in the firm exists in relation to matters moving through a lifecycle. That lifecycle is the coordinate system within which all law firm operations take place.
A Target Operating Model for a law firm is therefore, by definition, a matter lifecycle ecosystem design. Technology enables this. It does not replace the design.
Three propositions follow:
One. The matter lifecycle must be documented before the TOM is designed. Not concurrently, not as a validation exercise after key decisions have been made. Before. The current state — every stage, every system, every handoff, every friction point — is the specification from which the target state is derived.
Two. No single platform orchestrates the full matter lifecycle. The integration architecture — how data and decisions pass between systems — is the most important and most consistently under-resourced element of a law firm technology programme.
Three. A TOM that does not organise itself around the matter lifecycle is not a TOM. It is a collection of functional plans that happen to coexist in the same organisation. They will not cohere at implementation. They will meet at the integration points and find they were designed for different versions of the same firm.
The matter lifecycle is not one of the things a law firm TOM is trying to fix. It is the thing the TOM is trying to serve.
Part of a series: see also “Why Data Must Come Before Systems,” “AI in the Matter Lifecycle,” and “Law Firm Transformation: A Practitioner’s Guide.”