Meeting templates and recipes: Standardizing outputs for repeatable meeting types

TL;DR: Standardizing meeting outputs stops research debt before it starts. Granola uses two features to do this: Templates structure how your AI-enhanced notes are formatted for each meeting type, and recipes are saved prompts you run after enhancement to extract insights or generate new content. The workflow: You jot rough notes during the conversation, Granola enhances them using your chosen template, then you run a recipe in chat to pull out feature requests, draft a follow-up email, or build an executive summary. The result: Consistent, queryable documentation without the synthesis overhead.

Most professionals spend significant time preparing for meetings and almost no time designing what happens after them. The problem isn't the conversation. It's the documentation gap that follows: Unstructured notes, inconsistent formats, and insights that can't be found when they matter. Across customer interviews, PRD reviews, and weekly 1-on-1s, that gap compounds until post-meeting synthesis becomes a second job in itself.

The structure behind consistent meeting summaries

A meeting summary template is a pre-defined structure that tells you and Granola exactly what to capture for a specific type of conversation. It specifies the sections you need, the questions each section should answer, and the format for presenting that information to anyone who wasn't in the room.

A strong template covers five core components: Meeting metadata (date, participants, objective), the agenda items discussed, decisions reached, action items with clear owners and deadlines, and next steps. The metadata and decisions sections are easy to overlook under time pressure, yet they provide the context that makes summaries useful months later.

The key insight is this: The template shapes the output, but it should never constrain the conversation itself.

Standardized notes with templates, deeper outputs with recipes

Consistency across meeting types produces compounding returns. Templates control that consistency: When every customer interview is enhanced using the same template, the output is structured the same way every time. Recipes then let you go further. Run an "Extract Feature Requests" after a product call and Granola chat searches the enhanced notes for every signal that maps to a product request. Run a "Generate Follow-up Email" and it drafts a structured follow-up using the decisions and action items already captured. When every IC memo uses the same template, partners can scan for the investment thesis in seconds. When a recipe runs across all IC memos in a folder, investment teams can surface patterns across the pipeline without manually reviewing each one.

Effective action items require three components: A specific task, a single owner, and a clear deadline. Writing "@Sarah: Share revised scope by Friday" beats "Follow up with engineering." That specificity appears reliably when your template demands it by design. From there, a recipe like "Compile Action Items with Owners" pulls every commitment across an entire folder of meetings and surfaces them in one place. The structure you define in the template is what makes the recipe's output trustworthy.

"I've been recruiting for nearly 15 years, and I genuinely wish I had Granola from the very beginning. Granola not only transcribes interviews accurately, it also organizes the information directly into my personalized template, which makes completing feedback scorecards fast and effortless." - Syl C. on G2

Granola's templates feature saves your custom note structures so you can apply the same enhancement format to every meeting of that type. The structure you defined once, you get back automatically every time. Recipes are the next layer: Saved chat prompts you build once and reuse to extract insights, generate deliverables, or surface patterns across your enhanced notes.

When to use templates and recipes vs. one-off notes

Not every meeting warrants a recipe. The table below clarifies when to invest in a standardized format and when a one-off note is sufficient.

A useful heuristic: If you run the same type of meeting regularly and the outputs feed into a decision, a repository, or a stakeholder report, build a template to standardize the enhanced notes and a recipe to automate the follow-on work. One-off notes work well for informal conversations where the content doesn't need to be comparable across sessions or retrievable months later.

"The AI Summary templates. Being able to choose what type of meeting it is and the notes being summarized accordingly. Also, the fact that Granola does not need to join your meeting." - Verified user on G2

Prevent research debt: Standardize insights

Research debt accumulates when insights from past conversations aren't captured in a format that's findable or comparable. The ACM's analysis of institutional memory loss points to a familiar pattern, suggesting that when institutional knowledge isn't preserved, teams revisit the same problems and pay the same costs to solve them again. Similarly, according to LinkedIn's organizational knowledge research, when key individuals leave, critical insights leave too, creating knowledge gaps that affect future operations. This isn't a people problem. It's a documentation architecture problem.

