​

Review Context and History

Topicflow reviews are informed by continuous context: meetings, feedback, goals, and work activity from integrations. This makes reviews more accurate and less reliant on memory.

​

What context is available in reviews

When writing or reading a review, Topicflow surfaces: Goals

• Goals for the review period
• Completion status
• Progress updates and notes
• Action items tied to goals

Feedback

• Feedback given by the manager
• Feedback from peers and stakeholders
• Feedback received during the review period
• Recognition

Meeting history

• One-on-one notes and agendas
• Topics discussed
• Action items created and completed
• Patterns over time

Work activity (from integrations)

• Code commits and pull requests
• Completed tasks and projects
• Customer interactions
• Sales activity, support tickets, etc.

This context reduces recency bias and ensures reviews are evidence-based.

​

Using goals in reviews

Goals provide objective criteria for performance evaluation. What to look for:

• Were goals achieved?
• Were goals adjusted appropriately when priorities shifted?
• How well did the person execute (speed, quality, autonomy)?
• Were goals realistic and meaningful?

Example: “You completed 4 of 5 Q1 goals. The API migration shipped 2 weeks early with zero downtime. The onboarding process improvement is 80% complete. The goal to reduce deployment time wasn’t achieved due to platform constraints, but you appropriately adjusted scope in March.” Goals create a clear, objective foundation for review content.

​

Using feedback in reviews

Feedback submitted during the review period surfaces automatically. What to look for:

• Themes across multiple feedback items
• Feedback from diverse sources (manager, peers, stakeholders)
• Growth in response to earlier constructive feedback

Example: “You received positive feedback from multiple peers for collaboration. Jordan noted your responsiveness during the project, and Sam highlighted your clear documentation. You also received constructive feedback in February about presentation clarity, and subsequent demos showed noticeable improvement.” Feedback makes reviews less subjective and more grounded in documented observations.

​

Using meeting history in reviews

One-on-one notes create a record of what was discussed throughout the period. What to look for:

• Topics that came up repeatedly (patterns)
• Commitments made and whether they were followed through
• Coaching given and whether growth happened
• Challenges discussed and how they were addressed

Example: “In our one-on-ones, we discussed your goal to improve stakeholder communication. You implemented the suggestion to send weekly updates, and stakeholder feedback in May confirmed this improved alignment.” Meeting notes provide context that memory alone can’t recreate.

​

Using work activity from integrations

Topicflow integrations pull in work context automatically:

• Code commits, PRs, and code reviews
• Completed tasks and project updates
• Customer calls and support tickets
• Sales activity and deals closed

What to look for:

• Volume and consistency of work
• Quality indicators (e.g., code review feedback, task completion rates)
• Collaboration patterns (e.g., cross-team PRs, stakeholder meetings)

Example: “Your work activity shows consistent execution: 150+ commits across 12 repos, 50 PRs reviewed (helping onboard junior engineers), and 8 customer demos delivered. This demonstrates both individual contribution and team support.” Work activity validates accomplishments without relying on self-reporting.

​

Combining multiple sources of context

The most effective reviews combine all available context: Goals → What was planned Feedback → How execution was perceived Meetings → What was discussed and coached on Work activity → What actually happened Example of combined context: “Your goal was to ship the checkout redesign by end of Q1. Meeting notes show we discussed scope and design trade-offs in January and February. Work activity shows 45 commits and 12 PRs over 8 weeks. Feedback from the product team praised the feature’s quality and your responsiveness to design feedback. The project shipped 2 weeks early.” This creates a complete, evidence-based picture.

​

Opening cited evidence

Citations in AI-generated content now open the referenced meeting, goal, feedback, or action item in a sidebar overlay, so you can check the source without leaving the review you’re working on. External links still open in a new tab.

​

How Topicflow AI surfaces context

Topicflow AI can help recall and summarize context: For managers writing reviews:

• “What were [person]‘s goals this quarter?”
• “What feedback did [person] receive during the review period?”
• “What did we discuss in one-on-ones over the last 3 months?”
• “What has [person] been working on based on integration data?”

For employees writing self-reviews:

• “What goals did I complete this quarter?”
• “What feedback did I receive?”
• “What accomplishments aren’t reflected in my goals?”

AI helps surface context quickly, but humans interpret performance.

​

Best practices

Review context before writing Don’t write reviews from memory. Read through meetings, feedback, and goals first. Reference specific examples Use context to provide concrete examples, not vague impressions. Look for patterns over time One incident isn’t a trend. Look at the full review period. Balance multiple sources Don’t rely only on goals or only on feedback. Use all available context. Acknowledge gaps If someone’s work isn’t well-documented (e.g., lots of in-person collaboration), acknowledge that and ask them to fill in context.

​

What’s next