AI Literature Review Generator: Create a Your Meeting Notes

Meeting Notes Are Literature Too

Formal literature reviews traditionally stop at published sources — journal articles, books, conference papers — on the reasonable assumption that publication is where knowledge becomes official. But knowledge doesn't wait for publication to exist. Working-group discussions, conference sessions, and practitioner consultations contain real evidence of what experts currently know, argue about, and are only starting to figure out — often a year or more before any of it appears in print, and sometimes never, if it stays the kind of tacit knowledge that experienced practitioners have but never quite formalize.

Treating meeting notes as literature means taking that evidence seriously on its own terms rather than as background color for something more official. This isn't a new idea — researchers have a name for it, grey literature or primary source review, and a long tradition of using it. What it means practically here: expert discussions get read for what they show about the state of knowledge at a given moment, not just mined for a good quote.

The payoff is specific. Meetings surface debates and open uncertainty that published papers, built to present settled conclusions, tend to smooth away. What a literature review from meeting notes maps, in other words, isn't a substitute for the published record — it's the layer underneath it that the published record usually leaves out.

---

Meeting Notes Literature Review Types

The primary source review

Treating meeting notes as primary documents that evidence what was known, discussed, and debated at a given time:

Structure:

• Introduction: The topic; the meetings being reviewed (what they were, who participated, when); why meeting notes constitute primary evidence worth reviewing
• State of knowledge at the time of these discussions: What the meeting discussions reveal participants understood about the topic when the meetings occurred
• Active debates: The questions and controversies the meetings reveal were actively debated among these experts
• Points of consensus: What the discussions reveal was broadly accepted
• Points of uncertainty: What experts acknowledged they didn't know — the explicit uncertainties in expert discussion
• Emerging positions: New ideas, framings, or approaches that appear in the meeting discussions
• Relationship to published literature: How what experts discussed in meetings relates to what appeared in published literature around the same time — convergences and divergences
• Conclusion: What the meeting notes as primary sources reveal about the state of knowledge on this topic

The primary source review is most valuable for historical research (what was known and debated at a specific time?), organizational research (how did institutional knowledge develop?), and documentation of practitioner knowledge that precedes publication.

The practitioner discourse synthesis

For meetings with domain experts, practitioners, or subject matter specialists — synthesizing what the expert discourse reveals:

Structure:

• Introduction: The meetings being reviewed (expert panels, working groups, practitioner consultations); what makes these discussions valuable sources of domain knowledge
• Expert consensus: What participants across meetings consistently agreed on — the practitioners' shared understanding
• Expert disagreement: Where expert views diverge — what practitioners with deep experience see differently, and what this suggests about the actual complexity of the topic
• Practitioner-specific knowledge: What the meeting discussions reveal practitioners know from experience that isn't in the published literature — the tacit dimension
• Practitioner concerns: What experts flagged as important problems, risks, or concerns that aren't yet in published literature
• Emerging frameworks: Conceptual frameworks that appear in the discussions — practitioner ways of understanding the topic that may or may not have formal articulation yet
• Synthesis: What the practitioner discourse collectively reveals about the topic that formal literature doesn't yet capture
• Implications: What the practitioner discourse suggests about where formal research should go

The organizational knowledge audit

Reviewing an organization's meeting notes to map what the organization knows about a topic:

Structure:

• Introduction: The organizational context; the meeting notes being reviewed; what this audit is meant to establish about organizational knowledge
• What the organization understands well: Topics on which the meeting discussions reveal consistent, well-developed organizational knowledge
• What the organization debates internally: Topics on which organizational meetings reveal ongoing internal disagreement
• Knowledge gaps: Topics where the meeting discussions reveal acknowledged gaps in organizational understanding
• Knowledge that hasn't been formalized: Expertise that appears in meeting discussions but hasn't been captured in formal documentation
• Outdated knowledge: Positions held in earlier meetings that have since been updated or contradicted
• Knowledge acquisition: What the organization has been learning — how knowledge on the topic has developed across the period of the meetings
• Recommendations: What the knowledge audit reveals about what the organization should document, study further, or reassess

---

Annotating Meeting Notes for Literature Reviews

The discussion context annotation

Meeting notes require context to be interpretable as literature:

