Agentic AI Systems for Legal, Tax, and Compliance Workflows
thomson_reuters · Legal · 2024 · source Agentic: yes · promotional bias: med · source-backed · extracted with prompt 0.5.2 (schema v2)
Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.
Problem
Domain: Legal, tax, and compliance
Thomson Reuters needed agentic systems that could make judgments and produce work in high-stakes expert workflows.
Constraints:
- Expert variability
- Proprietary content
- High-stakes compliance
- Adjustable autonomy
Architecture
Thomson Reuters frames agentic systems as adjustable agency dials rather than a binary architecture. Autonomy ranges from atomic tasks to self-evolving workflows; context ranges from model parametric knowledge to RAG and multiple controlled/web sources; memory ranges from stateless retrieval to persistent shared workflow memory; coordination ranges from single tasks to tool delegation and multi-agent collaboration. Those dials sit on top of decomposed legacy applications: tax engines, validation engines, source-document extraction, proprietary legal content, search/fetch/citation tools, and evaluation rubrics from domain experts.
Diagram confidence: reconstructed (reconstructed from prose).
flowchart LR agency-dial-controller[Agency dial controller] --> autonomy-dial[Autonomy dial] agency-dial-controller --> context-dial[Context dial] agency-dial-controller --> memory-dial[Memory dial] agency-dial-controller --> coordination-dial[Coordination dial] coordination-dial --> legacy-application-tools[Legacy application tools] legacy-application-tools --> tax-engine[Tax engine] legacy-application-tools --> legal-research-tools[Legal research tools] context-dial --> proprietary-content[Proprietary content] legal-research-tools --> proprietary-content evaluation-rubrics[Evaluation rubrics] --> agency-dial-controller
Components
| Component | Role | Interacts with |
|---|---|---|
Agency dial controller |
Use-case decision layer setting autonomy, context, memory, and coordination levels. | Autonomy dial, Context dial, Memory dial, Coordination dial |
Autonomy dial |
Controls whether work is atomic or self-planning/replanning. | Agency dial controller |
Context dial |
Controls parametric, RAG, controlled, web, and evolving data-source context. | Agency dial controller, Proprietary content |
Memory dial |
Controls stateless, workflow-shared, or persistent cross-session memory. | Agency dial controller |
Coordination dial |
Controls single-task execution, tool delegation, or multi-agent collaboration. | Agency dial controller, Legacy application tools |
Legacy application tools |
Decomposed tax, legal, compliance, and research systems exposed to agents. | Coordination dial, Tax engine, Legal research tools |
Tax engine |
Calculation and validation engine used by tax-return agents. | Legacy application tools |
Legal research tools |
Search, fetch, citation comparison, and citation validation tools. | Legacy application tools, Proprietary content |
Proprietary content |
1.5-plus terabytes of Thomson Reuters legal/tax/compliance content. | Context dial, Legal research tools |
Evaluation rubrics |
Domain-expert evaluation criteria for variable expert workflows. | Agency dial controller |
Data flow
A tax or legal workflow sets the agency dials appropriate to risk. For tax, source documents are parsed, fields are mapped to a tax engine, rules are applied, validation errors feed back into more document retrieval, and the return is completed. For legal research, the assistant uses litigation-research tools to search, fetch, compare, and validate citations over proprietary content before producing an answer.
3 supporting quotes
Why this architecture
Thomson Reuters uses dials because risk tolerance varies across legal, tax, and compliance tasks. Some workflows can tolerate high agency and exploration, while high-precision tasks need constrained autonomy, controlled context, and validation. Decomposing legacy systems as tools preserves decades of domain logic instead of rebuilding everything from scratch.
3 supporting quotes
Models used: LLMs
Scale
- Thomson Reuters references one and a half plus terabytes of proprietary content.“And so uh as I mentioned we have one and a half plus terabytes of proprietary content that we build uh our products on.”transcript, stated
Alternatives considered (roads not taken)
Binary agent/non-agent framing
Rejected because: The source argues agency is a tunable spectrum by use case and risk.
Rebuild AI workflows from scratch
Rejected because: Legacy systems contain tuned domain logic and validation engines that agents can use as tools.
Patterns
tool-use-orchestration (expert-workflow)
Legacy applications are decomposed into tools that agents can use.
agent-memory (workflow-state)
Memory is treated as a configurable dial in the agency model.
Tradeoffs
How to define agentic behavior.
Chose adjustable dials over binary agent/non-agent classification.
Rationale: The summary says Thomson Reuters treats agency as dials rather than a binary state.
How to set agency in expert workflows.
Chose risk-calibrated autonomy/context/memory/coordination dials over one uniform agent behavior.
Rationale: Legal and tax workflows vary in precision requirements and user tolerance for autonomous exploration.
Evaluation
Thomson Reuters emphasizes rigorous evaluation for expert judgment variability.
Metrics: expert judgment variability · workflow quality
Outcomes
- The systems include tax return generation and legal research workflows over proprietary content.
The transcript references 1.5+ TB of proprietary content in the summary.