How Often Should Employee Performance Reviews Happen?

Start with one documented employee performance review a year, supported by regular check-ins and feedback on actual work. Add an earlier or second formal review when goals change substantially. Choose the cadence according to the decisions each conversation serves and whether employees have time to act on feedback.

An annual meeting should never have to reconstruct twelve months of work from memory. Nor should every conversation about a project become a rating. Set a schedule for three different jobs: assessing a period of performance, checking progress on goals, and giving feedback while the work can still change.

How often should formal employee performance reviews happen?

For many employers, one formal performance review each year is a workable starting point. A second documented review can help when responsibilities or goals change substantially within the year. The number is a design choice, not a research-backed optimum for every organization. Acas recommends at least an annual review in its UK guidance, alongside regular informal conversations; the CIPD describes formal appraisals as typically occurring once or twice a year.

This is a planning example, not a rule. A monthly check-in may fit a team with shifting priorities. A longer project may call for a conversation at the end of each phase. Decide what the manager and employee will do differently after each meeting before adding it to the calendar.

What should happen between formal performance reviews?

Between formal reviews, a manager and employee should check whether the goals still fit the work, discuss specific examples, and agree on the next action. A short record of changed goals or promised support makes the later appraisal more accurate. Acas advises regular informal conversations and a written record of formal reviews.

Suppose a team lead is now responsible for onboarding two people, though the original goals cover only client delivery. Waiting for the annual review would leave a large part of the job invisible. At the next check-in, the manager can revise the goals, ask what support the lead needs, and agree on what successful onboarding would look like. The formal review can then assess work the employee actually had a chance to do.

There is no sound basis for turning weekly feedback into weekly formal appraisal. A CIPD evidence review finds that specific, constructive, fair feedback matters more than sheer frequency; one study it cites found monthly feedback more effective than weekly feedback. A field study of feedback conversations reported better outcomes with more frequent conversations in its observed range. Neither study compares annual, semiannual, and quarterly formal review cycles. Agree on a rhythm, then check whether people have time to use the feedback.

When should an employer change the performance review cadence?

Change the review cadence when the standard interval leaves an employee or manager without a timely decision. A new hire, a changed role, a short work cycle, or a persistent gap between goals and available support can justify an earlier formal point or more frequent check-ins. First identify which conversation is missing.

For example, the American Academy of Pediatrics suggests 90-day or six-month evaluation points for new staff in pediatric practices. That is a useful onboarding example, not a general rule for every employer. UConn's own check-in process calls for goal conversations at least every two months and allows existing meetings to serve that purpose. Neither interval needs to become your company's policy by default.

If a role's goals remain stable but the employee needs help on a current project, add a check-in or give timely feedback. If responsibilities have changed enough that the original criteria no longer describe the job, revise the goals and consider a documented midyear review. If managers cannot prepare credible examples for the extra reviews, adding another formal cycle may make the process worse.

Should pay decisions and development feedback happen in the same performance review?

Pay decisions and development feedback serve different purposes, so give each a clear place in the review process. When practical, discuss growth and support in a conversation separate from the meeting that delivers a pay or promotion decision. The CIPD evidence review warns that ratings for administrative and developmental purposes can differ, and recommends separating those conversations.

An employee hearing a compensation decision is likely to focus on its consequences. A development discussion needs room to examine specific work, ask questions, and plan what happens next. Even if the meetings must be close together, state the purpose of each, use consistent criteria, and let the employee respond to the evidence. A review schedule cannot make a poorly explained decision feel fair.

Development may also involve the conditions under which someone does their best work. Our Team Alignment Profile describes working preferences, motivation, and pace; its scores describe preferences rather than ability or performance. Keep those discussions distinct from evidence used to rate an employee. For a broader look at how leaders put strengths to work, see how leaders use strengths without turning them into labels.

How can HR tell whether a performance review schedule is working?

Test the schedule by asking whether goals stay current, feedback leads to a useful action, and formal reviews contain few surprises. Ask employees and managers about those outcomes after a cycle. A calendar full of completed forms tells you that meetings happened; it says little about whether the process helped anyone do better work.

Look at a small sample of recent reviews and check-ins:

• Were the criteria agreed before the work was assessed, and updated when responsibilities changed?
• Can both people name a specific example and what happened after the feedback?
• Did the employee have a chance to explain the work, the constraints, and the support needed?
• Did a concern first appear in the formal review, when an earlier conversation could have addressed it?

If goals are stale, shorten the interval between goal check-ins. If appraisals contain surprises, improve the quality and timing of feedback before adding another rating. If the same paperwork repeats without changing decisions, simplify the formal cycle. The CIPD's review puts fairness, credible evidence, and employee input at the center of useful feedback. Our guide to measuring leadership development offers a related way to check whether manager behavior changes after a development effort.

Keep the schedule that makes expectations clear while there is still time to act on them. An annual review can document the year; the conversations that make it fair and useful happen throughout it.