The VPS Capability Framework: Structure, Levels and How It Works

The VPS Capability Framework is one of the most widely used workforce tools in the Victorian public sector, and arguably one of the most inconsistently applied. I've seen it treated as a development checklist, a recruitment scoring matrix, a performance review template, and occasionally as organisational wallpaper. The gap between what the framework is designed to do and how it lands in practice is significant, and it starts with a misunderstanding of what kind of construct it actually is.

What Is the VPS Capability Framework?

The VPS Capability Framework is a government-mandated capability taxonomy that defines the behaviours, knowledge, and attributes the Victorian Public Service workforce needs to deliver on current and future objectives.

Published and maintained by the Victorian Public Sector Commission (VPSC), the framework establishes a common language for capability across the VPS. It describes what good performance looks like at different levels, independent of any specific role or agency. You can read the framework directly on the VPSC website.

The framework is underpinned by the Victorian public sector values: responsiveness, integrity, impartiality, accountability, respect, leadership, and human rights. Those values aren't decorative. They shape what capabilities look like in practice across the public sector and distinguish VPS capability expectations from their private sector counterparts.

Why Does the VPS Capability Framework Exist?

The Victorian public sector employs over 300,000 people across dozens of departments, agencies, and statutory bodies. Without a common framework, each organisation would define capability independently, resulting in inconsistent hiring standards, fragmented development activity, and no shared basis for workforce planning.

The VPS Capability Framework solves a coordination problem. It gives every agency in the VPS a shared definition of what good looks like, from a frontline employee in a service delivery role to a secretary running a central agency. That shared definition matters for workforce mobility, talent identification, and sector-wide planning in ways that agency-specific frameworks simply cannot replicate.

This is a problem the OECD has documented consistently across public sector systems globally. Research from the OECD's Public Employment and Management directorate shows that centralised competency frameworks, adopted by 72% of OECD Adherents, strengthen workforce planning coordination and reduce redundancy in how governments identify and develop talent.

The VPS framework operates in that tradition. It's not just a learning and development tool. It's an infrastructure decision.

How Does the VPS Capability Framework Work in Practice?

The framework is built around two structural dimensions: capability groups and proficiency levels.

Capability groups organise related capabilities into thematic clusters. The framework covers five groups: Personal Effectiveness, Relationships and Communication, Results, Business Enablers, and People Management (the last applying specifically to those in management roles). Each group contains a set of discrete capabilities. Personal Effectiveness might include self-awareness, adaptability, and professional credibility. Results covers goal-setting, decision-making, and delivering on commitments.

Proficiency levels describe how each capability is expressed at different stages of development and seniority. The VPS uses four levels: Foundational, Applied, Accomplished, and Leading. These are cumulative, meaning that the behaviours at the Accomplished level include everything defined at Foundational and Applied. This matters for how the framework is used in practice. You don't reset expectations at each level; you build on them.

The framework is designed to be applied across the employee lifecycle. In recruitment, capabilities can anchor role descriptions and structured interview criteria. In onboarding, they give new employees a clear picture of what's expected. In development conversations, they provide a shared vocabulary for discussing growth and identifying gaps. What you actually need to do well at any of this is understand how capability frameworks are designed to function; not just what they contain.

For comparison, the NSW Public Service Commission operates a comparable framework for its jurisdiction. I've written a detailed breakdown of the PSC Capability Framework, which covers how the NSW model differs structurally and where the two frameworks converge in their underlying logic.

What the VPS Capability Framework Is NOT

This is where a lot of implementation goes wrong.

The VPS Capability Framework is not a performance management tool. It describes capability expectations, not performance standards. Using it to assess whether someone "met expectations" in a review cycle conflates two different questions: what someone is capable of, and what they actually delivered.

It is not a competency model. A competency model defines the specific knowledge, skills, and behaviours required for particular roles or role families. The VPS framework is broader and more generic. It applies across the entire public sector, not to a specific function or job type. A capability framework and a competency model serve different purposes. I've written about what capability actually is and how it differs from competency in more depth, but the short version is that capability describes potential and future readiness, where competency describes current role-specific requirements.

It is not a skills taxonomy. The VPS framework does not decompose work into discrete, transferable skills the way a framework like SFIA does. It describes capabilities at a higher level of abstraction, which makes it useful for culture and development conversations but less precise for workforce planning that requires skills-level data.

It is not a substitute for a well-designed role architecture. The framework doesn't tell you which capabilities are required for which roles. That requires job design work to translate framework capabilities into role-specific requirements.

The VPS Framework and Broader Public Sector Standards

