Book research and writing accumulates knowledge across multiple dimensions simultaneously: the intellectual content of the book being written, the craft understanding developed through the work of writing it, the professional wisdom gained from navigating the publishing process, and the reading intelligence built through the author's engagement with other books. Without structured note-taking, each of these accumulates in undifferentiated form — or doesn't accumulate at all.
Four templates structure the note-taking contexts that most directly build retrievable author knowledge: reading and research notes, idea development notes, chapter drafting notes, and craft and professional practice notes. Each template captures the layer of knowledge specific to that context in a form that can be retrieved when the relevant need arises — at chapter nine, at the next book's research phase, or at the next editorial conversation.
Template 1: Reading and Research Notes
Reading and research notes are the primary knowledge capture tool for authors during the research phase. They convert reading from an experience into a retrievable research asset.
READING AND RESEARCH NOTES
Source: [Title + Author + Publication + Date]
Type: [ ] Book [ ] Academic article [ ] Journalism [ ] Primary document [ ] Interview
URL (if online): [Link]
Archive URL: [archive.org backup]
Date read/captured: [When]
Page numbers: [For physical books — needed for citations]
PROJECT CONNECTION:
Relevant to: [Book project or "general KB"]
Chapter/section: [Where this might be used]
Argument function: [ ] Core evidence [ ] Counterargument [ ] Background [ ] Key quote
[ ] Opening or anchor [ ] Illustration [ ] Not yet clear
WHAT I CAPTURED:
Key passage(s): [Verbatim for direct quotes; paraphrased with "[paraphrase]" notation]
Specific data or claim: [If statistical or factual — captured verbatim]
MY READING NOTES:
Why this matters for the project: [The connection I see]
How this connects to other sources: [If I notice a relationship to other KB entries]
What this complicates or contradicts: [If this challenges something I thought I knew]
Questions this raises: [What I want to investigate further]
CRAFT NOTE (if applicable):
What this source does particularly well (structurally or prosily): [Craft observation]
How it applies to my own writing: [Specific connection]
CITATION INFORMATION:
Complete citation: [Drafted now, in required format]
FACT-CHECK STATUS:
[ ] Verified [ ] Not yet verified [ ] Flagged for verification
KB UPDATE:
[ ] Added to research KB (project + argument function tags)
[ ] Added to craft KB if applicable
The "what this complicates or contradicts" field is the intellectual honesty field that produces better books. Research that doesn't challenge prior understanding isn't building an argument; it's confirming a bias. The source that complicates something the author thought they knew is often the most intellectually valuable source — it's the place where the argument has to genuinely grapple with difficulty rather than just accumulate supporting evidence.
The "paraphrase" notation in the captured content section is the ethics and accuracy discipline. Noting which captured content is verbatim quotation vs. paraphrase is the habit that prevents accidental plagiarism — passages that were paraphrased during note-taking and not marked as such may be mistaken for quotations when writing.
Template 2: Idea Development Notes
Idea development notes capture the process of working through an argument or idea — the intellectual thinking that happens between research sessions and across the weeks of the research and writing process.
IDEA DEVELOPMENT NOTES
Date: [Date of this note]
Idea: [What idea, argument, or question this note is about]
Project: [What book or project this relates to]
Status: [ ] Initial [ ] Developing [ ] Working hypothesis [ ] Confirmed [ ] Revised
CURRENT FORMULATION:
How I'd state this now: [The clearest version of the idea at this moment]
WHAT SUPPORTS THIS:
Evidence from research: [Cross-references to research KB entries]
My own reasoning: [How I've reasoned to this position]
WHAT COMPLICATES OR CHALLENGES THIS:
Evidence against: [What makes this harder to sustain]
Counterargument: [The best opposing view]
My response to the challenge: [If I have one]
WHAT'S STILL UNRESOLVED:
[ ] Open question: [What I don't yet know or understand]
HOW THIS HAS EVOLVED:
Previous formulation: [How I stated this before]
What changed it: [Reading, thinking, or conversation that developed it]
CONNECTIONS:
Related ideas in KB: [Other ideas this connects to]
Potential for a larger argument: [If this connects to something bigger]
KB UPDATE:
[ ] Idea/argument KB updated
The "how this has evolved" field in idea development notes is the intellectual development record. An idea that's been refined through research and thinking — with the evolution documented — is an argument the author can speak to with genuine depth. An idea that arrived fully formed and hasn't been examined is an assertion.
Template 3: Chapter Drafting Notes
Chapter drafting notes capture what the author learns while writing a chapter: what's working, what isn't, where the argument is strong, where it's weak, and what the chapter needs that it doesn't yet have.
CHAPTER DRAFTING NOTES
Chapter: [Number + working title]
Date: [Date of this note]
Draft status: [ ] Outline [ ] First draft [ ] Revision [ ] Near-final
WHAT I'M TRYING TO DO:
This chapter's argument: [What it must establish]
How it connects to adjacent chapters: [Transitions in and out]
What the reader should think/feel after this chapter: [Intended impact]
WHAT'S WORKING:
[Passages or sections that are doing what they should]
What makes them work: [Why — specific to the craft]
WHAT'S NOT WORKING:
Issue: [Specific problem]
Type: [ ] Argument gap [ ] Unclear prose [ ] Structural problem [ ] Pacing [ ] Other
Proposed fix: [What I think would address it]
RESEARCH GAPS:
Claims made that still need support: [List with approximate location in chapter]
STUCK POINTS:
Where I got stuck: [In the chapter]
What's causing the blockage: [Why this is hard]
What I've tried: [Approaches that haven't worked]
What might help: [Possibilities]
POST-DRAFT REFLECTION:
What this draft taught me about the chapter's argument: [Insight from drafting]
What I'd do differently in revision: [If I could start this chapter again]
What this chapter has clarified about the book's overall argument: [If it has]
KB UPDATE:
[ ] Research KB: verify all claims that need support
[ ] Craft KB: capture anything about what worked or what didn't that generalizes
The "stuck points" field is the diagnostic field that prevents writer's block from becoming invisible. Articulating why drafting has stopped — what's causing the blockage — makes it more tractable than leaving it as the vague feeling that the chapter isn't working. And "what I've tried" documents the dead ends so they don't get re-tried.
Template 4: Craft and Professional Practice Notes
Craft and professional practice notes capture the professional learning that accumulates through the work of writing, publishing, and maintaining a writing career.
CRAFT AND PROFESSIONAL PRACTICE NOTES
Date: [Date]
Type: [ ] Craft insight [ ] Editorial feedback [ ] Professional practice
[ ] Reading observation [ ] Self-critique
IF CRAFT INSIGHT:
The insight: [What I learned about craft]
What prompted it: [What experience or reading produced this insight]
How it applies going forward: [How this changes my approach]
Example: [If applicable — a passage from my own or another's work]
[ ] Craft KB updated
IF EDITORIAL FEEDBACK:
Source: [Editor / Beta reader / Writing group / Other]
Feedback received: [What they said]
What I think about it: [My assessment — do I agree?]
How I'm incorporating it: [What changes, if any]
[ ] Applicable to future work?: [ ] Yes: [How] [ ] No
[ ] Craft KB updated if applicable
IF PROFESSIONAL PRACTICE:
The learning: [What I learned about the business or practice of writing]
Context: [What produced this learning]
What I'd do differently: [Concrete change]
Whether this generalizes: [Is this specific to this situation or broadly applicable?]
[ ] Professional practice KB updated
Editorial feedback captured with "what I think about it" is the professional judgment field. Not all editorial feedback is right; some represents the editor's preferences, some reflects misunderstanding, some is genuinely correct. The author who captures feedback with their own assessment builds the judgment to distinguish useful feedback from feedback to respectfully decline — which is a skill that takes time and reflection to develop.
Key Takeaways
-
The "paraphrase" notation prevents accidental plagiarism. Noting which captured content is verbatim vs. paraphrased at the time of capture prevents passages paraphrased during note-taking from being mistaken for quotations when writing.
-
"What this complicates or contradicts" is the intellectual honesty field. The source that challenges prior understanding is often the most valuable — it's where the argument has to genuinely grapple with difficulty.
-
Chapter drafting notes should include "what I'd do differently in revision." The insight available immediately after completing a draft — while the chapter's problems are fresh — is worth capturing before it's replaced by the optimism of distance.
-
Editorial feedback should be captured with the author's own assessment. Distinguishing editorial feedback worth incorporating from feedback to decline respectfully is a professional judgment that improves with practice and reflection.
-
"Stuck points" with diagnosis is more tractable than undifferentiated writer's block. Articulating specifically why drafting stopped — what's causing the blockage — makes it more tractable than leaving it as a vague sense that the chapter isn't working.
Conclusion
Four note-taking templates structure the professional knowledge contexts most important for authors: reading and research notes with "what this complicates" as the intellectual honesty field and "paraphrase" notation as the ethics discipline; idea development notes with evolution documented, not just the current state; chapter drafting notes with "stuck points" diagnosis and "what I'd do differently" as the post-draft insight capture; and craft and professional practice notes with editorial feedback captured alongside the author's own assessment. The KB update step on each template — routing captured knowledge to the appropriate domain — is what converts individual note-taking into the professional knowledge base that makes each book build on the intellectual and craft work of all the books before it.
Build your author note-taking practice with WebSnips — use "paraphrase" notation in reading notes (mark [paraphrase] vs. verbatim at capture time: the discipline that prevents accidental plagiarism when using notes months later in draft); fill "what this complicates or contradicts" in reading notes (the source that challenges what you thought you knew is more valuable than the one that confirms it; the argument that grapples with complications is stronger than the one that only accumulates supporting evidence); capture idea evolution in development notes (how I stated this before + what changed it + current formulation: the intellectual history shows genuine thinking, not just assertion); write "what I'd do differently in revision" immediately after completing a chapter draft (the insight when problems are fresh is more specific than the insight after distance; and more specific than "this chapter needs work"); capture editorial feedback with YOUR ASSESSMENT (what you think about it: right / reflects editor's preference / misunderstands the intent; building the judgment to accept or respectfully decline is a career-long skill that requires explicit reflection); update KB after every reading session and draft chapter (on-trigger updates — not later, not at the end of the project — are what make the KB function as a live resource rather than a reconstruction exercise).