How to Write Meeting Recap from Competitor Research (With
How to write a meeting recap from competitor research — a step-by-step guide for founders and solo operators who want to document a competitive
AI Writing & Creator Studio
How to write a meeting recap from your highlights — a step-by-step guide for students and lifelong learners who want to produce a synthesis document that
A PhD student walks out of a 90-minute seminar on cultural capital having highlighted key passages across three assigned readings beforehand and watched the discussion draw on all of them. Two days later, sitting down to write the seminar report, she remembers the shape of the argument but not the specifics — was it Bourdieu's own definition the group debated, or someone's gloss on it? Which reading did the digital-participation question actually come from? The standard approach, writing from memory, produces exactly this kind of impressionistic report: right about the general shape of the discussion, unreliable on who argued what and from where.
A meeting recap written from the highlights she made before the seminar avoids this entirely, because the textual anchors are sitting right there as she writes. Instead of a vague gloss, the recap can say precisely which definition was on the table and where it came from — grounding the discussion in the same passages the seminar actually engaged with, rather than a memory of them.
WebSnips' meeting recap generator works the same way: feed it the highlights that were actually discussed, and the specificity that makes a recap useful survives the two-day gap between seminar and write-up.
Highlights play a double role for discussion-based learning:
As meeting prep: You highlight before the discussion to identify the passages you expect to reference, the claims you want to interrogate, and the moments in the text that raise questions you want to bring to the group.
As meeting record: After the discussion, your highlights serve as the textual anchor for what was discussed — each highlight is a potential citation for a claim the discussion built on, a passage someone quoted, or a definition the group debated.
This double role means your highlights can serve as both background research and citation material for the recap. The challenge is knowing which highlights are now relevant (ones the discussion actually engaged with) and which were preparation that didn't end up getting discussed.
The first step after the meeting: go through your highlights and sort them by whether the discussion actually engaged with them.
HIGHLIGHT RELEVANCE SORT
Reading: [Title, Author, Year]
Chapter/Section: [...]
Highlight: "[Highlighted passage]"
Discussion relevance:
□ Directly quoted or referenced in discussion
□ Implicitly engaged (the discussion was about this idea without quoting it)
□ My prep highlight — not actually engaged in discussion
□ Contested in discussion (participants disagreed about this passage's meaning)
If engaged: What was said about it?
"[Brief note of what was said in discussion about this passage]"
This sort produces two categories: highlights that are now evidence for the recap (engaged in discussion), and highlights that were preparation only. The recap uses the first category; the second can stay in your reading notes.
Before drafting, map the discussion's engagement with the assigned texts:
READING ENGAGEMENT MAP
Reading 1: [Title, Author, Year]
Overall engagement level: [Heavy / Moderate / Light / Not engaged]
Themes from this reading that the discussion focused on: [List]
Most-referenced passages: [List with brief context]
Authors' positions on [discussion theme]: "[Their position as you understand it from highlights]"
Reading 2: [Title, Author, Year]
[Same structure]
Cross-reading moments:
Where the discussion put two readings in dialogue with each other:
"[Reading A]'s claim X was discussed alongside [Reading B]'s claim Y"
What the group concluded about this dialogue: [...]
This map becomes the structural backbone of the recap — it shows the discussion's architecture.
The key structural decision for a highlights-grounded meeting recap: organize by TEXT or by THEME?
Organize by text: Section 1 = what was discussed about Reading 1; Section 2 = what was discussed about Reading 2. Useful when the discussion was sequential (went through readings in order) or when the recap audience will read it alongside the original texts.
Organize by theme: Section 1 = Theme X (drawing on multiple readings); Section 2 = Theme Y. Useful when the discussion was thematically organized, or when the recap audience cares about the themes more than the individual readings.
Most academic seminar recaps work better organized by theme, because seminars themselves often draw on multiple readings to address a single question or debate. Your highlight map (showing cross-reading moments) will tell you which themes cut across the readings.
HIGHLIGHTS-GROUNDED RECAP STRUCTURE
Seminar: [Course, Topic, Date]
Readings discussed: [List]
Summary (2-3 sentences): The seminar explored [themes] through [readings].
Key questions: [What questions the discussion centered on]
Tone: [Constructive debate / mostly consensus / exploratory]
Section 1: [Theme 1]
The discussion focused on [specific question or claim].
From [Author]: "[Highlighted passage relevant to this theme]" (Author, Year, p. X)
Discussion engagement: [How participants engaged with this — agreement, complication, debate]
From [Author 2]: "[Contrasting highlighted passage]" (Author 2, Year, p. X)
Discussion outcome: [What the group concluded or where they left this theme]
Section 2: [Theme 2]
[Same structure]
Notable moments:
[Any specific exchanges, unexpected readings of a text, or moments of genuine insight]
Open questions:
[Questions raised in discussion that weren't resolved — these are the seeds of future thinking]
Readings cited:
[Full citation list for all readings]
The discipline for highlights-grounded recaps: you're working with two types of content that need different attribution:
Textual claims: What the assigned authors argue, as evidenced by your highlighted passages. Attribution: "Author (Year) argues that..." + direct quote from highlight if possible.
Discussion claims: What seminar participants said, argued, or concluded. Attribution: "The group noted that..." or "Several participants argued that..." — specific individuals may be named (with permission) or anonymized.
The blend of these two types of attribution is what makes a highlights-grounded recap distinctive: it shows both what the texts argue and how the discussion engaged with those arguments, keeping each clearly attributed.
The common mistake: attributing discussion claims to the text authors ("Foucault argued that surveillance is a form of power that the group found applicable to social media") when the second part is the discussion's claim, not Foucault's. The clean version: "Foucault (1975) argued that surveillance is a form of disciplinary power. The seminar discussion applied this framework to social media platforms, with participants noting that algorithmic content curation shares structural features with Foucault's panopticon."
Context: A second-year sociology PhD student attended a 90-minute seminar on "Space, Power, and Social Control" with three assigned readings:
She highlighted 14 passages across the three readings. The discussion was organized around three questions posed by the instructor. Five of her 14 highlights were directly engaged.
Before (from memory, no highlight grounding):
Seminar Report — Space, Power, and Social Control
The seminar discussed Foucault's panopticon and how it applies to modern prisons. We also talked about Wacquant's article on how prisons and ghettos are connected in the US. Gilmore's book was mentioned but we didn't get to it much. The main debate was about whether Foucault's theory works for racial capitalism.
Completely non-specific; Gilmore's engagement actually more significant than this suggests; "whether Foucault's theory works for racial capitalism" is a vague reconstruction of a more specific debate.
After (highlights-grounded):
Seminar Report: Space, Power, and Social Control [Course Name], [Date], [N] participants
The seminar addressed three questions about the readings: (1) How does Foucault's panopticism model apply to contemporary carceral geography? (2) What does Wacquant's "deadly symbiosis" add that Foucault's framework lacks? (3) How does Gilmore's political-economic analysis relate to both?
Theme 1: The limits of panopticism for race-based analysis
Foucault's core claim in the Panopticism chapter is that modern power operates through surveillance and the possibility of being watched — what he calls "an inspecting gaze" — rather than through spectacle. He writes: "He who is subjected to a field of visibility, and who knows it, assumes responsibility for the constraints of power; he makes them play spontaneously upon himself." (Foucault, 1975, Chapter 3)
The discussion noted that Foucault's framework makes power relatively abstract and formal — a structural relation of visibility — without attending to the racial constitution of who gets surveilled in contemporary US contexts. Several participants found this the most productive tension in the seminar: the panopticon model is analytically useful but racially underspecified.
Theme 2: Wacquant's "deadly symbiosis" as racial-geographic supplement
Wacquant (2001) argues that the ghetto and the prison function as two instruments of the same system: "The ghetto functions as a kind of ethnoracial prison in the city while the prison functions as a judicial ghetto in the legal landscape." (p. 101) This parallel construction was the seminar's most debated passage.
The discussion engaged this claim through two opposing readings. One group of participants saw the symmetry as Wacquant's analytical strength — the "two instruments" framing forces attention to the racial-spatial dimension that Foucault's panopticism omits. Another group found the symmetry overstated: the prison and the ghetto function differently for different populations (women, immigrants, the mentally ill) in ways the neat symmetry obscures.
Theme 3: Gilmore's political-economic frame
Though assigned, Gilmore received less discussion time. The one passage that did come up was her definition of racism as "the state-sanctioned or extralegal production and exploitation of group-differentiated vulnerability to premature death." (Gilmore, 2007, p. 28) Participants found this framing more actionable than Foucault's for policy analysis — it points toward specific structural interventions rather than a generalizable critique of disciplinary power.
Open questions (not resolved):
Specific; textual evidence cited with passage reference; discussion engagement clearly attributed as the group's (not the authors'); open questions captured for follow-up.
I'm writing a seminar recap for [Seminar/Course, Topic, Date].
Assigned readings: [Title, Author, Year — list]
Seminar structure: [How the discussion was organized — questions, themes, reading order]
Highlight inventory (engaged in discussion only):
Reading 1: [Title]
Highlight: "[Passage]" — (Author, Year, p./Chapter X)
Discussion engagement: [What was said about this passage]
Attribution type: [Textual claim / Discussion claim]
Reading 2: [Same structure]
Discussion structure:
Theme 1 / Question 1: [What was discussed]
Which readings engaged: [List]
Key moments: [Specific exchanges or insights]
Conclusion: [Where the group landed]
Theme 2: [Same structure]
Draft a highlights-grounded seminar recap that:
- Opens with summary (seminar topic, organizing questions, tone)
- Organizes by theme (NOT by reading — themes cut across readings more usefully)
- For each theme: names the textual claim from each reading (with highlighted passage), then the discussion engagement
- Keeps textual attribution ("Foucault argues...") and discussion attribution ("the group noted...") clearly separated
- Includes "open questions" section for unresolved threads
- Closes with full citation list
Attribution rules:
Textual: "[Author (Year)] argues that..." + direct highlighted passage where possible
Discussion: "The group noted that..." or "Participants debated whether..."
Cross-reading: "[Reading A's claim] was discussed alongside [Reading B's claim]..."
Never: Attributing the discussion's conclusion to the textual author
A meeting recap from your highlights turns a seminar or discussion session into an intellectually honest document — one that shows not just what was said but what textual evidence it was grounded in, what the group agreed on, what was contested, and what questions remained open. The preparation work is mostly done: you highlighted before the discussion. The recap work is connecting those highlights to what was said, organizing by theme rather than chronology, and keeping textual claims and discussion claims clearly attributed. The result is a document that serves future discussions as well as the one you just left.
To go deeper, check out Building a Personal Knowledge Base.
More WebSnips articles that pair well with this topic.
How to write a meeting recap from competitor research — a step-by-step guide for founders and solo operators who want to document a competitive
How to write a meeting recap from your knowledge base — a step-by-step guide for remote team leads and ops people who want to produce a recap that
How to write a meeting recap from your web clippings — a step-by-step guide for knowledge workers and consultants who want to produce a cited, credible
How to write a meeting recap from a collection of sources — a step-by-step guide for academic researchers and PhD candidates who need to document a lab
How to write a meeting recap from your meeting notes — a step-by-step guide for product managers and strategists who want to convert raw, fragmented
How to write a meeting recap from your saved research — a step-by-step guide for writers and journalists who want to produce a grounded, cited recap that