Reducing synthesis time and ensuring findable insights

Research suggests that workers spend the majority of their day on coordination activities, leaving relatively little time for strategic work. Executives lose the equivalent of two full working days weekly to manual administrative tasks. For product managers running four to eight customer interviews weekly, post-meeting synthesis is one of the heaviest drains in that administrative load.

Standardized formats cut synthesis time in two ways. First, you're not deciding what to include on every call, because the template already specifies the sections. Second, when you use Granola's AI enhancement guided by your rough notes, the AI fills in transcript context for each section you've flagged. Write "Pricing objections" in your notepad and Granola pulls every relevant exchange from the transcript into that section. The structure you defined in your template shapes what the AI surfaces. From there, a recipe takes over: Run "Summarize Pricing Objections Across Q2 Calls" in chat and Granola searches every enhanced note in the folder and returns source-linked citations from each conversation.

Stakeholders dismiss qualitative research when they can't verify it. "How many customers said that?" is the question that kills actionable insights in roadmap discussions. When every customer interview is enhanced using the same template, querying across all sessions becomes straightforward. Save a recipe called "Identify Top Onboarding Friction Points" and run it against your Customer Research folder. Granola chat searches across every tagged interview, returns source-linked citations, and tells you exactly which conversations surfaced each pattern. That's the difference between "we heard this a few times" and a precise count of which customers flagged which issues in which quarter.

Setting up your meeting summary repository

Granola's shared team folders helps you organize all meetings of a given type in one place. Create a "Customer Research" folder and add every discovery call. Investment teams can create an "IC Memos" folder for pipeline notes. Every team member with folder access can query across all meetings in that collection, regardless of who ran the original call.

This structure addresses the knowledge-walks-out-the-door problem directly. Research doesn't live in one person's note app. It lives in a shared folder that survives turnover and is queryable by any team member you share the folder with, using a company email domain, regardless of who ran the original call.

Generating follow-up emails with a recipe

A standardized follow-up email is the handshake between your meeting and the work that follows it. Granola's follow-up email recipe is a saved chat prompt: After Granola enhances your notes, you run the recipe and it drafts a structured follow-up from the decisions and action items already captured in your notes. When every follow-up from a customer call uses the same recipe, recipients know exactly where to find decisions and next steps without reading every line.

Follow-up email recipe: What it pulls from your notes

Effective follow-ups require three components: A brief context paragraph restating the meeting purpose, a decisions and agreements section, and a list of action items with owners and deadlines. The follow-up email recipe pulls these from your enhanced notes automatically. The context paragraph matters because recipients who weren't in the meeting need enough background to act on the summary. If your template captured the meeting objective clearly, the recipe can restate it without you rewriting it.

Granola's recipes library includes a built-in follow-up email recipe. You can customize the chat prompt to match your specific follow-up structure, specifying tone, length, and which sections to prioritize. It runs after enhancement, not during note-taking.

Build your meeting summary template

Before you can run a recipe, you need a template that structures your enhanced notes consistently. A complete meeting summary template covers these components:

• Meeting metadata: Date, participants, absentees (important for accountability), and the stated objective
• Key discussion points: A brief account of each agenda item covered
• Decisions made: Every resolution, agreement, or direction confirmed during the meeting
• Action items: Task, owner, and deadline for each commitment made
• Open questions: Anything that was raised but not resolved
• Next steps: Upcoming milestones and the timeline for reaching them

Tracking absentees helps ensure key stakeholders know which decisions were made without them and can provide input before execution begins.

Customer interview: Template structure and recipes

