Why your organization needs a levels document

Executive overview

Unfair or inconsistent pay causes employees to slack off or quit — yet 95% of employers struggle with it. A levels document ties compensation directly to measurable skill, scope, and experience, making pay transparent and defensible.

HR should lead the project, but managers do the heavy lifting. The result is a shared framework that guides raises, reduces liability, and frees HR from ad-hoc compensation disputes.

A levels doc turns pay from a source of resentment into a driver of intentional growth.

What a levels document is

• A visual grid mapping skill, scope, and years of experience to compensation — unique to each team.
• The sum of skill and scope (scored 1–8) plus years of experience determines the level; the level determines the salary band.
• Not company-wide — works best per team, because each team has distinct moving parts.
• Makes career advancement concrete: employees can see exactly what they need to do to reach the next level.

The four categories

• Years of experience — scale it beyond four or five years to reflect real career trajectories.
• Skills — defined by the manager; describes what an entry-level hire can do and what competency looks like at each step up.
• Scope — how a team member fulfils the team's purpose; the difference between meeting requirements and improving on them.
• Compensation — set by HR once the other three categories are defined; requires payroll knowledge most managers lack.

Skills in practice

• Managers outline the skill floor for entry-level and the ceiling for senior levels (e.g., coding in one language vs. deploying code across five+).
• A subject-matter-expert (SME) section lets managers map cross-training opportunities for specialised roles.
• Standard HR procedures — communication guidelines, policy adherence — can be embedded as levelling criteria, incentivising compliance without enforcement overhead.

Scope vs. skill — a key distinction

• Skill: learning to run payroll without oversight.
• Scope: identifying flaws in payroll and implementing fixes that improve the whole process.
• Levelling up scope raises expectations of leadership, not just task execution.

Why HR should lead this project

• Compensation — HR understands the org's budget and can tie levels to economic realities like inflation or downturn.
• Compliance — levels docs support pay transparency laws (already in force in many states); should live in the employee handbook or HRIS, accessible to all.
• Standardisation — removes manager discretion from individual raise decisions; a documented standard prevents pay inequity and the resentment it causes.
• Prosperity — skilled employees generate higher revenue, enabling better hiring, retention, and benefits — freeing HR to pursue higher-value work.

The cost of not having one

• A manager gives a raise to reward a one-time win; teammates with steadier growth feel passed over.
• Resentment spreads through back channels; effort drops; people quit.
• HR ends up recruiting to fill gaps, disrupting budgets and strategic projects.
• A levels doc prevents this cycle by making the rules visible and consistent before disputes arise.