You open your laptop for exam revision. You have notes scattered across multiple apps: some lectures in OneNote, some cases in Notion, some random thoughts in Apple Notes, some handwritten notes you photographed in your phone.
You spend 20 minutes searching for that case summary you know you wrote. You find three versions—different levels of detail, potentially conflicting information. You're not sure which is correct.
You abandon searching and just study from your textbook instead. Your notes, which should be your most valuable revision resource, are too disorganized to actually use.
Here's the uncomfortable reality: most law students have poor note-taking systems. They take notes passively during lectures. They don't organize systematically. They create hundreds of disconnected documents. When exam revision arrives, their notes are more burden than benefit.
The students with strong exam performance usually have strong note-taking systems. Their notes are organized, accessible, interconnected, and actually useful during revision.
The difference isn't which app they use. Students with good systems use various apps (Notion, OneNote, Obsidian, even Google Docs). The difference is they've designed systems around their apps—intentional structures that organize information so it's findable and useful.
Let's examine what makes note-taking systems work, what apps are actually suited for law students, and how to organize your notes so they become your most powerful revision tool.
### Why Your Current Note-Taking System Probably Fails
Most law students' note-taking has predictable problems.
Problem 1: Passive transcription
You sit in lectures and type everything the tutor says. You're documenting the lecture, not learning from it.
You never reread these notes. They're word-for-word lecture transcript with no structure, no highlighting of key concepts, no synthesis.
During revision, you open them and find 40 pages of barely-organized prose that takes hours to extract useful information from.
Problem 2: No hierarchy
Your notes have no distinction between: core principles (what you must know), important cases (what you should know), examples (nice to know), and tangents (irrelevant).
Everything is equal. You study minor examples with the same intensity as core principles.
Problem 3: Disconnected information
Each lecture/topic becomes isolated document. There's no linking between related concepts.
When you study Topic A and it connects to Topic B, you don't realize it because your notes are separate.
Problem 4: Poorly named files
You have notes titled: "Law notes," "lecture notes," "notes 2," "important stuff," "stuff I need to remember."
When you search for something, you can't find it because the naming is inconsistent and unhelpful.
Problem 5: No review system
You take notes once during lectures. You never review or refine them.
Notes that made sense immediately after lectures become cryptic weeks later. By exam time, they're nearly useless.
Problem 6: Wrong app for the job
You use Word (designed for long-form prose) for note-taking (which benefits from structure and navigation).
Or you use OneNote (designed for casual capture) for serious law study (which benefits from organization and linkage).
The app doesn't match the task.
### What Actually Matters in Note-Taking
Before choosing apps, understand what makes systems work.
Feature 1: Searchability
Your system must let you find information quickly.
Can you search across all notes? Can you find a case by name? Can you find all notes on a topic?
Feature 2: Organization
Information must be categorized logically.
By module. By topic within module. By case type. By principle. The organization should match how you think about material.
Feature 3: Navigation
You should be able to move between related notes easily.
If Note A references Case B, you should be able to click and jump to Case B notes.
Feature 4: Simplicity
The system shouldn't be so complex that maintaining it becomes a burden.
Elaborate note-taking systems often fail because students spend more time organizing than studying.
Feature 5: Accessibility
You should be able to access notes from any device—laptop, tablet, phone.
You might want to review notes on your phone during breaks. Your system should allow this.
Feature 6: Review mechanisms
Your system should support active review, not just passive reading.
Can you easily see what you've reviewed and what you haven't? Can you flag areas for focused revision?
Feature 7: Flexibility
Needs change throughout the year.
Early in term, you're learning. Your notes are long and detailed. Later, you're synthesizing. Your notes become brief summaries.
Your system should adapt to these changing needs.
### Apps That Work for Law Students
Different apps have different strengths. None is universally "best." Choose based on what your system needs.
Option 1: Notion
Strengths:
Highly organized. You can structure notes hierarchically (Module > Topic > Case > Analysis).
Searchable across all notes.
Can link between notes easily ("See also: Case X").
Database features let you organize cases by principle, area, importance.
Modern and flexible.
Weaknesses:
Steeper learning curve. Setting up a good system takes time.
Free version has limits. Paid version is £8/month.
Offline access limited on free version.
Best for: Students who want sophisticated organization and don't mind initial setup time.
Example structure:
Database of all cases with fields: Case name, year, area (contract/tort/etc.), key principle, facts, holding, significance.
Another database of topics with links to relevant cases.
Module pages linking to topic pages.
This structure lets you search cases by principle, navigate by topic, see relationships between cases.
Option 2: OneNote
Strengths:
Familiar Microsoft product. Many students already use it.
Good hierarchical organization (Notebook > Section > Page).
Good for capturing notes quickly during lectures.
Relatively simple to use.
Free version is robust.
Weaknesses:
Search is less powerful than newer apps.
Linking between notes is clunky.
Not ideal for complex organization of interconnected information.
Best for: Students who prefer simplicity and already use Microsoft products.
Example structure:
Notebook per module.
Sections for each topic within module.
Pages for each case/concept within topics.
Simple but functional.
Option 3: Obsidian
Strengths:
Powerful linking system. Notes naturally interconnect.
All your notes are plain text files stored locally (you own them, not dependent on app company).
Very flexible. You design your own structure.
Affordable (free or £40 lifetime license).
Excellent for interconnected thinking.
Weaknesses:
Steep learning curve. Requires understanding of markdown and file systems.
Offline-first (can sync to cloud, but primary storage is local).
Less intuitive for capturing notes during lectures.
Best for: Students comfortable with technology and who want maximum flexibility.
Example structure:
Folder per module. Notes on cases/topics. Use wikilinks ([[ ]]) to link related notes. Create index note listing all cases and topics in module.
When you're studying and encounter reference to related case, you click link and jump to it.
Option 4: Google Docs/Drive
Strengths:
Extremely simple. Everyone can use it.
Accessible from any device.
Good for collaborative notes (shared with study group).
Free.
Weaknesses:
Poor for complex organization. Designed for long-form writing, not interconnected note systems.
Difficult to maintain when you have dozens of documents.
Navigation is clunky.
Best for: Simple note-taking or collaborative notes with study group.
Example structure:
Folder per module. Doc per topic or case.
Simple but requires discipline to keep organized.
### Building Your System: The Process
Choosing an app is step 1. Building a system is step 2.
Phase 1: Decide your structure
Before you open the app, decide how you'll organize information.
Example structure:
Module level: Constitutional Law
Topic level: Parliamentary Sovereignty
Case level: Miller (No 1)
Concept level: What is parliamentary sovereignty? Can it be limited?
This hierarchy shapes everything. Different structures work for different people.
Phase 2: Set up your app around this structure
Create folders/databases matching your hierarchy.
Example Notion setup:
Databases: Modules, Topics, Cases, Principles
In Cases database: Fields for Case name, Module, Topic(s), Principle(s), Year, Facts, Holding, Significance
Relationships: Cases link to Topics. Topics link to Principles. Principles link to related Cases.
Phase 3: Develop note templates
Create standard formats for different note types.
Case note template:
Case name | Year | Citation
Facts: [What happened?]
Issue: [What legal question?]
Holding: [What did court decide?]
Ratio: [What's the binding principle?]
Significance: [Why does this case matter? How does it relate to other cases?]
Connection to principles: [Link to related principles]
Topic note template:
Topic name
Definition: [What is this topic?]
Key cases: [Cases that establish law on this]
Core principles: [What must you understand?]
Common confusion: [What do students often get wrong?]
Exam frequency: [Does this appear often on exams?]
Using templates ensures consistency. You always know where information is.
Phase 4: Populate incrementally
Don't try to enter all notes at once. Do it as you learn.
After each lecture, create case notes or topic notes while material is fresh. But don't just transcribe. Synthesize.
After each module, review your notes. Refine them. Fix organization issues. Add connections.
Phase 5: Build review schedule
Set regular review times to maintain and refine notes.
Weekly: Review notes from that week's lectures. Are they clear? Do they connect to previous material?
Monthly: Review entire module so far. Look for patterns. Create summary notes.
Before exam: Review all notes. Mark areas for focused revision.
### Preventing Common System Failures
Good systems fail for predictable reasons.
Failure 1: Over-engineering
You create complex system that's so elaborate maintaining it becomes burden.
You spend more time organizing notes than studying.
Prevention: Keep it simple. Start basic. Add complexity only if needed.
Failure 2: Passive capture
You create system but still passively transcribe lectures into it.
System is just repository of lecture notes, not learning tool.
Prevention: Be intentional about what you capture. Synthesize instead of transcribing.
Failure 3: No maintenance
You set up system initially then never update it.
Notes become outdated. Organization breaks down. System becomes useless.
Prevention: Schedule review time. Build maintenance into your routine.
Failure 4: Wrong app choice
You choose app that doesn't match your needs.
Prevention: Try free versions first. Spend a week with an app before committing.
Failure 5: No integration with revision
Your notes exist separately from your revision.
During revision, you're reading textbook instead of using notes.
Prevention: Make notes your primary study resource. Design them specifically for revision, not just lecture capture.
### How Digital Note-Taking Affects Your Performance
Good systems directly improve exam performance.
During lectures:
You're capturing information effectively. You understand what matters. You're thinking critically about material while learning it.
During revision:
Your notes are your primary resource. They're organized, searchable, and interconnected.
Instead of spending time finding information, you're studying information.
You're reviewing synthesized material, not raw lecture transcripts.
In exams:
You're confident in your knowledge because you've reviewed systematically.
You can access recall because you've organized information clearly.
The mark impact:
Students with strong note-taking systems typically outperform those without by 8-12 percentage points.
Not because they know different material. Because they've organized material more effectively, reviewed more systematically, and can access knowledge more readily under exam pressure.
### The Bottom Line
Digital note-taking done right is your most powerful study tool.
Done wrong, it's an elaborate filing system you never actually use.
To master digital note-taking:
Choose appropriate app: Match app to your needs, not trends. Simple is often better.
Design structure intentionally: Decide your hierarchy before you start entering notes.
Create templates: Consistency makes notes useful during revision.
Populate incrementally and intentionally: Don't just transcribe. Synthesize as you go.
Review and refine regularly: Notes should evolve as you learn. Maintain them actively.
Make notes your primary study resource: During revision, study from notes, not textbooks.
Start simple. Don't spend hours building perfect system. Start basic. Use it for a week. Refine based on what works and what doesn't.
Your note-taking system should save you time and effort during revision. If it's creating burden, simplify it.
The goal isn't perfect organization. The goal is usable organization that supports your learning.
Master digital note-taking, and you'll have the most valuable revision resource available: clearly organized, carefully synthesized notes on everything you've learned.
That's the difference between having notes and having a note-taking system.
The latter transforms your exam performance.
