How Often Should You Do Performance Reviews?
Most teams land in one of three places: annual, quarterly, or continuous. A common, workable answer is a fuller review twice a year or quarterly, with lighter check-ins or pulse surveys in between. For field and trades teams, the better question is not how often but when. Timing should follow the work (seasonal ramps, project milestones, new crew), not a fixed calendar. Frequent but light beats rare and heavy, because the goal is to catch problems early while they are still cheap to fix.
So how often should you actually do reviews?
The short answer: most teams do well with a fuller review quarterly or twice a year, plus lighter check-ins in between. The longer answer depends on your team, and especially on whether your work follows a calendar at all.
There are really three common cadences, and each has a clear trade-off.
Annual. One formal review a year. It is the lowest effort and the easiest to schedule, which is exactly why it is so common. The problem is that feedback moves at the speed of the calendar. Something that came up in February does not get said until the review in November, by which point it is either forgotten or has already turned into a bigger issue.
Quarterly. A review every three months. This is frequent enough that nothing festers for long, and recent enough that both people remember the specifics. The cost is the obvious one: it is more meetings, and if each one is a heavy, sit-down, fill-out-the-whole-form event, people start to dread them.
Continuous. Ongoing feedback, light and frequent, often with a small formal checkpoint a couple of times a year. This catches problems the fastest and keeps coaching close to the work. The risk is that "continuous" quietly becomes "never," because without some structure the check-ins are the first thing to get skipped when everyone is busy.
Most teams that get this right do not pick one. They run a fuller review on a quarter or half-year rhythm and keep something lighter going in between.
Why annual-only reviews tend to fail
A once-a-year review asks one conversation to do a year's worth of work. That is where it breaks down.
Feedback gets stale. By the time you sit down, the good and the bad have blurred into a vague overall impression, and recency bias takes over, so the last month ends up standing in for the whole year.
It also raises the stakes too high. When the review only happens once, every point in it feels like a verdict. People get defensive, managers soften the hard parts to avoid a blowup, and the actual issues never get named clearly.
And it is slow to correct anything. If someone has been drifting since the spring, an annual review in the fall is not coaching. It is a postmortem. The whole value of a review is changing what happens next, and annual-only gives you very few chances to do that.
Why field teams should not be locked to a fixed calendar
Most review advice assumes an office where the work is roughly the same in March as it is in September. Field and trades work is not like that.
Your year has a shape. There is a busy season and a slow season, ramp-ups when you are bringing on crew, and stretches where everyone is heads-down on a big job. A review tool that auto-fires "your quarterly review is due" on a fixed date will reliably pick the worst possible week, dropping paperwork on a foreman in the middle of your busiest month.
Project timing matters more than the calendar. The right moment to review a crew member is often right after a major project wraps, while the work is fresh, or right before the busy season when you are setting expectations. Those moments do not fall on tidy quarterly boundaries.
This is the part of the calendar problem we built around. With FieldCon, review cycles are started by an admin when the timing actually fits the business, not by a cron job picking dates during setup. You decide that now is the right week, choose who is in the cycle, and run it. Reviews happen on your schedule, not the software's.
Where lighter check-ins and pulse surveys fit
The fix for "annual is too slow" is not just doing the full, heavy review four times as often. That burns people out. The better pattern is to keep the fuller review on a sensible rhythm and put something lighter in the gaps.
Lighter check-ins are short, low-stakes one-on-ones. No forms, no scores, just a quick conversation about how the work is going and what is in the way. They keep the relationship current so the fuller review is a continuation, not an ambush.
Pulse surveys do the early-warning job. A few quick questions sent out between reviews surface the things people will not say in a hallway, like a crew that is quietly frustrated, a new hire who is already drifting, or a manager who is losing the room. We use pulse surveys for exactly this, to catch problems while they are still small and cheap to fix, before they show up later as turnover and rework. The point is to learn something between the bigger reviews instead of flying blind until the next one.
A simple cadence for a trades or field company
If you want a starting point you can put in place this quarter, here is a balanced one:
- A fuller review twice a year, timed to your work rather than the calendar. Anchor one before the busy season and one after it winds down, or tie them to the end of major projects. This is the deeper, on-the-record conversation.
- A short check-in monthly or every other month. Fifteen minutes, no paperwork. Just enough to stay current and surface anything that needs attention before it grows.
- A pulse survey between the fuller reviews. A quick read on how people are actually feeling, so you are not waiting six months to find out something is wrong.
Run that for a year and adjust. If problems are still slipping through, tighten the rhythm. If people feel over-reviewed, loosen it. The cadence should serve the work, not the other way around.
If you would rather not stitch this together by hand, that is what we built FieldCon to do. You start a cycle when the timing fits, run pulse surveys between the fuller reviews, and keep the whole thread visible without forcing artificial deadlines on crews who are already busy. See how it works on the pricing page.
The bottom line
There is no single correct frequency, but there is a clear pattern that works: frequent and light beats rare and heavy. Run a fuller review quarterly or twice a year, keep lighter check-ins and pulse surveys going in between, and for field teams, let the timing follow the work instead of a fixed calendar. The goal is not to fill out more forms. It is to catch what matters early, while you can still do something about it.
Frequently asked questions
Is once a year enough for performance reviews?
For most teams, no. An annual-only review means feedback can sit for ten or eleven months before anyone says it out loud, which is too late to change anything and too long to remember the details. Annual works better as the deeper, formal checkpoint sitting on top of lighter check-ins through the year, not as the only conversation.
Should field and trades teams review on a fixed schedule?
Not strictly. Crews ramp up and down with the season and with projects, so a rigid calendar tends to fire reviews during your busiest weeks and skip the moments that actually matter. Tie the fuller review to the work instead, after a big project wraps or before the busy season, and use light check-ins to keep the thread going between them.
What is a good performance review cadence to start with?
A simple, durable starting point is a fuller review twice a year, a short one-on-one check-in monthly or every other month, and a pulse survey between the bigger reviews. Adjust the timing of the fuller review to fit your seasons and project schedule rather than locking it to fixed dates.