Competency Framework Examples: A Complete Guide for 2026

Last reviewed August 2026

A competency framework is a structured set of the knowledge, skills and behaviours that define effective performance in each role across an organisation. The best competency framework examples share one shape: a small number of competencies, each defined in plain language, with three to five proficiency levels described as observable behaviour. Below are worked examples for core, leadership, functional and industry-specific frameworks, plus a sample layout you can copy.

What a competency framework is

If you have ever looked at a generic job description and wondered what success actually looks like in practice, a competency framework is the answer. It replaces a list of duties with a map of the behaviours and skills required to do the job well, and it describes what "good" looks like at each stage. That standard does four jobs at once: it removes some of the bias from hiring, gives people a clear line of sight to their next role, shows where the skill gaps are, and gives learning something to aim at. The glossary entry on competency frameworks has the short definition; the competency framework builder guide covers how to construct one from scratch.

Frameworks fall into four categories, and most organisations end up with a mix: core competencies that apply to everyone, leadership competencies for people who manage others, functional competencies for a discipline or department, and industry-specific competencies where regulation or safety sets the bar.

Sample competency framework layout

Before the examples, here is the structure each competency entry should follow. Every good competency framework sample uses some version of it.

Core competency framework example

Core competencies are the universal behaviours expected of every person in the organisation, regardless of department or seniority. They are tightly bound to your culture and values: if the business prides itself on customer success and new thinking, the core framework must reflect that. Common examples are communication, collaboration, adaptability and results orientation.

The discipline is in defining what each one looks like in action. For adaptability, a framework might state: "Demonstrates the ability to adjust to new information, changing conditions, or unexpected obstacles without losing focus on the end goal." Then it describes that at each level. A developing employee adjusts when told; a proficient one re-plans their own work and warns others; an advanced one helps the team through the change; an expert redesigns the process so the change sticks. Written that way, the competency can be observed and discussed rather than argued about.

Leadership competency framework examples

Leadership needs a distinct set of behaviours beyond technical expertise. Moving from individual contributor to manager means shifting from personal output to team enablement, and the framework has to describe that transition. Keeping the model small is what makes it usable: one framework example recommends 4 to 5 competencies with three clear proficiency levels for leadership roles, including a decision-making competency that moves from making timely decisions in one's own area to taking accountable cross-functional decisions.

If your managers are not using a model like this, the problem is usually structural rather than motivational. The piece on why leadership competency frameworks gather dust explains the common failure points and how to fix them.

Functional and role-based competency examples

Where core competencies apply to everyone, functional competencies belong to a department or discipline. They break down the technical skills and domain knowledge required to progress within a career track. Role-based competency examples often use four proficiency levels; one template maps engineering problem-solving from resolving known issues with guidance to defining system-wide fixes and coaching the team.

The same tiering works in any function. In a sales framework, "Customer focus" might progress like this:

• Level 1 (Entry): Identifies basic customer needs and responds to enquiries promptly.
• Level 2 (Intermediate): Anticipates common customer objections and provides tailored responses.
• Level 3 (Advanced): Builds strategic partnerships and acts as a trusted advisor to key accounts.
• Level 4 (Expert): Shapes the organisation's go-to-market approach based on deep customer insight.

With levels mapped this clearly, people never have to guess what they need to do to earn the next step. Tools like Compono Develop map these competencies directly to learning pathways, so the framework points at specific development rather than sitting in a document.

Industry-specific and regulated competency examples

Some industries need highly specialised frameworks, particularly where regulation, safety, licensing or accreditation sets the standard. In manufacturing, healthcare, construction and public safety, a competency framework is a risk-management asset as much as a career tool. One example for operations includes safety leadership, team coordination, continuous improvement and stakeholder communication, each tied to observable behaviours such as weekly safety walks or quarterly process-improvement actions.

In these settings a competency is often tied to a certification or a regulatory standard. A logistics framework might include "Heavy machinery operation" and list the exact regulatory codes, the required safety training, the renewal period and the evidence needed to prove proficiency, so compliance is built into the daily expectations of the role. Where the stakes are highest, in government licensing and credentialling, the framework needs to be paired with assessment and a defensible record; that is the territory Compono Assure covers, and the state government competency framework guide walks through the public-sector version.

Building capability for all: a framework everyone can use

A common failure is a framework that only describes leaders and specialists, leaving most of the workforce with nothing to grow into. "Building capability for all" means every role, from the front line to the executive, has a competency profile with levels and a route between them. In practice that looks like a short core set for everyone (four to six competencies), a functional set per discipline (three to five), a leadership set for anyone who manages people, and clear evidence rules for each level. It also means the framework is visible to employees, not held by HR, so people can see where they sit and what the next level asks of them. That visibility is what turns a document into a development culture, and it is what a learning platform should make easy: each competency linked to the learning that builds it, and each completion recorded against the level it proves.

How to put the framework to work

The biggest mistake HR leaders make is treating a competency framework as a set-and-forget PDF. To change performance it has to run through the whole employee lifecycle. In recruitment, use the core and functional competencies to write structured interview questions, so candidates are judged against objective criteria rather than gut feel. In onboarding, introduce new hires to the framework in the first week so they know what success looks like. In performance and development conversations, make it the shared reference: the manager and the employee are looking at the same levels and the same evidence. In learning, tie every course to a competency and a level, so completions mean something.

A workforce intelligence platform such as Compono brings that data together, so proficiency levels and skill gaps are visible across the organisation rather than scattered through spreadsheets and appraisal forms. That is the difference between a framework that describes capability and one that builds it.

Frequently asked questions

What is a competency framework?

A competency framework is a structured model that sets out the knowledge, skills, observable behaviours and proficiency levels required to perform a role effectively, usually with levels for each competency so progress can be described and assessed.

How many competencies should a role have?

Keep it focused. Aim for four to six core competencies that apply to the whole company, plus three to five functional or role-specific ones. Overloading a role makes the framework hard to measure and manage.

What does a leadership competency framework example look like?

Typically four to five competencies (for example strategic thinking, developing others, decision making and change management) with three proficiency levels that describe the shift from leading a team to leading managers to leading the organisation.

What is the difference between a skill and a competency?

A skill is a specific learned ability, such as using a CRM or writing code. A competency is broader: it combines skills, knowledge, judgement and behaviours to describe how someone applies their abilities to achieve an outcome, such as strategic problem solving.

How do you measure competencies?

Through behavioural indicators and proficiency levels. Managers observe whether an employee consistently shows the behaviours described for their level, usually assessed in performance reviews, 360-degree feedback or, in regulated roles, formal assessment and certification.