Job architecture in a new HR system
The system stores your levels and job families. It cannot decide them. The setup timeline will push you to decide them in a hurry.
Short answer: Settle your levels, job families and the owner of new jobs before the system is configured. Load current titles as jobs and every report, band and pay data filing built on them inherits the mess. If time runs short, load levels first and keep families broad.
This is general information, not legal advice.
What the data and the rules say
A new platform rarely cleans up the data on its own. In a May 2026 survey of 405 senior leaders at employers with more than 1,000 staff in seven markets, 77% of those implementing or running a major HR and payroll platform still relied on manual checks, parallel systems or legacy backups. Fewer than three in ten reported significant progress on core outcomes [1]. The survey covered large employers and did not test causes. Our reading is simple: A system records the job data it is given, good or bad.
The rules now read those job fields. California employers with 100 or more employees file a yearly pay data report that counts staff and pay by job category. From 1 January 2027, the law replaces its 10 broad categories with 23 occupational groups, from chief executives to transportation and material moving. The same law requires demographic data to be collected and stored apart from personnel records [2]. In the EU, the pay transparency directive requires gender pay gap figures by category of workers. These are groups of people doing the same work or work of equal value, set by the employer on gender-neutral criteria [3]. Each of these reports starts from the job fields in your HR system.
What it means for a company of 50 to 500 people
The setup workbook arrives before the decisions. In the first weeks of an implementation, the project team asks for job codes, families and levels. The go-live date is fixed, so HR fills the sheet from current titles. The architecture is then whatever was typed that week. Every band, approval rule and report built later inherits it.
Titles get loaded as jobs. When each title becomes its own job record, one role splits into several codes. Two people doing the same work land in different groups, which is exactly what a pay gap report then counts. Our guide on mapping job titles to levels covers how to level the work before you settle the titles.
Levels exist only as numbers. A level field that runs from 1 to 7 with no written difference between the steps looks complete in the system and settles nothing. Managers then pick a level by pay or tenure. Our guide on whether job families or levels come first explains why the level definitions are the part to finish first.
Nobody owns new jobs after go-live. Anyone with the right access can create a job code. Without one owner and a rule for approving new jobs, codes multiply within months. That is how a clean build goes stale long before anyone plans to revisit it.
Our view
The HR system stores decisions. It does not make them. We would settle three things on paper before anyone opens the setup workbook: The level ladder with what separates each step, the job families and who approves a new job. If the go-live date cannot move and those decisions are not ready, load levels first and keep families broad. Splitting a family later is a small change. Re-leveling every employee record once bands and reports depend on it is not. We would never load titles as jobs to save a week. If you file a California pay data report, map your jobs to the new categories during the build rather than in a spreadsheet each spring.
Where we help
Our job architecture and leveling work sets your levels and job families and maps every role to them before your HR system is configured, so the system stores decisions you have already made. To discuss your own timeline first, Book a free call.
Sources
- Strada, Workforce Possibility Report 2026 press release (405 senior decision makers at organizations with 1,000+ employees in seven markets, published 27 May 2026), checked 2026-11-03
- California Government Code §12999, current text and the version added by SB 464 (Stats. 2025, ch. 760), operative 1 January 2027, checked 2026-11-03
- Directive (EU) 2023/970 on pay transparency, Articles 3 and 9 (EUR-Lex), checked 2026-10-25