Your Reward Policy Says One Thing. Your Spreadsheets Do Another.

Most organisations have a reward policy. Fewer have a reward process that actually enforces it.

That gap, between what the policy document says and what happens during the annual cycle, is where governance risk quietly accumulates. It’s where mandates get overridden without a paper trail. Where exceptions become habits. Where a RemCo or auditor eventually asks a question nobody can cleanly answer.

It’s not a people problem. It’s a tooling problem.

The policy exists. The process doesn’t always follow it.

Here’s a scenario that will feel familiar to most reward practitioners.

Your organisation has a compensation policy. It defines increase mandates by grade and performance rating. It sets rules around short-term incentive (STI) eligibility and payout caps. It specifies who needs to approve what, and at which level.

That policy lives in a document. Probably a well-written one.

But when the annual cycle kicks off, that policy gets translated into a spreadsheet - manually, by someone on the reward team, under time pressure, across multiple business units, in multiple versions. The rules are embedded in formulas that someone built two years ago. The approval chain runs over email. Exceptions are noted in a comment cell or not noted at all.

By the time the cycle closes, the outputs may broadly reflect the policy. But there’s no reliable way to prove it. No audit trail. No traceability. No single view of what was applied, where, by whom, and why.

If that’s your process, your policy is providing the intention of governance, not the reality of it.

Why this matters more than it used to

Reward governance has traditionally been treated as an internal concern - important, yes, but manageable behind closed doors. That's changing.

Pay transparency regulation is expanding. Shareholders and governance agencies are scrutinising remuneration reports more closely. Remuneration committees are under pressure to demonstrate that pay decisions are defensible, consistent and free from bias. And internally, employees and HRBPs are asking sharper questions about how compensation decisions are made.

A policy document doesn't answer those questions. A governed, traceable process does.

The organisations that are ahead of this aren't waiting for legislation to force the issue. They're building the infrastructure now - not because it's a compliance exercise, but because it makes the reward function materially better at its job.

What "connecting policy to process" actually means

It's a straightforward idea that's surprisingly hard to execute in a spreadsheet-based environment.

Connecting policy to process means that when your compensation policy says increases are capped at X% for Grade DU employees with a performance rating of Y, the system enforces that cap - automatically, at the point of entry, before any approval is sought. It means that if a manager tries to exceed the mandate, the system flags it, routes it for exception approval, and records the outcome with a timestamp.

It means your STI scheme rules - eligibility criteria, performance weightings, payout formulas - are configured once, applied consistently, and visible to every stakeholder with the appropriate access level. Not rebuilt from scratch every cycle in a new workbook.

It means your long-term incentive (LTI) grants are managed against the scheme rules you've actually approved, with vesting schedules, performance conditions and IFRS 2 accounting handled in the same system that ran the grant process.

And it means that when your CFO, Head of Reward, or RemCo asks "who approved this, and was it within mandate?", the answer is a click - not a forensic search through email chains and spreadsheet versions.

The three places the gap usually shows up

In practice, the policy-to-process gap tends to be most visible in three areas.

Increase mandates and overrides. Policies define mandates. But without a system that enforces them, overrides happen informally and often without adequate documentation. By the time the cycle is audited, the rationale for an exception may exist only in someone's memory.

Incentive scheme consistency. STI calculations that should follow a formula sometimes get adjusted at the last minute based on manager discretion or late-changing performance data. Without a configured system, it's difficult to distinguish a legitimate adjustment from an undocumented one.

Approval chains. Most organisations have a clear view of who should approve what on paper. In practice, approval often means an email sign-off, a verbal in a meeting, or a decision that gets ratified retrospectively. That's not an audit trail. It's a risk.

None of this is unusual. It's the natural result of trying to run a complex, rule-driven process in a tool that wasn't designed for it.

What a governed system changes

When your compensation policy is built into the platform rather than transcribed into a spreadsheet, a few things change fundamentally.

Mandates become enforceable, not just documented. Rules apply at the point of entry, not after the fact. Exceptions require a deliberate approval step and that step is recorded.

Approval workflows become traceable. Every decision, every override, every sign-off has a timestamp and an owner. The audit trail isn't assembled after the fact; it builds itself as the cycle runs.

Stakeholders get the right view, not just a report. The Head of Reward sees the full cycle in real time. The CFO sees cost impact by business unit. Line managers see their team, their budget, and their mandate - nothing more, nothing less. RemCo sees outcomes and governance documentation that's ready to present, not prepared overnight before the meeting.

And the reward team gets time back. Not time to do more administration - time to actually analyse, advise and improve. Which is what the function is supposed to be doing.

A practical starting point

If the policy-to-process gap is a problem you recognise, the starting point isn't a system overhaul. It's a process audit.

Map your last reward cycle. For each step - mandate setting, data loading, manager decisions, approvals, letter generation - ask: where does the policy actually get enforced? Where is the audit trail? Where does the process rely on an individual's judgment or memory rather than a documented, traceable step?

The gaps that surface are the places where governance is happening on paper but not in practice. They're also the places where a system like alignd can have the most immediate impact, not by replacing your reward philosophy, but by making it operationally real.

A compensation policy is only as good as the process that executes it. If that process lives in a spreadsheet, the policy is, at best, a guide. At worst, it's a liability.

Want to see how alignd connects your reward policy to a governed, traceable process? Book a demo and we'll walk through your specific cycle.