For product managers running discovery research, the customer interview template should structure the enhanced notes to capture both raw customer voice and connection to product decisions. A well-structured discovery template captures the participant's role and context, the core problem statement in the customer's own language rather than your interpretation, and the current workarounds they're using. Once the template consistently structures those sections, recipes like "Extract Feature Requests," "Identify Recurring Pain Points," and "Generate Interview Summary for Stakeholders" can run across your entire research folder.

A strong customer interview template includes:

• Participant context: Role, company size, how they use the product today
• Problem statement: One-line summary using the customer's language, not a feature request
• Key observations: Direct quotes and specific examples from the conversation
• Current workarounds: What they're doing now in the absence of the solution they need
• Product signals: Feature requests, friction points, and moments of delight
• Connection to roadmap: Which existing tickets or decisions this interview informs
• Follow-up needed: Any open threads requiring a response or further research

A useful discipline: Capture rough customer language during the call and let AI surface the exact quotes from the transcript afterward. A note like "pricing too opaque, can't benchmark against competitors" is enough in the moment. Granola finds the exact exchange in the transcript and pulls it into the "Key observations" section of your template. You stay present. The detail appears afterward. Then run an "Extract Competitive Objections" recipe in chat and every pricing and positioning signal from the past quarter surfaces in one place with source-linked citations.

"I recently started using the Granola AI notetaker app in my meetings, and I'm absolutely obsessed. It's so much better than the AI notetakers that just join a meeting, because it doesn't disrupt the flow at all. I can keep taking my own notes, and I never have to worry about missing anything important." - Verified user on G2

PRD meetings: Template structure and summary recipes

PRD kickoffs and reviews generate high-stakes decisions that need to survive the sprint, the quarter, and the eventual departure of whoever held the context in their head. A standardized template ensures nothing critical gets buried in a wall of unstructured notes. From there, recipes like "Identify Open Questions with Owners" or "Generate PRD Decision Summary" let you pull structured outputs from those enhanced notes without manual synthesis.

What your PRD template should capture

A PRD template should always structure the following sections:

• Problem statement reviewed: A brief restatement of the problem being addressed, confirmed by the meeting
• Goals confirmed: What success looks like, with measurable criteria where possible
• Non-goals confirmed: What is explicitly out of scope, to prevent scope creep
• Key decisions and rationale: What was decided and why, including alternatives that were rejected
• Open questioquestions with owners: Every unresolved item, with a named person responsible for closing it

The "non-goals" and "open questions" sections are valuable for preventing repeat conversations. Without them, teams risk revisiting the same decisions in later sprints.

Documenting PRD outcomes and gaps

PRD meetings often surface something that isn't ready: A technical dependency that isn't scoped, a data requirement that nobody owns, or a design question that needs customer validation before engineering can begin. A dedicated "Gaps and blockers" section in your recipe captures these explicitly rather than letting them disappear into the general notes.

For each blocker, capture: What's missing, who needs to resolve it, and by when it needs resolution to keep the timeline intact. That structure transforms a vague concern into a trackable item.

Blueprint for a PRD kickoff template

A PRD kickoff template prompt for a standard review session:

• Problem recap: One-paragraph restatement of the problem from the PRD
• Goals and non-goals confirmed: Bullet list, agreed by the group
• Key technical decisions: Architecture, tooling, or integration choices made during the session
• Design questions outstanding: Visual or UX decisions that require further input
• Gaps and blockers: What's missing, who owns it, and the resolution deadline
• Immediate next steps: The key actions required before the next review
• Meeting notes author: Named PM responsible for distributing the summary

See Granola's template customization documentation for instructions on specifying length, detail level, and section order in your template prompt. Once your template is in place, save a "Generate PRD Status Update" recipe to draft stakeholder summaries from the enhanced notes without starting from scratch each time.

IC memo templates and recipes for investment committee meetings

