How to Write Meeting Recap from Your Saved Research (With

An Unsourced Claim in a Meeting Becomes a Fact the Moment It's Written Into the Recap

Say someone in a strategy meeting states that "churn is well above the industry average," with no source behind it, and watch what happens next: the standard recap records it as if it were established. That's the quiet failure built into most meeting recaps — they're logs, faithfully recording who said what and what got decided, and a log inherits the meeting's information quality without ever checking it. A reader who wasn't in the room learns what was argued, not whether it was true.

If you'd gathered research before the meeting — market data, published studies, competitor analysis — that same claim doesn't have to go unexamined in the write-up. The recap can note what the actual industry benchmark is, and whether the claim as stated holds up.

That's the specific upgrade a meeting recap from your saved research makes possible: a document that connects what was discussed to evidence you can verify, rather than just recording that the discussion happened. WebSnips' meeting recap generator is built to make that connection — pulling in the research you already gathered wherever it's relevant to what got said in the room.

This format is most valuable for:

• Writers and journalists covering organizational decisions, policy discussions, or strategic briefings who need to produce a recap that a general audience can evaluate critically
• Knowledge workers presenting a research debrief and then writing a follow-up document that captures both what the research shows and what the team decided based on it
• Consultants delivering a research synthesis meeting who need a written record that shows the evidence behind each decision

---

The Two Modes of Saved Research for Meeting Recaps

Saved research enters a meeting recap in two distinct modes, and it's important to know which mode you're in:

Mode 1: You saved research to prepare for the meeting

You gathered background research before the meeting — to brief yourself, to anticipate questions, to understand the territory. The meeting happened, and now you're writing a recap. Your pre-read research gives you factual grounding to verify what was said, provide context for audience members who weren't prepared, and ground specific claims in evidence.

Mode 2: The saved research IS the content of the meeting

The meeting was itself a research synthesis session — a research debrief, a competitive intelligence briefing, an editorial planning meeting based on accumulated research. In this case, the research isn't background context; it's the substance that was presented and discussed. The recap needs to summarize the research and capture how participants responded to it.

The writing process is slightly different for each mode, but both produce a superior product to the standard meeting-as-log format.

---

When Saved Research Elevates a Meeting Recap

The specific things saved research adds to a meeting recap:

Verified evidence for factual claims made in discussion: A meeting participant says "productivity drops significantly for remote workers after 18 months" — your pre-saved research includes a Stanford/Bloom (2015) study on remote work that provides an actual, citable data point. The recap can include this: "Research supports this concern: Stanford's landmark remote work study found that remote call-center workers showed lower promotion rates than in-office counterparts over 21 months, though productivity (as measured by completed calls) was higher for remote workers during that period. The productivity/career-trajectory tradeoff the team discussed reflects a real and documented tension."

Context that meeting participants assumed but didn't explain: Industry context, historical precedent, or field background that meeting participants knew but didn't articulate. Your research lets you add this context for readers who weren't in the room.

Correction of inaccurate claims (handled carefully): When a claim made in the meeting contradicts what your research shows, the recap can note the discrepancy accurately. This requires judgment — recaps aren't editorials — but an accurate recap can say "The team's consensus view was X; published research on this topic suggests the relationship is more nuanced" rather than simply recording an inaccurate claim as fact.

Citations that give the recap credibility: A recap that says "the team agreed that subscription models outperform transactional ones for SaaS retention" is making an assertion. A recap that says "the team agreed this aligns with published research: Zuora's 2022 Subscription Economy Index found subscription business model revenue growth runs at 3-4x the rate of companies in the S&P 500" gives readers something to evaluate and builds trust in the document.

---

Step 1: Organize Your Research Before Writing

Before writing the recap, organize your saved research by the topics discussed in the meeting:

RESEARCH-TO-MEETING TOPIC MAP

Meeting: [Title, Date, Participants]

Topic 1 discussed: [What was discussed — e.g., "churn rate vs. industry benchmark"]
  What was claimed in the meeting: "[The specific claim]"
  Research I have that's relevant:
    1. [Source, Author, Year] — [What it shows relevant to this topic]
       Key finding/data: "[Specific data or finding]"
  Verification status: [Claim supported / partially supported / contradicted / unverifiable]

Topic 2 discussed: [...]
  What was claimed: [...]
  Research: [...]
  Verification: [...]

Decisions made:
  Decision 1: "[What was decided]"
    Research that informed this decision: [Source]
    Whether this decision aligns with what the research shows: [Supported / Partial / Mixed]
    
Action items:
  [Standard action items — these don't need research verification, just accurate capture]

---

Step 2: Select the Recap Format Based on Purpose and Audience

Meeting recaps serve different audiences and therefore need different formats. With research to draw on, you have more format options than the standard log provides:

The Decision Record format: Focuses on what was decided and why, with the research supporting each decision. Useful for strategic planning, product decisions, or any meeting where the decisions need to be justified to stakeholders who weren't present.

The Research Debrief format: Suitable when the meeting was itself a research presentation. Structured as: research presented → key findings → team response and discussion → decisions or next questions. Best for teams conducting ongoing research programs.

The Evidence-Grounded Summary: A hybrid of summary and analysis. Presents what was discussed in the order it happened, but integrates research context and citations to ground each major topic. This is the most common mode for writers and journalists covering meetings.

The Briefing Memo: Inverts the standard recap format — leads with conclusions and decisions, then provides supporting evidence and discussion for each. Best for executive audiences who want the so-what before the how-we-got-there.

FORMAT SELECTION CHECKLIST

Who will read this recap?
  □ Meeting participants (who were there and need a reminder)
     → Standard summary format is fine; research = verification layer
  □ Stakeholders who weren't present (need context)
     → Evidence-grounded summary or Briefing Memo
  □ Executive decision-makers (want decisions + evidence)
     → Decision Record or Briefing Memo
  □ External audience (writers, journalists — needs source transparency)
     → Research Debrief with full citation
  □ Public record (policy, official proceeding)
     → Decision Record with comprehensive citation

What was the meeting's primary output?
  □ Decisions → Decision Record format
  □ Research synthesis → Research Debrief format
  □ Strategic alignment → Evidence-Grounded Summary
  □ Project progress → Standard log with research grounding for specific claims

---

Step 3: Draft the Grounded Recap

Start with the meeting's structure — what topics were covered, in what order — and integrate your research at each juncture where it adds value.

EVIDENCE-GROUNDED RECAP DRAFT STRUCTURE

Meeting: [Title, Date, [N] participants]
Purpose: [What the meeting was trying to accomplish]
Outcome summary: [1-2 sentences — what was decided or produced]

Section 1: [Topic 1 from the meeting]
  What was discussed: [The discussion, 2-4 sentences]
  Research context: "This discussion reflected a documented pattern in the literature:
    [Specific finding from saved research, attributed]." — [Citation]
  Decision or conclusion: "[What the group concluded on this topic]"
  Supporting evidence: "[Research finding that grounds this decision]" — [Citation]

Section 2: [Topic 2]
  [Same structure]

Key decisions:
  1. [Decision] — Rationale: [Brief + research citation if applicable]
  2. [Decision] — Rationale: [...]

Action items:
  □ [Task] — Owner: [Name] — Due: [Date]
  □ [Task] — Owner: [Name] — Due: [Date]

Next meeting: [Date, agenda]

Sources consulted:
  [Full citation list for all research referenced in the recap]

---

Before/After Worked Example

Context: A senior content strategist at a digital media company attended a 90-minute editorial strategy meeting about whether to shift their content mix toward video and audio formats. She had saved 6 pieces of research in preparation: a Reuters Institute Digital News Report chapter on audio content, an Pew Research report on video news consumption, a NiemanLab analysis of hybrid content strategies, and two industry case studies on publication format shifts.

The meeting involved the Editor-in-Chief, three senior editors, and the head of product. Multiple claims were made during the meeting that her research could verify or contextualize.

Before (standard meeting-as-log format):

Editorial Strategy Meeting — November 4, 2024 Attendees: [List]

Agenda: Content Format Strategy

The EIC opened by noting that video engagement has been declining across the industry and we need to explore alternatives. Several editors argued for leaning into audio since podcast consumption is growing. The product head raised concerns about production costs. After discussion, the team decided to pilot a weekly podcast series in Q1 and evaluate after 3 episodes.

Action items:

• [Name] to draft podcast format proposal by Nov 15
• [Name] to get production cost estimates
• Reconvene Dec 3

Accurate record of the meeting. Completely devoid of evidence. "Podcast consumption is growing" — is it? How much? Among which audiences? The reader has no way to evaluate whether the decision is well-founded.

After (evidence-grounded recap):

Editorial Strategy Meeting: Content Format Pivot November 4, 2024 | Attendees: [List]

Outcome: Team voted to pilot a weekly podcast series beginning Q1 2025, with evaluation after 3 episodes. Decision was grounded in published research on audio consumption trends and cost-benefit analysis.

---

Context: Why this meeting happened

The EIC opened with the observation that video engagement has been declining across the publishing sector. This is consistent with Reuters Institute Digital News Report (2023) data, which found that short-form video news consumption has plateaued in most Western markets after its pandemic-era rise, with younger audiences (18-24) showing the steepest declines in video news consumption — down 8 percentage points from 2022 to 2023.

Discussion: The case for audio

Three senior editors argued that audio represents a more durable growth format than video for news content. Their argument: podcast listening has shown more sustained growth than video news. The evidence supports this: Pew Research Center's 2023 Podcast Listening report found monthly podcast listening in the United States reached 42% of adults over 12, up from 26% in 2017 — representing consistent compound growth rather than the spikier pattern seen in video news.

The product head raised the cost concern: audio production for a regular series involves real resources. After discussion, the team landed on a model using a single host format (lower production cost) with archival material rather than original reporting as primary content — a format NiemanLab analysis has documented several mid-size outlets using successfully as a first audio product.

Decision and rationale:

A weekly podcast pilot in Q1 2025. Format: single host, 25-30 minutes, drawing on the publication's existing reporting. Evaluation after 3 episodes using: listener completion rate, email subscriber conversion from podcast, and production hours per episode.

The decision aligns with patterns documented in NiemanLab's 2022 analysis of format experiments at mid-size digital publications, which found that audio pilots of 4-6 episodes allowed teams to develop format intuitions before committing to ongoing production infrastructure.

Action items:

• [Name] — podcast format proposal — due Nov 15
• [Name] — production cost model — due Nov 18
• Full team — reconvene Dec 3 to finalize Q1 launch plan

Sources:

• Reuters Institute Digital News Report 2023, Chapter 4: Video and Audio News Consumption
• Pew Research Center (2023). Podcasting Fact Sheet. Journalism.org
• NiemanLab analysis, 2022. "Format experiments at mid-size digital publishers"

Same meeting. Dramatically more useful document. Every claim grounded in evidence; decision rationale made explicit; reader can evaluate whether the team's logic was sound.

---

How to Avoid Over-Editorializing

The most important discipline in a research-grounded recap: the document is still a recap, not an editorial. Your job is to ground the discussion in evidence, not to argue a position.

Signs you've crossed from grounding to editorializing:

• The research you cite mostly contradicts what the meeting decided (selective citation to undermine the decision)
• The "research context" sections are longer than the discussion sections they're grounding (research has taken over)
• You're including research that wasn't relevant to the meeting's discussion (padding)

The test: "Does this research help the reader understand what was discussed and why, or does it advance my view of what should have been decided?" Only the former belongs in a recap.

---

Prompts to Reuse

Meeting Recap From Saved Research

I'm writing a meeting recap for [Meeting Title, Date, Participants].
Meeting purpose: [What the meeting was trying to accomplish]
Outcome: [What was decided or produced]
Primary audience: [Meeting participants / Stakeholders / Executive decision-makers / Public]
Format: [Evidence-grounded summary / Decision record / Research debrief / Briefing memo]

Meeting topics and research mapping:
Topic 1: [What was discussed]
  Claims made: "[Specific claims made in discussion]"
  Research I have:
    1. [Source, Author, Year] — [Key finding relevant to this topic]
  Verification: [Claim supported / partially / contradicted]

Topic 2: [Same structure]

Key decisions made: [List with brief rationale]
Action items: [Name, task, due date]

Draft a [format] meeting recap that:
- Opens with outcome summary (what was decided / produced)
- Integrates research citations at each relevant juncture
- Clearly attributes claims to research vs. discussion vs. both
- Presents the evidence as grounding, not editorializing
- Includes a full citation list at the end

Attribution rules:
"Research supports this [decision/concern]: [Source, Year] found that..."
"This discussion reflects [a documented pattern / what the evidence shows]: [Citation]"
"This claim was contested in the meeting; published research suggests: [Citation]"
Never: presenting research citations as the meeting's conclusion

---

Key Takeaways

1. A meeting recap from saved research elevates the format from log to evidence record: the standard log records what was said; the research-grounded recap records what was said AND whether it was supported by evidence.
2. Choose your format based on the audience: participants need a reminder (standard format fine); stakeholders and executives need evidence-grounded formats that show the decision rationale.
3. Map research to meeting topics before writing: organize your saved research by the discussion topics covered, and identify what each source verifies, contextualizes, or complicates.
4. Ground, don't editorialize: cite research that helps readers understand the discussion, not research that argues against the decisions made.
5. Close with a full citation list: a meeting recap with citations is a credible document; the citation list should be complete, not abbreviated.

---

Conclusion

A meeting recap written from your saved research is one of the most practical upgrades to a standard professional document. The log format — accurate record of who said what — has its place. But when the meeting involved claims that can be verified, decisions that should be grounded in evidence, or a research synthesis that needs to be documented, the grounded recap produces something the log can't: a document that helps readers evaluate the thinking, not just know the outcome. The research you saved before the meeting becomes the framework that lifts the recap from a record to an analysis.

Related reading: Building a Personal Knowledge Base.