How to Write Meeting Recap from A Collection Of Sources

The Richest 90 Minutes in a Lab's Week Usually Goes Undocumented

A weekly lab meeting can cover eight papers, three competing methodological frameworks, two ongoing studies, and a handful of unresolved questions about how to proceed — genuinely the most intellectually dense hour and a half most research groups spend together. Then it ends, and what gets written down almost never matches what happened in the room. Three outcomes are typical:

(a) Nothing gets written, and the discussion survives only in the memory of whoever attended (b) A vague narrative gets written ("we discussed multiple papers on X and decided to try Y") that loses the actual intellectual content within a week (c) A paper-by-paper list gets written that records what each source says but not what the discussion worked out from them

None of these serves the people who most need the record: lab members who missed the meeting, future members trying to understand why the lab works the way it does, or a PI who wants to trace how a decision was reached.

WebSnips' meeting recap generator is built for the alternative: keeping the sources and the discussion in one document, so it's clear which papers framed which moments and where the group's thinking went beyond what the literature actually showed.

---

What Makes an Academic Research Meeting Recap Different

Most meeting recaps serve teams that had a meeting about a topic. Academic research meetings are different: the meeting is often itself a structured engagement with a body of literature, where the sources are not just background context but the actual agenda items.

The differences have implications for the recap format:

Standard team meeting	Academic research meeting
Meeting is about a business problem; sources are context	Meeting often IS a literature engagement; sources are agenda items
Decisions are operational (what will we do)	Decisions are intellectual (what does the evidence support; what do we investigate)
Action items: tasks with owners	Action items: investigative tasks + next readings
Open questions: operational gaps	Open questions: theoretical and methodological gaps
Recap audience: team members, stakeholders	Recap audience: lab members, external collaborators, future project members
Citation is supplementary	Citation is central — the recap is partly a structured reference document

This means the recap structure needs to show the literature engagement explicitly, not just as a list of references at the end.

---

Organizing Your Source Collection for a Recap

Before the meeting, you may have a collection of sources — papers, preprints, datasets, technical reports — that the discussion was organized around. After the meeting, the first step is mapping which sources the discussion actually engaged and how.

POST-MEETING SOURCE ENGAGEMENT MAP

