What belongs in a pay policy?
A pay policy states your decisions. Procedures, yearly numbers and plan terms live somewhere else.
Short answer: A compensation policy should record the decisions that govern pay: Who it covers, how pay is set at each event (hiring, reviews, promotions, moves and pay outside the range), who decides and how people can ask about pay. Step-by-step procedures, this year's numbers and incentive plan terms belong in separate documents with their own owners.
Thirty-eight pages nobody opens
Picture a 140-person medical billing company in Cincinnati, Ohio. Two years ago, its first head of people wrote a compensation policy. She started from a template a peer had shared and added to it each time a question came up. It is now 38 pages long. It describes the merit cycle step by step, including which spreadsheet columns managers fill in. It lists the salary bands for every job as they stood in 2024. It sets out the sales commission rates. It has a section on a compensation committee the company has never had. It also says that employees must keep their pay confidential.
Managers do not use it. When a question comes up, they message the head of people. The bands in the policy are two refreshes out of date, so nobody trusts its numbers. The merit steps no longer match the payroll system. The company has hired in California and started recruiting in Ireland. A new finance lead reading the policy for the first time finds the confidentiality clause and asks whether it is lawful.
Then a dispute arrives. An employee who left before the pay review points to a line saying "all employees receive an annual pay review with an increase reflecting performance" and asks for the increase. The company had meant it as a description. The employee reads it as a promise.
This is a composite of a common situation at companies this size, not a client. The details are illustrative. The pattern is common because a compensation policy tends to become the place where every pay question gets written down, whether or not it belongs there.
Why writing a pay policy is hard
A compensation policy is the document that sets the rules for pay decisions: How pay is set and changed and who decides. It sits below the philosophy, which says why the company pays the way it does. It also sits below the strategy, which says what it will do this year. Our note on philosophy, strategy and policy covers how the three differ. This guide is about the policy itself: What goes in and what does not.
Two good goals pull against each other. The first is completeness. A policy is meant to answer pay questions without someone having to ask the head of people. Every time a manager asks something the policy does not cover, it feels like a gap to fill. Adding the answer seems responsible.
The second goal is durability. A policy is only useful if people trust it and it stays true. That means it has to be short enough to read, stable enough to survive a year and careful enough not to promise things the company cannot keep. Every detail added for completeness is another line that can go stale, contradict the system or be read as a commitment.
Most companies settle this by accident. In a 2025 survey of 133 employers in Canada, 75% of those without a formal compensation strategy said they followed consistent internal guidelines that were not written down. Another 25% left pay decisions to individual managers [1]. The same survey found that employee handbooks and policy documents were the most common way employers told staff about their approach to pay, used by 38% [1]. In a 2026 survey of more than 3,000 organizations, 63% said they believed their compensation policies drive positive outcomes [2]. Many companies have something written down and many believe it works. Far fewer have asked whether what is written is the right thing.
The law adds pressure from both sides. Pay rules increasingly expect decisions to be written down. The EU pay transparency directive requires employers to make the criteria used to set pay and pay progression easily accessible to staff [6]. At the same time, what is written can be held against the company if it reads like a promise or restricts rights staff already have.
Five ways a pay policy goes wrong
Each of these starts with a reasonable instinct: Write it down, use what others have done, be specific, reassure people, keep it simple. The cost comes from putting the wrong kind of content in the wrong document.
"Put every step in the policy so nobody has to ask"
What it looks like: The policy explains how to run each process: Which form to fill in, which system screen to use, the order of approvals, the dates for each stage of the merit cycle. Over time it becomes a manual.
Why smart teams fall into it: Procedures are what managers ask about most. Writing them into the policy seems to answer the questions where people will look. It also feels thorough, which is reassuring to a board or an auditor.
What it costs: Procedures change far more often than decisions. A new payroll system, a new approval tool or a change of review dates can make a page of the policy wrong overnight. Once managers find one outdated step, they stop trusting the rest, including the parts that are still right. The decisions that matter get buried among instructions. A manager looking for "can I offer above the range?" has to read past three pages on how to submit the offer. Procedures belong in a guide that HR owns and updates freely. The policy should say what the rule is and point to where the steps live.
"Start from a template, it's quicker"
What it looks like: The company takes a policy from a peer, a former employer or a template site and edits it. Sections for things the company does not have, such as a compensation committee or a job evaluation panel, stay in because nobody is sure whether they matter.
Why smart teams fall into it: A template looks complete and professional. Starting from a blank page is slow and the head of people often has no time. If another company used it, it seems safe.
What it costs: A template answers someone else's decisions. It describes governance the company does not have, which makes the whole document look like fiction. Worse, templates often carry clauses that are not lawful where the company now employs people. A line asking staff to keep their pay confidential is a common example. California bars employers from requiring employees to refrain from disclosing their wages, from asking them to waive that right and from disciplining anyone who does [3]. The EU directive says workers may not be prevented from disclosing their pay to enforce equal pay and asks member states to prohibit contract terms that restrict it [6]. A policy copied from a company in a different place, or written before these rules, can put the company in breach the day it hires somewhere new.
"Write this year's numbers in, so it's specific"
What it looks like: The policy states this year's merit budget, the band tables, the target percentile as a number for each job family, the location rates and the commission percentages. Every figure the company uses sits in one document.
Why smart teams fall into it: A policy without numbers can feel vague. Managers want to know the actual figure, not that "the budget is set each year". Putting them in the policy seems more honest than leaving them out.
What it costs: The numbers change every year and some change every quarter. A policy that contains them is out of date almost as soon as it is approved, or it has to be re-approved every time a figure moves. In practice it falls behind and the company ends up with two versions of the truth: The figures in the policy and the figures in the system. When a dispute arises, the outdated number in the policy is the one people quote. The better pattern is a policy that states the rule ("bands are reviewed once a year and approved by the chief executive and finance lead") and a separate schedule that holds the current figures, with a date and an owner.
"Add a line to reassure people"
What it looks like: The policy includes friendly statements meant to build trust: "Every employee receives an annual increase." "We always pay at the 60th percentile." "Bonuses will reflect individual contribution." "Sales staff will be paid commission on every deal they close."
Why smart teams fall into it: The company wants staff to feel secure and a policy full of conditions reads as cold. The intent is a description of what usually happens, not a guarantee. Many handbooks also carry a general line saying they are not a contract, which feels like enough protection.
What it costs: Staff and courts may read a description as a promise. In one Minnesota case, the state's highest court held that a general handbook disclaimer was ambiguous as applied to a paid time off policy, so the policy could still be enforceable as a contract. The employer, the court said, should have been more precise about what it intended [5]. A sentence that says everyone gets an increase may be read the same way in a year when the company decides to freeze pay. Incentive promises carry extra risk. In California, an employment contract that pays commissions must be in writing, set out how commissions are calculated and paid and be signed, with a receipt from the employee [4]. A line in a general policy is not a substitute for that plan document and may conflict with it. Our guide on commission on revenue, margin or ACV covers why plan terms need their own careful wording.
"Cover the main cycle and leave the awkward cases"
What it looks like: The policy covers starting pay and the annual review in detail. It says little or nothing about what happens on promotion, on a move to a different location, when someone is paid above the band maximum, on return from long leave or when an employee asks how their pay was set.
Why smart teams fall into it: The main cycle affects everyone, so it gets the attention. The awkward cases are rarer, harder to write rules for and often decided case by case anyway. Leaving them out keeps the document short.
What it costs: The awkward cases are where most disputes come from. A promotion with no rule for the raise, a transfer with no rule for location pay or a person above the maximum with no rule for future increases all become negotiations. Each one sets a precedent and different managers answer them differently. These are also the cases the law increasingly asks about. The EU directive expects the criteria for pay progression to be accessible, not just the criteria for starting pay [6]. California lets an employee ask for the pay scale for their own position [7]. A policy that is silent on how such a question is answered leaves the manager on the spot. Our guide on pay decisions the EU wants written down covers what "accessible criteria" asks for in practice.
What belongs in a pay policy
A sound pay policy is not measured by its length. It is measured by whether a manager can find the rule for a real situation in a few minutes and whether that rule is still true a year later. Several qualities set it apart.
It records decisions, not procedures. Each section states a rule and the reason for it in plain words: How starting pay is set within a range, what earns a merit increase, what a promotion does to pay, what happens outside the range. Where a process sits behind a rule, the policy names the document that holds it.
It covers every pay event, including the rare ones. Hiring, the annual review, promotion, transfer between roles or locations, pay above or below the range, return from leave and exceptions all have a rule, even if the rule is "decided case by case by the chief executive, with the reason recorded". A short rule for a rare case is better than silence.
It says who decides. The policy names the roles that approve each kind of pay decision and where the line sits between a manager's call and an exception. The detail can live in a one-page approval matrix. Our guide on who approves a pay exception covers why that line matters.
Numbers live in a dated schedule. Bands, budgets, location rates and percentile targets sit in a separate schedule with an owner and a review date. The policy says how and when they are set. The schedule says what they are now.
Plan documents stand on their own. Commission plans, bonus plans and equity plans have their own documents, written carefully for the legal weight they carry. The policy says such plans exist and who approves them. It does not restate their terms.
It describes without promising. Where the company wants to reassure, it says what it intends and what it depends on: "We aim to review pay each year. Increases depend on performance and the budget." It avoids "always", "every" and "guaranteed" unless the company truly means them.
It tells people how to ask. The policy says how an employee can ask how their pay was set or what the range for their role is and who answers. It does not restrict staff from discussing their own pay.
It has an owner and a date. One person owns the policy. It is reviewed on a fixed cycle, usually alongside the pay review. Each version is dated.
Where the policy will be used in several countries, we would expect local counsel to review it before it is adopted. A policy that works in one place can carry wording that does not work in another.
The calls only you can make
A policy turns choices into rules. The choices themselves belong to the company's leaders, not to whoever drafts the document.
How much discretion do managers keep? A tight policy gives consistent answers but slows managers down. A loose one is faster but produces different answers in different teams. Decide where the line sits for each pay event.
How much will you share with staff? Some companies publish the full policy to everyone. Others share a summary and keep the detail for managers. Pay transparency laws are narrowing the choice, but there is still a real decision about tone and depth.
Which commitments are you willing to make? If the company wants to promise an annual review or a minimum increase, it can. It should do so knowing the promise may be held to. If it does not want that, the wording has to say so plainly.
Who owns the policy? At most companies this size, the owner is the head of people with the finance lead as co-approver. What matters is that one person is accountable for keeping it true.
How will the awkward cases be handled? Deciding in advance what happens to someone above the band maximum or moving to a cheaper location is uncomfortable. Deciding it during the conversation with that person is worse.
The numbers and the law
- Unwritten rules are common. In an October 2025 survey of 133 Canadian employers, 58% had a documented compensation philosophy and 57% a documented strategy. Among those without a formal strategy, 75% followed consistent internal guidelines that were not written down and 25% left pay decisions to individual managers. Of employers that had seen more pay questions from staff, 51% had revised their compensation policies and documentation [1].
- Confidence in policies. In a survey of 3,413 organizations run in late 2025, 63% believed their compensation policies drive positive outcomes and 61% said they have a compensation strategy [2]. These are the publisher's own figures.
- California, pay secrecy. Employers may not require employees to refrain from disclosing their wages, ask them to sign a waiver of that right or discipline them for disclosing [3].
- California, commission plans. Where an employment contract pays commissions for work in the state, it must be in writing and set out how commissions are computed and paid. The employer must give a signed copy and obtain a signed receipt [4].
- California, pay scale on request. An employee may ask for the pay scale for the position they currently hold [7].
- Handbook promises. The Minnesota Supreme Court held in 2021 that a general disclaimer in an employee handbook was ambiguous as applied to its paid time off policy, so the policy could still be an enforceable contract [5]. This is one state's ruling, reported here through a law firm's summary.
- European Union. Employers must make the criteria for pay, pay levels and pay progression easily accessible to workers. Workers may not be prevented from disclosing their pay to enforce equal pay and member states must prohibit contract terms that restrict this [6]. Member states were due to transpose the directive by 7 June 2026.
This is general information, not legal advice. Employment and pay rules differ by state and country and change over time. Have counsel review a pay policy before it is adopted.
Our view
We think a good pay policy is shorter than most people expect. It states the decisions that govern pay, covers every pay event including the rare ones, names who decides and tells staff how to ask. Everything else lives in documents built for it: Procedures in a guide HR can change freely, numbers in a dated schedule and plan terms in plan documents.
We are wary of templates. They save a day of drafting and cost months of credibility, because they describe a company that does not exist and often carry clauses that no longer hold where the company employs people.
And we would choose every "always" and "every" in a policy on purpose. A sentence written to reassure is often the sentence quoted back in a dispute.
Where we help
Our compensation policy work turns your own bands and pay decisions into a written policy for one country, with a one-page approval matrix and short summaries for managers and staff. We keep procedures, numbers and plan terms in their own places, so the policy stays true. Your counsel reviews it before use. See compensation policy for how a project is scoped and priced. If a conversation would help first, Book a free call.
Sources
- Western Compensation & Benefits Consultants, Staying Competitive: Employer Compensation Philosophy, Strategy & Benchmarking (October 2025; 133 employers), checked 2026-10-28
- Payscale, 2026 Compensation Best Practices Report (3,413 responses, October to December 2025), checked 2026-10-28
- California Labor Code section 232, checked 2026-10-28
- California Labor Code section 2751, checked 2026-10-28
- Jackson Lewis, Minnesota Supreme Court holds general contract disclaimer in employee handbook may not prevent creating contractual obligations to pay out PTO (12 February 2021; on Hall v. City of Plainview, No. A19-0606, decided 3 February 2021), checked 2026-10-28
- Directive (EU) 2023/970 on pay transparency, Articles 6, 7 and 34 (EUR-Lex), checked 2026-10-25
- California Labor Code section 432.3, subsection (c)(2), checked 2026-10-28