The Hidden Governance Risk in your Reward Process

Most organisations running an annual salary review will tell you the process works. Spreadsheets go out to managers. Numbers come back. Payroll runs. Letters follow. The cycle closes.

What they can’t tell you, in most cases, is who changed which number, when, and why. Whether every person in that file was actually eligible for an increase. Whether the outcomes bear any resemblance to the compensation philosophy that was presented to the board six months earlier.

The error nobody built in on purpose

Consider a scenario that’s more common than most reward teams would like to admit. A company runs its annual salary review across a few thousand employees. The process is managed through a spreadsheet distributed to numerous mangers and executives. They make their allocation decisions. The file comes back. Payroll runs.

Somewhere in that file, there are employees who joined in the last three months. Nobody intended to give them a salary increase. But they appeared in the spreadsheet, and no rule existed to catch them as ineligible. So they went through.

This isn’t a data entry error. It’s what happens when a process runs without governance: no eligibility logic, no automated checks, no mechanism to catch what shouldn’t be there.

The root cause isn’t incompetence. Reward teams in this position are highly capable - they’re running a process that was designed for a different era, on tools that weren’t built for this level of complexity.

Spreadsheets don’t have eligibility rules. They don’t flag employees who joined in the last three months, or those already sitting above the maximum of their pay range. They contain whatever data was loaded at the start of the cycle. If that data is incomplete or out of date, the errors travel with it.

When the mistake surfaces, there’s no record

The harder problem isn’t the error itself. It’s the aftermath.

When something goes wrong in a spreadsheet-based process, the question becomes: how did this happen? In most cases, the honest answer is: we don’t know. Changes were made in cells, versions were emailed, someone adjusted a figure during consolidation. The record is gone.

There is no audit trail. No timestamp on who changed what. No explanation for why a number moved between version 4 and version 7 of the file.

The governance gap boards don’t see

Most boards approve a reward strategy. They set mandates, define principles, sign off on a budget. What they don’t see is how that strategy translates into the actual cycle - who gets what, on what basis, with what checks in place.

When a Head of Reward is asked “what happened in last year’s increase cycle?” the answer should come from a system. Not from someone reconstructing events from a folder of Excel files with dates in the filename.

The gap between what the board approves and what actually runs in practice is, in many organisations, completely ungoverned. That’s a real risk. It shows up in payroll errors, inconsistent outcomes, and pay equity gaps that nobody can explain because the data to explain them no longer exists in a reliable form.

What a governed reward cycle actually looks like

A governed process doesn’t mean more bureaucracy. It means the rules that already exist - in the compensation philosophy, in HR policy, in employment contracts - are encoded in the system that runs the cycle.

Eligibility rules apply automatically. An employee who joined in the last three months doesn’t appear in the increase population because the system flags them before the cycle starts. A manager who tries to allocate an increase above mandate needs to provide a reason and that reason is time-stamped and stored.

When the cycle closes, there is a record: who made which decision, when, and why. If there’s an error, it can be traced. If there’s a dispute, it can be resolved. If a RemCo or auditor asks what happened, there’s a clear answer.

The process, in other words, matches the promise.

The question worth asking now

Reward teams don’t set out to run opaque cycles. The opacity is inherited - from the tools, from legacy workflows, from the assumption that “it’s always been done this way so it must be working.”

It works until it doesn’t. Until someone joins the business and asks a basic question and nobody can answer it. Until an employee challenges their increase and there’s no record of how it was decided. Until payroll has already run and you’re trying to explain to an employee that they received the incorrect increase and it needs to be adjusted down.

Most organizations are carrying more governance risk in their reward process than they realize. The spreadsheet doesn’t surface it. That’s precisely the problem.

This is the category of problem alignd exists to solve, not by replacing your compensation philosophy, but by giving it somewhere to actually run. Eligibility rules that apply before the cycle starts. Mandate controls that flag when a manager goes outside the guardrails. An audit trail that answers, with a click, who changed what and when. A real-time view of where the process stands, without waiting for files to come back.