How to Write an Essay from Your Meeting Notes
How to write an essay from your meeting notes — a step-by-step guide for product managers and strategists who want to turn primary research from user
AI Writing & Creator Studio
How to write an essay from your bookmarks — a step-by-step guide for knowledge workers who want to turn a focused reading project into an argued
A bookmark is a pointer, not a source: it saves the URL, not the text. That distinction matters more for essay writing than for almost any other format, because an essay needs specific, accurately quoted evidence — and a bookmark, on its own, gives you a title and a promise that you found something worth returning to.
Knowledge workers who bookmark consistently build focused libraries around topics tracked for months or years — AI regulation, remote work, a technology category — that could support a genuine argument about what the reading showed. What they can't skip, unlike a web clipping, is reopening each source to extract the exact passage before it can be cited.
WebSnips' essay generator can draft from that extracted evidence once you've gathered it. This guide covers the three-phase process specific to bookmark-based essays — identifying the argument before re-reading, extracting evidence strategically, and drafting from it — so a year of bookmarking turns into a publishable, accurately cited essay.
The essay process differs depending on your source type:
| Bookmarks | Web Clippings | |
|---|---|---|
| What's saved | URL (pointer) | Extracted text |
| Re-reading needed | Yes — must open the page to get the text | No — text is in the clip |
| Quote accuracy risk | Higher (rely on memory or must re-read) | Lower (text is in the clip) |
| Time to essay-ready | Longer (re-read + extract) | Shorter (extract from clip) |
| Bookmark value for essays | High when annotated; lower when URL-only | N/A (clippings are already more essay-ready) |
The implication: if you bookmark a lot but rarely clip, the essay process requires a strategic re-reading step where you open each selected bookmark and extract the specific evidence the essay needs. That step is worth doing — it's faster than an original research pass because you already know why you saved each link — but it's a step that doesn't exist when working from clippings.
The value of annotated bookmarks is exactly here: if you added a context note when you bookmarked ("saved for the specific point about customer-led growth maturity in SMB vs enterprise"), you know which part of the article to read for evidence before you open it.
A bookmark essay is often a "reading project essay" — the synthesis of a sustained reading project on a focused topic. The format:
Structure:
This format is honest about its own process: "I spent [time] reading about X. Here's where I landed and why." It's appropriate for Substack essays, personal blogs, professional newsletters, and LinkedIn long-form. The reading project essay is trusted by readers because it acknowledges the process that produced the argument.
Because bookmarks require re-reading, the essay process has a distinct three-phase structure:
Start with the argument, not the sources. Review your bookmark titles and your context notes (if you saved them) and identify:
The argument should be clear enough that you could state it in one sentence before you open a single bookmark. This is the key difference from "open everything and see what argument emerges" — that approach produces summaries, not essays.
With the argument identified, select 5-8 bookmarks as primary evidence and open each one specifically to extract:
You're not re-reading the full article — you're confirming that the article supports what you think it supports, and extracting the exact text you'll use. This targeted re-reading takes 5-10 minutes per source, not the full reading time.
With 5-8 sources extracted and quoted, draft using the same process as any sourced essay — argument stated, evidence organized by function, complication engaged, conclusion arrived at.
Write this sentence: "After reading widely on [topic], I believe [specific, arguable claim]."
If you can't write it, do more reading first. The essay you're writing is the argument you've formed across a reading project — it should exist in your head before you draft.
From your collection, identify which bookmarks support which parts of the argument:
Select for argumentative function, not for recency or impressiveness.
For each selected bookmark:
This is the extraction step that doesn't exist for web clippings. It's the cost of a URL-pointer library — but if your context notes say which part of the article you saved it for, it's a much faster extraction.
I'm writing a reading-project essay on [topic].
My central argument: [After reading widely on this, I believe X because Y]
My bookmark evidence, extracted and organized by function:
Premise/context bookmark:
Source: [Publication, author, date, URL]
Extracted text: "[Exact quote or finding I'll cite]"
Function: [What this establishes]
Supporting bookmarks:
Bookmark 2:
Source: [Publication, author, date, URL]
Extracted text: "[Quote or finding]"
Function: [What this supports]
[Continue for 5-8 bookmarks]
Complicating bookmark:
Source: [Publication, author, date, URL]
Extracted text: "[The counterargument]"
Function: [This challenges my argument because...]
Draft a 2,000-2,500 word reading-project essay:
- Opens with the question or problem that drove the reading
- Middle develops the argument through prose, organized by argumentative stage
- Cites each source inline: "[Author], writing in [Publication] ([year]), argues..."
- Includes the complicating source as a genuine challenge
- Ends with where the reading project landed — what I now believe, and why
No headers (or sparse), no bullet points, prose format
First-person or second-person voice
Before publishing, verify:
The strategic re-read in Phase 2 makes this fast: you've already extracted the relevant passage, so verification is just confirming the essay matches the extraction.
Reading project: Knowledge worker has 40 bookmarks on remote work and distributed team management accumulated over two years.
Central argument: "Two years of remote work discourse has been dominated by arguments about productivity — is remote better, or is in-office better? The question is wrong. The real question is whether your work requires synchronous collaboration or asynchronous execution, and the answer to that question should determine your work location policy."
Bookmarks selected (5):
Before (opening from a URL-list essay): "Remote work has been widely debated since the COVID-19 pandemic. Some studies show productivity increases, while others show decreases. There are advantages and disadvantages to both remote and in-office work..."
No argument, no citations, the "debate has two sides" structure that produces no original contribution.
After (reading-project essay, opening): "I have 40 bookmarks on remote work. I've been adding to that collection since the spring of 2021, mostly in the hours after yet another conversation about whether to 'return to office.' I've read the Stanford productivity studies, the Microsoft Work Trend Index, the GitLab remote report, the Harvard Business School research on talent mobility, and several hundred thousand words of practitioner writing on distributed teams. Here's what I believe after all of that, stated directly: the return-to-office debate is asking the wrong question.
The question that generates heat — 'is remote work better or worse than in-office?' — presupposes that work is a single thing, that productivity is a single thing, and that the location policy is therefore a single question with a single answer. None of those presuppositions is correct. Choudhury's 2020 Harvard Business School research shows significant productivity gains for software developers working fully distributed — but the same researcher notes that those gains depend heavily on documentation infrastructure and asynchronous communication culture that most companies haven't built. GitLab's 2022 remote work report, drawn from a company of 1,500+ employees with no physical offices, documents what that infrastructure looks like in practice: not remote work as 'office work done from home,' but a fundamentally different operational model..."
The essay opens honestly with the reading project as its source of authority, cites specific researchers by name, and makes a specific argument about what the accumulated reading shows.
I'm writing a reading-project essay on [topic].
My argument (formed across the reading): [Specific claim]
Extracted evidence from my bookmarks:
[5-8 sources: publication, author, date, URL, specific extracted text, function]
Draft a 2,000-2,500 word essay:
- Opens with the reading project ("I've been reading about X...")
- Arguments through prose, minimal or no headers
- Each source cited inline with author + publication + year
- Complicating source engaged seriously
- Concludes with where the reading landed
First-person voice
Writing an essay from your bookmarks converts a reading project into an original argument — one your audience can read and say "I didn't see it that way until now." The additional step (strategic re-reading to extract evidence) is the cost of a URL-pointer library, and it's worth it: bookmark essays that cite specific, verified sources are more credible than those that cite sources from memory. Start with the position your bookmark library has persuaded you toward, select 5-8 bookmarks by argumentative function, re-read strategically to extract the evidence, and draft from there.
To go deeper, check out Web Clipping vs. Bookmarking.
More WebSnips articles that pair well with this topic.
How to write an essay from your meeting notes — a step-by-step guide for product managers and strategists who want to turn primary research from user
How to write an essay from your clipped articles — a step-by-step guide for marketers and content strategists who want to turn their swipe files and
How to write an essay from your knowledge base — a step-by-step guide for remote team leads and ops people who want to externalize institutional knowledge
How to write an essay from your reading notes — a step-by-step guide for students and lifelong learners who take notes while reading and want to develop
How to write an essay from your saved research — a step-by-step guide for writers and journalists who want to turn accumulated research into a well-cited
How to write an essay from your web clippings — a step-by-step guide for knowledge workers and consultants who want to convert their saved web research