Can you require staff to train on their own phone? (BE/NL)

Whose phone is a Benelux question

Mobile training runs into one practical question almost immediately: whose phone? A lot of American guidance barely notices it, because the personal phone is assumed. In Belgium and the Netherlands it is more contested, and a policy written on the American assumption tends to start a conversation nobody at head office wanted to have.

This guide is about how to decide. It does not rule on privacy law or on when employee representatives have to be consulted; where those questions come up, it says so.

Two rules frame the question before privacy does

Two provisions bear directly on asking somebody to train on their own phone, and neither is a privacy rule.

Belgian Codex art. I.2-21 requires the employer to give every worker sufficient and appropriate training on well-being at work for their workstation or function, with two explicit conditions: the cost is not borne by the worker, and the training takes place during working time. Read that against a request to use a private phone, on a private data plan, in a break or at home. The time is the obvious problem. The cost is the less obvious one, and it is real: mobile data has a price, and so does a phone new enough to run a current browser.

Dutch Arbobesluit art. 7.11a requires that instructions for work equipment reach the worker in comprehensible form, and Arbowet art. 8 asks for information and instruction adapted to each worker. Both are usually quoted about language, rightly. They also bear on the device: instruction that only exists on a screen somebody does not have is not reaching them at all.

Neither settles the question alone. Together they set the frame: the employer owes the instruction, carries the cost and delivers it on the employer's time. A private phone can be a way of meeting that. It cannot be a way of shifting it.

The decisions to write down

A workable policy is short: a handful of positions, each of which somebody will eventually test.

Before rolling the policy out across a network, put it in front of your prevention adviser or occupational health service and whoever handles employment law for you. If you have a works council or a CPBW, involve them early. That is a process recommendation, not a legal ruling, and it is the cheapest insurance available.

The alternative has to be real

"Private phone voluntary, shared device available" is only true if somebody can actually find the shared device at the end of a late shift.

If a site cannot produce that, the voluntary policy is decorative, and the people who decline to use their own phone are simply not being instructed. That failure is invisible in the numbers: those people show up as incomplete and look like a motivation problem.

What changes when a device is shared

Shared devices work, with two known frictions.

The first is identity. Training records have to attach to a person, not a device. Somebody opens their own session, does five minutes and closes it, so the next person is not recorded as them. Make that step as short as possible; every second in it is a second in which the shift decides not to bother.

The second is contention. One device for twenty people is a queue, and a queue at the end of a shift is a queue nobody joins. This is where module length matters most: a module of 3-5 minutes fits a real gap, a 30-minute one does not, and the difference is far larger on a shared device than on a personal one.

The middle path that works: most people use their own phone because it is genuinely more convenient, and the shared device carries those who decline plus those whose phone is too old. Designed that way, it is not a fallback nobody uses but a real path with light traffic. Content that assumes a large screen fails here too: a PDF of a slide deck on a five-year-old phone has technically been delivered and practically has not.

Why voluntary is the version that holds

A required-device policy creates people with a reason to object: an old phone, a small data plan, or simply no wish to have work on a private device. Each is a legitimate position, and without an alternative each becomes a dispute you have to settle one by one or collectively. An optional policy with a working alternative removes the objection instead of answering it. Nobody has to be persuaded, and the instruction still reaches everyone, which is the only outcome the two provisions above care about.

How Aristotl handles it

Aristotl runs in the phone's browser. There is no app to install, no store download and no permissions request, which removes most of what a device policy would otherwise have to cover. Workers join through a link or QR code per site or team, without a company email, and the same course opens on a private phone, a shared tablet or a desktop.

Courses are 3-5 minutes, so they fit a gap between tasks and a short queue for a shared tablet. Content is translated per worker, so comprehensible form does not depend on the language the original was written in. Completion attaches to the person, not the device, so a shared tablet produces the same record as a private phone.

Take one site and one shift and find out how many people would genuinely rather not use their own phone. That number decides your policy, and most organisations have never asked.