"Discussion context annotation:

• Meeting type: [expert panel / working group / practitioner consultation / internal team meeting / conference session]
• Participants: [how expert they are — not names, but characterization: e.g., 'four product practitioners averaging 12 years experience' or 'three academic researchers active in this field']
• Stakes and context: [what were these discussions in service of? high-stakes decisions produce different discussions than exploratory conversations]
• Recording quality: [verbatim transcript / detailed notes / summary notes — affects how closely the notes can be quoted as primary evidence]
• Confidentiality: [if the meetings were confidential, the literature review should handle attribution carefully]"

The expertise calibration annotation

For practitioner discourse synthesis — establishing how to weight expert views:

"Expertise calibration annotation:

• Expert [A]: [area of expertise; specific experience relevant to this topic; why their views have particular weight or particular limits]
• Expert [B]: [same]
• Consensus assessment: [when multiple experts agreed, were they speaking from similar or diverse experience? Same-background consensus is weaker evidence than diverse-background consensus]
• Dissent significance: [when experts disagreed, what does the disagreement reveal? — different experience bases, genuinely contested questions, or different frameworks for understanding the topic]"

---

Configuration for Meeting Notes Literature Review Generation

The primary source review configuration

"Generate a primary source review from the meeting notes, treating the notes as primary documents that evidence what was known, discussed, and debated at the time of these discussions. The review should be organized chronologically or thematically — not by meeting, but by what the meetings collectively show about the topic. 'Active debates' should be specific: what was the actual content of the debates? 'Relationship to published literature' requires honest comparison: where did expert discussion precede publication, follow it, or diverge from it? If the notes are from confidential discussions, attribute to 'one participant' or 'several participants' rather than to named individuals."

The practitioner discourse configuration

"Generate a practitioner discourse synthesis from the meeting notes, focusing specifically on what experts with practical experience discussed that goes beyond or precedes the formal literature. The 'practitioner-specific knowledge' section is the core of this review: what do the meeting discussions reveal practitioners understand from experience that isn't yet in formal publications? This should be specific — not 'practitioners have deep experience' but 'practitioners in these discussions consistently reported that [specific finding], which contrasts with the formal literature's assumption that [formal assumption].' Cite specific meeting discussions throughout."

---

Key Takeaways

1. Meeting notes constitute primary literature — expert discussions, working group notes, and practitioner consultations contain knowledge that precedes publication; treating them as primary sources enables literature reviews that capture current and tacit knowledge.
2. Three meeting notes literature review types: primary source review (treating meeting notes as primary documents evidencing the state of knowledge at a time), practitioner discourse synthesis (mapping what experts discuss that goes beyond the published literature), organizational knowledge audit (mapping an organization's documented knowledge base).
3. Discussion context annotation establishes the interpretive basis — meeting notes need context (who participated, what the meetings were for, how the notes were recorded) to be used credibly as primary literature.
4. Expertise calibration assesses how to weight expert views — diverse-background expert consensus is stronger evidence than same-background consensus; expert disagreement reveals where the topic is genuinely contested.
5. Meeting notes capture the debate before publication — the unpublished discussions reveal controversies, uncertainties, and emerging positions that the published literature, with its emphasis on settled conclusions, often smooths over.

---

Conclusion

Meeting notes — expert panels, working group discussions, practitioner consultations, organizational deliberations — contain knowledge that formal publication apparatus doesn't capture: the debates before conclusions are settled, the practitioner insights before they're formalized, the institutional knowledge before it's documented. The literature review from meeting notes takes this knowledge seriously as primary evidence, treating expert discussion as a form of literature that reveals the state of knowledge in ways that published sources can't. The primary source review maps what expert discussions revealed was known, debated, and uncertain at a specific time. The practitioner discourse synthesis extracts what practitioners with deep experience know from practice — the tacit dimension of professional knowledge that often precedes and sometimes diverges from formal research. The organizational knowledge audit maps what an organization knows, debates, and has yet to formalize. WebSnips captures meeting notes with discussion context, expertise calibration, and discourse quality annotations that guide the Creator Studio to generate literature reviews that treat expert knowledge — wherever it exists — as worth systematic review.

For more on this, see Best Web Clipper Extensions.