Discovery field guide / Department
How to find AI opportunities in Legal & Compliance
Where should discovery start?
Start with the path of a matter or control review, from incoming request to a decision someone can defend. Find repeated evidence collection, clause comparison, and missing-context follow-up. Interview the reviewer who owns the judgment as well as the person preparing the file. Keep assistance with preparation distinct from legal advice, compliance conclusions, and decisions that require qualified professional accountability.
The shared framework
Fourteen stages, from objective to portfolio.
Every guide uses this sequence to connect a business problem to an accountable investment. Revisit earlier stages when new evidence changes the assessment.
Stage 1: Business Objective
Name the outcome the organization is trying to move, so every later idea has something to be measured against.
Stage 2: Department
Locate the team that owns the objective and the work that feeds it.
Stage 3: Process
Describe how the work actually runs today: steps, handoffs, systems, and exceptions.
Stage 4: People
Capture who performs and depends on the work, and what they know that no document records.
Stage 5: Problem
State the friction in plain terms: delay, rework, error, cost, or risk, with evidence.
Stage 6: Opportunity
Frame a specific improvement that addresses the problem, not yet tied to any technology.
Stage 7: AI/Automation Fit
Compare AI, RPA, IDP, workflow automation, process redesign, and no technology change.
Stage 8: Value
Estimate benefit in the objective's own terms, with assumptions written down.
Stage 9: Feasibility
Check data, systems, skills, and change capacity needed to deliver.
Stage 10: Risk
Surface compliance, quality, security, and adoption risks and the controls they need.
Stage 11: Scoring
Rate each opportunity on the same dimensions so comparisons are consistent and explainable.
Stage 12: Prioritization
Sequence opportunities by score, dependencies, and capacity, with reasons people can challenge.
Stage 13: Investment
Match approved effort to the sequence; people with budget authority decide what gets funded.
Stage 14: Portfolio
Track opportunities over time as a living set: delivered, in flight, waiting, and retired.
Start with one observable journey
Choose one recurring matter type, such as a standard agreement deviation or a control-evidence request. Trace a normal file and a contested one using approved, sanitized material. Identify what the reviewer needed to know, where it came from, and which judgment could not be delegated.
This guide is about finding process improvements, not legal advice or a claim that a tool satisfies any jurisdiction's professional, regulatory, or privilege requirements. Responsible counsel and compliance owners define those boundaries.
Where to look in the work
Matter intake and missing context
Inspect requests returned because the business purpose, counterparties, jurisdiction, or deadline was unclear. Capture repeated clarification rather than assuming the legal team's review is the bottleneck. A structured intake form or explicit escalation rule may address the delay without interpreting legal text.
Evidence assembly around recurring reviews
Follow how staff retrieve agreements, identify versions, compare clauses against approved positions, and assemble control evidence. Separate finding a source from interpreting its consequences. A current playbook with an owner is a different foundation from a collection of past agreements that may contain exceptions.
Who to interview and what each person knows
Reviewer and matter coordinator
Ask counsel or a compliance reviewer to mark where they exercised judgment on an actual file, then ask the coordinator what preparation consumed effort. Include a business requester. Their experience can show whether the problem is queue visibility, missing evidence, or truly repetitive review.
Information-governance and control owners
Bring records management, privacy, security, and relevant control owners into the discussion. Establish privilege, confidentiality, retention, legal-hold, and access expectations before selecting a dataset. Permission to see a document in one matter does not imply permission to reuse it across matters.
What to ask: follow the evidence
What makes this source authoritative?
Ask how reviewers confirm the current executed version, applicable jurisdiction, and approved internal position. Which exception overturned the apparent standard? Request an example where a citation was correct but incomplete. Record how amendments, dates, and contextual exclusions change the conclusion.
What must remain a professional decision?
Ask which outputs may be drafts, which require sign-off, and how uncertainty is communicated to the business. What happens if a deadline or obligation is missed? Capture escalation duties and evidence needed to reconstruct the decision, not just the final document text.
Signals of opportunity, and reasons to look elsewhere
Repeatable preparation with source provenance
Bounded retrieval, completeness checks, or comparison against an approved playbook can justify investigation when every result can be checked against its source. Repeated hunting for an executed version may instead signal document-governance failure. Resolve that foundation before promising reliable interpretation.
Clear reviewer disagreement categories
Look for review corrections that can be explained and measured, such as missed defined terms or omitted amendments. If experts disagree because the matter requires negotiation or evolving interpretation, do not disguise that uncertainty as a classification task with one correct answer.
How to evaluate what you find
Test omissions, not only plausible output
Use approved examples with amendments, cross-references, unusual clauses, and misleadingly similar provisions. Check missed obligations and unsupported assertions separately. Require exact source references and an explicit unknown state; polished prose cannot substitute for complete, defensible review.
Count retained professional review
Assess whether preparation reduces total reviewer work once verification and correction are included. Confirm matter-level access, retention, provider terms, and any restrictions on processing privileged material with responsible counsel. Do not describe a successful extraction trial as approval for autonomous advice.
How to compare, prioritize, and invest
Begin with bounded preparation
Prefer a recurrent evidence packet or playbook comparison over open-ended legal reasoning. Put version control and document ownership ahead of a model if those are missing. Assign an accountable reviewer who can define what an acceptable draft must contain and when it must be rejected.
Invest where defensibility improves
Compare candidates on completeness, traceability, deadline reliability, and total preparation-plus-review effort. Treat confidentiality and professional duties as constraints, not risks that a high value score can cancel. Pause the trial on unsupported conclusions or loss of evidence provenance.
Turn observations into a comparable opportunity record
Describe the current process before naming a solution. Record the trigger, owner, input, steps, handoffs, systems, output, and exception path. Separate what you observed from what someone recalled and what you still need to verify. A vivid interview story is a useful lead, not proof that every case behaves the same way. Validate it against a sample of ordinary work and difficult exceptions, with the limits of that sample made explicit.
Measure active work separately from waiting. Note the observation period, case mix, frequency, and source of each estimate. Include the receiving team's effort, checking, correction, and escalation so a local improvement does not merely transfer work. Describe the outcome in operational terms before attaching a monetary value. Capacity released is not automatically a budget saving; explain what can actually change and which manager has authority to make that change.
Compare interventions before selecting a tool
If a rule is explicit and the input is structured, test ordinary workflow automation first. If the task repeats a stable interface action, examine RPA and an integration alternative. If the difficulty is reading documents, consider IDP with source checks. AI may help where language or variable evidence requires interpretation, but its output still needs a task-specific acceptance standard. Process redesign or no technology change may be the right answer when policy, ownership, or an unnecessary step causes the problem.
Write down why each alternative would or would not address the observed cause. Do not compare a carefully controlled AI proposal with an artificially weak version of the current process. Include data repair, access approval, integration, training, review, and upkeep in each feasible option. An unavailable prerequisite is a reason to sequence work or pause, not a detail to hide inside a feasibility score.
Agree on a decision, not just a demonstration
Before a trial, name the business owner, evaluator, permitted data, review boundary, and person who can stop it. Define acceptable outputs and failures that must trigger escalation. Use examples held out from development, including missing information and uncommon cases. Compare the complete task with the baseline, including human verification and downstream consequences. Preserve the evidence behind the result so another owner can challenge the conclusion.
Keep value, feasibility, risk, and evidence confidence visible separately. A candidate with an attractive benefit estimate is not ready if its owner cannot obtain the data or operate the controls. Record the decision to investigate, pilot, wait, reject, or retire, with a reason and a condition for revisiting it. After delivery, compare observed results with assumptions rather than leaving the original estimate in the portfolio as fact.
Use the evaluation guide for the evidence standard and the prioritization guide to compare qualified candidates. Your leaders make funding decisions; a score or a discovery tool supplies structured evidence, not investment authority.
Continue through the discovery framework
Browse all departments and industriesRelated practice notes
For focused interview techniques, examples, and scoring detail alongside this field guide:
Structure a legal-review workflow in IntakeOS
Bring a sanitized process description, evidence sources, and the professional sign-off boundary. Explore IntakeOS qualification without submitting privileged matter content unless your own counsel has approved that use.
IntakeOS supports structured interviews, qualification, and comparison; it does not make funding decisions or replace professional review. Learn about VARA, review the trust page, or explore the platform before sharing sensitive information.
Explore discovery in an IntakeOS demo