Digital competences in public administration: how to use DigComp

The starting problem

"Digital skills" appears in nearly every public administration training plan. It almost never appears in a form that lets you say, twelve months later, whether the objective was met.

The reason is that "digital skills" is not a competence: it is a family of very different competences. Protecting personal data, judging the reliability of a source and collaborating on a shared document do not develop together and are not measured the same way.

DigComp solves exactly that problem: it gives separate names to separate things.

What changes in practice

From declaration to measurement. With 5 areas and 21 competences, an office's needs are described per competence and per level, not as a percentage of staff "trained". The result is a snapshot you can compare with last year's.

From course catalogue to objectives. A course anchored to identified DigComp competences produces verifiable outcomes. A course titled "digital literacy" produces attendance certificates.

From perceived needs to real ones. The gaps that emerge from a competence-level mapping are often not the expected ones. Safety and data management usually turn out to be far more exposed than productivity tools, which are the best covered in training catalogues.

Three recurring mistakes

1. Confusing tools with competences. Training on a specific piece of software does not develop a DigComp competence: the competence is transferable, the tool is not. Software changes; the ability to evaluate information stays.

1. Using one level for everyone. DigComp describes progressive proficiency levels. A plan that treats all staff as a homogeneous block wastes training on those who do not need it and leaves behind those starting further back.

1. Stopping at the mapping. A competence survey that does not turn into planning decisions is a cost with no return. DigComp's value lies in connecting the snapshot to the choices.

Where to start

• Define profiles before people. Which competences, at which level, does an administrative officer need? A technician? A manager? The profile is built once and reused.
• Survey with a coherent instrument. A structured self-assessment on DigComp competences is more useful than a generic questionnaire about "comfort with technology".
• Plan by gaps. Training goes where the distance between expected profile and measured level is greatest, not where supply happens to be available.
• Measure again. Without a second survey you do not know whether the training worked.

Explore the 5 areas, 21 competences and proficiency levels on the DigComp portal at ExplorerHub.