What is Competence?

Ask ten people in a regulated organisation what competence means and you will likely get ten different answers. Some will describe it in terms of qualifications — the certificates and licences that demonstrate a person has completed a recognised programme of training. Others will describe it in terms of experience — the years spent in a role, the range of situations encountered, the depth of practical knowledge accumulated over time. Others still will describe it in terms of behaviour — the way a person approaches their work, the judgements they make under pressure, the standards they hold themselves and others to.

All of these descriptions capture something real. None of them, on its own, is sufficient. And the gap between a partial understanding of competence and a complete one has significant consequences for the organisations responsible for managing it.

A working definition

In the context of regulated industries, competence is best understood as the ability to perform a defined task or role to a defined standard, under the conditions likely to be encountered in practice. That definition has four components, each of which matters.

The first is ability. Competence is not about what a person knows in the abstract — it is about what they can do. A person who understands the theory of a procedure but cannot apply it correctly under operational conditions is not competent to perform that procedure. Competence is demonstrated through performance, not through knowledge alone.

The second is a defined task or role. Competence is always competence at something. It is not a general attribute that a person either has or does not have — it is specific to the tasks and responsibilities of a particular role, in a particular operational context. A person who is highly competent in one role may not be competent in another, even if the roles appear similar.

The third is a defined standard. Competence requires a benchmark — a description of what good performance looks like, against which an individual's performance can be assessed. Without a defined standard, assessment is subjective and inconsistent, and the organisation cannot make reliable claims about the competence of its workforce.

The fourth is the conditions likely to be encountered in practice. This is the element most often overlooked. Competence assessed under ideal conditions — in a classroom, on a simulator, or during a planned exercise — may not reflect competence under the conditions that actually arise in operations: time pressure, incomplete information, equipment that is not behaving as expected, or the cumulative effects of fatigue and workload. A robust competence framework takes account of the realistic range of conditions in which tasks will be performed.

The components of competence

Competence in a regulated industry context is generally understood to comprise four components: knowledge, skills, experience, and behaviour. Each contributes something distinct, and a framework that addresses only some of them will produce an incomplete picture of an individual's capability.

Knowledge is the foundation. It encompasses the technical understanding required to perform a task — the principles behind a procedure, the hazards associated with a process, the regulatory requirements that apply to a role. Knowledge can be assessed through written or oral examination, and it is often the easiest component to measure. But knowledge alone does not constitute competence.

Skills are the practical capabilities that translate knowledge into performance. They include both technical skills — the ability to operate equipment, follow a procedure, or apply a technique — and non-technical skills, sometimes described as human factors, which include communication, situational awareness, decision-making, and teamwork. Non-technical skills are increasingly recognised as critical determinants of safety performance in high-hazard environments, and a competence framework that addresses only technical skills is incomplete.

Experience is the accumulated exposure to the range of situations, conditions, and challenges that a role involves. It is what allows a person to apply their knowledge and skills reliably across the variety of circumstances they are likely to encounter — including the abnormal and the unexpected. Experience cannot be assessed directly, but it can be taken into account in the design of assessment processes and in the judgements made about an individual's readiness to perform safety-critical tasks independently.

Behaviour is the most complex component. It encompasses the attitudes, values, and dispositions that shape the way a person approaches their work — their commitment to following procedures, their willingness to raise concerns, their response to pressure, their relationship with risk. Behaviour is influenced by organisational culture as much as by individual disposition, and it is the component of competence most resistant to change through training alone.

Why the definition matters

The reason precision in defining competence matters is straightforward: the definition shapes the framework. An organisation that defines competence primarily in terms of qualifications will build a framework centred on training and certification. An organisation that defines it in terms of demonstrated performance will build a framework centred on assessment and evidence. An organisation that takes all four components seriously will build a framework that addresses knowledge, skills, experience, and behaviour — and that uses assessment methods appropriate to each.

Regulators in the UK's major hazard sectors have moved steadily towards the broader, performance-based definition. The Health and Safety Executive's guidance on competence management, the expectations set out in sector-specific safety cases, and the findings of major incident inquiries all reflect an understanding of competence that goes well beyond qualifications and training records. Organisations whose frameworks are built on a narrower definition are likely to find, when subjected to regulatory scrutiny, that their assurance is less robust than they believed.

Implications for competence management

A clear definition of competence has direct implications for how a Competence Management System is designed and operated. It means that competence requirements must be defined in terms of tasks and standards, not just job titles and qualifications. It means that assessment must test performance, not just knowledge. It means that the conditions under which assessment is conducted must reflect the conditions of actual operations. And it means that the framework must address all four components of competence — knowledge, skills, experience, and behaviour — not just the ones that are easiest to measure.

It also means that competence is not a one-time achievement. A person who was assessed as competent at a point in time may not remain competent as procedures change, as equipment is modified, as their role evolves, or simply as the passage of time erodes skills that are not regularly exercised. A framework built on a genuine understanding of competence will include processes for maintaining and reassuring competence over time, not just for establishing it initially.

Download the full guide for a detailed exploration of what competence means in practice and how to build a framework that reflects its full scope.