Setup Considerations: compensation cycle design

What this achieves

A compensation cycle is a governed process with a defined start, a defined population, and a defined budget. Most of what makes a cycle go well or badly is decided before it launches, because launching creates a plan for every participant and starts managers working.

Decision 1: who the cycle covers

Scope is set once, at creation. Decide whether this round is company-wide, a set of departments, or a named list of people.

A company-wide cycle is easier to explain and harder to run, because every manager has to participate on the same timetable. A departmental cycle is easier to finish and invites the question of why one department was included and another was not.

Example: HC Corp UK Ltd running its first cycle over Engineering and Sales covers 34 and 21 people, which is small enough to finish and large enough to expose whatever is wrong with the bands.

Decision 2: the planning window against the effective date

The planning window is when managers work. The effective date is when money changes. They are independent, and the gap between them is your margin for error.

Leave enough room after Planning End for review, approval, and application before the effective date arrives. A cycle applied after its effective date still writes that date onto the record, but the increase then has to be picked up as a retrospective payroll matter rather than a normal run.

Example: a 1 April effective date at HC Corp UK Ltd with planning ending 25 March leaves under a week for HR to review every proposal, approve the cycle, and apply it. Ending planning in February would leave a month.

Decision 3: strict or flexible budget

Option	Description
Strict budget	Over-budget proposals cannot be approved. The envelope holds, and exceptions have to be handled by changing the budget.
Flexible budget	An over-budget proposal can be approved with a recorded reason, which is kept as an audited override.

Strict looks disciplined and tends to push the real decision somewhere that is not recorded. Flexible keeps the exception inside the system, attached to a name and a reason, which is what you will want when someone asks a year later why one increase was larger than the rule allowed.

Decision 4: whether to link a performance cycle

Linking a completed performance cycle feeds ratings into the recommendation. Without a link, recommendations are driven by position in range alone, and every manager starts from the same number regardless of how the person performed.

Only link a performance cycle that is genuinely finished. A cycle still in progress produces ratings that will change after managers have already seen them.

Decision 5: how you will handle non-participation

Not every manager finishes. Approving a cycle while plans are still in draft or submitted marks those plans as Skipped, and the employees behind them receive no increase in this round.

Decide in advance whether a silent manager means no increase for their team or a chase. This is the decision most likely to be made by accident, at the end of a cycle, under time pressure.

What is expensive to change later

Decision	Cost of changing later
Scope	High once launched. Plans have been created against the population you chose.
Merit matrix	High once launched. The cycle keeps working from the copy taken at creation.
Effective date	Medium. It is what gets written onto records and read by payroll, so moving it after application is a correction rather than an edit.
Budget enforcement	Medium. Changing the rule mid-cycle changes what managers were told they could do.
Total budget amount	Low to medium. Departmental allocations are set at launch and can be revisited while planning is open.
Name and description	Low. They are labels.

What happens next

Once these decisions are settled you can create the cycle and launch it. Launch is the irreversible-feeling step: it creates the budgets and one plan per participant, and it is the moment managers can see the round exists.