Performance Review Cycles for Small Teams: Timing, Reminders, and What Actually Gets Done

The review that never happens

Most small companies have a performance review process on paper. Far fewer have reviews that actually take place on time. The pattern is familiar: somebody sets up an "Annual Review" in January, it sits there with a name and two dates, and by the time anyone remembers it, half the team is overdue and the other half had theirs in a hallway.

The problem is rarely motivation. It is that a review cycle, as most teams set it up, is a label rather than a schedule. Nothing in it decides who is due, nothing tells the manager it is time, and nothing marks the difference between "running" and "forgotten".

This guide covers the three decisions that turn a cycle into something that runs: when reviews fall due, who they cover, and who gets reminded.

Decision one: a shared window, or each person's own date?

There are two honest ways to time reviews, and they suit different teams.

A shared window puts everyone in scope on the same dates — "reviews happen in the first two weeks of March". It is easy to explain, it lines up with budget and compensation planning, and managers can block out the time in one go. The cost is a crunch: a manager with eight reports does eight reviews in a fortnight, and someone who joined in February is reviewed after a few weeks.

A hire-date schedule measures from each employee's own start date. Nobody is reviewed after three weeks, and the load spreads across the year. The cost is that it is invisible without a system — no spreadsheet reminds you that Priya's anniversary is on the 14th.

A hire-date schedule also handles more than the one-year mark. The same idea covers "once, three months in" for an end-of-probation conversation, or "every six months" for a team that wants more frequent check-ins. Two edge cases are worth deciding up front, because they will come up: someone who started on 29 February, and someone who started on the 31st of a month. A sensible rule reviews the first on 28 February in years without a 29th, and holds the second to the last day of a shorter month rather than letting it spill into the next one.

How to choose: if your compensation decisions happen on a fixed date, use a shared window for the review that feeds them. If your reviews are mostly about development and fit, a hire-date schedule is fairer and easier on managers. Many teams run both — a shared annual cycle and a hire-date check-in for new joiners.

Decision two: who is in scope?

A cycle that covers "everyone" is the default, and it is often wrong. Engineering may review twice a year while sales reviews quarterly. A pilot programme might start with one department. Contractors may not be reviewed at all.

Whatever you choose, two checks keep scope honest:

• The scope you set should be the scope that is saved. It sounds obvious, but it is worth confirming that a department-wide cycle really covers that department — and only that department — before the first reminder goes out.
• Look at how many people a cycle actually covers. A department that has been reorganised to zero people reads exactly the same as one with thirty, unless the cycle shows its headcount. Glance at the number before you rely on it.

Decision three: who is reminded, and when?

A cycle that creates no reminders is a row nobody hears about. The question is how many reminders, and how far ahead.

One reminder is almost always wrong. Send it a month ahead and it is forgotten by the time it matters; send it the day before and there is no time to prepare. Two reminders cover both jobs:

• About two weeks ahead — when there is still time to gather notes, look back at goals, and book the meeting.
• A few days ahead — when it has to be done, and the reminder is a nudge rather than a plan.

Teams that hold reviews on a tight schedule sometimes add a third on the day itself. More than a handful starts to read as noise.

The reminder should go to the person responsible for holding the review — usually the employee's manager — not to an HR inbox that then has to forward it. And it should stop the moment a cycle is paused or has ended, so nobody is chased for a review cycle that finished last quarter.

Keep "running" and "finished" separate

A common trap is a cycle status that someone has to set by hand: Draft, Active, Completed. "Completed" is the one that never gets set, because nobody owns the moment a cycle is finished — and whether a review is done is really a fact about one person's assessment, not about the cycle.

A simpler model works better:

• Active — the cycle sends reminders.
• Draft — it is being set up and sends nothing.
• Ended — its end date has passed. Nobody needs to mark it; the dates say so.

Probation is its own thing

It is tempting to run end-of-probation reviews as just another cycle called "3 Months Probation". That covers the reminder, but probation usually carries more than a review date: an agreed period, the possibility of an extension, and a decision that may affect someone's employment. Keep the probation review on the employee's own record, with its own period and extension date, and treat a hire-date review cycle as a complement to it rather than a replacement. (We cover probation reviews in more detail in a later post.)

Link the review to the conversations before it

The most useful reviews are the ones nobody is surprised by. When regular one-to-ones are linked to the review they lead up to, the review becomes the last step of a conversation that has been happening all along — the notes are already written, the goals have already been discussed, and the meeting is about what comes next.

A short checklist

• Choose the timing that matches the purpose: a shared window for pay decisions, hire dates for development.
• Set the scope, then check the headcount the cycle actually covers.
• Send two reminders to the person who holds the review: one to prepare, one to act.
• Let the end date close the cycle, rather than relying on someone to mark it complete.
• Keep probation on the employee's record, with its own period and extension.

How BookYourPTO handles it

In BookYourPTO, a review cycle runs either on specific dates for everyone in scope or on each employee's hire date — once a set number of months in, every year on the anniversary, or every few months. A cycle covers everyone, one department, or a chosen list of people, and the list shows how many people each cycle currently covers. Reminders go out 14 and 3 days ahead by default, and administrators can choose up to six per cycle. A cycle is created Active, can be switched to Draft to pause it, and reads as Ended once its end date has passed. The probation review stays on each employee's profile with its own period, extension and reminders.