> ## 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. # Meeting Context for Performance > How meetings connect to goals, feedback, and performance reviews # Meeting Context for Performance Meetings aren't just status updates — they're where performance management actually happens. Here's how meeting context feeds into the broader performance system. ## Meetings create performance history Every one-on-one is a data point about: * What was worked on * What challenges came up * What feedback was given * What commitments were made * What progress was achieved Over time, these meetings build a rich history that makes performance reviews more accurate and less stressful. **Why this matters** Without meeting notes: * Reviews rely on recent memory (recency bias) * Accomplishments from months ago get forgotten * Feedback feels like it's coming out of nowhere With meeting notes: * Reviews reference actual conversations from the whole period * Patterns become visible (not just isolated incidents) * Feedback has been given continuously, not just at review time ## Goals get discussed in meetings Goals don't exist in isolation — they're reviewed, adjusted, and updated in one-on-ones. **In meetings, you can:** * Review progress on goals * Identify blockers * Adjust goals if priorities change * Create action items to move goals forward * Celebrate when goals are achieved **How this appears in Topicflow:** * Goals surface in meeting agendas when they're stale or off-track * Action items can be linked to goals * Goal progress is visible in meeting context * Past meeting notes show the history of goal discussions When it's time for a performance review, you can see how goals were managed throughout the period, not just whether they were completed. ## Feedback happens in meetings Most continuous feedback is given during one-on-ones, not through formal feedback submissions. **Informal feedback in meetings:** During a one-on-one, you might say: * "The way you handled that client issue was really strong" * "I noticed the project update was late — what happened?" * "Your presentation to leadership was clear and well-structured" This is feedback, but it's conversational. **Formalizing feedback from meetings:** When feedback is important enough to reference later, you can: 1. Give the feedback in the meeting 2. Document it in the notes 3. Create a formal feedback item Formal feedback items become part of the performance record and are visible during reviews. **Why both matter:** * **Informal feedback** (in notes) keeps the conversation natural * **Formal feedback** (as a feedback item) ensures it's captured for reviews You don't need to formalize everything — but meaningful observations should be saved. ## Action items create accountability Commitments made in meetings become action items, and completed action items demonstrate follow-through. **What this looks like:** * Manager: "Can you get me the project plan by Friday?" * Direct report: "Yes" → action item created Next meeting: * Action item surfaces in the agenda * Discuss whether it was completed * If not, identify blockers or adjust priorities **During reviews:** Completed action items show: * Whether commitments were followed through on * Patterns of execution * How development action items from previous reviews were addressed Action items aren't just task tracking — they're evidence of reliability and execution. ## Work context from integrations Topicflow pulls work activity from 200+ tools: * Code commits and pull requests * Completed tasks and project updates * Customer interactions * Sales activity * Support tickets This context appears in meeting views automatically. **Why this matters for performance:** Instead of asking "What did you work on this week?", you can see: * 12 commits across 3 repos * 5 pull requests reviewed * 2 support tickets resolved * 1 customer demo delivered This frees up meeting time for coaching: * "I saw you worked on the billing refactor — what was challenging about it?" * "You've been in a lot of customer calls lately — what themes are you hearing?" * "Your PR review volume is high — is that taking time away from your own work?" The data is the starting point, not the outcome. The coaching conversation is what matters. ## Topicflow AI uses meeting context When preparing for a review or one-on-one, Topicflow AI can reference: * Past meeting notes and topics discussed * Action items created and completed * Goals reviewed in meetings * Feedback given during conversations **Example prompts:** * "What have we discussed in one-on-ones over the last quarter?" * "What action items has \[person] completed related to their goals?" * "What feedback have I given in meetings this quarter?" AI doesn't replace the human review — it helps you recall what actually happened. ## Best practices **Document meaningful conversations** If feedback was given, a decision was made, or a commitment was created, capture it in notes or action items. **Reference meeting notes during reviews** Don't write a review from scratch. Read recent meeting notes to recall what actually happened. **Use meetings for continuous feedback** Don't save all feedback for the review. Give it in one-on-ones, document it, and reference it later. **Connect meeting topics to goals** When discussing a goal in a meeting, create action items or note progress explicitly. **Let integrations do the heavy lifting** Don't spend meeting time on status updates that Topicflow already knows. Use that time for coaching and development. ## What's next Learn how to run effective one-on-ones See how meeting context informs reviews Understand goal tracking and discussions Learn about continuous feedback