Human Resources Competency Model
Most organisations that ask for a "human resources competency model" actually want three different things at once: a generic list of HR skills, a capability statement for the function, and an assessment tool for performance reviews. These are not the same artefact, and conflating them is why so many HR competency projects stall before they produce anything usable. A human resources competency model is a specific, narrower thing than any of those, and it only works when it is built as one.
What Is a Human Resources Competency Model?
A human resources competency model is an applied selection of competencies drawn from an organisation's broader competency framework, tailored to the HR function as a job family. It defines what effective performance looks like for people working in HR roles, expressed as proficiency levels and behavioural indicators rather than a duties list.
The distinction between a competency and a competency model matters here. A competency is the integration of skills, knowledge, judgement and behaviour applied effectively in the context of a role. A model is what you get when you select and calibrate a set of those competencies for one specific group, in this case, HR professionals, rather than the whole organisation.
This means a human resources competency model is not a standalone document invented from scratch. It is a function-specific instance of something larger. If your organisation does not yet have a governing competency framework, what gets called an "HR competency model" is usually a one-off list with no structural foundation underneath it, which is part of why these projects are hard to maintain past their first year.
Why a Human Resources Competency Model Exists
HR is unusual among corporate functions because it is simultaneously a discipline with its own technical competencies (employee relations, reward, talent acquisition, workforce planning) and a function that is expected to model the behavioural standard for the rest of the organisation. A generic, organisation-wide competency framework rarely captures this dual demand with enough precision to be useful for HR-specific decisions such as capability gap analysis, succession planning within the function, or HR career pathing.
The model exists to solve a specific problem: translate broad organisational competencies into something specific enough to assess, develop and recruit against within HR. Occupational classification systems can describe the tasks and worker characteristics associated with HR roles in general terms, but they are not built to express an organisation's own performance standard. The U.S. Department of Labor's O*NET database is a useful illustration of the difference: it catalogues the knowledge, skills and work activities typical of human resources specialists across the labour market, which is valuable for workforce data, but it is not calibrated to any one organisation's proficiency expectations or career structure. A human resources competency model has to do that calibration.
How a Human Resources Competency Model Works in Practice
In practice, a human resources competency model is built by selecting competencies from three layers and applying them to the HR job family.
Core competencies. These are the competencies every employee in the organisation is expected to demonstrate, carried into the HR model as the shared baseline. They are not unique to HR, but they sit inside the model because HR professionals are assessed against them like everyone else.
Behavioural or interpersonal competencies. HR work is relationship-heavy by design, so this domain tends to carry more weight in an HR model than it would in a purely technical function. Stakeholder influence, conflict resolution and ethical judgement typically sit here.
Technical or functional competencies. This is where the model becomes genuinely HR-specific: recruitment and selection, employee relations, remuneration and benefits, workforce planning, HR systems and data, and increasingly, AI literacy applied to people decisions. The full distinction between this layer and the broader concept of a competency model is covered in more depth elsewhere, but the short version is that a competency model is the applied instance, and the technical domain is where that application is most visible.
Each competency in the model is then set against proficiency levels, usually four to six, defined by scope, autonomy, complexity and impact rather than job title or tenure. An HR coordinator and an HR business partner might both be assessed against "employee relations," but the behavioural indicator at each level describes a materially different standard of judgement and independence.
What a Human Resources Competency Model Is Not
It is not a job description. A job description lists duties and reporting lines; a competency model describes the standard of performance behind those duties, independent of any single role title.
It is not a competency framework. The framework is the organisation-wide governing system, the rules, definitions and proficiency architecture that apply across every function. The HR competency model draws on that framework but is scoped to one job family. An organisation can have one framework and dozens of models sitting underneath it.
It is not a competency matrix. A matrix is the grid that plots people or roles against required and current proficiency. It is an assessment artefact built from the model, not the model itself. Building the matrix before the model exists is one of the more common ordering mistakes in this space.
It is not an occupational skills taxonomy. Classification systems describe what HR work generally involves across the labour market. A competency model describes what good performance looks like inside one organisation's specific context, calibrated to its own standards and career structure.
Named Frameworks Behind Human Resources Competency Models
Two named reference points dominate this space, and it is worth knowing what each one actually covers before borrowing from it.
The Society for Human Resource Management's Body of Applied Skills and Knowledge sets out behavioural competency clusters spanning leadership, business and interpersonal domains, alongside a technical HR knowledge domain, and was built from large-scale research with practising HR professionals. It underpins SHRM's certification exams, which means it is calibrated for individual credentialing rather than organisational performance management, a distinction worth holding onto if you are adapting it for internal use.
The CIPD's Profession Map takes a different structural approach, setting out core knowledge and core behaviours that apply to every people professional regardless of specialism, with specialist knowledge layered on top for different HR disciplines. It is closer in spirit to a true framework-and-model structure, since it explicitly separates the universal layer from the specialist layer.
Neither is a substitute for building your own model. Both are useful as calibration references, particularly for proficiency level descriptors and for checking that your technical competency list has not missed an established domain. My related piece on HR competency models goes further into how organisations adapt these named frameworks for internal use.
Common Failure Modes
Building the model before the framework. Without a governing framework underneath it, an HR competency model has no shared definitions, no consistent proficiency scale, and no mechanism to stay aligned with the rest of the organisation. It becomes an island, and islands get abandoned at the next HR system change.
Treating it as a duties checklist. When competencies are written as tasks ("processes payroll", "runs onboarding") rather than as integrated, levelled behaviour, the model collapses back into a job description with extra formatting. It stops being assessable.
Skipping the technical domain calibration. HR teams sometimes default to a purely behavioural model because the interpersonal competencies feel more universal and easier to write. The result is a model that cannot distinguish a strong employee relations specialist from a weak one, because the functional expertise was never defined.
Letting it go stale. HR's own technical domain changes faster than most functions right now, particularly around HR systems, data and AI-supported decision-making. A model that is not reviewed against current practice within two to three years will misrepresent what good HR performance actually looks like.
Trade-Offs and Constraints
A human resources competency model is worth building when the organisation has, or is building, a governing competency framework, when HR has enough internal role variation to justify levelled proficiency rather than a flat skills list, and when the output will genuinely drive decisions such as recruitment criteria, development planning or succession within the function.
It is not worth building in isolation if the organisation has no framework at all. In that case, a narrower, faster reference such as the 5 Competency Model for HR Professionals is often more realistic as a starting point than a full model build, with the proper framework-anchored model following once the organisation-wide structure exists.
The constraint to hold onto throughout is scope discipline. An HR competency model describes the HR function, not the entire workforce, and trying to make it do double duty as the organisation's whole competency framework is how these projects lose their precision.
FAQ
What is the difference between an HR competency model and an HR competency framework?
A framework is the organisation-wide governing system that defines competencies, proficiency levels and rules of application across every function. A model is the applied selection from that framework, scoped specifically to the HR job family.
How many competencies should a human resources competency model include?
Most usable models hold between eight and fifteen competencies across core, behavioural and technical domains. Beyond that range, models become difficult to assess against consistently.
Is the SHRM BASK the same as a human resources competency model?
No. The SHRM BASK is a certification framework built for individual credentialing across the HR profession generally. An organisation's own HR competency model is calibrated to its specific proficiency standards and career structure, though it can reference the BASK's competency domains.
Can a human resources competency model exist without a competency framework?
It can be drafted without one, but it will lack a consistent proficiency scale and shared definitions, which limits how reliably it can be assessed against or maintained over time.
How often should a human resources competency model be reviewed?
Every two to three years at minimum, and sooner if HR's technical domain shifts materially, such as the introduction of new HR systems or AI-supported decision tools.
Does a human resources competency model apply to all HR roles equally?
The competencies are shared across the job family, but the proficiency level expected at each competency varies by role. An HR coordinator and a head of HR are assessed against the same competency set at different levels of scope, autonomy and complexity.