What is a competency framework?
A competency framework is the structured description of what a role requires, expressed as competencies that can be assessed. An assessment score has no meaning on its own; the framework is what turns it into a statement about whether someone can do their job. It is also what connects training to the role definitions an organisation already maintains.
Also called: Competency model, Capability framework
Why a score means nothing until it is mapped to a role
An organisation without a competency framework ends up reporting training volume, because volume is the only thing it can measure. Hours completed and modules passed say nothing about whether the people holding a regulated role are competent to hold it, which is the question a supervisor eventually asks. Mapping assessments to competencies is tedious work, and it is the work that converts a learning record into an assurance artefact. The framework also determines what a gap means, since a gap is only identifiable against a stated requirement.
- A framework converts a score into a statement about role readiness.
- Gaps can only be identified against a requirement that has been written down.
- Assessment items tagged to competencies make coverage measurable per role.
- Supervisory questions are asked about roles rather than about modules.
How a competency framework works
- Competencies are defined per role at a level of detail an assessment can address.
- Each competency states the evidence that would demonstrate it.
- Modules and assessment items are tagged to the competencies they cover.
- Required levels are set per role, with the regulatory basis recorded where one exists.
- Each learner's evidence is aggregated against their role requirement and the gap reported.
How a competency framework is evaluated
A framework is assessed on whether it supports a defensible statement about any individual's readiness. Examine the following for each role in the framework:
- coverage of each competency by at least one assessed item
- proportion of competencies with stated evidence requirements
- agreement between framework levels and supervisory judgement
- share of roles with a current and approved requirement set
- time to answer whether a named person meets their role requirement
Limitations, risks and common failure modes
- Frameworks are written at a level of abstraction no assessment can reach.
- Role definitions in the directory and in the framework diverge within a year.
- Competencies are mapped once at launch and never remapped as modules change.
- A single module is tagged to so many competencies that coverage becomes meaningless.