Investment committee meetings require documentation that communicates precisely to partners and decision-makers who weren't in the room. The stakes are high: a significant financial decision rests on what's written, not on memory of the conversation. Visible's investment memo framework identifies the core components as: Executive summary (including company overview, valuation, target returns, risks, and investment thesis), market opportunity (TAM: Total addressable market, SAM: Serviceable available market, SOM: Serviceable obtainable market, trends, and growth potential), business overview (business model, acquisition strategy, product-market fit, and value proposition), and financial analysis (historical performance, projections, and key metrics).

Design your IC memo template

An IC memo template should structure these sections:

• Investment thesis: Three to five specific, falsifiable claims about why this investment wins
• Company and market summary: Business model, market size, competitive position
• Team assessment: Founder background, relevant track record, identified gaps
• Financial snapshot: Key metrics, runway, and valuation context
• Key risks: The two or three most material risks and how the team addresses them
• Deal terms: Investment amount, valuation, and structure
• Due diligence status: What has been verified and what remains outstanding
• Recommendation: A clear yes, no, or conditional decision with the rationale

The "recommendation" section is most often omitted from ad hoc IC notes. Including it in the template ensures every memo concludes with a decision, not a summary. From there, a recipe like "Summarize Deal Risks Across Pipeline" or "Extract Investment Thesis by Stage" can run across the IC folder and surface patterns across all memos in the pipeline.

"background without joining as a bot or recording audio means I can actually be present in conversations. No awkward 'there's a bot in this call' energy... The summaries it produces are actually good, not just a raw transcript dump, but key insights and actions." - Aprielle D. on G2

Resolving IC memo blockers and actions

IC meetings often end with conditional decisions: "Yes, pending reference checks" or "Interested, needs updated cap table." These conditions need to be documented with the same specificity as the decision itself, including a named owner and a resolution date.

A "Conditions and actions" section in the IC template follows a structure like: Condition, Owner, Resolution date, Status. That table turns a verbal condition into a trackable item. A saved "Review Outstanding Deal Conditions" recipe, run against the IC folder, surfaces every condition with a citation back to the meeting where it was set, useful for pipeline status reviews.

How saved formats maintain quality while saving time

The compound value of a template isn't the first meeting it formats. It's the twentieth. Once you've settled on a structure that your team trusts, every new meeting of that type automatically meets the same standard without anyone thinking about it. Recipes compound in the same way: A "Generate Weekly Research Digest" recipe that runs across your Customer Discovery folder delivers the same structured output every time, regardless of who ran the calls that week.

Ensuring consistent meeting summaries

Best practices for maintaining quality across your Recipe library:

• Review templates regularly. Meeting types evolve. A customer interview template built early in the year may need new sections months later if your product or market has shifted. Review your recipes at the same time: If the template structure changes, the recipe prompt may need to reflect new section names.
• Keep sections outcome-focused. Each section heading should answer: What decision or action does this section enable? If a section doesn't connect to an outcome, remove it.
• Store all meetings in named folders. Consistent folder naming across your team makes folder-level queries reliable. Descriptive names like "Customer Discovery Q2 2026" make it easier to find and query relevant conversations.

Customize your templates and recipes fast

Through Granola's template customization you can modify any existing template without rebuilding from scratch. Navigate to "All Templates" from the template menu or "Manage templates" from the Settings menu. Select the template you want to adjust, update the prompt, and save. The revised format applies to all future meetings using that template. Recipes are edited separately in the recipes library: Find the saved chat prompt, update the instruction, and the revised recipe applies to all future runs.

A well-structured template prompt includes four elements: The purpose and context of the meeting type, the desired length and level of detail, the sections you expect, and any specific instructions like "include verbatim quotes where the customer describes a pain point." A well-structured recipe prompt includes: The specific output you want (e.g. a follow-up email, a list of feature requests, an executive summary), the source scope (a single meeting or a folder), the format for the output, and any filtering instructions like "only include items flagged as blockers."

"I find Granola incredibly helpful and intuitive for taking notes in meetings... I appreciate being able to customize note formats and access full transcripts for reference." - Catherine S. on G2

