Every few months someone asks me for a competency framework for their HR department. In most cases what they need is a smaller thing: a role-level selection of competencies pulled from the organisation's existing framework and tailored to the roles inside HR. The two get used interchangeably, and the mix-up matters, because building a governance system for one function when you needed a role profile is a lot of work for the wrong result. This article takes the system view: how to structure the framework for the HR function, how it relates to the organisation-wide one and when it is worth building at all.
What Is a Competency Framework for an HR Department?
A competency framework for an HR department describes the competencies that define good performance across the roles in the HR function, organised by domain and set against proficiency levels. In most organisations HR already sits inside a broader competency framework, and the department needs a set selected from it for HR roles, not a second framework running alongside. Where there is no organisation-wide framework and HR is the first function to formalise this work, the departmental structure does act as its own framework, complete with domains, levels and behavioural indicators. For one HR role, the competencies and required levels are a competency profile.
Either way the content is the same. A workable structure names the competencies HR roles are assessed against, groups them into domains, defines each at every level and states the observable behaviour expected. Without levelled behavioural indicators the whole exercise stays a list of aspirational words that nobody can assess a person against.
In most organisations HR draws on the existing framework and does not build a second one.
A note on terminology. A competency framework is also called a competency model, especially in the United States. I use competency profile for the competencies and required levels for one role, and competency matrix for the grid of required against current proficiency. Usage varies by region, and I explain the differences in this competency model definition.
Why HR Needs One
HR tells the rest of the organisation to define capability requirements, assess proficiency and manage development on a defensible basis. That is hard to do credibly while running its own recruitment, employee relations and workforce planning from vague job descriptions and instinct. A framework for the department gives HR the discipline it asks of engineering, sales and operations: named competencies, set proficiency expectations and a basis for hiring, developing and succession planning that does not depend on one manager's view of who is good at HR.
It also exists because HR is not one job. It is a job family covering recruitment, employee relations, compensation and benefits, learning and development, workforce planning, business partnering and HR operations, each with a different mix of technical competencies. That is a different question from what belongs in a general HR competency framework.
How It Is Built: Layers
A small set of core competencies applies to every HR role: stakeholder communication, sound judgement under confidentiality constraints and commercial awareness of the business HR supports. Beside it sit the specialist domains for each sub-discipline. Recruitment competencies differ from employee relations competencies, which differ again from reward. A well-built HR business partner competency framework shows how one HR job family is broken into competencies distinct from the rest.
Levels reflect scope, autonomy, complexity and impact, not title.
Four to six proficiency levels works, set by the scope, autonomy and complexity of the work at each level and not by title or years of service.
Starting From SHRM and CIPD
Most organisations do not start from a blank page. The SHRM Body of Applied Skills and Knowledge defines eight behavioural competencies in its 2026 edition: leadership and navigation, ethical practice, inclusive mindset, relationship management, communication, business acumen, consultation and analytical aptitude, plus HR expertise as a technical domain. The CIPD Profession Map takes a related approach, setting out core knowledge for every HR professional with specialist knowledge areas such as workforce planning or employee experience, written at four levels of impact. SHRM's is behavioural and North American in origin. The CIPD's is knowledge-based and impact-levelled.
What It Is Not
Most requests for a framework for HR are really requests for a role profile.
- Not a role profile. A profile is the selection built for one role, level or cohort, such as business partners or recruitment. The framework is the structure it draws from. See the competency framework guide.
- Not a capability framework. A capability is something a person carries across roles and contexts, durable and transferable. A competency is defined against one role's requirements. The HR framework says what good performance looks like in HR roles today, not the portable abilities a person holds.
- Not a job description or a curriculum. A job description states accountability. The framework states the standard of performance in meeting it. A levelled indicator is not a curriculum outline or a development plan.
Common Failure Modes
- Built in isolation. A structure unconnected to whatever the rest of the organisation uses, or built when there is none, cannot be compared with anything else and gets treated as HR's private artefact.
- One flat list. Not mapped to HR's actual job family. Frameworks built bottom-up, with research, data collection, focus groups and case interviews across the roles involved, hold up far better than ones drafted from a template.
- No behavioural indicators. Naming stakeholder management without describing it at each level leaves assessors guessing.
Trade-Offs and Constraints
A dedicated framework for the HR department is worth the effort when the function is large enough to have distinct job families, when workforce planning or succession inside HR is a live problem or when an HR information system selection needs competency data to run on. It is usually not worth it for a small team of two or three generalists, who can adopt the SHRM or CIPD standard directly with light adaptation to their own language. It is also premature when the organisation has no framework at all and no near-term plan to build one, because HR building its own in isolation risks one more competency list nobody outside HR trusts.
FAQ
Is a competency framework for the HR department the same as an HR competency model?
There is no difference in structure. Competency model is the usual US name for the organisation-wide system and competency framework is more common in the UK and Australia. The competencies and levels for one HR role are a competency profile.
What should it include?
A core layer common to every HR role, such as stakeholder communication and commercial awareness, plus domains for each sub-discipline: recruitment, employee relations, reward, learning and development, workforce planning and business partnering.
How many proficiency levels?
Four to six, set by scope, autonomy and complexity.
Should HR build its own before the organisation has one?
Generally no. Build or contribute to the organisation-wide framework first, then select HR's set from it.
What is the difference between a competency framework and a capability framework for HR?
A competency framework defines what good performance looks like in specific HR roles today. A capability framework describes broader, transferable abilities a person carries across roles and contexts.
Which named standards do HR frameworks draw on?
The SHRM Body of Applied Skills and Knowledge and the CIPD Profession Map are the two most widely adopted starting points, reflecting different views of what predicts strong HR performance.