The VPS Capability Framework sits within a broader ecosystem of public sector workforce instruments. The VPSC also publishes the VPS Executive Classification Framework, which governs senior role classifications separately from capability definitions. These instruments are related but distinct.

Internationally, frameworks like the OECD's own competency model define fifteen core competencies grouped into three clusters for its own workforce. The VPS framework shares structural characteristics with these approaches: a finite set of capabilities, multiple proficiency levels, and behavioural indicators that translate abstract constructs into observable practice.

The 2024 review of workforce capability across the Victorian public sector by the Victorian Auditor-General's Office examined whether public service agencies had the policies and practices in place to actually build workforce capability. The findings were instructive: having a framework is not the same as using it systematically. Most agencies lacked the integration between recruitment criteria, development activity, and capability data that makes a framework genuinely useful.

Common Failure Modes in VPS Framework Implementation

The most persistent failure is framework adoption without integration. Agencies acknowledge the VPS framework exists, may reference it in position descriptions, but don't use it consistently in hiring decisions, development conversations, or workforce planning.

A second failure mode is level inflation. Organisations routinely set capability level expectations higher than the work genuinely requires. A role that demands Applied-level capabilities gets pegged at Accomplished, which distorts recruitment, discourages strong candidates who self-screen out, and inflates development expectations.

A third is mistaking proficiency level for seniority. The four levels are not synonymous with classification levels. A VPS 3 could legitimately be expected to perform at Applied or Accomplished level depending on the role. Treating the framework as a direct mapping to grade conflates two different systems.

Underlying most of these failures is a weak connection between the framework and the real work. The framework describes generic capabilities. Translating those into what genuinely matters for a specific agency, function, or role requires deliberate capability framework design work that doesn't happen automatically when an agency adopts the VPSC document.

Trade-offs and Constraints of the VPS Capability Framework

The VPS Capability Framework's strength is also its constraint. A framework that applies across the entire Victorian public sector cannot be highly specific. It necessarily describes capabilities at a level of generality that accommodates a nurse, a policy analyst, and a procurement manager under the same headings. That breadth is useful for sector-level consistency but creates tension when agencies need precision.

For roles with highly technical or specialist requirements, the VPS framework will always need to be supplemented with role-specific capability or skills definitions. Treating the framework as a complete picture of what a specialist role requires will produce under-specified hiring criteria and development plans that don't address what the role actually demands.

The framework is also a static instrument applied to a dynamic context. Capabilities that were fit for purpose five years ago may not fully reflect what the VPS needs now, particularly as digital, data, and AI capabilities become increasingly central to public sector work. The 2025 Capability Development Statement signals that the VPSC recognises this gap. Whether the framework itself is updated to reflect evolving capability demands remains to be seen.

Frequently Asked Questions About the VPS Capability Framework

What is the VPS Capability Framework?

The VPS Capability Framework is the Victorian Public Service's sector-wide capability taxonomy, published by the Victorian Public Sector Commission. It defines the behaviours, knowledge, and attributes required of the VPS workforce, organised into five capability groups and expressed across four proficiency levels.

What are the four proficiency levels in the VPS Capability Framework?

The four proficiency levels are Foundational, Applied, Accomplished, and Leading. They are cumulative: each level includes the behaviours defined at all preceding levels. The levels are not directly mapped to VPS classification grades, though in practice higher grades typically correspond to higher proficiency expectations.

How is the VPS Capability Framework used in recruitment?

In recruitment, the framework is used to anchor capability-based selection criteria. Role descriptions draw on relevant capabilities and proficiency levels to define what the position requires. Structured interviews and other selection tools are then designed to assess candidates against those capability expectations.

What is the difference between the VPS Capability Framework and a competency framework?

The VPS Capability Framework describes broad capabilities that apply across the public sector, independent of specific roles or functions. A competency framework defines the specific knowledge, skills, and behaviours required for a particular role, function, or job family. The two can coexist: an agency might use the VPS framework for sector-wide consistency and develop supplementary competency frameworks for specific occupational groups.

Is the VPS Capability Framework the same as the VPS Executive Classification Framework?

No. The VPS Capability Framework defines capability expectations across the workforce. The VPS Executive Classification Framework governs the classification and remuneration of executives. They are related instruments but serve different functions. The executive framework draws on capability concepts, but classification is a separate system from capability definition.

Who maintains the VPS Capability Framework?

The framework is maintained by the Victorian Public Sector Commission (VPSC). The VPSC also provides supporting tools including a capability self-assessment instrument and a career development planning resource.