The GCC comp-review calendar: how to run the October-December cycle

Gulf comp cycles run on a predictable rhythm: budgets get set between October and December, and decisions land with employees between January and March. Teams that treat this as a single event in Q4 tend to arrive at the review with stale data and no time to defend it. Teams that treat it as a calendar, with each stage timed against the next, arrive with a position they can hold under questioning.

Why the timing matters more than the template

A comp review is not one meeting. It is a sequence: gather data, model scenarios, calibrate outliers, get sign-off, then communicate. Compress that sequence into a single December scramble and something gets skipped, usually the calibration step, which is exactly the step that catches a manager who has quietly let one direct report drift 20 percent below the rest of the team.

Running the sequence on a calendar also protects the data itself. Market pay moves during the months a review takes to run. A benchmark pulled in September and used unchanged in February is describing a market that may have already shifted, particularly at grades where hiring demand is active.

The month-by-month playbook

September: refresh the benchmarks. Pull current, source-counted pay data for every sector and level in scope before you build a single scenario. Doing this early means the rest of the cycle works from one dataset instead of chasing a moving number as new figures come in.

October: model the scenarios. With current benchmarks in hand, build the budget scenarios: a flat increase pool, a merit-differentiated pool, and a targeted-adjustment pool for roles that have drifted below market. Cost each one against the actual headcount, not a rough estimate, so the board conversation in November starts from real numbers.

November: calibrate the outliers. This is the step most reviews skip under time pressure, and the one that matters most. Cross-check every proposed increase against the role's percentile position in the market data, not the manager's recommendation alone. A manager advocating strongly for one report and staying quiet on another is a calibration signal, not a fact to accept at face value.

December: get sign-off. Bring the finished scenario, cost, and outlier list to whoever approves comp decisions, whether that is a board, a comp committee, or a founder wearing that hat. Every number in the deck should trace back to a source count and a date, so a question about where a figure came from has an immediate answer.

January through March: communicate. Decisions land with employees in a compressed window across the region as budgets get approved and rolled out. Prepare manager talking points ahead of this window rather than during it, particularly for anyone whose increase is below the pool average, so the conversation has a reason attached to the number rather than the number on its own.

The three data inputs each stage needs

Current market bands, source-counted and dated, feed the September refresh and the October modelling. Without them, scenario costs are built on a benchmark that may already be a quarter or two old by the time it is used.

Internal pay data by role and level, matched to the same seniority ladder the market bands use, feeds the November calibration. A ladder mismatch here is what lets an outlier hide: if internal levels and market levels are not mapped to each other, a below-market role can look correctly paid because it is being compared to the wrong external rung.

A written record of every decision and its rationale feeds the sign-off stage and pays for itself the following year, when someone asks why a specific role got the increase it did and the answer needs to be more specific than "that felt right at the time."

What breaks the cycle

Stale data is the most common failure. A September benchmark carried unchanged into a March conversation is describing a market that has likely moved, and a manager relying on it is negotiating from a number that is already out of date.

The second failure is having no source trail for the board. A comp committee that asks where a number came from and gets "market rate" as the answer will not approve the scenario with confidence, and should not. A comp committee that gets "18 verified sources, refreshed in September" approves faster and pushes back less.

The third failure is skipping the calibration step under time pressure and going straight from modelling to sign-off. This is the step that catches the manager who has quietly favoured one direct report over another for two review cycles running, and it is also the step teams cut first when the calendar has compressed into a single Q4 sprint. Protecting the November slot on the calendar is what keeps that check from disappearing.

Running this against real numbers

Book a demo to see the current, source-counted bands for your sectors before you start the September refresh. For a workflow built specifically for the calibration stage, see a new CHRO's first 90 days on comp for the questions a board typically asks and the data that answers each one. And the free Reverse Benchmarking Tool is the fastest way to spot-check a single role's percentile position before it goes into a scenario.