Reviews best practices and implementation guide

​

Overview

Use this guide to introduce Reviews in Teamper without reproducing every existing performance-management process at once. Start with one clear use case, run a small first cycle, and use what you learn to improve the next one. Reviews works best when you need a consistent process for employees to reflect on their work and for managers to provide structured feedback. You can create templates and cycles, collect self-reviews and reviewer feedback, and track completion.

​

Who can use this

• HR administrators and company admins who set up review cycles
• Managers who provide reviewer feedback
• Implementation teams supporting a company rollout

​

Start with one simple use case

Choose one outcome for your first cycle before you create any questions. A simple periodic performance review for one department, or a probation review for a small group of employees, is usually a good fit. Avoid starting with every department, every employee, or every existing form. A smaller rollout makes it easier to validate assignments, set expectations, and improve the process before you repeat it.

​

Design a useful review template

Keep the first template focused. Aim for questions that help someone prepare for a specific conversation or decision, rather than a long list of general prompts.

• Ask a small number of clear questions. Five to eight focused questions is a practical starting point for a first cycle.
• Separate reflection from rating. Use text questions for examples, achievements, challenges, and development needs; use ratings only when they will inform a decision or conversation.
• Ask one thing at a time. For example, ask “What achievement are you most proud of this period?” instead of combining achievements, challenges, and goals in one question.
• Use the same question only when both the reviewee and reviewer should answer it. Otherwise, give each audience questions that fit their perspective.
• Add concise instructions when people need context, such as the review period or what evidence to include.

Create reusable questions in a review template. You can load that template into a draft cycle and adjust it for that cycle without changing the original.

​

Choose participants, reviewers, and dates

Select reviewees who are part of the use case you chose. For a first rollout, keep the group small enough that HR can check every assignment before launch. For each reviewer question, make sure every reviewee has an eligible reviewer. Use the employee’s manager where that is appropriate, then review the roster for recent manager changes, new starters, or people who should not be in the cycle. Set a launch date when reviewers and reviewees can reasonably begin. Give participants enough time to write thoughtful responses, accounting for holidays and busy periods. A one- to two-week window is a sensible starting point for a short first review; extend it when your questions require more preparation.

​

First review cycle playbook

1. Define the purpose, participants, reviewer expectations, and completion deadline for one simple review use case.
2. Create a review template with focused reviewee and reviewer questions.
3. Open Reviews, then Review cycles, and click Create review cycle.
4. In Basics, give the cycle a name that identifies its purpose and review period.
5. In Questions, load your template and confirm the questions, instructions, and rating choices.
6. In Participants, select Specific employees for a small rollout, then choose the reviewees.
7. In Timeline, set the Launch date and Completion deadline.
8. Save a draft and review the cycle roster. Confirm every reviewer assignment where reviewer questions are included.
9. Communicate the purpose, expected effort, and deadline before you click Save & schedule.
10. Monitor the roster after launch, follow up on exceptions, and close the cycle when the review process is finished.

​

Check before you launch

Use this checklist while the cycle is still a draft:

• The cycle has one clear purpose and a name that participants will recognize.
• Questions are short, specific, and appropriate for the reviewee or reviewer.
• Each included reviewee has the correct reviewer when reviewer questions are used.
• The Launch date and Completion deadline allow enough time for considered responses.
• Participants have been told why the review is happening, what they need to do, and when it is due.
• HR knows who will follow up on missing responses and who will close the cycle.

​

Communicate expectations

Tell reviewees and reviewers about the cycle before it launches. Explain the purpose, the expected time to complete it, the deadline, and how the answers will support the next conversation. You can use this message as a starting point:

We are launching a review cycle to help you and your manager prepare for a useful conversation about the review period. Please complete your assigned review in Teamper by [completion deadline]. Share specific examples where you can, and contact [HR contact] if your reviewer assignment is not correct.

When the cycle becomes active, Teamper sends reviewees and reviewers an Inbox task and email notification. A scheduled cycle is not available to participants before its launch date.

​

Monitor progress and support conversations

Use the cycle roster to monitor completion instead of manually checking in with every participant. Focus follow-up on people with missing responses, incorrect assignments, or access issues. Send one reminder near the middle of the cycle and a final reminder before the deadline when needed. Treat self-reviews and reviewer feedback as preparation for a conversation, not just forms to complete. Managers should compare the employee’s reflection with their feedback, identify examples to discuss, and agree on practical next steps together.

​

Close and improve the next cycle

When the review process is complete, close the cycle. A closed cycle no longer accepts changes. Before repeating the process, review what happened:

• Which questions produced useful discussion and which were unclear or repetitive?
• Did participants have enough time?
• Were reviewer assignments accurate?
• Where did completion slow down?
• What feedback did employees and managers give about the experience?

Make only the changes that address those findings, then reuse the template for the next cycle. A reliable, lightweight cycle is more valuable than a complex process that people cannot complete well.

​

Common setup mistakes

​

The template is too long

Remove questions that do not support the cycle’s purpose. Start with a small set of prompts and add detail only when a later cycle shows it is needed.

​

Questions are unclear or combine several topics

Rewrite each prompt so it asks for one response. Use plain language and say which period, goal, or behavior the person should consider.

​

The first rollout includes too many people

Run the first cycle with one department or a small group. Expand after you have tested questions, assignments, communication, and timing.

​

Reviewer assignments are wrong

Review the roster before scheduling. Correct manager changes and assign an eligible reviewer to every reviewee who needs reviewer feedback.

​

The deadline is unrealistic

Move the dates before launch. A completion deadline must be on or after the launch date, and participants cannot submit incomplete reviews after the cycle closes.

​

Participants did not know what to expect

Communicate the purpose, expected effort, reviewer relationship, and deadline before the cycle launches. Do not rely on the launch notification alone to explain the process.

​

FAQs

​

Which review workflows are not supported?

Reviews does not support configurable multi-step approvals, peer or client feedback workflows, weighted scoring, calibration, or confidential management-only notes. Keep your first process within the available self-review and assigned-reviewer workflow.

​

Related articles

• Reviews overview
• Create review templates
• Create and manage review cycles