Buy a leveling framework or build one?
A framework gives you shared words. Where each line falls is still your decision.
Short answer: Buy the language, own the decisions. A commercial leveling framework or a survey publisher's level guide gives you tested wording and easier market matching. It does not place your jobs, decide where each level starts or meet equal pay rules for you. The sound middle path is one level guide in your own words, with a written crosswalk to the market levels you buy.
Three frameworks, one company
Picture a 220-person payments software company in Atlanta with 35 people in Dublin. It has no company-wide levels yet. It does have three leveling frameworks.
The first came with its salary survey. To submit data and read results, the comp team matched each job to the survey publisher's levels, so the publisher's level codes already sit in a spreadsheet next to every role. The second came with its compensation software, which ships with a preset ladder and asks for every employee to be placed on it before bands can be loaded. The third arrived with the new head of engineering, who brought the career ladder from a much larger tech company and has started using its level names in offer letters.
Now the CFO wants it settled. The question is simple: Why not license one framework, roll it out to everyone and be done this quarter? The head of people is less sure. The Dublin office will fall under Ireland's pay transparency law. Managers keep asking what "senior" means. The last promotion round produced arguments that nobody could settle with anything written down.
Both of them have a point. A bought framework would save months of drafting. But none of the three frameworks says where the line between two levels falls for this company's jobs. That is what the arguments were about.
This is a composite of a common situation, not a client. The pattern is the point. Growing companies rarely choose between buying and building in one clean decision. They collect partial frameworks from their survey, their software and their senior hires, then have to decide which one to stand behind.
Why buy or build is a hard call
A leveling framework is a set of level definitions: What the work at each level demands, written so that any job can be placed on the scale. The difficulty is that the framework has two jobs that pull against each other.
It has to travel. Levels are how you compare your jobs with the market. Survey publishers level jobs in their own terms so that many companies can match to the same benchmarks. If your levels line up with theirs, matching is quick and consistent from year to year. The more your levels are your own, the more each market match becomes a fresh judgment.
It has to fit. Levels are also how you describe careers inside the company: What a promotion means, where the manager track splits and how many steps a career has. A framework written to fit every company fits none of them exactly. Its words describe generic work. Its number of levels was chosen with someone else's size in mind.
Buying looks faster than it is. A bought framework comes with definitions, often training and sometimes a scoring method. It does not come with your placements. Every job still has to be read against the words and put somewhere. That is most of the work and nearly all of the argument.
Building looks cheaper than it is. Writing your own level guide costs nothing in license fees. It costs months of drafting and review. A homegrown guide with no tie to market levels also leaves the comp team translating at every survey cycle.
Then there is the law. In the EU, pay structures have to let employers compare work of equal value on objective, gender-neutral criteria [4]. A framework's reputation does not answer that. The way it is applied inside your company does [2]. Many companies are still early in this work. In a survey of 525 organizations fielded in late 2025, a compensation software and data provider found that 51.4% had a formal job architecture and roughly 30% were planning or building one [1].
Five traps in choosing a leveling framework
Each of these traps starts from a sensible wish: To save time, to match the market or to borrow something proven. Each one hands a decision to the framework that the company still has to make.
"We bought it, so leveling is done"
What it looks like: The company licenses a framework, runs a training session and treats the levels as settled. Managers then place their own people, usually on the level that matches each person's current title or pay.
Why smart teams fall into it: The framework is well designed and widely used. It is easy to believe that the hard thinking came in the box.
What it costs: The box holds definitions, not decisions. Where the line sits between two levels in your company, which jobs land on which side and who settles a dispute are still yours to decide. The EU's toolkit on gender-neutral job evaluation makes the point directly: Even a system that is formally gender-neutral can let bias in through the way its criteria are defined, applied, weighted or interpreted inside an organization [2]. When managers place their own people, the new framework ends up recording today's pay order in new words. Placing by title carries title inflation straight into the new levels.
"The survey's levels are our career levels"
What it looks like: The company takes the survey publisher's level codes from the matching spreadsheet and makes them the internal levels. Career paths, promotion criteria and titles are written around them.
Why smart teams fall into it: The matching is done and the codes are tied to market data. Using them inside the company seems like one less translation to maintain.
What it costs: Survey levels are written for matching across many companies, not for describing careers in one. They are broad by design. Their number may not suit your size either. Promotions then follow a data publisher's categories rather than real changes in your work. The levels are also tied to one source. If you later change survey or add a second source with its own levels, you either relabel everyone or keep levels that no longer match your data. Employees notice when their level changes for reasons that have nothing to do with their job.
"Its factors already cover the law"
What it looks like: The company chooses a widely used framework and treats its factors as proof that the levels meet equal pay rules.
Why smart teams fall into it: The framework has a long track record and analytical factors. It looks more defensible than anything written in-house.
What it costs: Frameworks measure different things. The leveling system the US Bureau of Labor Statistics uses for its own compensation survey, for example, rates jobs on knowledge, job controls and complexity, contacts and physical environment, on a scale of 1 to 15 [3]. The EU directive names skills, effort, responsibility and working conditions. It asks that relevant soft skills are not undervalued and that the criteria are agreed with workers' representatives where they exist [4]. Neither list is wrong, but nobody has mapped one to the other for your jobs until you do. In the UK, a tribunal can set aside a job evaluation study that discriminates or is otherwise unreliable [5]. In the US, a classification system offered to explain pay differences has to reflect the duties of the jobs and be applied the same way to everyone [6]. A respected method does not meet either test on its own. The way you applied it has to.
"We'll write our own from scratch"
What it looks like: A working group drafts level definitions for every family from a blank page. Each family writes in its own style. The drafts go through round after round of comments.
Why smart teams fall into it: The company's work feels unusual. A framework in its own words feels more honest and easier to explain.
What it costs: Months of drafting, then a translation problem that never ends. Families write differently, so a level 4 in sales and a level 4 in engineering stop meaning the same thing. Level wording drifts toward describing the people the group has in mind rather than the work. Because nothing ties the levels to market levels, the comp team makes a fresh judgment for every survey match each year. A homegrown guide that took two quarters can still be harder to defend than a borrowed one applied with care.
"Use the ladder from my last company"
What it looks like: A senior leader brings the career ladder from a former, usually larger, employer and rolls it out in their function. Other functions follow, or don't.
Why smart teams fall into it: The ladder is real, detailed and proven somewhere. It saves months. The leader already knows how to use it.
What it costs: It was proven for another company's size, work and pay. A ladder built for thousands of engineers often has more steps than a company of 200 needs, so each step gets thin and promotions come fast (see how many job levels you need). It also tends to cover one function, so the company ends up with one family on a borrowed scale and every other family on something else. Then the level names leak into offer letters and titles. They become promises before anyone has checked what they mean here.
What a sound leveling framework looks like
A sound leveling framework is not the most detailed one. It keeps the shared language and the company's own decisions apart. It also writes both down. Several qualities set it apart.
One level guide in the company's own words. Every family uses the same levels and the same account of what changes from one level to the next, such as scope, complexity, independence and impact. Family examples sit under the shared definitions, not in place of them. Levels come before the full family tree (see job family or level first).
Borrowed wording where it helps. Many sound guides take phrasing from a survey publisher's level guide or a licensed method, especially where that language is already used to match jobs. Borrowing words is fine. What matters is that the company decided where each line falls.
A written crosswalk to each market source. For each survey or data tool you buy, a short record shows which of your levels matches which of theirs, with a reason where the match is not clean. When you change data source, you redo the crosswalk, not the levels.
Placements made on the work, with a reason. Each job is placed by what it demands, not by title or pay. The reason is kept. A small group from several functions reviews placements together, so no manager levels only their own team.
Criteria you can map to the law. Where the company has EU staff, the guide shows how its factors cover skills, effort, responsibility and working conditions, including the people and emotional demands of a job [4]. Where the mapping has a gap, the gap is closed before pay is attached to the levels. If you also score jobs with points, the same mapping applies to the scoring plan (see which job evaluation method to use).
Criteria employees can read. In the EU, the criteria used to set pay and pay progression have to be easily accessible to workers [4]. A level guide that only the comp team can open fails that test, whoever wrote it.
One owner and a review rhythm. One person owns the framework, settles disputes and reviews it when the company's work changes. A request for a new level is a decision for the owner, not a favor a manager can win.
A quick check: Take two jobs from different families that sit on the same level. Ask whether someone outside the company could read your guide and your reasons and reach the same placement. If the answer depends on who wrote the definitions, the decisions are not yet written down.
The calls only you can make
Whichever route you take, a few decisions stay with the company. No framework makes them for you.
Whose language do you borrow? If one survey supplies most of your market data, borrowing its level wording keeps matching simple. If you use several sources, your own wording with a crosswalk to each is more stable. Choosing a salary survey and choosing level language are linked decisions (see which salary survey to buy).
How many levels and where does the manager track split? No framework answers this for your size and your work. It is a statement about how careers grow here.
Is a licensed method worth its cost? A licensed method can bring training, consistency and support. It also brings fees and sometimes a tie to one provider's data. Whether that is worth it depends on how many people will apply it and how often you will re-level.
Who places jobs and who settles disputes? Managers, a panel or the comp team. Each choice trades speed against trust. Whoever places jobs, the reasons should be written down.
What do employees see? The full guide, their own family's definitions or only their level. Where the EU directive applies, pay criteria must be accessible [4]. Elsewhere it is a choice. The less people can see, the more each promotion has to be explained one case at a time.
The law and the numbers
- How common it is. In a survey of 525 organizations fielded in November and December 2025, 51.4% had a formal job architecture, roughly 30% were planning or building one and 22% did not use job leveling to inform pay [1].
- Bias in a neutral system. The EU's 2026 toolkit on gender-neutral job evaluation says bias can enter a formally neutral system through how its criteria are defined, applied, weighted or interpreted within an organization [2].
- EU criteria. Pay structures must let employers assess equal value on skills, effort, responsibility and working conditions, agreed with workers' representatives where they exist, without undervaluing relevant soft skills (Directive (EU) 2023/970, Article 4(4)) [4].
- EU access to criteria. Employers must make the criteria used to set pay, pay levels and pay progression easily accessible to workers. Member states may exempt employers with fewer than 50 workers from the progression part (Article 6) [4].
- EU burden of proof. An employer that has not met the directive's transparency duties, including Article 6, has to prove there was no pay discrimination in a dispute (Article 18(2)) [4].
- UK. Where a job evaluation study has given two jobs different values, a tribunal treats them as not of equal value, unless it suspects the study discriminates because of sex or is otherwise unreliable (Equality Act 2010, section 131) [5].
- US. Under federal equal pay guidance, a job classification system used to explain pay differences must accurately reflect job duties and be applied consistently [6].
- Public frameworks exist. The US Bureau of Labor Statistics levels jobs for its compensation survey on four factors and 15 levels. It describes the method publicly [3].
This is general information, not legal advice. Pay transparency and equal pay laws differ by country and state. Check the rules where your people work.
Our view
We think you should buy the language and own the decisions. Borrow level wording where it saves time and keeps market matching consistent, especially from the survey you rely on most. Then write one company level guide that says, in your own words, where each level starts and ends. Keep the crosswalk to each market source next to it, not inside it.
We would not let a framework's name stand in for the work of placing jobs. That is where the cost sits and where the risk sits. We would not spend two quarters writing every definition from a blank page either. Most of the value is in the placements and their reasons, not in the prose.
And we would keep the framework portable. If changing your salary survey or your software would force you to re-level your people, the levels belong to the tool, not to you.
Where we help
Our job architecture work writes one level guide for your company, with proven wording borrowed where it helps. It places your current jobs on it with a reason for each. Our job evaluation can add a crosswalk to the grades or survey levels you already use.* The entry point is our Leveling Starter Kit, for up to three job families. If a conversation would help first, Book a free call.
*We don't provide market data. We use the data you have or buy. No data yet? We help you choose a survey or tool that fits your size and budget.
Sources
- Salary.com, 2026 State of Pay and Compensation Practices Report, press release (14 April 2026; 525 organizations, November to December 2025), checked 2026-10-27
- European Institute for Gender Equality, EU-wide guidelines on gender-neutral job evaluation and classification: Step-by-step toolkit (26 March 2026), page 19, checked 2026-10-27
- US Bureau of Labor Statistics, How pay and benefits change as job level rises: Data from the National Compensation Survey, Beyond the Numbers vol. 6 no. 8 (June 2017), checked 2026-10-27
- Directive (EU) 2023/970 on pay transparency, Articles 4, 6 and 18 (EUR-Lex), checked 2026-10-26
- Equality Act 2010, section 131: Assessment of whether work is of equal value (legislation.gov.uk), checked 2026-10-26
- US EEOC, Compliance Manual Section 10: Compensation Discrimination, 10-IV.F.2.d (job classification systems), checked 2026-10-26