Review workflows let you save your review workflows and reuse them whenever you need. Create a workflow once for your annual review process, then launch it again next year without rebuilding everything from scratch.
This article walks you through creating workflows, configuring each step, setting permissions, and managing your workflow library.
π‘ Still using our previous review system? See Classic Reviews documentation for help with one-on-one and 360 reviews.
What is a review workflow?
A workflow is a blueprint for your review workflow. It defines:
Which steps are included (feedback, meeting, signature)
Who participates at each step
What questionnaires people complete
Who can see what information
Who administers and views the reviews
Once you create a workflow, you can launch unlimited campaigns from it. Each campaign follows the workflow's workflow but applies to different employees.
Workflow vs. campaign
Think of it this way:
Workflow = The recipe for how your review process works
Campaign = Actually running that review process with specific employees
You create workflows once and reuse them many times. You create campaigns whenever you want to run reviews.
Creating your first workflow
Workflows are created from the review workflow page. Here's how to build one from scratch.
Access the workflows page
Go to New reviews > Workflows in the main navigation
Click New workflow
You'll see the workflow builder with several sections to complete.
Set basic information
Start by defining what your workflow is for:
Workflow name
Choose a name that describes the review type.
Good names: "Annual Performance Review," "90-Day New Hire Check-in," "Manager Feedback Survey"
Review period
Select which time period this review covers. This helps employees understand what timeframe they're being evaluated on.
π‘ Tip: Create separate workflows for different review types rather than trying to make one workflows fit everything. You might have workflows for annual reviews, quarterly check-ins, new hire reviews, and manager feedback β each optimized for its specific purpose.
Configure review admins
Review admins can manage all aspects of reviews created from this workflow. They can add or remove participants, move reviews through steps, and close reviews.
Who gets admin access automatically
HR and Group HR (only on employees from their groups) roles are always review admins as well as campaign adminss. You don't need to add them β they have access by default.
Add additional admins
You can give admin access to:
Managers β Every manager becomes a review admin for their own team's reviews only. They can manage reviews where they're the employee's manager, but can't access other departments' reviews.
When to use: If you want managers to handle their own team's reviews without involving HR for every step.
Specific users β Add individual people by name who should be review admins for all campaigns from this workflow.
When to use: If you have an HR partner, talent manager, or executive who needs to oversee all reviews.
Groups β Give admin access to everyone in a specific group.
When to use: If you have an "HR team" or "People Ops" group that should all have admin access.
You can combine these. For example: HR (automatic) + all managers + one executive assistant.
Configure review viewers
Review viewers can see all review content but can't make changes. They have read-only access to everything.
This is useful for people who need visibility without needing to manage the process β like skip-level managers, HR business partners, or executives.
Add review viewers
Choose who gets read-only access:
By role:
Managers β Can view reviews for their direct reports
Other roles β Any role you've defined in your system
By user:
Add specific people who should see all reviews from campaigns using this workflow
By group:
Give viewer access to everyone in a group, like "Leadership Team" or "People Operations"
π‘ Tip: Be thoughtful about review viewers. While transparency is good, some employees feel uncomfortable knowing their skip-level manager or other executives are reading their reviews. Consider your company culture when setting this up.
Set up the feedback step
The feedback step collects input from multiple people using a questionnaire. This step is optional β turn it on only if you want to collect written feedback.
Enable or disable feedback
Toggle the feedback step on or off. If you disable it, you must enable the meeting step (you need at least one of the two).
Name the step
Give your feedback step a name that participants will see. The default is "Feedback," but you can customize it to match your language.
Examples:
"Peer feedback"
"360 feedback"
"Performance input"
"Team feedback"
Add a description (optional)
Write instructions or context that participants will see when completing their feedback.
Example: "Share specific examples of this person's strengths and areas for growth. Your feedback will be visible to the employee and their manager during the review meeting."
Choose a questionnaire
Select which questionnaire feedback givers will complete. You can choose any questionnaire from your question templates.
π Note: You can use any questionnaire type β there's no longer a distinction between one-on-one and 360 questionnaires. However, questions about goals, skills, and training will be skipped in the beta. This feature is coming soon.
Select feedback givers
Choose who will give feedback by adding roles or specific users:
By role:
Manager β The employee's direct manager
Peers β Colleagues sharing the same manager
Direct reports β People the employee manages
Reviewee β The employee themselves (for self-reflection)
Manager N+2 β The manager's manager
By user:
Add specific people who should give feedback for every review using this workflow
You can add multiple feedback givers. A typical 360 setup might include: manager + 3-5 peers + employee.
Feedback visibility rules
Feedback givers never see each other's responses. This is automatic and can't be changed β it prevents bias and encourages honest feedback.
The feedback content becomes visible to meeting participants and signature participants only if you configure those later steps to show it.
Set up the review meeting step
The review meeting step is where participants discuss the review and create a summary. This step is optional β but if you disable feedback, you must enable this step.
Enable or disable the meeting
Toggle the review meeting step on or off. If you disable it, you must enable the feedback step (you need at least one of the two).
Name the step
Customize what participants see. Default is "Review meeting," but you can use your own terminology.
Examples:
"Performance discussion"
"Development conversation"
"Check-in meeting"
"Review session"
Add a description (optional)
Provide context about what should happen during this step.
Example: "Meet with your manager to discuss feedback, review accomplishments, and set goals for the coming period. Your manager will write a summary of the conversation."
Choose a questionnaire
Select which questionnaire will be used during the optional preparation and the note taker will complete when writing the summary. This can be the same as or different from the feedback questionnaire.
Common approaches:
Same questionnaire β Feedback and summary use the same questions for consistency
Different questionnaire β Meeting uses forward-looking questions (goals, development) while feedback was backward-looking (performance, accomplishments)
π Note: Goals, skills, and training questions will be skipped in the beta. This feature is coming soon.
Enable preparation (optional)
Preparation is a sub-step within the meeting that lets participants draft their responses before the actual meeting happens.
When to enable preparation
Turn preparation on when you want participants to think through their responses in advance:
Structured annual reviews where people need time to reflect
Reviews covering complex topics requiring thought
Situations where meeting time is limited and you want productive discussions
When to skip preparation
Turn preparation off for:
Quick informal check-ins
Simple conversations that don't need advance preparation
Reviews where spontaneous discussion is more valuable than structured input
Configure preparation participants
Choose who should prepare by selecting roles or specific users:
Common setups:
Employee only β They prepare, manager doesn't (lets employee drive the conversation)
Manager only β Manager prepares, employee doesn't (manager-led review)
Both β Manager and employee both prepare (balanced, thorough approach)
You can add others too, like skip-level managers or HR partners who will attend the meeting.
Preparation visibility
Decide whether preparation participants can see the feedback from the feedback step while preparing:
Show feedback during preparation:
Participants see all feedback responses when drafting their preparation. They can reference specific comments and respond to themes they notice.Hide feedback during preparation:
Participants prepare without seeing the feedback. Feedback will be shared during the meeting itself.
Most organizations show feedback during preparation so people can prepare thoughtful responses. Hide it only if you want fresh, uninfluenced preparation.
Configure the meeting summary
The meeting summary is where the final review gets written. Every meeting needs these settings:
Select the note taker
Choose who will write the summary. Only one person can be the note taker:
Common choices:
Manager β Most common setup
Reviewee β For self-directed reviews where employees document their own development
Specific user β If you always have the same person (like an HR partner) write summaries
The note taker is the only person who can edit the summary. Others can view it (based on your settings), but only the note taker can write.
Select meeting participants
Choose who participates in the meeting or needs to see the summary:
This typically includes:
The employee being reviewed
Their manager (if not the note taker)
Sometimes: skip-level manager, HR partner, or another stakeholder
All meeting participants can see the summary the note taker is writing.
Set summary visibility
Decide what the note taker and other meeting participants can see while working on the summary:
Options:
Feedback β Show responses from the feedback step
Preparation β Show draft notes from the preparation phase
Both β Show everything
None β Show only the summary questionnaire itself
Common setups:
Everyone sees everything β full transparency during the meeting
Everyone sees preparation only, no feedback β keeps the meeting focused on prepared talking points
Choose based on how much information you want available during the meeting conversation.
Set up the signature step
The signature step lets participants review the completed review and formally acknowledge it. This step is completely optional.
Enable or disable signature
Toggle the signature step on or off. Many organizations skip signatures for informal reviews and only use them for annual reviews or PIPs.
Name the step
Customize what participants see. Default is "Signature," but you can match your terminology.
Examples:
"Review acknowledgment"
"Sign off"
"Final approval"
Add a description (optional)
Provide instructions for signature participants.
Example: "Review your completed performance review and acknowledge that you've read and discussed it with your manager. You can add optional comments if needed."
Select signature participants
Choose who needs to sign by selecting roles or specific users:
Common setups:
Employee only β Standard acknowledgment that they've seen their review
Manager only β Manager certifies the review is complete and accurate
Both employee and manager β Mutual acknowledgment
Plus HR or skip-level manager β Additional oversight and approval
You can add as many signature participants as needed.
Set signature visibility
Decide what each signature participant can see when reviewing before they sign:
Options:
Feedback β All feedback responses
Preparation β All preparation drafts
Summary β The meeting summary
Any combination β Mix and match based on what you want each person to see
Common setups:
Signers sees everything β full transparency
Signers sees summary only β oversight without all the details
All signature participant have the same visibility.
π‘ Tip: Think carefully about signature visibility. Employees sometimes feel uncomfortable if they know their skip-level manager is reading all their feedback verbatim. Consider whether summaries are sufficient.
Review and save your workflow
Once you've configured all your steps, you'll see an overview showing:
Which steps are enabled
Who participates in each step
What questionnaires are used
What visibility settings you've chosen
Validation
The system checks for common issues:
Missing required fields (like questionnaires or note taker)
Configuration problems (like no participants selected)
Step requirements (at least feedback or meeting enabled)
If something's wrong, you'll see an error message explaining what needs to be fixed.
Save the workflow
Click Save workflow to add it to your workflow library. You can now use it to launch campaigns or continue editing it.
Managing your workflow library
All your workflows live on the New reviews > Workflows page.
View workflows
The workflow list shows:
Name β What you called the workflow
Description β Notes about when to use it
Created by β Who built it
Last used β When a campaign was last launched from this workflow
Steps included β Icons showing feedback, meeting, and/or signature steps
Use the search bar to find workflows by name or filter by steps included.
Edit a workflow
Click any workflow to open it and make changes. Your edits won't affect active campaigns β only new campaigns launched after you save the changes.
Duplicate a workflow
Click the three-dot menu next to any workflow and select Duplicate. This creates a copy you can customize without changing the original.
When to duplicate:
Create variations of the same review type (like different questionnaires for different departments)
Build a new workflow that's similar to an existing one
Test changes without risking your working workflow
Delete a workflow
Click the three-dot menu and select Delete. You can delete workflows that are currently being used by active campaigns.
β οΈ Important: Deleting a workflow doesn't affect campaigns already launched from it. Those campaigns continue running normally.
Launch a campaign from a workflow
Click Use as campaign draft from the workflow's three-dot menu. This takes you to the campaign builder with all the workflow's settings pre-filled.
See Launching Your First Campaign for details on customizing settings for specific campaigns.
Workflow best practices
Follow these guidelines to build maintainable, reusable workflows:
Name workflows clearly
Use descriptive names that explain the review type and when to use it:
β "Annual Performance Review - Manager + Peers"
β "90-Day New Hire Check-in"
β "Manager 360 Feedback - Direct Reports"
β "Review workflow 1"
β "Test"
Use descriptions
Add notes about:
Which employees it's designed for
Any special instructions for the review process
This helps other HR admins use your workflows correctly.
Keep workflows focused
Create separate workflows for different review types rather than trying to build one universal workflow:
One workflow for annual reviews
Another for quarterly check-ins
Another for new hire reviews
Another for manager feedback
This keeps each workflow simple and purpose-built.
Test before wide rollout
Before launching a workflow company-wide:
Create the workflow
Launch a test campaign with just a few employees
Have them complete the full review process
Gather feedback on what worked and what was confusing
Edit the workflow based on what you learned
Roll out to everyone
Review visibility thoughtfully
Consider your company culture when setting who can see what:
More transparency builds trust but may reduce honest feedback
Too much restriction can feel secretive and create distrust
Find the balance that matches your values
When in doubt, ask employees what they're comfortable with.
Document your workflows
Keep notes (in the description field or separately) about:
Why you made specific configuration choices
What you learned from previous years
Changes you want to make next time
This helps you (and future HR team members) improve the workflows over time.
Examples
Here's how different organizations structure their workflows:
Tech company annual review
Steps: Feedback β Meeting (with preparation) β Signature
βFeedback from: Manager + 3 peers + employee
βMeeting: Manager and employee both prepare. Manager is note taker. Both can see feedback during preparation and meeting.
βSignature: Employee and manager both sign. Both see everything.
βWhy this works: Comprehensive 360 input, thoughtful preparation time, structured discussion, formal documentation.
Retail company quarterly check-in
Steps: Meeting only (no feedback, no signature)
βMeeting: Manager and employee both prepare for 15 minutes. Manager is note taker. Neither sees feedback (there isn't any) during meeting.
βWhy this works: Quick and lightweight. No overhead of collecting formal feedback. Just a structured conversation.
Healthcare org new hire 90-day review
Steps: Feedback β Meeting
βFeedback from: Manager + 2 peers
βMeeting: Only manager prepares. Manager is note taker. Manager sees feedback during preparation, employee sees it during meeting.
βSignature: Skipped (developmental, not evaluative)
βWhy this works: Gathers input from early colleagues, focuses meeting on development, keeps it informal without requiring signatures.
Nonprofit manager feedback
Steps: Feedback β Signature
βFeedback from: Direct reports only (anonymous)
βSignature: Manager reviews and acknowledges. Skip-level manager also reviews and signs.
βWhy this works: Upward feedback without face-to-face discussion. Manager's manager provides oversight. No meeting needed β feedback speaks for itself.
Startup performance improvement plan
Steps: Meeting (with preparation) β Signature
βMeeting: Manager and employee both prepare. Manager is note taker. Both see each other's preparation during meeting.
βSignature: Employee, manager, and HR all sign. All three see everything.
βWhy this works: Clear expectations documented. Multiple parties acknowledge understanding. Formal process with proper documentation.
Frequently asked questions
Can I edit a workflow that's being used by active campaigns?
Can I edit a workflow that's being used by active campaigns?
Yes, but your changes won't affect campaigns already launched. Only new campaigns will use the updated workflow.
Can I use the same workflow for different departments?
Can I use the same workflow for different departments?
Yes. Workflow are organization-wide. You can set the participants in the workflow or when you launch a campaign by selecting specific departments or groups.
What happens if I delete a workflow that was used for old campaigns?
What happens if I delete a workflow that was used for old campaigns?
Nothing. Past campaigns keep running and historical data remains accessible. Deleting a workflow only prevents you from launching new campaigns from it.
Can I have different questionnaires for different employees in the same campaign?
Can I have different questionnaires for different employees in the same campaign?
No. All employees in a campaign use the same questionnaires defined in the workflow. If you need different questionnaires, create separate workflows and run separate campaigns.
Who can create and edit workflows?
Who can create and edit workflows?
HR and Group HR roles can create and edit workflows. Other users can't access the workflow builder even if they're review admins.
Can I create a workflows without choosing questionnaires yet?
Can I create a workflows without choosing questionnaires yet?
No. You must select questionnaires when building the workflow. However, you can change which questionnaire is used when you launch a campaign from the workflow.





