> ## Documentation Index > Fetch the complete documentation index at: https://docs.topicflow.com/llms.txt > Use this file to discover all available pages before exploring further. # Agendas, Notes, and Follow-ups > How to structure meetings with agendas, capture notes, and ensure follow-through # Agendas, Notes, and Follow-ups Effective meetings have three components: preparation (agendas), documentation (notes), and accountability (follow-ups). Here's how each works in Topicflow. ## Agendas Agendas give meetings structure and ensure important topics don't get forgotten. **Adding agenda items** Both participants can add items to the agenda: * Before the meeting (recommended) * During the meeting (when something comes up) * From suggestions provided by Topicflow AI **Types of agenda items** * **Discussion topics**: "Q2 goals planning" * **Updates**: "Status on project X" * **Decisions needed**: "Should we prioritize feature A or B?" * **Feedback**: "Feedback on last week's presentation" * **Follow-ups**: "Review action items from last meeting" **Agenda item sources** Topicflow can automatically suggest agenda items based on: * Open action items from previous meetings * Stale or off-track goals * Recent feedback * Upcoming deadlines or review cycles **Working through the agenda** During the meeting, you can: * Check off items as you discuss them * Reorder items if priorities shift * Add new items if something important comes up * Mark items to carry over to the next meeting When a topic doesn't have an explicit assignee, the person who created it is assigned by default — so it's always clear who owns each item. Not everything on the agenda needs to be discussed every time. Prioritize what matters most. ## Notes Meeting notes create a shared record of what was discussed, decided, and committed to. **What to capture in notes** * Key discussion points * Decisions made * Feedback given * Blockers or challenges identified * Next steps or commitments **What not to capture** You don't need a verbatim transcript. Notes should be useful for future reference, not exhaustive documentation. **Who takes notes** Either participant can take notes during the meeting. Often: * Managers take notes in early one-on-ones * Ownership shifts to direct reports over time * Both contribute as the relationship matures **Note visibility** By default, meeting notes are visible to both participants. This creates transparency and shared context. **Private notes** Each meeting also has a Private Notes tab where you can capture thoughts visible only to you — coaching observations, preparation reminders, or sensitive context you don't want in the shared record. Private notes are never shown to the other participant. **Formatting notes** Use simple formatting to make notes scannable: * Bullet points for discussion topics * Bold text for decisions * Action items captured separately (not just in prose) Type `/` in the meeting notes editor to open the slash-command menu, which provides quick access to formatting options and AI actions without leaving the keyboard. **Using notes for review preparation** When preparing for a performance review, you can: * Scroll through past meeting notes * Search for specific topics or keywords * Reference decisions or commitments made over time Notes create a performance history that's grounded in actual conversations. ## Follow-ups and action items The most important output of a meeting is often what happens after it. **Creating action items** During the meeting, create action items for: * Commitments made ("I'll send you that doc by Friday") * Tasks identified ("Let's schedule a meeting with the design team") * Development activities ("Complete the React training module") **Action items vs. notes** * **Notes**: Record what was discussed * **Action items**: Track what needs to be done Both are valuable, but action items create accountability. **Action items in the next meeting** Open action items automatically surface in the next meeting's agenda. This creates a natural follow-up loop: 1. Create action item in meeting 2. Work on it before the next meeting 3. Discuss progress or mark complete 4. Create new action items as needed **When action items don't get done** If action items consistently don't get completed: * Discuss whether they're actually important (if not, delete them) * Identify blockers (and create new action items to resolve them) * Reassess priorities or capacity The goal isn't to create more tasks — it's to track the things that actually need to happen. ## Meeting history Every meeting in Topicflow maintains a history: * Past agendas * Previous notes * Completed action items * Work context from integrations **Why history matters** * **Reference past decisions**: "What did we decide about X last month?" * **Track patterns**: "This has come up three meetings in a row" * **Prepare for reviews**: "What have we discussed over the last quarter?" * **Onboarding**: New managers or direct reports can read past notes to understand context **Searching meeting history** You can search across: * All meetings with a specific person * Meetings in a date range * Meetings containing specific keywords * Meetings where specific topics were discussed ## Best practices **Prepare before the meeting** Add agenda items ahead of time. Don't walk in unprepared and default to status updates. **Notes don't need to be perfect** Capture enough to be useful. Don't let note-taking interfere with the actual conversation. **Action items should be specific** "Think about goals" is vague. "Draft 3 Q2 goals by Friday" is actionable. **Review the previous meeting's notes** Start by checking in on action items and topics that needed follow-up. **Use context from integrations** Don't manually report on work that Topicflow already knows about. Use that time for coaching and discussion instead. ## What's next Learn how to conduct effective one-on-ones Get AI help with agendas and summaries Learn more about managing action items