Training frontliners who have no laptop and no email

The phone is the only channel, not the preferred one

Most writing about mobile learning treats the phone as an option: a convenience for people who travel, a second screen for people who already have a first one. For the people this guide is about, that framing is wrong in a way that changes every decision after it.

A picker, a counter assistant, a line operator, a cleaner, a driver, a temp on their first shift: none of them has a desk. Most have no company laptop, and a large share have no company email address either. There is no evening at a home computer where the outstanding module gets finished, because there is no account to log in with. The phone is the only thing that reaches these people at all.

Settle the channel before the design

Before anyone argues about module length or video, answer a more basic question: through which route does an instruction physically arrive at a person with no company device and no company mailbox?

There are four candidates and only one scales.

A printed sheet reaches everyone but proves nothing and cannot be updated. A screen in the break room reaches whoever looks at it. A back-office PC shared by a whole site reaches people one at a time, and only when the office is free, which on a busy floor is never. A link on the phone reaches everyone, at any hour, in any language, and leaves a record. Across many sites and shifts, it is the only route that gets the same instruction to the night shift at your fourteenth site. Everything else here is about making that route work honestly.

What the law asks of the channel

The phone answers the Dutch duty to instruct in comprehensible form well (Arbobesluit art. 7.11a, Arbowet art. 8), because it puts the instruction at the point of use in the person's own language. Working time is a different duty: in Belgium, Codex art. I.2-21 puts training inside working time and at no cost to the worker, which makes it a scheduling question, covered next. Whether you may ask for the worker's own phone at all has its own answer: see can you require staff to train on their own phone.

Working time is a scheduling decision

Putting training on a phone makes it possible to train at any moment. That does not mean you may.

So schedule it. Give the module a window inside paid time and say so when you assign it. Tell supervisors the five minutes are theirs to allocate, the same way a handover or a stock count is. Look at completion times now and then: if a site's completions cluster after the last shift ends, you have found a scheduling problem there, not a motivated workforce. Deciding this once and telling managers costs nothing, and it removes the most common objection a works council or a CPBW raises.

Design for a screen held in one hand

The device changes the content, not just the container.

Length matters most, because frontline attention comes in gaps of a few minutes between a delivery and a queue; why short modules get finished covers the arithmetic. Language is not cosmetic either: on a mixed floor, a module in one language does not meet "comprehensible" for part of the shift.

Test on the oldest phone on the floor

Testing on the communications manager's new phone tells you nothing. Most of what breaks in a mobile rollout breaks in the first ninety seconds, and none of it shows in a demo on a laptop.

One more check belongs in writing before you sign with any vendor: how does somebody without a company mailbox receive their first invitation? The answer decides whether part of your workforce can be reached at all.

How Aristotl handles it

Aristotl was built for this workforce rather than adapted to it. Everything runs in the browser, so there is nothing to install on anyone's phone. The same link opens on a phone, a shared tablet in the back office or a desktop, so a site that keeps a shared device needs no separate build.

Workers join through a link or QR code per site or team, without a company email. Your own procedures, handbooks and instructions become courses of 3-5 minutes with a knowledge check, and content is translated per worker from one master version, so one course reaches a mixed floor in the languages people read. Completion is recorded per person and viewable per site and version in the platform, which is what you need the day someone asks you to show that an instruction was given.

Pick one procedure that reaches your floor today as a printed sheet or an email nobody opens. Open it as a mobile module the way a worker would: on your own phone, on mobile data, standing up. If it does not work there, it does not work.