By default, both templates and recipes are private to you. Sharing either with your organization requires signing in with a company email domain. Once shared, any team member can apply the same template to their meetings or run the same recipe against their notes, ensuring consistency across everyone running the same meeting type.

Find insights with recipes across your templates

Standardized templates make recipes significantly more useful. When all of your customer interviews are enhanced using the same template structure, a recipe like "Surface Onboarding Friction Points from the Last 90 Days" searches consistently labeled sections rather than unstructured transcripts. The inline citations point back to the exact conversation, and you can redirect the query toward specific folders if the initial results miss context you know exists.

"With Granola I don't have to worry anymore about taking meeting notes, I can just write down things I really care about and let Granola take care of the rest. Love that I can easily share my notes with my colleagues as well, and that we can all chat with the meeting transcript so everyone can see the full context of the meeting, even if they weren't there." - Jess M. on G2

For teams running sensitive IC or discovery conversations, Granola deletes audio after transcription and holds SOC 2 Type 2 certification (a compliance audit covering security controls and processes). You get structured, AI-enhanced notes with full transcript access, without stored audio.

Try Granola for free. Download the Mac, iOS, or Windows app, connect your calendar, and run your next customer interview or PRD review with a Recipe to see how standardized formats save synthesis time.

FAQs

How do I edit a saved template?

Navigate to "All Templates" from the template menu or "Manage Templates" in Settings, select the template, edit the prompt, and save. The updated format applies to all future meetings using that template.

How do I edit a saved recipe?

Open the Recipes library, find the saved chat prompt you want to update, edit the instruction, and save. The updated recipe applies to all future runs.

What types of meetings work best with templates?

Templates deliver the most value for recurring meeting types where outputs need to be comparable across sessions: Customer interviews, PRD kickoffs, IC memos, and weekly 1-on-1s. Ad hoc check-ins rarely need a standardized format.

When should I add a recipe?

Add a recipe when you regularly need a specific output from those enhanced notes: A follow-up email, a feature request digest, a stakeholder summary, or a cross-meeting pattern analysis.

How many templates and recipes should I create?

Start with two or three templates for your highest-frequency, highest-stakes meeting types. A customer interview template, a PRD template, and a 1-on-1 template cover most PM workflows. Build a matching recipe for each: "Extract Customer Insights," "Generate PRD Decision Summary," and "Draft Follow-up Email." Add more as patterns emerge in how you use the outputs.

How do I share templates and recipes across my team?

Click "Private to me" on any template or recipe and select your sharing preference, which requires signing in with a company email domain. By default, both templates and recipes are private to you.

Key terminology

Template: A saved prompt in Granola that specifies how your AI-enhanced notes should be structured for a specific meeting type. Applied during enhancement, after the meeting ends. templates define the sections, level of detail, and format of the enhanced note output. You set a template once; Granola applies it every time you enhance notes for that meeting type.

Recipe: A saved chat prompt in Granola that you run after your notes have been enhanced. Recipes extract insights, generate deliverables, or surface patterns across meetings. Examples include "Extract Feature Requests," "Generate Follow-up Email," and "Create Executive Summary." Recipes operate on already-enhanced notes, not on raw transcripts during enhancement.

Research debt: Accumulated unprocessed or unfindable insights from past meetings. Research debt grows when notes are unstructured, unsearchable, or stored in personal documents rather than a shared repository.

Synthesis: The process of reviewing multiple interviews or meetings to identify patterns, themes, and actionable insights. Templates reduce synthesis time by making enhanced note outputs comparable across sessions. recipes reduce it further by automating the extraction and aggregation steps.

Human-in-the-loop enhancement: The product approach where you jot rough notes during a meeting and AI enhances them using transcript context afterward. You control what stays and what gets removed.

Institutional memory: The collected knowledge from past conversations, decisions, and research that an organization retains over time. Templates make individual meeting notes consistent and comparable. recipes make it possible to query across those notes at scale. Together, they make institutional memory searchable and durable across team changes.