HR Operations & Pay Equity

Off-Cycle Raises: A Policy That Keeps Your Pay Structure Intact

Off-cycle requests are where pay structures quietly come apart. This guide sets out the triggers, approval steps and decision log a small company needs.

Rovaryn Digital · November 17, 2026 · 7 min read

One manager asks, one gets a yes, and nobody writes down why

It is the second week of July. A team lead messages you: her best analyst has been approached by a recruiter, and she would like a raise approved before the next review cycle. You say yes, because losing the analyst would cost more. In August a second manager asks for the same thing for a person in a different job. This time you hesitate, because you cannot remember what you based the first decision on. By October there are five requests, three approvals, and a spreadsheet tab called "misc adjustments" that only you can read.

Nothing in that story is reckless. Each decision was reasonable in isolation. The damage is cumulative: people with the same job now sit at unexplained distances from one another, some are above the midpoint of their range with no stated reason, and a board member or outside counsel asking "why does this person earn more than that one?" gets a shrug instead of a document.

An off-cycle raise policy fixes this without banning flexibility. This guide sets out which triggers qualify, who approves, how every request is checked against the salary range, and how each decision is recorded so you can explain it later.

Decide which triggers qualify before anyone asks

The most common policy failure is having no list at all, so every request is judged on how persuasive the manager is. Write down the short list of reasons an increase may happen outside the regular cycle, and treat everything else as "wait for the cycle."

A workable list for a small company usually has four entries:

  • A change in role. A promotion or a significant, permanent expansion of duties. The person moves to a different range, and the new minimum may already sit above their current pay.
  • A correction. The person is paid below the minimum of their own range, or an analysis shows an unexplained gap against peers in the same job.
  • A retention risk with evidence. A documented outside offer or a market change affecting a scarce skill, where the manager can say what the company loses if the person leaves.
  • A location change. The person moves and the applicable range moves with them.

Equally important is a short list of things that do not qualify: a personal financial hardship, a manager's general feeling that someone is "doing great," or a peer's recent raise with no job-based reason attached. Those may be sympathetic, but they are cycle conversations. Naming them in the policy gives managers a clear answer they can deliver without it feeling personal.

Build the approval path so it matches the size of the change

Approval under an off-cycle raise policy should not be a ceremony, but it should never be one person's private decision. For a company with ten to two hundred people, three layers is usually enough:

  1. The requesting manager completes a short written request: who, what role, what increase, which trigger, and what happens if the answer is no.
  2. HR (or whoever holds the pay structure) checks the request against the range and against peers, then adds a recommendation.
  3. An executive approver signs off. For larger increases, or for any request that would place someone above the midpoint, add a second approver such as the finance lead.

Keep the thresholds in the policy itself, expressed as percentages or range positions you choose, so the rule applies the same way whether the request arrives in July or December. Set a response time as well. A request that sits for three weeks is a request that gets answered with a counter-offer from someone else.

One rule is worth stating explicitly: the person requesting the increase never approves it, and a manager never approves an increase for someone who reports to them. That is basic separation of duties, and it costs nothing.

Check every request against the range, then the peers

This is the step that keeps the pay structure intact. A request is not complete until someone has answered two questions: where does this person sit in their range today, and where will they sit afterward?

The standard measure is the compa-ratio: (current salary ÷ range midpoint) × 100. Our guide to how the compa-ratio works covers the mechanics in more detail, so here is only a worked example with round numbers. Suppose the range runs from $48,000 to $72,000, so the midpoint is $60,000. An analyst earning $54,000 has a compa-ratio of 90. A proposed raise to $58,000 would take that to about 96.7, still below the midpoint, which makes it easy to defend. A proposed raise to $66,000 would produce a compa-ratio of 110, which should trigger the second approver and a written reason.

Then look sideways. Pull the pay of everyone else in the same job and ask whether the raise creates a new gap that you could not explain. A new hire who earns more than a tenured colleague, or a recently approved raise that jumps one person past a more experienced peer, creates the exact compression problem that off-cycle increases tend to cause. If the proposed raise would leave the person well ahead of colleagues with comparable duties, the policy should send the request back for either a stronger job-based reason or a plan to look at the peers too.

This is also a good moment to think about pay equity. Off-cycle increases are discretionary by nature, and discretionary decisions are where unexplained differences between groups tend to appear. Reviewing them periodically, as described in our pay equity audit guide, lets you see patterns that no single request would reveal.

Write the off-cycle raise policy as a one-page document

Once the triggers, approval path and range check are settled, the written off-cycle raise policy itself can be short. One page is enough, and a short policy gets followed. Include:

  • Purpose and scope. One or two sentences on why the policy exists and who it covers.
  • Qualifying triggers and the list of non-qualifying reasons.
  • Required evidence for each trigger, such as the outside offer, the role description, or the range and peer comparison.
  • The approval path, with thresholds and the response time.
  • The range rule. Whether increases may take someone above the midpoint, and what extra approval that needs.
  • The effective date convention. For example, increases take effect on the first day of the next pay period after final approval, never backdated by a manager's promise.
  • What happens to the next cycle. State whether an off-cycle increase counts toward, or reduces, the person's merit eligibility. Leaving that undefined is how someone ends up with a second raise two months later and a colleague with none.
  • Where decisions are logged and who owns the log.

The policy is not a legal document, and it should not read like one. If it touches jurisdiction-specific obligations, confirm those with the relevant authority or your employment counsel rather than relying on a general template.

Log each decision so you can explain it later

A decision you cannot reconstruct is a decision you will end up defending from memory. For every request, approved or declined, keep one record containing the requester, the date, the trigger, the compa-ratio before and after, the peer comparison, each approver, the outcome and the reasons. Declined requests matter as much as approved ones, because consistency is visible only when both are on file.

Retention periods vary by place, so check the rule that applies to you. California's law, for example, requires job title and wage history to be retained for the duration of employment plus three years after termination (as summarized by Sidley Austin). Maine's pay-history recordkeeping requirement, with the same duration-plus-three-years period, applies to all employers (per Vensure and Mondaq). Those statements describe two specific states; they are not a general rule, and the exact obligations for your location are worth confirming with the state labor department or counsel.

Whichever tool you use, the structure matters more than the format. The Off-Cycle Increase Request & Decision Log is a downloadable template built for this step: off-cycle requests are where pay structures quietly come apart, one manager asks, one gets a yes, and there is no record of why. You fill it in manually, and it pairs with a SalaryRange account, which holds your ranges and an immutable, timestamped compliance audit trail for the range work itself. For the wider picture, the Pay Action Ledger & Audit Trail Workbook is the record of every pay change you made and who approved it. Our piece on a compliance audit trail for salary ranges explains why that record is worth keeping from the start.

If you are building the rest of your pay processes alongside this one, the HR operations resource hub collects the related guides in one place. Start with the four triggers, one page of policy and one log, and your off-cycle raise policy will give the next request somewhere to go.

Ready to go beyond the guide?

Join the waitlist for Salary Range Builder.

See your ROI

How much is non-compliance costing you?

Browse templates

HR compensation templates, ready to download.

Get new guides in your inbox

One email when a new article goes live. Unsubscribe with one click.

More from HR Operations & Pay Equity