Mega-projects across the GCC — NEOM, Red Sea, Diriyah, Qiddiya, the Dubai Urban Master Plan 2040 — are hiring tens of thousands of contractors, subcontractors, and consultants over the next five years. The procurement teams awarding those contracts increasingly require vendors to demonstrate a structured career-progression framework: defined levels, defined positions, defined skills with target values per level, and auditable progression plans. The reason is straightforward — mega-project owners need confidence that contractors can deliver at scale without sacrificing safety, quality, or Saudization ratios. This article breaks down why skills-based HR has become a procurement prerequisite in the GCC, the five components of a career-progression framework that actually sticks, and how U HR's Level Definitions, Position Catalog, Skill Catalog, and Level Progression Plans fit together.
Why skills-based HR matters for GCC mega-projects #
The shift from job-title-based HR to skills-based HR is not a Western trend that the GCC is copying; it is a structural response to how mega-projects actually operate. A contractor delivering a NEOM sub-development may need 200 civil engineers, 80 safety officers, and 50 QA/QC inspectors across three shifts and four sites — and the procurement owner needs to know that each person meets a defined competency bar before they step on site. Job titles alone do not establish that bar; skill catalogs with target values per level do. Skills-based HR also supports Saudization compliance: by defining skills and target values per level, employers can show MHRSD exactly which roles Saudis are qualified to fill and which require expat expertise, turning Nitaqat from a defensive compliance exercise into a workforce-planning tool. The same logic applies to mega-project safety: a Skill Catalog that tracks safety certifications per level lets the project owner verify that every contractor on site has the right training, which is the foundation of any ISO 45001 or Civil Defense audit.
The five components of a career-progression framework #
A career-progression framework that actually sticks has five interlocking components. Skip any one of them and the framework collapses into a spreadsheet exercise within a quarter. The components map directly to features in modern HR systems, which is why skills-based HR is a software question as much as a process question. The five components below are not optional; they are sequential — each one depends on the previous one to mean anything in practice.
Level Definitions and Position Catalog #
Level Definitions are the codified, organisation-wide ladder of levels — typically 8 to 12 bands — that every employee, manager, and recruiter refers to. The point of having an explicit Level Definitions object in the HR system is to prevent level inflation: without a shared ladder, each manager invents their own, and 'senior engineer' means something different in every department. The Position Catalog is the catalogue of every position the organization can hire into, each mapped to a level and a set of advancement criteria. Without a Position Catalog, job postings drift away from the level framework within months — recruiters write whatever title sounds competitive, and the org chart loses its meaning. U HR's Level Definitions and Position Catalog features enforce that every position has a level, a reporting line, and advancement criteria, so the ladder is the same whether you are hiring in Riyadh, Jeddah, or Dammam — and procurement owners can audit the framework in minutes rather than weeks.
Skill Catalog with target values per level #
The Skill Catalog is where skills-based HR earns its name. It is the catalogue of competencies — technical skills, behavioural skills, certifications — each with a target value per level. For example, 'structural analysis' might be expected at level 2 (basic), level 3 (proficient), and level 4 (expert) for civil engineers, with each level having an explicit target value. U HR's Skill Catalog lets HR define skills, attach target values per level, and assess employees against those targets — producing a competency matrix that procurement owners can audit. This is the single feature that turns an HR system from a record-keeping tool into a workforce-capability tool, and it is what mega-project procurement teams increasingly ask to see during vendor qualification. The same Skill Catalog doubles as a Saudization-planning asset: by mapping which skills Saudi nationals currently hold versus which the project needs, you can target training investments rather than relying on blunt expat-to-Saudi ratios alone.
Level Progression Plans and calibration #
Level Progression Plans are the individual paths that move employees up the ladder — with progress, dates, and approval — turning levels from a static label into a visible career trajectory. U HR's Level Progression Plans let managers and employees co-author a path: which skills need to move from level 2 to level 3, by when, with what evidence, and approved by whom. The employee sees their personal level path through the U HR Employee app, turning career progression from a once-a-year conversation into a visible, trackable artifact. Calibration is the periodic review that keeps the framework honest: without quarterly cross-manager calibration, level inflation creeps in and the framework loses its credibility. U HR's Skills & Calibration feature gives HR leaders an org-wide view of skills, approvals, and tracks across companies, while the Employee Manager app surfaces this for CHROs and COOs who need to oversee level management organization-wide. Together, progression plans and calibration convert the framework from a document into a managed workflow.
Common pitfalls in career-framework rollouts #
Most career-framework initiatives fail in the same predictable ways, and the failures are visible in the HR system's data within months. The first pitfall is defining levels without skill targets — the ladder exists but no one knows what competency bar each rung represents, so promotions become tenure-based rather than merit-based. The second is building the framework in a spreadsheet that HR owns alone — without manager and employee touchpoints in the daily HR system, the framework stays theoretical. The third is skipping calibration — without quarterly cross-manager reviews, level definitions drift department by department. The fourth is failing to surface progression plans to employees — when employees cannot see their own path, they assume there isn't one. The fifth is treating the framework as a one-time project rather than a living artifact — without ongoing updates to skills, target values, and positions, the framework ossifies within a year.
How U HR implements skills-based HR #
U HR implements the five-component framework as native domain objects rather than configuration overlays. The U HR Manager app exposes Level Definitions, Position Catalog, Skill Catalog, and Skills & Calibration as first-class screens — each with EN+AR labels, RTL layout, and multi-entity scoping. The U HR Employee app exposes Levels and Level Progression Plans to every employee, so a Saudi engineer in NEOM can open their phone, see their current level, see the skills they need for the next level, and see the date their manager has targeted for the next review. The Employee Manager app surfaces Skills & Calibration and Level Management for executives overseeing the framework across companies — turning calibration from a quarterly meeting into a continuous oversight workflow. Approval Workflows centralize level changes, skill endorsements, and progression-plan approvals — so that every change is auditable, which is exactly what mega-project procurement owners ask to see during vendor qualification. The result is a framework that lives inside the daily HR system rather than in a slide deck that nobody opens after the kickoff.
From framework to people-first workflow #
The strongest career-progression frameworks are not the most complex — they are the ones employees actually use. That requires the framework to live inside the daily HR system rather than in a slide deck or a spreadsheet, and it requires employees to see their own path without asking HR. U HR's people-first positioning is exactly this: Levels and Level Progression Plans are surfaced to every employee through the U HR Employee app, alongside Attendance, Working & Finance Info, and Self-Service Requests. Career progression becomes part of the employee's daily HR experience rather than an annual HR-only ritual. When employees can see their path, managers can calibrate, and executives can oversee — all in one connected system — the framework stops being a project and starts being the operating model. If you are starting a skills-based HR initiative in 2026, begin with Level Definitions, build the Position Catalog next, then stand up the Skill Catalog for your highest-stakes roles, enable Level Progression Plans in the employee app, and protect the first quarterly calibration meeting on every executive's calendar. Book a 30-minute HR audit demo with the Ukkera team, or start a free 14-day U HR trial to model your own framework.