Onboarding thousands of frontline employees who do not have a computer

A care operator or a security group hires dozens of people a month, spread across the country, into roles that never touch a computer. Onboarding is a binder and an instructor who visits once a week. The people who most need consistent training are the people hardest to reach with it, and the gap shows up in service quality long before it shows up in a report.

The use case

The agent delivers training over the channel the employee already has on their phone, at the pace they set. It checks comprehension rather than attendance. It flags to the branch manager who has not finished and who is stuck on the same step as four other people, which is usually a sign that the step is badly written rather than that the four people are slow.

What it is worth to the business

Two things, and the second one is the one that gets budget approved.

First, an employee reaches competence sooner, which matters most in exactly the roles with the highest turnover. Second, you hold a record of who was trained on what and when. In a regulated care or security operation that record is not a nice-to-have. It is the thing an inspector asks for, and assembling it by hand after the fact is a week of somebody's life.

Four decisions you have to make

1. Is the training mandatory or recommended. This changes the entire design. Mandatory means gating, escalation and an audit trail. Recommended means none of that, and a much smaller build.
2. Who sees the report. The branch manager, or only HR at head office. If the branch manager cannot see it, the branch manager will not act on it, and completion will stall no matter how good the content is.
3. What counts as finished. Viewed the content, or answered correctly. Be honest about which one you are actually willing to enforce, because the second one will generate arguments in week two.
4. How many languages. In this sector that is not a theoretical question. Hebrew, Russian and Arabic are ordinary requirements, and retrofitting a second language into a system built for one is more expensive than starting with two.

Where to start

One role, one region, one month of hires. The measure worth watching is not completion rate. It is how many questions the branch manager stops having to answer twice.

Technical footnote

A messaging channel, a content engine, a dashboard. No app to install, because the install step is where this category of project dies. The unglamorous half of the work is content structure, not delivery: material written for an instructor to narrate does not survive being sent as messages, and rewriting it is most of the project.