Your PhD comps reading list does not need another heroic notebook; it needs a cockpit. When the list grows from “ambitious” to “small private weather system,” Obsidian can turn scattered PDFs, half-lit marginal notes, seminar memories, and exam anxiety into a working map. In about 15 minutes, you can build a practical setup that helps you track what to read, what to remember, and what still looks suspiciously untouched. This guide gives you a simple Obsidian structure, a repeatable reading workflow, and a comps-friendly review system without turning your vault into a digital attic with a search bar.
Why Obsidian Works for PhD Comps
Comprehensive exams are not only a test of reading. They are a test of retrieval under pressure. You are asked to remember arguments, methods, debates, dates, schools of thought, and the odd article your adviser mentioned once in a hallway, as if it arrived carved on stone tablets.
Obsidian works well because it stores notes as local Markdown files, supports internal links, and lets you build structure gradually. That matters for PhD comps because your understanding changes. A book that looked “background” in September may become the hinge of your entire exam answer in March.
I once watched a doctoral student maintain three systems at once: a spreadsheet for readings, a Word document for summaries, and sticky notes on a kitchen cabinet. The cabinet knew too much. Obsidian lets the cabinet retire with dignity.
What Obsidian solves
A good Obsidian setup helps you answer four questions fast:
- What have I read?
- What do I still need to read?
- What does each text argue?
- How do these texts speak to one another?
That fourth question is where comps prep becomes doctoral thinking. Not “Smith says X.” More like: “Smith responds to Jones by shifting the unit of analysis, while Lee later critiques both for ignoring institutional scale.” That is the exam-answer honeycomb.
Why not just use a spreadsheet?
A spreadsheet is excellent for tracking. It is less excellent for thinking. Obsidian can do both. You can use properties for status, author, year, field, theme, and exam list, while still writing prose notes beneath the metadata.
Think of the spreadsheet as a clipboard. Think of Obsidian as a reading room with secret doors. Both have their place, but only one lets a concept in one book knock politely on the wall of another.
- Use it for both metadata and written thinking.
- Let links show relationships between authors and concepts.
- Keep the system boring enough to survive a bad week.
Apply in 60 seconds: Create one note called “Comps Home” and make it the front door of your vault.
Who This Is For / Not For
This setup is for PhD students preparing for comprehensive exams, qualifying exams, field exams, or major reading-list reviews. It also works for master’s students preparing thesis literature reviews, but the design assumes a large reading load and a need for synthesis.
This is for you if
- You have 80 to 400 readings across several fields, lists, or exam areas.
- You need to compare authors, theories, methods, and debates.
- You already use Zotero, Mendeley, EndNote, PDFs, or a departmental bibliography.
- You want a system that works offline and does not trap your notes in a fragile app format.
- You want less panic-searching and more “I know exactly where that argument lives.”
This may not be for you if
- You only need a one-page reading tracker for a short seminar.
- You hate plain text and prefer visual dashboards above all else.
- Your department requires all notes inside a specific institutional platform.
- You spend more time designing systems than reading. No judgment. Many of us have polished the lantern instead of walking into the cave.
The promise and the boundary
Obsidian will not read Foucault for you. It will not make a 900-page historiography become a charming pamphlet. It will, however, give every reading a home, every argument a handle, and every exam theme a path back to evidence.
| Situation | Best Choice | Why |
|---|---|---|
| Under 40 readings | Spreadsheet plus simple notes | Low overhead wins. |
| 80+ readings across fields | Obsidian vault | Links and synthesis notes start paying rent. |
| Heavy citation work | Obsidian plus Zotero | Bibliographic data stays cleaner. |
| Very low tech patience | Start with five folders only | A smaller system is easier to trust. |
Core Vault Structure
Your vault structure should be boring, stable, and easy to explain while holding a cold cup of coffee. If your folders require a diagram, a priest, and three plugins to understand, the system is already chewing on your sleeve.
Start with this folder structure:
00_Comps_Home 01_Readings 02_Field_Notes 03_Concepts 04_Exam_Answers 05_Templates 06_Archive 99_Attachments
00_Comps_Home
This is your dashboard, but keep it humble. It should link to your major lists, weekly plan, exam themes, and unread readings. Avoid turning it into a glowing spaceship panel unless that genuinely helps you read.
A student once told me her dashboard had more widgets than her car. She was proud until she realized she had not opened an actual article in three days. The dashboard should point toward reading, not become the reading.
01_Readings
Every book, article, chapter, report, or major primary source gets one note here. Use a consistent naming convention:
AuthorYear - Short Title.md Ahmed2019 - What Is Islam.md Scott1998 - Seeing Like a State.md Tsing2015 - Mushroom at the End.md
Consistency matters because you will search your vault when your brain is wearing socks on its hands. Use names that are readable, not cryptic.
02_Field_Notes
Create one note per exam field, committee list, or thematic cluster. Examples:
- Field - Political Theory
- Field - Environmental Humanities
- Field - Race and Empire
- Field - Methods and Historiography
These notes become your bridges. They summarize patterns across readings instead of storing one reading at a time.
03_Concepts
Concept notes are for ideas that recur across texts: biopolitics, settler colonialism, affect, state capacity, archive, sovereignty, labor discipline, modernization, ritual, gendered space, and whatever else keeps appearing like a scholarly raccoon at midnight.
Each concept note should include definitions, key authors, disagreements, examples, and exam-ready framing.
04_Exam_Answers
This folder holds practice answers, outlines, timed drills, and question banks. Your goal is not only to know the reading list. Your goal is to answer under exam conditions with calm, organized force.
For adjacent productivity systems, you may find this related guide useful: time management strategies for overwhelmed workers. The same principle applies to comps: the system must protect energy, not merely organize ambition.
Build a Reading List Database That Stays Human
A PhD comps reading list database should track progress without turning you into a clerk for your own anxiety. The goal is not perfect metadata. The goal is reliable orientation.
Use Obsidian properties at the top of each reading note. You can add them manually, through templates, or with supported Obsidian features. Keep the fields limited at first.
Recommended properties
--- type: reading status: unread author: year: title: field: themes: - exam-list: - priority: medium pages: read-date: citation-key: ---
Notice what is missing: twenty-seven little boxes for vibes, difficulty, snack pairing, and the moon phase under which the article was assigned. You can add more later. At the beginning, fewer fields mean fewer excuses.
Status options
Use a small status menu:
- unread: not started
- skimmed: inspected intro, conclusion, headings, or reviews
- reading: actively in progress
- noted: literature note completed
- synthesized: connected to at least one field or concept note
- exam-ready: usable in a timed answer
The jump from “noted” to “exam-ready” is where many students overestimate progress. A summary is not an exam answer. It is lumber. Useful, yes. But someone still has to build the house.
Eligibility checklist: what belongs in the database?
- Required books and articles from committee lists
- Optional readings your adviser repeatedly mentions
- Foundational works you cite in several practice answers
- Key review essays or historiography pieces
- Primary texts only if your exam expects direct discussion
Do not put every random PDF into the comps database. A reading list is a gate, not a swamp.
| Need | Spreadsheet | Obsidian |
|---|---|---|
| Progress tracking | Excellent | Good with properties |
| Argument summaries | Awkward | Excellent |
| Concept linking | Weak | Strong |
| Timed answer prep | Limited | Strong |
- Use six to ten properties at first.
- Track status in plain language.
- Only include readings that matter for exam performance.
Apply in 60 seconds: Pick one status menu and use it for every reading note starting today.
The Literature Note Template for Comps Reading
The literature note is the heart of your Obsidian setup. This is where a reading becomes usable knowledge. Not pretty knowledge. Usable knowledge. There is a difference, and comprehensive exams are famously uninterested in pretty piles.
A clean template
--- type: reading status: reading author: year: title: field: themes: priority: citation-key: --- # AuthorYear - Short Title ## One-sentence claim Write the central argument in one sentence. ## Why this matters for comps Explain how this reading fits the field, debate, method, or exam theme. ## Core argument - Main claim: - Supporting claim 1: - Supporting claim 2: - Supporting claim 3: ## Method / evidence What sources, data, archive, theory, or method does the author use? ## Key terms - Term: - Definition: - Related concept note: ## Useful quotes or page references - p. 12: - p. 48: - p. 101: ## Connects to - [[Concept - ]] - [[Field - ]] - [[AuthorYear - ]] ## Possible exam use Use this reading to answer questions about: ## Critique What are the limits, blind spots, or counterarguments? ## Memory hook One weird, vivid, or plain-English way to remember it.
The memory hook may feel silly, but it works. One student remembered a dense institutional theory article as “the one where rules become furniture.” Not elegant. Extremely useful at 9:00 a.m. during a timed exam.
What to write first
Do not start with quotes. Start with the one-sentence claim. If you cannot write it, the reading is not yet yours. That is not failure. That is the smoke alarm doing its job.
Use this formula:
In this text, [Author] argues that [main claim] by showing [evidence/method], which matters because [field-level significance].
How long should each note be?
For most articles, aim for 300 to 700 words. For major books, 800 to 1,500 words may be reasonable. If every note becomes 3,000 words, your vault is wearing a velvet cape and refusing to do chores.
A quick rule:
- Minor reading: one claim, three bullets, two links
- Core article: claim, argument, method, critique, exam use
- Major book: chapter map, field significance, multiple concept links
Short Story: The Article That Would Not Sit Still
Maya had one article on her list that kept turning slippery. She read it twice, highlighted half the PDF, and still could not explain it without beginning, “It’s kind of about power, but also language, but also institutions.” The article had become academic soup. So she opened one Obsidian note and forced herself to write only three lines: the author’s claim, the evidence used, and the debate it joined. It took twenty minutes and one dramatic sigh. Then something changed. The article did not become easy, but it became positioned. A week later, when she drafted a practice answer, that same note gave her a clean transition between two theorists. The lesson was not “write perfect notes.” The lesson was smaller and more durable: when a text feels foggy, make it answer three plain questions before you ask it to become brilliant.
Zotero and Citation Workflow
For most PhD students, Zotero and Obsidian should work as partners, not rivals. Zotero is your reference manager. Obsidian is your thinking space. When they switch jobs, everyone gets cranky.
Use Zotero for bibliographic records, PDFs, citation styles, and collections. Use Obsidian for literature notes, synthesis notes, exam plans, and concept maps.
The basic workflow
- Add the reading to Zotero.
- Clean the title, author, year, publication, and DOI if needed.
- Add the item to a Zotero collection named after your comps field.
- Create or copy a citation key.
- Create an Obsidian literature note using the same citation key or author-year pattern.
- Link the note to field and concept notes.
One doctoral candidate told me her citations were “mostly fine,” which in dissertation language can mean anything from tidy to a raccoon holding a library card. Clean them early. Future-you deserves mercy.
Recommended citation-key format
Use a format that remains readable:
smithStatePower1998 brownArchiveSilence2012 nguyenMigrationMemory2020
Readable citation keys help when you write in Markdown, LaTeX, Google Docs, Word, or any mixed academic toolchain. Even if you never write final prose in Obsidian, stable keys prevent citation chaos later.
Do you need plugins?
You can build a strong system with core Obsidian features alone: folders, links, templates, properties, search, tags, and daily notes. Plugins can help, but install them slowly. Every plugin is a little houseguest. Some wash the dishes. Some rearrange the furniture at 2:00 a.m.
| Question | Why It Matters |
|---|---|
| Does it support plain-text export? | Your notes should remain usable if you leave the tool. |
| Can you restore deleted files? | Comps season is not the time for file tragedy theater. |
| Does it work offline? | Libraries, trains, and campus Wi-Fi all have moods. |
| Is your data readable outside the app? | Markdown gives you more long-term control. |
Show me the nerdy details
For a stable academic workflow, separate bibliographic truth from interpretive notes. Bibliographic truth includes author names, dates, titles, journal details, DOI, ISBN, and citation keys. Keep that in Zotero or your chosen reference manager. Interpretive notes include your summary, critique, exam use, and links to concepts. Keep those in Obsidian. This separation reduces duplication, makes citation cleanup easier, and prevents your reading notes from becoming brittle if a plugin changes. The method also supports future writing because your citations remain structured while your ideas remain flexible.
For a broader note-taking comparison, this internal guide on note workflow habits pairs well with the Obsidian setup here.
Daily Reading Workflow for Tired Humans
The best Obsidian setup is the one you can use on a Thursday afternoon when your brain has become oatmeal with footnotes. Build the workflow for the tired version of yourself, not the mythical self who wakes at 5:00 a.m. and reads German theory with lemon water.
The 45-minute reading loop
Use this loop when you are short on time:
- 5 minutes: Preview the reading. Check abstract, intro, headings, conclusion, and bibliography.
- 25 minutes: Read actively. Mark argument moves, not every beautiful sentence.
- 10 minutes: Fill the literature note template.
- 5 minutes: Add two links: one field note and one concept note.
This will not capture everything. Good. Comps prep is not the art of capturing everything. It is the art of capturing what you can use.
The 15-minute rescue workflow
On grim days, use this:
- Read the abstract, introduction, and conclusion.
- Write one sentence: “This text argues…”
- Add status: skimmed.
- Add one reason it may matter for the exam.
That is not cheating. That is triage. Emergency rooms do not alphabetize the bandages before helping the patient.
Weekly review
Once a week, open your Comps Home note and answer:
- Which readings moved to “exam-ready”?
- Which field is being neglected?
- Which concept has too many links but no synthesis?
- Which practice answer should I draft next?
One student I worked with did this every Friday with a cheap pastry and a timer. She called it “the pastry audit.” The pastry did not write the notes, but morale is not a minor variable.
- Use a 45-minute loop for normal days.
- Use a 15-minute rescue workflow for hard days.
- Review weekly so the vault does not drift.
Apply in 60 seconds: Add a “This week” checklist to your Comps Home note.
Mini calculator: reading pace estimate
Use this simple calculator to estimate how many readings you need per week. It is intentionally plain. No fireworks, no guilt confetti.
Comps Reading Pace Calculator
Enter your numbers and calculate your weekly target.
Synthesis Notes and Exam Answers
Literature notes help you remember individual texts. Synthesis notes help you think across them. For comprehensive exams, synthesis is the golden hinge.
Create one synthesis note for each major exam theme. Examples:
- Theme - State Power and Legibility
- Theme - Archive and Silence
- Theme - Race, Labor, and Capital
- Theme - Methods Debate: Ethnography vs. Archives
- Theme - Environmental Crisis and Governance
The synthesis note template
# Theme - [Name] ## Exam-ready claim A clear argument you could defend in a timed answer. ## Main debate What are scholars arguing about? ## Key camps ### Camp 1 - Authors: - Claim: - Evidence: ### Camp 2 - Authors: - Claim: - Evidence: ## Tensions - Tension 1: - Tension 2: - Tension 3: ## Best readings to cite - [[AuthorYear - Short Title]] - [[AuthorYear - Short Title]] - [[AuthorYear - Short Title]] ## Possible exam questions - Question 1: - Question 2: ## Practice answer outline Intro: Body 1: Body 2: Body 3: Conclusion:
Move from “about” to “argues”
Weak synthesis says, “These readings are about state power.” Strong synthesis says, “These readings disagree over whether state power operates mainly through coercion, classification, consent, or infrastructure.” That sentence has teeth.
When you build synthesis notes, use verbs: argues, contests, reframes, extends, rejects, complicates, historicizes, revises. Verbs keep the note alive.
Practice answers inside Obsidian
Create one note for each practice question. Use a naming pattern:
Practice - State Legibility and Resistance Practice - Methods in Migration History Practice - Canon Formation in Literary Studies
Each practice answer should include:
- A thesis in two sentences
- Three to five readings you can use well
- One counterargument
- One sentence explaining why the debate matters
A helpful internal companion is this guide on organizing a home library. A comps vault is, in spirit, a library with a pulse.
Visual Vault Map
Here is a simple visual model of how your Obsidian comps vault should move. The flow is not linear forever. It is a loop: reading creates notes, notes create synthesis, synthesis creates better reading.
Visual Guide: The Comps Vault Loop
Create a note with author, year, field, status, and priority.
Capture claim, method, evidence, critique, and exam use.
Connect the reading to field notes, concept notes, and related authors.
Turn groups of readings into debates, camps, tensions, and claims.
Use synthesis notes to write timed outlines and exam responses.
Risk scorecard: is your vault helping or hiding?
| Signal | Low Risk | High Risk |
|---|---|---|
| Time spent formatting | Under 10 minutes per day | More than actual reading time |
| Links | Meaningful and selective | Everything linked to everything |
| Templates | One reading template, one synthesis template | Twelve templates and no finished notes |
| Exam practice | Weekly outlines or timed answers | Only summaries, no practice |
Common Mistakes
Most Obsidian problems are not technical. They are behavioral problems wearing tiny software hats. The app is flexible, which is lovely until flexibility becomes a fog machine.
Mistake 1: Building the cathedral before reading the book
It is tempting to design the perfect vault before the first serious reading week. Resist. Start with folders, one template, and a dashboard. Add complexity only when the pain is real.
Mistake 2: Writing summaries that never become arguments
A summary says what the author wrote. An exam answer uses that author to build a claim. Every note should include “possible exam use,” even if it is only one rough sentence.
Mistake 3: Over-tagging
Tags can help, but too many become academic confetti. Use tags sparingly for workflow status or broad categories. Use links for meaningful intellectual relationships.
Mistake 4: Treating backlinks as wisdom
A backlink means two notes are connected. It does not mean the connection is useful. Write a sentence explaining the relationship. “Connects to Marx” is less useful than “Both texts treat labor as a social relation rather than only an economic input.”
Mistake 5: Not practicing retrieval
Reading feels productive. Highlighting feels productive. Organizing feels productive. But exams reward retrieval. Close the notes and practice answering. This is where the gears bite.
- Use notes to support claims, not just collect summaries.
- Keep tags and plugins restrained.
- Practice retrieval every week.
Apply in 60 seconds: Open one completed note and add a “possible exam use” sentence.
Privacy, Backup, and Risk
Academic notes can contain unpublished ideas, adviser comments, draft arguments, interview reflections, personal field notes, or sensitive research material. That makes privacy and backup part of the setup, not a decorative afterthought.
This is especially important if your research involves human subjects, confidential archives, institutional review board requirements, Indigenous data sovereignty, health information, minors, political risk, workplace data, or vulnerable communities.
Safety and disclaimer
This guide is educational and practical. It is not legal, university compliance, cybersecurity, or research ethics advice. If your notes include confidential, regulated, or human-subject research data, follow your university’s policies, IRB requirements, grant terms, data management plan, and adviser guidance.
Backup rule: three copies, two places
At minimum, keep:
- One working copy on your computer
- One local backup on an external drive
- One secure cloud or institutional backup, if allowed
The Library of Congress has long encouraged personal digital archiving practices built around keeping files organized, named clearly, and backed up. NIST also publishes cybersecurity guidance that can help users think more clearly about authentication, device security, and data protection.
What not to put in Obsidian without a plan
- Raw interview transcripts with identifiable details
- Medical, legal, or financial records from participants
- Confidential adviser or committee correspondence
- Restricted archival images or documents
- Passwords, API keys, or login credentials
I once saw a student keep everything in one folder named “important stuff.” It contained exam notes, passport scans, fieldwork data, and a lasagna recipe. The lasagna was innocent. The folder was not.
Simple naming and backup hygiene
Use readable folder names. Avoid strange characters in file names. Test your backup by restoring one note. A backup you have never tested is a locked umbrella in a rainstorm.
For related document-control habits, see this internal guide on paper pile triage. Digital and physical clutter often share the same little goblin: delayed decisions.
- Back up your vault in more than one place.
- Keep confidential research data out unless approved.
- Test file recovery before exam season gets loud.
Apply in 60 seconds: Copy your vault to an external drive or approved backup location today.
When to Seek Help
Most setup problems can be fixed with a simpler template and a calmer workflow. But some situations deserve outside help, especially when the issue touches academic requirements, data security, disability access, or mental health.
Ask your adviser or committee when
- You are unsure which readings are truly required.
- Your list has grown beyond what can realistically be prepared.
- You need to prioritize fields before the exam date.
- Your practice answers are drifting away from committee expectations.
Ask your university library when
- You need help with Zotero, citation styles, or database exports.
- You want to organize PDFs legally and efficiently.
- You need access to missing books, articles, or interlibrary loan.
- You are unsure how to manage research data responsibly.
Ask campus IT or research compliance when
- Your notes include confidential research data.
- Your project has IRB or data management requirements.
- You are using cloud sync for sensitive material.
- You need secure storage approved by your institution.
Ask for personal support when
If comps prep is affecting sleep, eating, panic, depression, or daily function, contact campus counseling, a clinician, or a trusted support person. Comprehensive exams are demanding, but they should not quietly consume the whole room.
There is no prize for suffering in perfect formatting. A vault can hold your notes. It should not have to hold your entire nervous system.
FAQ
How do I use Obsidian for a PhD reading list?
Use one note per reading, a consistent folder structure, properties for status and field, and synthesis notes for major themes. Start with a simple dashboard that links to your reading list, field notes, concept notes, and practice answers.
Is Obsidian good for comprehensive exams?
Yes, especially when your exam requires synthesis across many books and articles. Obsidian helps you connect readings, build concept notes, and draft practice answers. It is less useful if you only need basic progress tracking for a short list.
Should I use tags or links in Obsidian for comps?
Use tags for workflow labels such as unread, reading, or exam-ready. Use links for intellectual relationships between readings, concepts, authors, fields, and debates. Links are usually more useful for exam synthesis because they can carry meaning in context.
Do I need Zotero with Obsidian?
You do not strictly need Zotero, but it is highly useful for PhD work. Zotero manages bibliographic data, PDFs, citation styles, and references. Obsidian is better for your own summaries, critiques, synthesis notes, and exam-answer planning.
How many notes should I make for each reading?
For most readings, one literature note is enough. For major books, you may add chapter notes if the book is central to your exam. Avoid making so many notes that you spend more time filing than thinking.
What is the best Obsidian template for PhD comps?
The best template includes a one-sentence claim, field relevance, core argument, method or evidence, key terms, useful page references, links to related notes, possible exam use, critique, and a memory hook. Keep it short enough to complete consistently.
Can I use Obsidian for timed practice answers?
Yes. Create a folder for practice answers and use one note per question. Link each answer to relevant readings and synthesis notes. This helps you move from collecting information to producing exam-ready arguments.
How often should I review my Obsidian comps notes?
Review weekly. Check reading status, neglected fields, weak concept notes, and practice-answer progress. A short weekly review prevents your vault from becoming a beautiful archive of unfinished intentions.
What should I avoid storing in my Obsidian vault?
Avoid storing sensitive human-subject data, confidential institutional files, passwords, restricted archival materials, or private participant information unless your university policies clearly allow it and you have an approved security plan.
Is Obsidian better than Notion for PhD comps?
Obsidian is often better for local Markdown files, offline work, internal links, and long-term control. Notion can be easier for polished databases and sharing. The better choice depends on your privacy needs, writing habits, and tolerance for setup.
Conclusion
The opening problem was not really “too many books.” It was too many books without a cockpit. An Obsidian setup for a PhD comps reading list gives you that cockpit: a place to track readings, write literature notes, connect concepts, protect your files, and practice actual exam answers.
Your next step is small enough to do within 15 minutes: create a Comps Home note, add the seven-folder structure, and make one literature note using the template above. Do not perfect the system first. Put one real reading into it. Let the vault earn its keep the old-fashioned way: by helping you think.
Last reviewed: 2026-06