Meeting: [Lab name / Project name, Topic, Date]
Sources brought to the meeting:
  1. [Author(s), Year. Title. Journal/Source] — Discussion engagement:
     □ Heavily discussed — central to a key decision
     □ Referenced as context — framed the discussion but wasn't the focus
     □ Contested — the group debated its findings or methodology
     □ Mentioned but not engaged in depth
     □ Not discussed (agenda item that didn't come up)
     
  2. [Same structure]

Cross-source moments (when two sources were put in dialogue):
  Source A vs. Source B: [What tension or convergence the discussion surfaced]
  Decision or conclusion from this dialogue: [What the group decided about the relationship]

This map shows the intellectual architecture of the meeting — which sources carried weight, where the group put sources in tension, and what gaps weren't filled.

---

Step 1: Identify the Meeting's Intellectual Decisions

Academic meetings make two kinds of decisions that both need to be documented:

Intellectual decisions: "We found the evidence for X to be sufficient / insufficient." "We decided the methodology in Source A is more appropriate for our context than Source B." "We accepted Source C's operationalization of the key concept." These decisions are about what the evidence shows and what the group accepts.

Operational decisions: "We will run pilot study Y before committing to the full design." "Next meeting: review papers on Z." "Anya will draft the methods section draft by [date]." These decisions are about what the lab will do.

Both need to be in the recap, but they serve different purposes and different audiences. Intellectual decisions tell the intellectual history; operational decisions create accountability.

---

Step 2: Capture Source Positions and Group Responses

For each heavily-engaged source, write a paired record: what the source claims and how the group responded.

SOURCE-DISCUSSION PAIR

Source: [Author(s), Year. Title. Journal/DOI]
Central claim engaged in discussion: "[The specific claim from this source that the meeting discussed]"
Group response:
  □ Accepted — group accepted this finding as support for [X]
  □ Accepted with qualification — accepted, but group noted [limitation or caveat]
  □ Contested — group debated whether this finding applies to [our context / methodology / population]
  □ Rejected — group rejected this claim because [reason]

Key exchange or insight from discussing this source:
  "[What was said that was most significant]"
  By whom (optional): [Name or "one participant" or "the PI" if anonymizing]
  
How this shaped the meeting's direction:
  "[What decision or reorientation followed from engaging with this source]"

---

Step 3: Document Cross-Source Tensions and Resolutions

Research meetings often spend significant time on questions like: "Source A says X, but Source B found the opposite — which finding applies to our work?" The recap should document these tensions explicitly, along with how (or whether) the group resolved them.

CROSS-SOURCE TENSION RECORD

Sources in tension: [Author A (Year)] vs. [Author B (Year)]
The tension: [Briefly — what they disagree about, and why it matters for the project]
Group's resolution:
  □ Accepted Source A's finding for our context because: [...]
  □ Accepted Source B's finding for our context because: [...]
  □ Decided the tension remains unresolved and requires: [further reading / our own data / methodological decision]
  □ Reframed the question in a way that dissolves the tension: [How]
  
Implication for project direction: [What the group's resolution means for the next steps]

---

Step 4: Draft the Research Meeting Recap

ACADEMIC RESEARCH MEETING RECAP STRUCTURE

Project / Lab: [Name]
Meeting: [Topic / session number / date]
Attendees: [Names or roles]
Sources discussed: [List — all sources brought to the meeting]

MEETING PURPOSE
[One sentence: what the group was trying to accomplish by the end of the session]

INTELLECTUAL DECISIONS MADE
1. [Decision about what the evidence supports / which methodology / which operationalization]
   Grounding: "[Which source(s) supported this decision]" + citation
   Dissent or qualification noted: [If any]
   
2. [Same structure]

CROSS-SOURCE TENSIONS RESOLVED (OR STILL OPEN)
[Each tension documented with resolution or "unresolved — requires..."]

LITERATURE GAPS IDENTIFIED
[Sources the group noted were missing from the collection; questions the literature doesn't address]

OPERATIONAL DECISIONS AND ACTION ITEMS
□ [Owner] — [Deliverable] — [Due date]
□ [Next readings to bring to next meeting]: [Source recommendations]

OPEN QUESTIONS (unresolved)
□ [Question] — Who needs to address it and by when: [...]

NEXT MEETING
Date: | Agenda: [What needs to be brought / what will be discussed]

SOURCES CITED IN DISCUSSION
[Full reference list for all sources engaged in the meeting]

---

Before/After Worked Example

Context: A quantitative sociology PhD candidate attended a weekly lab meeting for a project on educational inequality. The group is designing a mixed-methods study and debated three papers on methodology:

1. Lareau, A. (2003). Unequal Childhoods: Class, Race, and Family Life. University of California Press. (Ch. 1-2 — conceptual framework)
2. Chetty, R., Friedman, J.N., & Rockoff, J.E. (2014). "Measuring the Impacts of Teachers: Evaluating Bias in Teacher Value-Added Estimates." American Economic Review, 104(9), 2593-2632.
3. Lubienski, C., & Lubienski, S.T. (2006). "Charter, Private, Public Schools and Academic Achievement." Teachers College Record, 108(7), 1385-1420.

The meeting was 80 minutes. The agenda: decide whether to use a value-added modeling approach (VAM) for teacher quality measurement, or a qualitative approach, or a mixed design.

Before (vague summary):

Lab Meeting — [Date] We discussed three papers. Lareau's work on family dynamics was useful background. The Chetty et al. paper on value-added modeling was debated — some in the group liked the approach, others had concerns. Lubienski on charter vs. public schools was noted as relevant. We decided to go with a mixed-methods design. Kenji will draft the methodology section.

Which concerns? What was the group's resolution of the VAM debate? Why mixed methods? No source quotes. Action item is vague (which methodology section? what draft?).

After (source-grounded research recap):

---

Educational Inequality Lab — Methodology Decision Meeting [Date] | Attendees: [PI name], [4 lab members] Sources discussed: Lareau (2003), Chetty et al. (2014), Lubienski & Lubienski (2006)

MEETING PURPOSE Decide whether to operationalize "teacher quality" using value-added modeling (VAM), qualitative observation, or a mixed approach for the inequality study.

INTELLECTUAL DECISIONS

1. VAM will not be used as the primary measurement approach; will be used as a secondary indicator only. Rationale: Chetty et al. (2014) provides strong evidence that VAM estimates are unbiased when controlling for observable covariates ("the estimates are not biased by nonrandom assignment of students to teachers" under the conditions they study). However, the group noted that Chetty et al.'s conditions — large administrative data, clear outcome metrics — don't match our smaller, multi-site context. The PI noted that VAM applied outside its validated conditions introduces bias rather than controls for it. Resolution: Use VAM as a secondary indicator where administrative data permits; primary measurement qualitative.

2. Lareau's (2003) "concerted cultivation vs. natural growth" framework adopted as the conceptual anchor for family dynamics. Rationale: The group found Lareau's distinction useful for operationalizing family interaction patterns. One lab member noted the framework is primarily applied to race and class, not as a predictor of teacher quality — but the group agreed that the cultural-capital dimension is relevant to our intervention context.

CROSS-SOURCE TENSION RESOLVED

Chetty et al. vs. Lareau's epistemology: Chetty et al. argues that what gets measured is what matters for outcomes; Lareau argues that the social processes that don't show up in administrative data are often the most explanatory. The group decided this is a productive tension for a mixed design, not a contradiction to resolve — quantitative indicators (Chetty framework) capture what; qualitative (Lareau framework) captures why.

LITERATURE GAP IDENTIFIED

Neither source addresses rural contexts. The group flagged this gap for the next meeting: is there comparable research on VAM and teacher quality in non-urban settings?

ACTION ITEMS □ Kenji — Draft methodology section for mixed-methods approach (VAM as secondary indicator, qualitative observation primary) — due [Date, 2 weeks] □ [Lab member] — Find 2-3 sources on VAM or educational inequality in rural contexts — bring to next meeting

OPEN QUESTIONS □ Will rural/non-urban context require us to validate Lareau's framework in our setting? — PI to advise before Kenji's draft is finalized

NEXT MEETING [Date] | Agenda: Review methodology draft; present rural context sources

SOURCES CITED

• Lareau, A. (2003). Unequal Childhoods: Class, Race, and Family Life. University of California Press.
• Chetty, R., Friedman, J.N., & Rockoff, J.E. (2014). Measuring the Impacts of Teachers. American Economic Review, 104(9), 2593-2632.
• Lubienski, C., & Lubienski, S.T. (2006). Charter, Private, Public Schools and Academic Achievement. Teachers College Record, 108(7), 1385-1420.

---

Complete intellectual record; cross-source tension documented with resolution; literature gap explicitly flagged; action items properly formatted.

---

Prompts to Reuse

Meeting Recap From a Collection of Sources

I'm writing a research meeting recap for [Lab/Group, Topic, Date].
Attendees: [Names or roles]
Sources brought to the meeting: [Full citation list]

Source engagement (from post-meeting memory):
For each source that was heavily discussed:
  Source: [Citation]
  Central claim engaged: "[What specifically was discussed]"
  Group response: [Accepted / Accepted with qualification / Contested / Rejected]
  Why: [Brief reason from the discussion]

Cross-source tensions:
  [Source A] vs. [Source B]: [What they disagree about]
  Group's resolution: [Accepted A / B / unresolved / reframed]

Decisions made:
  Intellectual decisions: [What the evidence supports, which approach, which operationalization]
  Operational decisions + action items: [Owner, deliverable, due date]

Open questions:
  [Unresolved methodological/theoretical questions, with who needs to address them]

Literature gaps noted:
  [What sources are missing; what questions the literature doesn't address]

Draft a research meeting recap that:
- Opens with meeting purpose and one-sentence outcome summary
- Documents intellectual decisions with the sources that grounded them (cited)
- Shows cross-source tensions explicitly and documents how (or whether) they were resolved
- Separates intellectual decisions from operational action items
- Includes a "Literature Gaps" section if any were identified
- Closes with full reference list

Attribution rules:
"[Source] argues / shows / found that..." = source's claim
"The group accepted / contested / rejected..." = group's response
"The group decided..." = intellectual or operational decision
Never: presenting the group's decision as the source's claim

---

Key Takeaways

1. Academic research meetings make two types of decisions: intellectual (what does the evidence support) and operational (what will we do next) — both need to be in the recap, clearly distinguished.
2. Document source engagement specifically: which claims from which sources the group engaged, accepted, contested, or rejected — vague "we discussed Source A" is not useful for readers trying to understand the intellectual history.
3. Cross-source tensions are the most valuable content to document: when the group puts two conflicting sources in dialogue, the resolution (or non-resolution) represents genuine intellectual work that should be preserved.
4. Literature gaps belong in the recap: noting what the collection didn't address gives future lab members the next research directions and explains why certain questions weren't resolved.
5. Full citations at the end: a research meeting recap is a reference document as well as a record — the citation list should be complete and properly formatted.

---

Conclusion

A meeting recap from a collection of sources preserves the intellectual work of a research meeting rather than just its operational decisions. For academic groups whose meetings are structured around engaging with literature, this is the core value of the recap: documenting which sources shaped which decisions, where sources contradicted each other and how the group resolved that tension, and what questions the available literature left unanswered. That record is the intellectual history of a project — and without it, each new lab member has to reconstruct the reasoning from scratch.

See also: Building a Personal Knowledge Base.