Competency Framework
Definition
Competency Framework
A competency framework is a written structure that lists the skills, behaviours and knowledge a job needs, with defined proficiency levels for each one. It is a static artefact you build once and then maintain, not an exercise you run against people.
Think of it as a ruler — the framework defines what good looks like at each level, so two managers rating the same person should land in roughly the same place.
Competency mapping is what you then do with it. The framework is the structure; mapping is the act of placing real roles and real people against that structure to find the gaps.
Most frameworks carry three layers: the behaviours everyone needs, the skills a job family needs, and the technical depth one specific role needs.
Key takeaways
- A competency framework lists competencies and defines proficiency levels for each of them.
- It is a static structure; competency mapping is the exercise you run against it.
- National models in the United States use tiered building blocks as a free starting template.
- A framework nobody maintains drifts out of date faster than the jobs it describes.
How it works
A competency framework works by fixing two things: the list of competencies that matter, and the ladder of proficiency levels under each. Once both are written down, hiring, training and promotion decisions can point at the same definitions.
| Level | What it means | Typical evidence |
|---|---|---|
| 1 Aware | Knows the concept, needs supervision | Completed induction module |
| 2 Working | Handles routine cases alone | Meets quality threshold unaided |
| 3 Practitioner | Handles exceptions and coaches peers | Reviews other people’s work |
| 4 Expert | Sets the standard others follow | Writes the process, trains trainers |
Contact centres use the levels to plan agent development. A level-two agent gets a coaching plan aimed at level three, and the plan names observable behaviours rather than a vague attitude score.
The framework also feeds routing. Skills-based routing needs a machine-readable record of who is certified at what level, which only exists if the framework defines those levels first.
Hiring inherits it too. A talent acquisition specialist writing an advert from the framework describes observable behaviours instead of buzzwords — which makes a shortlist defensible when a rejected candidate asks why.
Two measures show whether the framework is real. Time to productivity should fall as training targets named competencies, and the employee productivity ratio should hold steady when people move roles.
Levels need spacing you can actually see. Four rungs work because people can tell them apart; eight rungs turn every calibration meeting into a debate about a five versus a six.
Calibration is the maintenance ritual. Two or three managers score the same sample of work, compare notes, and adjust the wording wherever they disagreed with each other.
Write the framework for whoever uses it under pressure. A supervisor deciding a promotion case at 5pm needs one page per role, not a 40-page manual with an appendix.
Keep the wording behavioural. “Resolves a billing dispute without escalation” can be observed and evidenced; “demonstrates ownership” cannot, and it turns every rating into an argument.
The U.S. Competency Model Clearinghouse publishes industry models built on a Building Blocks Model, which supplies three underlying tiers that are the foundation of each industry model.
Those tiers get revised as work changes. In September 2024, the Tier 2 block covering basic computer skills was updated to reflect emerging digital demands.
Frameworks decay if nobody owns them. The U.S. Office of Personnel Management currently marks its own competency guidance as being rescinded or revised under Executive Order 14151, which is the maintenance problem in public view.
Examples
Competency frameworks look different by sector, but the shape holds. Three examples make it concrete: a national industry model, a BPO quality framework, and a small firm’s one-page version, and each earns its keep differently.
National industry models are the free starting point. They describe the foundation and technical competencies an entire sector needs, which saves a small HR team from writing a whole dictionary from scratch.
BPO providers usually run a two-axis version. One axis covers service behaviours such as empathy and de-escalation; the other covers process depth on a named client programme.
A 30-person agency can do the whole thing on one page — six competencies, four levels each, one sentence per cell, reviewed every January.
Banks and insurers go the other way. Regulated roles carry mandatory competencies with evidence requirements attached, so the framework doubles as an audit trail when a supervisor asks.
Public agencies publish theirs openly. That transparency lets candidates self-assess before applying, which trims the volume of unsuitable applications a hiring team has to read.
Technical teams often bolt a certification layer on top — a cloud or security credential maps to a named level, so the evidence arrives ready-made.
Retail chains use levels for store progression. Each rung unlocks a task list and a pay band, which makes the framework the spine of a career path rather than an HR document.
Whatever the size, the failure mode is identical. A framework written once and never revisited ends up describing a job nobody in the building still does.
Related terms
A competency framework rarely stands alone, so the entries below cover the roles and measures that sit around it. Read them together if you are building the structure for the first time.
- Training Specialist: the role that turns framework levels into actual course content.
- Training Completion Rate: the simplest check on whether framework-linked training is landing.
- Agent Development: the contact-centre practice the framework’s levels are usually built for.
- Time To Productivity: the ramp measure that falls when training targets named competencies.
- Skills-Based Routing: the routing method that depends on certified proficiency records.
FAQ
What is the difference between a competency framework and a job description?
A job description lists duties for one role. A framework defines the underlying skills and behaviours across many roles, with levels attached, so the two work together rather than replacing each other. Most organisations keep both and link them.
How many competencies should a framework contain?
Between six and twelve for most organisations. Past that, raters stop reading the definitions and start guessing. Cut ruthlessly: a competency nobody has ever rated below level three is not doing any work.
What is the difference between a competency framework and competency mapping?
The framework is the structure you measure against; mapping is the act of measuring roles and people against it. You cannot run a mapping exercise without a framework in place first.
How often should a framework be reviewed?
Once a year is normal, with an extra review whenever a major technology or regulation changes the work itself. Version the document so people can see what changed and when.
Do small companies need one?
Yes, because a one-page framework beats an undocumented set of expectations living in one manager’s head.
Buyers checking how a provider defines and levels its people can compare firms in the Outsource Accelerator directory.
Independent
