Capability Frameworks: Examples, Types and How Organisations Use Them
Most organisations that say they are building capability could not tell you which specific capability framework they are working from. Some are inventing definitions as they go. Others have borrowed language from adjacent constructs without realising it. The ones that get it right are working from a named, structured framework with proficiency levels and behavioural indicators, and they can point to real examples of how similar frameworks have been applied in comparable contexts.
This article covers what capability frameworks actually are, the different types in use, and several named examples across sectors and use cases.
What Are Capability Frameworks
A capability framework is a structured document that defines the capabilities required of a workforce or role family, expressed at multiple proficiency levels. Each capability is described with observable indicators of what it looks like at each level, from foundation through to advanced or expert performance.
The term is used across government, the private sector, and professional associations, but the underlying structure is consistent: a defined set of capabilities, a levelling system, and descriptors that tell you what each capability looks like in practice.
Capability frameworks are used for workforce planning, role design, recruitment, performance assessment, and career development. Their value depends entirely on specificity. A capability framework that lists "communication" as a capability without defining what good communication looks like at each level is not doing useful work.
Why Capability Frameworks Exist
The problem capability frameworks solve is ambiguity. Without a shared definition of what the workforce needs to be able to do, organisations make inconsistent hiring decisions, set inconsistent performance expectations, and develop people against undifferentiated standards.
This is particularly visible in large organisations where the same role is performed very differently across teams or locations. A capability framework creates a common language. It makes workforce requirements explicit and assessable rather than inferred.
A second, related problem is succession and mobility. Without defined capability levels, organisations struggle to identify development gaps or assess readiness for more senior roles. A well-designed capability framework provides the architecture for talent decisions across the workforce lifecycle.
Types of Capability Frameworks
Capability frameworks vary in scope and structure depending on their purpose. Three broad types are most commonly seen in practice.
Whole-of-workforce frameworks define the capabilities expected across an entire organisation or sector, often with a common core and additional role-specific layers. These are most common in large public sector organisations and professional bodies that need consistent standards across diverse role families.
Function-specific frameworks define the capabilities required in a particular discipline or domain, such as digital, data, finance, or HR. They are more granular than whole-of-workforce frameworks and are often adopted from a named external standard rather than built internally from scratch.
Role-level frameworks define capabilities for a specific role or role family. These sit closest to the work and are most useful for recruitment and performance assessment, but require more design effort to create and maintain.
Examples of Capability Frameworks
The most useful way to understand what a capability framework looks like in practice is to examine real ones. The following examples span sectors, disciplines, and geographies.
APS Data Capability Framework
The Australian Public Service Commission's Data Capability Framework provides a common language for defining data-related capability across the Australian Public Service. It outlines 22 essential data competencies across seven levels of responsibility, from foundation-level awareness through to advanced application. The framework was developed through a cross-agency working group and has been updated to align with SFIA to enable greater consistency across government and with industry. The APS Data Capability Framework is a well-documented example of a function-specific framework developed for a whole-of-sector audience and grounded in an existing international standard.
NSW Public Service Capability Framework
The PSC Capability Framework, administered by the NSW Public Service Commission, defines the capabilities required across the NSW public sector workforce. It organises capabilities into four groups: personal attributes, relationships, results, and business enablers. Each capability is described across five proficiency levels. The framework is applied in recruitment, performance development, and workforce planning across NSW government agencies. It is a well-documented example of a whole-of-workforce framework applied at scale across a diverse workforce.
Victorian Public Service Capability Framework
The VPS Capability Framework defines what the Victorian Public Service workforce needs to be capable of, organised across five capability groups and four proficiency levels. It is applied in recruitment, development, and performance assessment and demonstrates how a government jurisdiction translates organisational strategy into workforce capability requirements at scale.
CIPD Profession Map
The CIPD Profession Map defines the knowledge and behaviours required of HR and people development professionals. It distinguishes between core behaviours expected of all HR practitioners, specialist knowledge required within practice areas, and the values that underpin professional practice. The Map is updated periodically to reflect the changing demands of the HR profession and is used by organisations and professionals across the UK and internationally as a reference for HR capability development.
DigComp
DigComp is a European Commission framework that defines digital competence for citizens across five areas: information and data literacy, communication and collaboration, digital content creation, safety, and problem solving. It uses proficiency levels from Foundation to Highly Specialised. DigComp is widely referenced in education and public policy contexts and is an example of a capability framework designed for a broad population rather than a specific workforce.
What Capability Frameworks Are Not
A capability framework is not a competency framework, though the two are often used interchangeably. Competency frameworks define the behaviours and performance standards required of a workforce, often including leadership expectations and personal effectiveness. Capability frameworks focus on what people need to be able to do, the skills, knowledge, and capacities that enable effective performance. The distinction matters in practice: building a competency model when you need a capability framework produces a document that cannot be properly applied to either purpose.
A capability framework is not a skills taxonomy. A skills taxonomy catalogues skills at a granular level, typically for workforce planning or job matching purposes. A capability framework clusters related skills and defines proficiency levels that describe how performance expectations increase with scope and responsibility. They serve different purposes and are built differently, though they are often used together in the same workforce system.
A capability framework is not a job description. A job description defines accountabilities and outputs. A capability framework defines the capacities needed to discharge those accountabilities effectively. Both are necessary, but they are not substitutes for each other.
Common Failure Modes
The most common failure in capability framework design is creating something too broad to be applied consistently. A framework that lists "problem solving" or "collaboration" without level-specific indicators cannot be used reliably in recruitment or assessment. Generality protects no one from the hard decisions that good capability design is supposed to make easier.
The second failure is misalignment between the framework and the actual work. Research on integrated human capability frameworks identifies that frameworks developed without co-design with practitioners in the relevant discipline lose their utility quickly. The frameworks that get used are the ones that reflect how the work is actually done, not how someone outside the function imagines it.
The third failure is building a framework and not embedding it in real processes. A capability framework that does not inform how roles are recruited for, how performance is assessed, and how development is planned is a document, not a system.
Trade-offs and Constraints
Whole-of-workforce frameworks offer consistency but require compromises at the level of individual disciplines. A single framework applied across diverse role families will always be more accurate for some roles than others. This is why many organisations operate a tiered approach: a common core supplemented by function-specific or role-specific layers.
Adopted frameworks, such as SFIA or the CIPD Profession Map, offer legitimacy and reduce design effort but may not reflect the particular context of your organisation without adaptation. Organisations that adopt an external framework wholesale without contextualisation often find that practitioners do not engage with it because the language does not match their day-to-day experience.
The design trade-off is always between breadth and specificity. A narrow, precise framework serves a specific population well. A broad, general framework covers everyone but tells individual practitioners less about what good looks like in their particular context. There is no design that resolves this tension entirely. The right answer depends on the scope of the workforce being covered and the primary use case the framework is built for.
Frequently Asked Questions
What is a capability framework?
A capability framework is a structured document that defines the capabilities required of a workforce or role family, with each capability described at multiple proficiency levels. It is used for workforce planning, recruitment, performance assessment, and career development.
What are some examples of capability frameworks?
Well-known examples include SFIA for digital and ICT roles, the APS Data Capability Framework for Australian public servants working with data, the NSW Public Service Capability Framework, the Victorian Public Service Capability Framework, the CIPD Profession Map for HR professionals, and the European Commission's DigComp framework for digital literacy.
What is the difference between a capability framework and a competency framework?
A capability framework defines what people need to be able to do, the skills and knowledge required for effective performance. A competency framework defines how people are expected to behave and perform. They are complementary but distinct, and conflating the two produces something that cannot be applied cleanly to either purpose.
Can a capability framework be used for recruitment?
Yes. A capability framework provides the basis for role-specific requirements that can be assessed through structured interviews, work samples, and capability-based assessment processes. It is more useful than a job description alone for identifying whether candidates can perform the work.
How many capabilities should a framework include?
There is no fixed number. Function-specific frameworks like SFIA include more than 120 skills. Whole-of-workforce frameworks like the NSW Public Service Capability Framework use a smaller set applied across the entire workforce. The right number depends on the scope of the framework and the diversity of the roles it needs to cover.
How often should a capability framework be reviewed?
Every two to three years in a stable environment. Frameworks covering rapidly evolving domains, such as data or digital, typically require more frequent review to remain aligned with what the work actually demands.