How to Set Up Continuous Feedback in Confirm: A Manager's Playbook
Annual reviews give you one data point per year: that's like navigating with a map from last January.
Continuous feedback changes this. When managers and employees exchange observations in real time, not just at review season, performance conversations become easier, ratings become more accurate, and surprises at review time nearly disappear.
Confirm's continuous feedback system is built into the same platform as your performance reviews, so the feedback you collect throughout the year feeds directly into your annual cycle. But it only works if managers know how to use it.
This playbook is a recipe for turning continuous feedback in Confirm from a feature your team doesn't use into a practice your managers actually follow.
The Recipe at a Glance
Outcome you're trying to achieve: A feedback rhythm where every direct report receives at least one piece of substantive, specific feedback per month, documented in Confirm, visible during review season, and not dependent on HR reminding anyone.
Ingredients:
- Continuous feedback enabled in your Confirm account (admin toggle in Settings)
- Managers briefed on how to send and request feedback (15 minutes; covered in Step 2)
- One feedback template per major work context (optional, but dramatically increases quality)
- A recurring 1:1 agenda item for reviewing feedback together
Time to set up: 30 minutes for admin configuration; 15-minute manager briefing; ongoing from there.
When to use this: Any time between formal review cycles. Also useful when onboarding new employees, when someone's performance is trending (up or down), or when a team just completed a major project.
When NOT to use this: As a replacement for difficult performance conversations. Continuous feedback is for developmental signal: ongoing observations that help someone improve. A performance issue that's affecting the team needs a direct conversation, not a feedback note.
Step 1: Enable Continuous Feedback in Confirm
In Confirm, go to Settings → Modules → Continuous Feedback.
Three settings to configure:
| Setting | Recommended | Reason |
|---|---|---|
| Who can send feedback | Everyone (not just managers) | Peer feedback is often more accurate than manager-only |
| Feedback visibility | Manager and recipient | No anonymous feedback: it doesn't produce behavior change |
| Feedback categories | On (use Confirm's defaults or customize) | Categories help receivers understand what type of signal they're getting |
The categories Confirm provides by default (Collaboration, Execution, Communication, Leadership) work for most orgs. If your company has defined competencies or values, replace these with those instead. Feedback tied to your actual framework means something during calibration.
Turn on notifications. By default, Confirm will notify employees when they receive feedback. Don't disable this: it's what makes the feedback feel real rather than disappearing into a system no one checks.
Step 2: Brief Your Managers in 15 Minutes
Most continuous feedback systems fail because managers think they need to write a paragraph every time they observe something. They don't.
Useful feedback in Confirm is 2–3 sentences:
- What you observed (behavior, not interpretation)
- What it produced (outcome or impact)
- What to do more of, or differently (optional but useful for developmental feedback)
Template for your manager briefing:
"When you see something worth noting: a strong presentation, a missed deadline, a peer who stepped up on a tough project — log it in Confirm under Feedback → New Feedback. Takes 90 seconds. The person sees it, it feeds into their annual review, and you'll have specific examples when you need them."
Send this as a Slack message before you launch. The managers who use continuous feedback most are the ones who understood it takes less than two minutes per entry, not more.
Step 3: Use AI Feedback Drafts for Recurring Situations
Confirm's AI assistant can draft feedback based on context you provide. This is most useful for recurring situations managers find hard to document:
- A team member who consistently goes beyond their scope on cross-team projects
- A direct report whose meeting communication style is creating problems
- An employee who recently delivered under difficult circumstances
To use it: Feedback → New Feedback → Use AI Draft. Type one sentence about what happened. Confirm will generate a draft using your company's framework and tone. The manager reviews and edits before sending. The AI generates the structure, the manager provides the judgment.
This isn't about automating feedback. It's about removing the blank-page problem that stops managers from writing anything at all.
Step 4: Build Feedback Requests Into Your 1:1 Rhythm
The most sustainable way to maintain continuous feedback is to make it part of existing rituals, not an additional task.
In Confirm, managers can request feedback on a specific employee from anyone in the org: Feedback → Request Feedback → Select Employee → Select Peers.
Where to use this:
- After a major project: request input from everyone the employee collaborated with
- Before a quarterly review: pull peer observations to add context to your own assessment
- When you suspect you might have a bias blind spot: request from people with more visibility into the employee's day-to-day work than you have
Don't request feedback on everyone at once. That creates survey fatigue. Use targeted requests: 2–4 per employee per quarter, targeting the peers and collaborators most likely to have useful signal.
Step 5: Review Feedback Together in 1:1s
Feedback in a system no one looks at is just data in a drawer.
Confirm's employee profile view (accessible to both manager and employee) shows all feedback in a timeline. During your regular 1:1, pull this up and review recent feedback together:
- What did you notice about this observation?
- Does this match what you're experiencing day-to-day?
- What's one thing you want to focus on based on this?
This doesn't need to be a formal agenda item. It's a 5-minute pull-out during a 30-minute 1:1. The value is making feedback a live tool rather than a historical record.
For managers who skip this step: feedback that's never discussed doesn't change behavior. The loop closes in conversation, not in the software.
Step 6: Surface Feedback During Review Season
When your formal review cycle opens in Confirm, all continuous feedback from the evaluation period is automatically available to managers in the review composer.
The review composer shows feedback entries in the right-hand panel as the manager writes. This means:
- Managers writing end-of-year reviews can cite specific observations from March, June, and September, not just whatever they remember from last month
- Ratings are anchored in documented evidence, which makes calibration conversations easier
- Employees see that their manager is aware of what they did throughout the year, not just at the end of it
This is where continuous feedback pays off. Without it, annual reviews are a recency bias exercise. With it, they're a summary of a documented record.
Common Problems and How to Fix Them
"Managers aren't sending any feedback."
Usually a training issue. The most common misconception: managers think feedback should only be sent after significant events. Reset this: feedback is for small observations too. A peer who handled a difficult client call well. A direct report who proactively flagged a problem. These take 60 seconds to log and add up to a meaningful record over a year.
"The feedback is too generic to be useful."
Enable categories and add templates. Confirm's template library lets you create pre-filled prompts for common situations (e.g., "After a client presentation, note what worked and what could be sharper"). Templates give managers a starting point that produces more specific, useful output.
"Employees aren't reading their feedback."
Check that Confirm notifications are enabled. Also: if the manager never discusses feedback in 1:1s, employees learn quickly that the feedback system doesn't matter. Usage follows from manager behavior, not from platform features.
Continuous Feedback vs. Annual Review: How They Connect
| Continuous feedback | Annual review |
|---|---|
| Informal, frequent, lightweight | Formal, periodic, structured |
| Any time | Twice a year (or once) |
| 2–3 sentences | Paragraphs |
| Behavioral and developmental | Evaluative and compensatory |
| Feeds into review | Synthesizes all feedback |
They work together, not as alternatives. Continuous feedback is sequential: Continuous feedback builds the record. The annual review interprets it.
FAQ
How often should managers send continuous feedback?
One substantive piece of feedback per direct report per month is enough to build a meaningful record. More than once per week starts to feel overwhelming and managers stop doing it. The goal is enough signal over a year to support calibration, not a running diary.
Can employees send feedback to their manager?
Yes, if you enable upward feedback in settings. This is worth doing, especially for managers who are newer to the role. The data is useful and most managers, when they know it's visible, take it seriously.
Does Confirm's AI coaching agent use feedback data?
Yes. If you've enabled Confirm's AI coaching agents in Slack or Teams, the agent reads continuous feedback as part of its context. When a manager asks for coaching on a direct report, the agent draws on documented feedback to provide specific, grounded suggestions rather than generic advice.
What's the difference between a feedback request and a 360 review?
A feedback request in Confirm is informal and doesn't require a formal review process. A 360 review is structured, comprehensive, and tied to the performance cycle. Use feedback requests throughout the year; use 360s as part of a formal cycle when you need comprehensive peer input at scale.
How long should we wait before expecting continuous feedback to change review quality?
Two full quarters. The first cycle after enabling continuous feedback will be better; managers have some documentation to reference. The second cycle is where the pattern shifts noticeably: ratings become more specific, calibration sessions are faster, and managers have examples ready without scrambling.
