The Review Cycle That Should Drive a Pay Change
Why this matters
Most small shops handle pay changes one of two broken ways: never on a schedule, so raises happen only when someone threatens to quit, or on an arbitrary anniversary date that has nothing to do with performance or the market. Both approaches teach your crew the wrong lesson, either that squeaky wheels get raises and quiet excellence does not, or that a raise is just a calendar event unrelated to what anyone actually did. A real review cycle ties pay decisions to a rhythm the whole crew can see and trust, which is what makes a raise feel earned instead of arbitrary.
What a review cycle actually needs to answer
A pay review is not just "does this person deserve more money." It needs to answer three separate questions in order, because getting the order wrong is how reviews turn into either rubber-stamp raises or awkward, subjective conversations nobody wins.
- Has their contribution changed? More skill, more responsibility, better quality, higher volume, since the last review.
- Has the market changed? What similar roles pay now versus when this person's rate was set, so you are not anchored to a number that has quietly gone stale.
- Can the business support a change either way? A deserved raise still has to fit the P&L, and a market shift downward is not a license to cut pay on people already performing well.
Answering contribution alone, without checking the market and the business's capacity, produces raises that feel generous in the room and unsustainable six months later.
The cadence: how often is often enough
Annual, on a fixed schedule, is the right default for most shops. Pick a cycle tied to something stable, either everyone's individual hire-date anniversary or one company-wide review month for the whole crew. A single company-wide month is usually easier to run consistently and lets you compare people fairly against each other in the same sitting, at the cost of a busier review season. Anniversary dates spread the workload but make it harder to compare people side by side.
Do not review pay more often than once or twice a year as a matter of course. Frequent, informal pay bumps outside a structured cycle teach the crew that pay is negotiable at any time, which invites exactly the "ask whenever, get it whenever" dynamic a cycle is supposed to prevent.
A true off-cycle change is still sometimes warranted, but it should be the exception with a clear trigger, not the norm: a role changed significantly, a retention risk is real and immediate, or a market shift is sudden enough that waiting for the annual cycle would cost you the person. Off-cycle changes that happen quietly and often are a sign the annual cycle is not doing its job.
What feeds the review, so it is not just a gut call
A pay review anchored in nothing produces a decision nobody can defend later, including to the person sitting across from you. Pull real inputs before the conversation:
- Performance data, not memory: callback rate, customer satisfaction score, jobs completed, quality signals specific to the role. Whatever you use to run performance pay day to day is what should feed the review too.
- A market check, even an informal one: what are similar shops in your area paying for this role and this experience level. You do not need a formal survey every year, but do not let a rate go five years without any outside comparison.
- The pay band for the role, if you have documented one. A review inside a documented band is a calibration exercise. A review with no band is a negotiation that starts from scratch every time.
Running the conversation itself
- Separate the performance conversation from the pay number when possible. Talk through the year's performance first, agree on where the person stands, and only then move to what that means for pay. Leading with the pay number turns the whole conversation into a negotiation instead of a shared look at the work.
- Explain the reasoning, not just the result. "Your callback rate dropped and you picked up the commercial certification, that's what's driving this" lands very differently than a number with no explanation attached.
- If the answer is no change, say so directly and say why, with a path forward if one exists. Silence or vagueness reads as either indifference or an unstated problem, and either interpretation damages trust more than an honest no would.
The consequence of skipping this discipline
Without a real cycle, pay drifts by who asks and who is squeaky, not by who earns it, and your best quiet performers eventually notice they are subsidizing everyone who is willing to make noise. A fixed, well-fed review cycle is what lets you say, honestly, that pay here tracks performance and the market, not persistence.
References
- Society for Human Resource Management (SHRM), performance review and compensation-cycle guidance
- U.S. Bureau of Labor Statistics, occupational wage data for market benchmarking
- See related: The Tech Who Wants a Raise: Decision Tree
- See related: Retroactive Pay Change vs Grandfather the Old Rate Decision Tree