Getting started with SFIA skills profiling across teams

Once SFIA skills profiling moves beyond one team, the work changes. It is no longer just about building good profiles. It is about helping different teams apply the framework in a similar enough way that the profiles can be compared and used together

It focuses on the choices and disciplines that often help a first implementation work well, including consistency of approach, calibration across teams and treating early profiles as a practical baseline that can improve through use. It complements the detailed guidance on how to construct individual profiles.

Note: Creating a skills profile requires a consistent and strong foundation of knowledge and understanding of SFIA. Before starting, ensure those involved have completed or are familiar with Foundation level training.

This page is about defining role requirements consistently. Formal assessment of individuals is a separate activity.

What you are trying to achieve
Profiles describe roles, not people
Aim for consistency before precision
Choosing the right pace
A useful starting methodology
Many organisations find it useful to begin with a limited and practical scope
Try to start with job families, not individual roles
Calibration across teams
Treating your first pass as a baseline
The role of leadership

What you are trying to achieve

A SFIA skills profile describes the skills and levels of responsibility required in a role. A set of profiles gives managers a common language for recruitment, development, workforce planning and career progression.

In a first rollout, the aim is not to produce perfect profiles. The aim is to produce profiles that are consistent enough to use and good enough to improve through use.

This can feel counterintuitive. Once a more rigorous framework is available, organisations often want to resolve every ambiguity before publishing anything. That usually delays the learning that comes from using the profiles in real situations.

A first scope is often one job family, one function or one business unit. That gives the organisation a tested method and a reference set of profiles before the work spreads further.

Profiles describe roles, not people

This is one of the most important principles in skills profiling, and one frequently overlooked in practice.

A skills profile describes what a role requires - the skill set and level of responsibility needed for someone to perform that role effectively within the team and the organisation. It describes the position, not the person currently in it.

The current postholder may exceed the role requirement in some areas, still be developing in others, or have taken on additional responsibilities that reflect their own development journey rather than the role itself. None of that should be written into the role profile.

SFIA supports two distinct and complementary activities: defining role expectations and assessing the people who perform those roles. Keeping those activities separate is essential. A clear role profile provides the baseline against which an individual’s capability can later be considered.

Why this matters in practice

When someone drafts a profile, it is natural to think about the people currently doing the role rather than the underlying role requirements.

This can produce profiles that reflect one individual's capabilities, development journey, and particular context - and that will be misleading for recruitment, potentially unfair in assessment, and difficult for a new person coming into the role to understand as a target.

This is especially likely in three situations:

The developing individual. A capable person may temporarily take on responsibilities beyond the role’s normal scope as part of a development opportunity. That experience is valuable, but it should not redefine the role profile itself. Otherwise, the profile becomes shaped by one person’s growth path rather than the role’s genuine and ongoing requirements.
The team structure gap. Someone is covering responsibilities that belong to an unfilled role elsewhere in the team. The profile should describe what the role requires in a properly structured team. The gap should be addressed through resourcing, not absorbed into the profile.
The familiar manager. A line manager’s detailed knowledge of a particular team member shapes the profile without them realising it. This is one reason why independent review or validation is valuable.

Good profiles outlast the current postholder.

A self-check question

When reviewing any draft profile, ask: if the current postholder left tomorrow and we recruited externally, would we genuinely require the new person to fulfil every element of this profile from the outset? If the honest answer is no, the profile is describing an individual rather than a role. Revisit any statements, skill selections, or skill levels that reflect the current individual rather than the enduring requirements of the role.

Aim for consistency before precision

People are more likely to trust profiling outcomes if similar roles are profiled in similar ways across the organisation.

A consistently applied set of profiles is significantly more valuable than a collection of individually optimised profiles that cannot be meaningfully compared. Consistency includes using the same approach to levelling, the same criteria for skill selection, and the same conventions for describing role purpose.
Inconsistent profiling undermines comparability, which is one of the organisational benefits of using SFIA. If different people apply the framework differently, the profiles cannot be used for calibration, workforce planning, or cross-team comparison. Recruitment and assessment conducted against inconsistent profiles will produce inconsistent outcomes. The organisation will realise only a fraction of the potential value from profiling.
Consistency does not require perfection. It requires a shared profiling approach before drafting begins, and discipline in applying that approach across the whole implementation - particularly across job families and across teams doing similar work.
Just as "perfection-as-delay" reduces value, "speed-as-shortcut" does the same in a different way. A consistent set of profiles produced too quickly, before managers have engaged with the framework or compared across teams, will be plausible on the page but fragile in use. Calibration, in particular, is not a step that can be compressed without losing the common understanding it produces.

Two practical disciplines support this:

Build job families together, not individual profiles in isolation. A job family - the set of roles at different levels of responsibility within one specialism - should be profiled as a unit, in a single working session where possible. This is not primarily an efficiency measure. It is a quality measure. The comparison between roles at increasing levels of responsibility within the same specialism (e.g. Junior, Mid, Senior and Lead) does more of the levelling work than any individual assessment in isolation. Profilers who try to level a single role without reference to adjacent roles in the family make more errors and produce less consistent results.

