---
title: Performance Reviews
slug: performance-reviews
icon: 🏅
docTags: 
createdAt: 2025-12-17T17:42:31.009Z
---

Performance reviews in ChartHop can be as simple or as sophisticated as you need them to be. We've seen everything from lightweight manager check-ins with three questions to elaborate 360-degree cycles with calibration workflows and competency matrices. The platform flexes to match your process — the key is designing intentionally for what actually works for your organization.

## Understanding What Performance Reviews Are For

Performance reviews in ChartHop are designed for feedback that's *about specific people* — whether that's self-reviews, manager reviews of direct reports, peer feedback, or upward reviews. The key principle: if you're asking someone to provide feedback about a specific reviewer or another identified person, that belongs in Performance Reviews.

**What belongs in Performance Reviews:**

- Manager reviews of direct reports
- Self-assessments
- Peer feedback (360-degree reviews)
- Upward feedback (reports reviewing their managers)

**What doesn't belong here:** If you're sending a form that's about no one in particular or is a deidentified survey (like pulse surveys, engagement feedback, or anonymous team health checks), use the Engagement module instead. Performance Reviews is built for identified, person-specific feedback that ties to your org chart.

## Setup Principles That Work Across Any Cycle

**Start with clean org chart data.** Whether you're running a simple or complex cycle, ChartHop pulls review relationships from your reporting structure. Recent transfers, dotted-line reports, managers covering multiple teams — handle these scenarios before launch, not during.

**Be realistic about timelines.** Build in buffer time. If you want reviews completed by a specific date, set your deadline a few days earlier. If you're running multi-stage reviews (self + manager + peer), stagger those deadlines so each phase completes before the next begins.

**Design your visibility intentionally.** When can employees see their reviews? What can they see? This varies wildly by company — some share everything immediately, others wait until after calibration. Either approach works in ChartHop, just decide upfront and configure accordingly.

**Think through your data flow.** If performance ratings connect to compensation, promotions, or succession planning, map those connections early. The more integrated your processes, the more valuable your review data becomes.

## What Makes Cycles Run Smoothly

**Pilot before full launch.** Whether you're running something simple or complex, test with a small group first. They'll catch configuration issues and process questions you didn't anticipate.

**Automate communications.** Set up reminders at key intervals. Create clear documentation for managers. The more you can automate and systematize, the less ad-hoc support you'll need to provide.

**Plan for edge cases.** New hires, employees on leave, recent transfers, open roles — decide how to handle these situations before they become questions.

**Keep forms focused.** Even in complex cycles, less is often more. Every question should serve a clear purpose. More questions don't automatically mean better data.

## Common Challenges (Regardless of Complexity)

**The surprise launch:** Always coordinate your ChartHop launch with your internal communications. 

**Visibility mishaps:** Test your settings thoroughly. Make sure people see what they're supposed to see, when they're supposed to see it.

**Mid-cycle changes:** Reporting relationships shift, people transfer, managers go on leave. Decide upfront how you'll handle these situations — freezing relationships at cycle launch versus allowing real-time updates.

Performance reviews in ChartHop work for everyone from 50-person startups running their first structured review to 15,000-person enterprises with sophisticated multi-rater cycles. The platform adapts to your process. Your job is designing something that fits your culture, your capacity, and your goals — then letting ChartHop handle the execution.