> ## 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. # Writing Effective Reviews > How to write clear, fair, and actionable performance reviews # Writing Effective Reviews Effective performance reviews are specific, balanced, grounded in evidence, and actionable. Here's how to write reviews that are fair and useful. ## Preparation before writing **Review the performance period** * What were the person's goals? * What feedback was given (by you, peers, stakeholders)? * What meetings and conversations happened? * What accomplishments or challenges occurred? **Use Topicflow context** * Read through recent one-on-one notes * Review goal progress and completion * Check feedback received during the period * See work activity from integrations (commits, PRs, tickets, deals, etc.) **Use Topicflow AI for recall** Topicflow AI can help: * "What accomplishments did \[person] achieve this quarter?" * "What feedback did \[person] receive during the review period?" * "What goals did \[person] complete or adjust?" **Avoid writing from memory alone** Memory is unreliable and biased toward recent events. Use documented context. ## Structure of an effective review **Accomplishments and strengths** * What did the person do well? * What goals were achieved? * What impact did they have? * What feedback or recognition did they receive? **Areas for growth** * What could improve? * Where did goals fall short? * What constructive feedback was given? * What patterns need addressing? **Goal evaluation** * Were goals achieved? * Were goals adjusted appropriately? * How well did they execute? **Development plan** * What should the person focus on next period? * What goals or action items will support growth? * What support or resources do they need? **Overall rating** (if used) * Does performance exceed, meet, or fall short of expectations? ## What makes review writing effective **Specific, not vague** ❌ "Good work this year" ✅ "You shipped 3 major features this year: the checkout redesign (2 weeks early), the API v3 migration (on time with zero downtime), and the analytics dashboard (which increased user engagement by 15%)" ❌ "Communication needs improvement" ✅ "Project updates were often late or missing key details. For example, the Q2 roadmap update was sent 3 days after the deadline and didn't include the budget variance explanation stakeholders needed" Specificity provides actionable insight. **Balanced, not one-sided** Every review should include: * What the person does well (to reinforce) * What could improve (to develop) Even high performers have growth areas. Even underperformers have strengths. **Evidence-based, not impressionistic** ❌ "I feel like you're not engaged" ✅ "You missed 4 of 12 one-on-one meetings this quarter and didn't respond to follow-up messages about rescheduling" Evidence makes feedback defensible and fair. **Future-focused, not just backward-looking** Reviews should: * Summarize the past period * Set direction for the next period * Create clear development goals **Aligned with prior feedback** Nothing in the review should be a surprise. If constructive feedback appears in the review, it should have been discussed during the period. ## Common mistakes in review writing **Recency bias** Focusing only on the last month or two, ignoring earlier accomplishments or issues. **Vague praise** "Great job" doesn't help someone know what to keep doing. **Surprise feedback** Raising issues in the review that were never mentioned before. **Comparing to others** Reviews should evaluate someone against expectations for their role, not against peers. **Focusing only on outcomes, not effort or growth** Sometimes goals aren't achieved due to factors outside someone's control. Evaluate effort, learning, and adaptation too. **Writing reviews too quickly** Thoughtful reviews take time. Don't rush through them. ## Writing constructive feedback in reviews Constructive feedback in reviews should: **Reference prior conversations** "As we discussed in our March one-on-one, project updates need to include more detail for stakeholders. This continued to be an issue in Q2." **Be specific and actionable** "For next quarter, structure project updates to include: current status, risks, dependencies, and next steps." **Acknowledge context** "The goal to ship Feature X by June wasn't achieved. This was partly due to the unexpected platform migration, but also because the scope wasn't adjusted when priorities shifted." **Focus on behavior, not character** "Updates were frequently late" not "You're disorganized" ## Writing about goal achievement **For achieved goals:** "You completed all 3 Q1 goals: shipped the API migration (2 weeks early), onboarded 2 new engineers (both ramped faster than average), and reduced support ticket volume by 25%." **For partially achieved goals:** "You made progress on 2 of 3 goals. The checkout redesign shipped successfully, and the onboarding improvements are underway. The goal to reduce deployment time wasn't achieved due to platform constraints, but you adjusted scope appropriately." **For missed goals:** "The goal to launch Feature X by June wasn't achieved. The project was delayed due to unclear requirements and shifting priorities. For next quarter, let's focus on tighter scoping and regular check-ins." ## Incorporating feedback from others If the review includes peer or stakeholder feedback: **Summarize themes** "Multiple peers highlighted your collaboration and responsiveness. Jordan noted that you unblocked the design team quickly, and Sam said your documentation made the handoff seamless." **Reference specific feedback** "As Taylor mentioned in their feedback, your presentation to leadership was clear and persuasive, which helped secure buy-in for the project." **Balance multiple perspectives** If feedback conflicts, acknowledge it: "Some peers noted your communication was strong, while others felt updates could be more frequent. Let's discuss how to balance depth vs. frequency." ## Using AI to draft reviews Topicflow AI can help draft reviews, but always review and edit: * AI can recall accomplishments and feedback * AI can suggest structure * AI cannot know interpersonal context or make performance judgments See [AI-assisted reviews](/reviews/ai-assisted-reviews) for details. ## Best practices **Start early** Don't write all reviews the day before they're due. Spread them out. **Use documented context** Reference meetings, feedback, goals, and work activity. Don't rely on memory. **Be honest and fair** Reviews should be accurate, even if the conversation will be difficult. **Discuss with the employee** Reviews shouldn't be surprises. Discuss the content in a review meeting. **Create actionable development plans** Every review should include clear goals or action items for the next period. ## What's next Use meetings, feedback, and goals in reviews Get AI help drafting reviews Ensure fairness across teams