Skill Mastery is the assessor's workbench inside U HR. It is the screen where a supervisor, a training lead, or an HR business partner records a proficiency value against a specific skill for a specific employee — and where every such recording carries the metadata that turns it from an opinion into evidence. A Skill Mastery record contains six fields: the employee, the skill, the proficiency value (typically on a 1–5 scale), the assessment date, the assessor, and the approval status. Those six fields are the smallest atomic unit of competency evidence in U HR, and they are what every downstream feature — Skills, Skill Approvals, Skills & Calibration, Career Progression, People Analytics — consumes. Without Skill Mastery, the rest of the cluster has nothing to render; without the rest of the cluster, Skill Mastery is just a spreadsheet with extra steps.
The six fields that make mastery evidence #
Each of the six Skill Mastery fields exists for a specific evidentiary reason. The employee and skill fields anchor the record to a real person and a real competency — they are pulled from Employee Records and Skill Catalog respectively, never typed in freehand, which prevents the spelling drift that destroys spreadsheet-based competency matrices over time. The proficiency value is a number, typically 1 to 5, drawn from a scale defined once at the catalog level — not a free-text comment that two assessors might interpret differently. The assessment date is a Hijri-and-Gregorian timestamp that lets Skills & Calibration flag stale records and lets Career Progression calculate time-in-skill for promotion criteria. The assessor is the named individual who recorded the value, scoped via HR Accounts so the assessor's authority is verifiable. The approval status is the audit-trail flag that proves the record was reviewed through Skill Approvals before it became canonical. Together these six fields answer the only question a Saudi Labour Law auditor or a NDMO reviewer actually asks: who says this employee has this skill, at what level, on what evidence, signed by whom?
How proficiency scales work in practice #
U HR does not force a single proficiency scale. The Skill Catalog lets HR define the scale per skill — typically 1 to 5, but some regulatory skills use a binary 0/1 (certified vs not certified) and some technical skills use a 1-to-10 scale for finer granularity. The choice matters because the scale determines what the gap calculation in the Skills screen actually means. A 1-to-5 scale with a target of 4 and a current mastery of 2 produces a gap of 2 — a meaningful, actionable number that the employee and their supervisor can plan around. A binary scale with a target of 1 and a current mastery of 0 produces a gap of «not yet certified», which is a different kind of conversation: it is a regulatory deadline, not a development goal. The Skill Mastery screen renders both kinds of gap correctly because the scale is part of the skill definition, not a global constant. This is the kind of design detail that distinguishes an HRIS built for skills-based organisations from one that bolted skills on as a custom field.
Skill gap analysis without spreadsheets #
Once Skill Mastery records exist for a population, skill gap analysis becomes a query rather than a project. The Skills & Calibration screen at the group level lets the HR Director filter by company, department, level, skill category, or skill type, and see the aggregate gap for that population in seconds. A typical query — «show me all HVAC technicians in the Jeddah facilities-management company whose mastery of "refrigerant recovery" is below the Level 3 target» — returns a list of employees with their current mastery value, the target, the gap, the last assessment date, and the assessor. From there, the HR Director can launch a training plan, schedule reassessments, or flag the gap for the next calibration session. This is the kind of analysis that takes a Saudi HR team two weeks to assemble from spreadsheets and one week to refresh; in U HR it is a saved filter that runs in under a second every time someone opens the page. The productivity gain compounds, because every mastery update from any assessor in any company refreshes the aggregate gap the moment the Skill Approval lands.
Why assessor identity is non-negotiable #
Every Skill Mastery record carries the assessor's identity, pulled from HR Accounts — not a free-text «assessed by» field that an employee could fill in themselves. This is not a UX nicety; it is a regulatory requirement. Saudi Labour Law articles on promotion decisions, MHRSD Saudization audits, and NDMO data-governance reviews all expect the HR system to be able to answer the question «who assessed this employee's skill, and on what date?» without consulting a side spreadsheet. Skill Mastery answers that question natively because the assessor field is a foreign key to the HR Accounts table, not a string. When an assessor leaves the company, their historical mastery records remain attributed to them — the audit trail does not decay. When an assessor changes roles, their new scope determines what they can assess going forward, but past assessments stay locked to the identity that made them. This is the kind of data-integrity detail that a Western HRIS retrofitted with a skills module typically gets wrong, because the underlying data model was not designed for evidentiary competency records.
A calibration scenario across five companies #
A Riyadh holding with five companies — construction, facilities management, catering, security, and landscaping — runs 47 assessors across the group. Each company has its own supervisors and training leads, and each tends to assess on a slightly different standard: the construction supervisors are strict on safety skills, the catering leads are lenient on customer-interaction skills, and the security assessors over-certify on equipment handling. The Skills & Calibration screen surfaces this drift at the group level: the HR Director sees that the average mastery value for "fire safety response" is 4.2 in the construction company, 3.1 in catering, and 4.7 in security — a spread that should not exist for a group-standardised safety skill. The calibration session that follows is not about changing the numbers in the system; it is about aligning the assessors' interpretation of the scale. Skill Mastery supports that workflow because every record is timestamped and attributed — the HR Director can filter to the assessors whose values look outliers, drill into the specific employees they assessed, and decide whether to require a reassessment or accept the deviation with a documented rationale. None of this requires exporting data; it is all native to U HR Manager.