Calibrate across teams before finalising. Once a first pass of profiles is complete within one team or function, compare them with profiles for roles of similar seniority in other teams. A "SFIA Level 4" role in one team should be broadly comparable to a "SFIA Level 4 role" in another. Where profiles for apparently similar roles differ significantly in their overall level, skill selection, or skill levels, the difference should be explicable by genuine differences in the roles - not by differences in how individual profilers have applied the framework.

Choosing the right pace

The pace at which profiles are produced matters as much as the consistency of the method. Different parts of the activity benefit from different speeds.

Some parts can sensibly be accelerated. First-pass drafting, exploration of candidate skills, comparison of related roles in a family and the generation of starting wording for role purposes can all be supported by AI tools or generic skills profiles from the SFIA website without loss of quality, provided outputs are reviewed by people who understand the framework.

Other parts should be paced deliberately. Agreement on what a role actually requires (rather than what the current postholder happens to do), calibration across teams, conversations between managers about adjacent roles in a family, and the engagement of leaders with the resulting picture of the workforce are activities whose value comes from the conversation itself, not the document that records its conclusion. Compressing these to the pace of AI-generated drafting tends to produce profiles that look complete but are operationally fragile.

Profiles built quickly without these conversations rarely survive their first significant use. A recruitment campaign reveals that the skills selected do not generate the right candidates. A development conversation reveals that the manager cannot explain what the next level looks like. A restructure reveals that adjacent roles in different teams are levelled inconsistently. Each of these is the consequence of bypassing work that the profiling activity was supposed to do.

The strongest implementations treat profiling as a programme of paced engagement rather than a content-production exercise. The artefact (the profile) is the visible output. The enduring outcome is a shared understanding of strategic priorities for people and skills, held by the managers and leaders who will use it.

A useful starting approach

This section is about how to start consistently, not the full mechanics of profile construction. For the detailed method, use Building SFIA-based skills profiles alongside this page. For a first rollout, do not try to use every nuance of SFIA on day one. Start with a method people can apply consistently. Once there is a baseline set of profiles, the more nuanced cases are easier to handle.

The simplified approach

Set the overall SFIA level by finding the level where all three defining generic attributes - Autonomy, Influence and Complexity - comfortably fit. Use the SFIA level essence statements as a first orientation.

SFIA level	Essence of the level
SFIA level 1. Follow	Follows instructions, completes routine tasks under close supervision, and requires guidance. Learns and applies basic skills and knowledge.
SFIA level 2. Assist	Assists and supports others, works under routine supervision, and uses discretion to solve routine problems. Actively learns through training and on-the-job experiences.
SFIA level 3. Apply	Performs varied tasks, including complex and non-routine, using standard methods. Plans and manages own work, exercises discretion, and meets deadlines. Proactively enhances their skills and impact.
SFIA level 4. Enable	Performs diverse complex activities, supports and guides others, delegates tasks when appropriate, works autonomously under general direction, and contributes expertise to deliver team objectives.
SFIA level 5. Ensure, advise	Provides authoritative guidance in their field and works under broad direction. Accountable for delivering significant work outcomes, from analysis through execution to evaluation.
SFIA level 6. Initiate, influence	Influences the organisation significantly, makes high-level decisions, shapes policies, demonstrates thought leadership, fosters collaboration, and accepts accountability for strategic initiatives and outcomes.
SFIA level 7. Set strategy, inspire, mobilise	Determines overall organisational vision and strategy, operates at the highest level, and assumes accountability for overall success.

If Autonomy, Influence and Complexity do not all point to the same level, pause and consider whether the role design is clear before reaching for the ±1 tolerance.

In a first implementation, all three attributes pointing to the same level is usually a strong signal that you have found an appropriate overall level.
Roles where the attributes genuinely diverge are the exception, not the rule.

Select professional skills at that overall level.

Where a skill is needed but at a lighter touch - supporting rather than leading, contributing rather than fully accountable - include it at one level below the overall level.

For a first implementation, many organisations find it simpler not to use skills above the overall role level until they have built confidence with the framework.

The conditions under which a skill above the overall level is legitimate are specific and require a confident grasp of the framework to apply correctly.
Build that confidence through a first pass of profiles before engaging with the +1 case.

Apply this consistently across the whole job family before finalising any individual profile.

Many organisations find it useful to begin with a limited and practical scope

For many organisations, that means beginning with a limited and practical scope rather than trying to profile everything at once. A first pass may focus on one job family, one team, one professional area, or a small cluster of roles linked to an immediate need such as recruitment, development or team redesign.

Starting small can make it easier to build familiarity with the framework, test how levelling decisions are being made, and see how profiles are used in practice before extending the work more broadly. It also makes it easier to compare drafts, refine the method and build confidence in the outputs.

Useful small starting points often include:

