Building a school-wide digital curriculum with DigComp

The document nearly every school has, and almost nobody uses

The school-wide digital curriculum is often a document written for a compliance requirement and never reopened. The reason is recognisable: it is written as a list of tools and activities, and a list of tools ages in two years.

A curriculum built on DigComp does not age the same way, because competences outlive tools. The ability to judge the reliability of a source remains the same competence whatever platform the source sits on.

The minimum structure that works

A useful curriculum answers three questions in this order.

1. Which competences. The 5 areas and 21 competences of DigComp 3.0 supply the closed list. There is no need to invent categories: there is a need to decide which competences the school commits to developing, knowing that declaring twenty-one is the same as declaring none.

2. In which years, at which level. This is where the real work is. Each selected competence is assigned to an age band with an expected proficiency level. DigComp's level progression -- from foundation to advanced -- provides the scale; the distribution across years is the school's pedagogical choice.

3. Verified how. A competence without an associated assessment task does not enter the curriculum: it stays an intention. The task need not be a structured test: an activity making the competence observable is enough.

The distribution criterion

The recurring mistake is distributing areas by subject -- safety to technology, information to language -- and considering the job done. DigComp areas do not correspond to disciplines; they correspond to types of activity.

A sturdier criterion: assign each competence to the context where it is naturally exercised. Digital collaboration lives in any group work on a shared document; source evaluation lives in any research task; safety lives at the moment students create accounts and handle credentials. Identifying those moments means talking to teachers, not consulting the timetable.

The two areas always left uncovered

In most real curricula two areas are systematically under-represented.

Safety. It appears as a code of conduct -- what you must not do -- rather than as competence: understanding how profiling works, recognising a phishing attempt, managing digital identity. These are things you teach, not things you ban.

Problem solving. The hardest area to place because it has no home subject. It concerns autonomy in solving a technical problem and in identifying your own competence needs. It only develops if you leave room for a problem that has not been solved in advance.

What it takes to avoid a dead document

• A small number of declared competences. Five competences actually attended to are worth more than twenty-one listed.
• Assessment inside subject plans, not in a separate annex.
• An initial survey, so you do not design against an imagined level. A tool like DigCompSat serves this purpose.
• An annual review of levels, not of content.

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