Legal reading and research are often treated as a single undifferentiated activity — "doing research." In practice, they're two different activities with different purposes, different tools, and different productivity structures. Conflating them produces reading sessions that drift into research, research sessions that expand through undirected reading, and professional development reading that never happens because matter-related research always has higher priority.
This guide separates the two activities and structures each with a workflow appropriate to its purpose.
Reading vs. Research: The Distinction
Reading is the professional development activity: staying current with legal developments in practice areas, understanding what courts and agencies are doing, and maintaining awareness of the industry context of the clients you serve. Reading is self-directed and horizon-expanding; it's not triggered by a specific matter.
Research is the matter-specific activity: finding the governing authority for a specific legal question in a specific jurisdiction for a specific matter. Research has a defined objective (the research anchor from the research workflow) and a saturation point (when the governing authority is found and supporting/adverse authority is documented). Research is triggered by a matter need.
Mixing the two in a single undifferentiated "research" session produces the worst of both: reading that doesn't produce knowledge base entries (because the reading is happening in a research context, not a development context), and research that doesn't have a saturation point (because reading habits don't have stopping conditions).
The Four Reading Streams for Lawyers
Professional reading for lawyers falls into four streams, each requiring a different cadence and extraction approach:
Stream 1 — Developments in Active Practice Areas:
New decisions, statutory changes, and regulatory guidance that affect practice areas where you have active clients or matters. This is the highest-priority reading because it directly affects the quality of advice you're giving right now.
Cadence: weekly. A weekly review of practice area alerts (Westlaw alerts, Lexis alerts, agency email lists, bar publications) ensures that significant developments are captured before they affect a matter. Daily review for practice areas with rapid development (securities, cryptocurrency, healthcare regulatory).
Extraction output: concept-level knowledge base entries for decisions that create new precedent, updated currency dates for entries affected by the new development.
Stream 2 — Adjacent Area Awareness:
Developments in practice areas that are adjacent to your primary work — areas where clients sometimes have questions, where referrals are made, or where regulatory overlap exists.
Cadence: monthly. The purpose is awareness, not depth; a monthly scan for significant developments provides enough coverage without the time commitment of active monitoring.
Extraction output: awareness notes (not full knowledge base entries) for items that might be relevant to client service.
Stream 3 — Client Industry Intelligence:
Business and regulatory developments in the industries served by the practice. Clients expect their lawyers to understand their business context; an attorney who's unaware of a regulatory development affecting the client's entire industry has a service gap.
Cadence: weekly scan for client industry publications; monthly review of regulatory calendars for anticipated rulemaking. This stream reads differently from legal research — it's reading for business context, not doctrinal analysis.
Extraction output: client context notes in the client intelligence section of the second brain; matter context updates when a development is immediately relevant to an active matter.
Stream 4 — Professional Obligation Updates:
Changes to the Model Rules, state bar ethics opinions, malpractice prevention content, and procedural updates from the courts where you practice.
Cadence: complete coverage of bar communications; quarterly review of ABA ethics opinions in practice areas of concern.
Extraction output: professional development tracker updates; procedural compliance notes; immediate action if an ethics opinion creates a current obligation.
The Reading Schedule
The reading schedule converts reading from "whenever I have time" (which usually means never, or only under pressure) into a protected professional activity:
WEEKLY READING SCHEDULE
Monday morning (45-60 min): Stream 1 — practice area alert review
Read: alerts from Westlaw/Lexis, agency email lists, bar publications
Extract: concept-level entries for new precedent; update currency dates
Wednesday afternoon (30-45 min): Stream 3 — client industry scan
Read: industry publications, regulatory calendar items
Extract: client context notes; matter context updates
Friday morning (30-45 min): Streams 2 and 4
Read: adjacent area items; bar communications; ethics opinions
Extract: awareness notes; professional development tracker updates
Total: 1.5-2.5 hours per week across all reading streams. Protected from matter work: if the reading time is available for matter work, the professional development reading never happens.
The Pre-Research Protocol
Before any matter-specific research session opens Westlaw or Lexis, the pre-research protocol runs:
Step 1 — Write the research anchor (5-10 minutes):
The specific legal question, the jurisdiction, the governing standard (if known), the opposing position (if adversarial), and what "done" looks like.
Step 2 — Check the concept-level knowledge base (5-10 minutes):
Search for the issue by canonical concept label and jurisdiction. What does the knowledge base already contain?
- Governing authority already captured with pinpoint citation → no Westlaw/Lexis needed for this holding; verify currency only
- Supporting authority partially captured → targeted Westlaw research to fill gaps
- Nothing in knowledge base → full research session required
Step 3 — Define the genuine gaps:
The research agenda is the list of items not in the knowledge base. The research session addresses only these items.
The pre-research protocol takes 10-20 minutes. For a matter where similar questions have been researched before, this protocol frequently saves 2-3 hours of Westlaw time by identifying authority already in the knowledge base.
The Research Session Workflow
With the pre-research protocol complete and the research anchor defined, the research session has a specific structure:
Opening (5 min): review the research anchor and the knowledge base check results. Know exactly what's being looked for.
Execution (variable): research in Westlaw or Lexis, organized by the categories in the research anchor. The research session captures:
- Governing authority (with verbatim key passage and pinpoint citation)
- Supporting authority (2-4 cases supporting the position)
- Adverse authority (the cases the other side will cite, with distinctions)
- All with current validity confirmed (KeyCite or Shepard's)
Saturation check (ongoing): after every 3-4 sources, pause and ask: "Has anything in the last 3-4 sources changed what I have? Have I found new gaps I didn't know about before?" When new sources are confirming rather than adding, and the research anchor's "done" criteria are met, the research is complete.
Closing (15-20 min): write the concept-level knowledge base entries for any new precedent discovered. Update the research session template (from Article 1762). Create the structured pull document if drafting follows this session.
The research session closes when the research anchor is satisfied — not when time runs out, not when the research feels exhaustive.
The Extraction Discipline: What Reading and Research Produce
Neither reading nor research produces lasting professional value without the extraction step:
From reading sessions:
| Content type | Extraction | Time |
|---|
| New circuit decision creating precedent | Concept-level knowledge base entry (full) | 10-15 min |
| Regulatory guidance update | Concept-level entry with currency note | 5-10 min |
| Client industry development | Client context note in second brain | 3-5 min |
| Ethics opinion | Professional development tracker update | 5 min |
| Adjacent area awareness item | Awareness note (brief) | 2-3 min |
From research sessions:
All new governing authority → full concept-level entry with verbatim key passage, pinpoint citation, conditions/exceptions, and currency date. This entry goes into the knowledge base within the same session, not deferred to a later knowledge management task.
The compounding math:
A lawyer who extracts from 8 reading items per week (down from 20 unfiltered items, post-triage) and from 3 research sessions per week builds approximately 600-700 knowledge base entries per year. Over 5 years, that's 3,000-3,500 entries — a concept-level archive that covers most legal questions that arise in the practice with prior research available in under 30 seconds.
A lawyer who reads the same amount but doesn't extract has 5 years of professional awareness and nothing retrievable.
Common Reading and Research Workflow Failures
Failure 1 — No pre-research knowledge base check. Westlaw is opened immediately when a legal question arises. Research that was done for a prior matter and is already in the knowledge base is done again. Fix: the pre-research protocol runs before every Westlaw or Lexis session.
Failure 2 — No saturation signal. Research continues past the point where the research anchor is satisfied. Two additional hours of research confirm authority already captured and find interesting but out-of-scope material. Fix: the saturation check runs after every 3-4 sources. When the anchor is satisfied and new sources are confirming rather than adding, the session closes.
Failure 3 — Reading without the triage filter. Everything in the alert stream is read, regardless of relevance to active matters or active clients. 3 hours per week of undifferentiated reading produces 2.5 hours of low-value awareness and 30 minutes of actually useful professional development. Fix: three-filter triage before reading (active matter relevance → client-relevant precedent → awareness value only → skip).
Failure 4 — Research produces matter-only notes. Every research session produces notes in the matter file. The concept-level knowledge base is never updated. Five years of research is scattered across 200 matter folders, none of it retrievable by concept. Fix: the research session's closing step — knowledge base entry status — is non-negotiable. The session doesn't close until the entries are written or confirmed unnecessary.
Key Takeaways
-
Reading and research are different activities with different structures. Reading is horizon-expanding professional development with stream-separated cadences; research is matter-specific and ends when the research anchor is satisfied. Mixing them produces sessions without stopping conditions.
-
Four reading streams for lawyers: Stream 1 (active practice area developments — weekly, highest priority); Stream 2 (adjacent area awareness — monthly); Stream 3 (client industry intelligence — weekly scan); Stream 4 (professional obligations — complete coverage of bar communications).
-
The pre-research protocol runs before every Westlaw or Lexis session: write the research anchor; check the concept-level knowledge base; define the genuine gaps that require research. This protocol frequently identifies prior research that eliminates 2-3 hours of duplicated Westlaw time.
-
The saturation signal ends research sessions at the right point. The saturation check (after every 3-4 sources: "are new sources adding or confirming?") prevents research from expanding indefinitely past the point where the anchor is satisfied.
-
Extraction is what converts reading and research into compounding professional value. A lawyer who extracts consistently for 5 years builds a concept-level archive that covers most practice area questions with prior research retrievable in 30 seconds. A lawyer who reads the same amount without extracting has 5 years of professional awareness and nothing retrievable.
Conclusion
The reading and research workflow for lawyers structures two different activities with the protocols appropriate to each: stream-separated reading schedules that match cadence to content type, triage filters that reduce reading volume without creating competence risk, the pre-research protocol that checks the knowledge base before every Westlaw session, saturation signals that define when research is complete, and extraction discipline that converts both reading and research into concept-level knowledge base entries that compound in professional value over a career. Together, these practices convert legal reading and research from a perpetually overloaded activity into a structured professional practice.
See also: The Ultimate Guide to Web Clipping.