What Is the SFIA Framework and How It Works
Most people I speak with in technology workforce planning use the term SFIA framework loosely. They mean a skills list, a competency dictionary, a stack of job descriptions, or sometimes just a maturity model with a technology label attached. The SFIA framework is none of those things on its own, and treating it as one is the quickest way to implement it badly.
I want to be precise about what the SFIA framework actually is, the problem it was built to solve, how it works in practice, and where it stops. This matters because SFIA is now embedded in workforce systems across hundreds of organisations, and a lot of that work rests on a shaky understanding of what the framework does.
What Is the SFIA Framework?
The SFIA framework (Skills Framework for the Information Age) is a global reference model that describes the professional skills and levels of responsibility required by people who design, build, manage and protect digital and technology systems.
It is maintained by the SFIA Foundation, a not-for-profit body based in the United Kingdom, and the current edition is SFIA 9.
The framework is built on two axes. The first is a catalogue of professional skills, each one a defined area of technology or digital practice such as software development, data management, or information security. The second is a set of seven levels of responsibility that describe how much autonomy, influence and complexity a person carries, independent of any particular skill.
A SFIA description of work is always a combination of those two things: a named skill, expressed at a specific level. That structure is what makes SFIA a framework rather than a list. It gives organisations a consistent, vendor-neutral language for technology work that holds steady across roles, teams and employers.
Why the SFIA Framework Exists
The functional problem SFIA solves is incoherent language. Without a shared reference, every organisation describes the same technology work differently. A "senior developer" in one company maps to a "lead engineer" in another and a "software specialist" in a third, and none of those titles tell you what the person can actually do or how much responsibility they hold.
That incoherence has real costs. It makes workforce planning guesswork, recruitment imprecise, and capability gaps invisible until they cause a failure. It also makes career progression opaque, because nobody can describe what moving up actually requires. This is the same conflation problem I have written about in the semantic crisis in work design, where loose terminology quietly undermines every system built on top of it.
SFIA exists to fix that at the level of technology and digital professions specifically. It gives a stable, common vocabulary so that skills can be compared, planned and developed across an organisation rather than reinvented in every team. The need is pressing enough that governments have adopted it nationally. The OECD's work on developing skills for digital government sets out why public sector digital workforces in particular need a structured, shared way to describe and build capability.
How the SFIA Framework Works in Practice
The SFIA framework works by separating two questions that organisations usually muddle together: what kind of work is this, and how much responsibility does it carry.
The Seven Levels of Responsibility
The backbone of SFIA is its seven levels of responsibility, running from Level 1 to Level 7. Each level is summarised by a guiding phrase, and the progression is deliberate, with each level building on the one below it in responsibility, accountability and impact.
- Follow
- Assist
- Apply
- Enable
- Ensure and advise
- Initiate and influence
- Set strategy, inspire, mobilise
What defines a level is not the skill itself but a set of generic attributes that apply across every skill. According to the SFIA Foundation's description of how the framework works, these attributes are autonomy, influence, complexity, knowledge, and business skills or behavioural factors. Autonomy, influence and complexity together indicate the level of responsibility. Knowledge describes what a person needs to understand to operate at that level. The behavioural factors describe how they need to work to be effective.
This is the part organisations most often miss. A level is a real thing in SFIA, with its own definition, and a person operating at Level 5 is expected to demonstrate the autonomy and influence of Level 5 regardless of which skill they are applying.
Professional Skills and the Skill-Plus-Level Grid
The second axis is the professional skills themselves. SFIA defines well over a hundred skills, each with a name, a unique four-letter code, a short description, guidance notes, and specific descriptions of how that skill looks at each relevant level.
Importantly, skills are not defined at all seven levels. A skill is described only at the levels where it genuinely occurs in real work, which keeps the framework grounded in practice rather than forcing artificial completeness.
To describe a role, you select the skills it requires and the level at which each is needed. A role might require one skill at Level 3 and another at Level 5. To assess a person, you do the same against their demonstrated capability and compare. That single mechanism, skill plus level, supports recruitment, workforce planning, role design and development planning from one consistent structure.
What the SFIA Framework Is Not
The SFIA framework is frequently mistaken for adjacent constructs, and the distinctions matter.
It is not a competency framework in the behavioural sense. A leadership competency framework describes behaviours and how they are demonstrated across roles of all kinds. SFIA does include behavioural factors, but its core purpose is to describe technical and professional skills in the digital domain, not to model leadership behaviour across an organisation.
It is not a capability framework. A capability framework defines what an organisation must be able to do, often spanning every function and role type. SFIA is narrower and more specific: it describes individual professional skills in technology and digital work. The two operate at different altitudes, and the distinction between capability and skill is exactly the distinction between a capability framework and SFIA.
It is not a job evaluation or grading system. SFIA levels describe responsibility, but they are not pay bands and they do not size jobs for remuneration. Mapping SFIA levels directly onto salary grades is a common and damaging shortcut.
It is not a learning catalogue. SFIA tells you what skill is needed at what level. It does not tell you how to develop it. Development still has to be designed separately.
How the SFIA Framework Sits Alongside Other Models
SFIA is one of several named frameworks practitioners encounter, and knowing where it fits prevents misapplication.
DigComp, the European digital competence framework, describes general digital literacy for the whole population. SFIA describes the deep professional skills of people whose job is technology. They are not competitors; they cover different audiences. The same is true of the Australian Core Skills Framework, which addresses foundational skills rather than digital professions.
Korn Ferry and Lominger models, and the broader competency-modelling tradition associated with bodies such as CIPD and SHRM, focus on behaviours, leadership and general management capability. SFIA is profession-specific and technical. Many organisations run SFIA for their technology workforce and a separate behavioural or leadership model for everyone, and that is a reasonable design rather than a contradiction. SFIA's own behavioural factors can be mapped to an existing model or adopted directly where none exists.
SFIA is precise about its scope, and it works best when it is not stretched to cover work it was never built to describe.
I talk more on this during this talk I gave for SFIA Week in 2025:
Where SFIA Framework Implementations Commonly Fail
The most common failure I see is over-profiling. Organisations assign too many skills to every role, often a dozen or more, and produce profiles so dense that nobody uses them. A good SFIA role profile names the few skills that genuinely define the role.
The second failure is treating SFIA as a performance appraisal tool. SFIA describes the skills and levels a role requires and assesses whether a person meets them. It is not a rating of how well someone performed last quarter, and using it that way makes people defensive and corrupts the data.
The third is copying standard skills profiles wholesale. The SFIA Foundation and others publish reference profiles, and they are a useful starting point. Adopting them without checking them against the actual work produces profiles that look credible and describe nobody.
The fourth is ignoring the generic attributes. Organisations pick skills and levels but never reference autonomy, influence and complexity, which means their levels drift and lose meaning. The generic attributes are what make a level a level.
Trade-Offs and When to Use the SFIA Framework
SFIA is the right choice when the work is genuinely digital or technology professional work and you need a shared, durable language for it. It is mature, internationally recognised, and adopted at national scale by governments including Australia and New Zealand. The Queensland Government, for example, sets out how agencies apply SFIA across recruitment, performance and capability development.
It is the wrong choice as a universal framework for an entire organisation. SFIA does not describe non-technology roles, and forcing it to cover finance, operations or frontline service work produces strained, low-value profiles. SFIA also carries a licensing arrangement, free for most uses with a fee for large or commercial use, which is worth understanding before adoption.
The honest summary is that SFIA is excellent at one job. Used for that job, it is one of the strongest frameworks available. Used as a substitute for capability architecture across a whole organisation, it disappoints.
SFIA Framework FAQ
What is the SFIA framework in simple terms?
It is a global reference model that describes digital and technology skills and seven levels of responsibility. Every SFIA description of work combines a named skill with the level at which it is needed.
Who maintains the SFIA framework?
The SFIA Foundation, a not-for-profit organisation based in the United Kingdom. The current version is SFIA 9.
How many levels does the SFIA framework have?
Seven levels of responsibility, from Level 1 (Follow) to Level 7 (Set strategy, inspire, mobilise). Each level is defined by autonomy, influence, complexity, knowledge and behavioural factors.
Is the SFIA framework the same as a competency framework?
No. A competency framework usually models behaviours across all roles. SFIA describes technical and professional skills in the digital domain, expressed at defined levels of responsibility.
Is the SFIA framework free to use?
Most use is free of charge. Large organisations and commercial or external use attract a licensing fee through the SFIA Foundation.
Can the SFIA framework be used outside IT?
Its scope is digital and technology professional work. It is not designed to describe non-technology roles, and using it that way produces weak profiles. Pair it with a separate framework for the rest of the workforce.