one job family with clear progression between roles
one team with an immediate recruitment or restructuring need
one professional area where role clarity or development paths are a priority
one team or function that has already shown interest in using SFIA
a pilot set of related roles that can later act as a reference point for wider adoption

The underlying profiling method does not need to change when the scope is small. What changes is that the work is easier to review, test and improve before broader consistency, governance and calibration become more important.

Try to start with job families, not individual roles

If you are deciding where to begin with your SFIA skills profiles, a useful starting point is often a complete job family rather than a single role, because the comparison between related roles makes levelling easier and improves consistency.

A job family gives you the comparative context that makes levelling simpler to observe and describe. It is easier to agree that a Senior Engineer is Level 4 and a Principal is Level 6 than to level either role in isolation - and once those are agreed, the Engineer at Level 3 often becomes obvious. The relative judgements within a family do most of the work. Absolute judgements made without reference to adjacent roles are harder and more error-prone.
Starting with a job family also produces something immediately useful. A complete family - with profiles at each level, differentiated by role purpose, skill selection and skill level - can be used for recruitment and development conversations straight away. A collection of individually profiled roles from across the organisation, with no internal coherence, is harder to put to use before further calibration work is done.
Choose the first job family based on where the profiling need is most immediate - a planned recruitment campaign, a team restructure, a development programme - rather than where it seems easiest. Profiling under a real use case produces better profiles and faster learning.

Calibration across teams

This section applies when your implementation extends beyond a single team or pilot scope.

Once profiles have been built for more than one team or function, calibration is essential before they are used for consequential purposes such as recruitment, grading or performance-related decisions.

Calibration means comparing profiles for roles of similar seniority across different teams and asking whether the levelling is consistent. It does not mean making all profiles identical. Genuine differences between roles should still be reflected. It means making sure that differences in profiles reflect differences in roles rather than differences in how people have applied the framework.

The most common calibration issues in a first implementation are:

Level drift between teams. One team's Level 4 is another team's Level 5, because profilers in different teams have made independent levelling judgements without reference to each other. This is best caught by bringing profilers together to compare profiles before publication, rather than discovering it through inconsistent recruitment or pay outcomes.
Skill selection drift. Different teams describe similar responsibilities using different SFIA skills, making comparison harder than it needs to be.
Role purpose inflation. Role purposes in one team are more ambitious in scope than those in another at the same level. This often reflects differences in how much the current postholder has been asked to do rather than differences in what the role requires.

A useful calibration exercise is to bring together the managers who have built profiles for equivalent roles across teams, present the profiles side by side, and ask each manager to explain how their role differs from the others at the same level.

Where the differences are immediately clear and explicable, the profiles are probably right.
Where they are hard to explain, further alignment work is needed.

Treating your first pass as a baseline

A useful way to think about your first pass of producing the profiles is that these are a baseline, not a permanent record. They will improve through use, and they should be expected to.

Revision is not an admission of failure.

It is the normal and healthy behaviour of an organisation learning to apply a new framework.

A profile that is revised after a recruitment exercise - because the skills selected did not generate the right candidates - is more useful than one that was never tested. A profile that is updated after a team restructure - because the role's responsibilities have genuinely changed - is doing exactly what a profile should do.

Plan a review cycle from the outset.

A first review e.g. twelve months after initial publication, or after the profiles have been used for at least one significant purpose, is a reasonable starting point.
The review should consider: whether the profiles have been used as intended; what they revealed about roles and skill requirements that was not previously visible; and where the profiling methodology itself needs to be refined.

Resist the pressure to treat the first pass as final.

Organisations that declare their profiles complete after a first implementation and resist subsequent revision lose the benefit of learning. Organisations that delay publication until profiles feel perfect may never publish them at all.

A practical way to think about a first implementation is to recognise that a SFIA skills profile is intended to be useful and workable, not perfect from the outset.

A SFIA skills profile is a model of the requirements of a role. It will never perfectly capture every nuance of every role in every organisational context, and it does not need to.
What matters is that the profile is consistent, useful, and open to improvement. Those are all achievable in a first iteration.
Perfection is not. Pursuing perfection is one of the most reliable ways to ensure that nothing gets done.

The role of leadership

SFIA skills profiling rarely stalls because the framework is impossible to understand. It more often stalls because the people doing the work do not have clear permission to make decisions, publish a first version and move on.

That is understandable. Organisations that have lived with unclear or inconsistent role descriptions can become very cautious once a more rigorous framework is introduced. People want to get it right. Without leadership support, that caution can turn into long debates, heavy sign-off and a growing sense that the work is harder than it needs to be.

Leaders need to set a practical expectation: the first version should be good enough to use, not perfect. It should be reviewed after use. The profiling team should have enough authority to decide, document and keep moving.

Leadership also matters when the pressure is in the opposite direction. If there is a push to produce profiles quickly (e.g., by copying generic profiles or using AI tools without thought) , leaders need to protect the conversations that make the profiles useful. Profiles produced without those conversations may meet the deadline, but they are unlikely to deliver the benefits the work was meant to achieve.

Next step: Building SFIA-based skills profiles

On this page