Three access walls: why frontline training does not reach everyone

Three separate constraints keep operational procedures from frontline workers in multi-site organisations. A temp placed at a client site with no issued device. A production worker whose phone ownership nobody has checked. A hospitality or food worker whose phone is banned in the place where the procedure applies.

Each has a different cause, removes a different set of channels and needs a different response. Treat all three as one problem, or solve one and assume the others follow, and you get partial coverage that counts as coverage in the report while an unknown share of the workforce is never reached.

Three questions show whether this is already happening in your network:

Partial reach looks like full reach

A system that reaches seventy percent of the workforce does not show the missing thirty. They do not appear in the reporting, and the system has no way to flag their absence. From head office the rollout looks complete; on the floor, part of the team is still working from what they were told before the procedure changed.

Operators describe the same pattern across sectors. In staffing, temps arrive at client sites with no device. In food production, phone ownership varies across shifts and nobody scheduling the rollout can see the split. In hospitality, phones are banned from the floor by policy.

The coverage number counts how many people the system can see. It does not count how many people the procedure needs to reach.

Temporary work shows where the problem starts. Belgium had 740,216 unique temporary workers in 2025, who worked 218 million hours, according to Federgon. The agency holds the contract, the payroll and the administrative record. The client site holds the HACCP procedures, the allergen protocols and the line instructions. The worker sits between the two, present at the site that owns the standards and employed by the firm that does not. Neither issues a device: the agency has no procedures to deliver on one, and the client has no employment relationship that would justify it. Service-voucher cleaners, working alone in a client's home with no supervisor and no employer infrastructure on site, face the same gap.

These are not edge cases. They are the people who staff production lines, clean buildings and handle food at scale.

The three walls

"Nearly everyone has a smartphone" is close enough to true for a population that it rarely gets examined for a workforce. The three patterns below are the conditions under which mobile-first is not solved. They work through supply (no device), distribution (uneven ownership) and policy (device banned).

Wall one: no device, no desk, nothing at the work site

A temp placed at a client site has no company laptop and no issued phone. The agency did not issue one because the placement may last weeks. The client did not because the worker is not their employee. The site's IT was sized for its own permanent staff.

The pattern repeats in home care, facility cleaning and warehousing: the worker is physically at a site that holds the standards, employed by an organisation that does not control that site, and carrying nothing the site's systems can reach. In the Netherlands, agency workers make up an estimated 4 percent of the working population, according to the Nederlandse Arbeidsinspectie.

A channel that assumes a company device or access to the client's internal systems cannot reach this group at all.

Wall two: uneven phone ownership

In a food plant running three shifts across several sites, some workers own a smartphone and some do not. The split is not documented and nobody has surveyed it. A mobile platform goes live and some workers register. The registration count looks like adoption. It is really a census of who owns a suitable phone and is willing to use it for work.

The danger is specific: you can no longer tell a worker who received a procedure and did not follow it from a worker who never received it. Both show up the same way, as a missing record. Where everyone has access, a missing record means non-compliance. Where access is uneven, it could be non-compliance or non-delivery.

That ambiguity spoils the whole report. A site completion rate of sixty percent might mean sixty percent complied and forty did not. It might also mean sixty percent were reachable and forty were never in the system. The number is correct; what the review concludes from it depends on which reading is true, and the number does not say.

A workforce with no devices is a visible problem that gets named in procurement. A workforce with some devices is an invisible one that corrupts the data without raising an alarm.

Wall three: the phone is banned where the procedure applies

In kitchens and food production, phones are not allowed on the floor or in the production area. A restaurant group with two hundred sites enforces it as policy during service, for the guest experience, for discipline and, in the kitchen, for hygiene.

Regulation (EC) No 852/2004 requires hygiene based on HACCP principles. Under good manufacturing practice, personal items are a contamination source, and a phone touched all shift long is exactly that. BRCGS, IFS and FSSC 22000 all require personal hygiene controls that in practice keep phones out of production zones. A worker entering a high-care area changes clothes, passes the hygiene barrier and leaves personal items, phone included, in a locker outside.

The procedure applies inside the zone. The device that could deliver it is outside. This is not a technology gap or a budget problem; it is a physical and regulatory separation between where the instruction lives digitally and where it has to be carried out.

No company email, no account

Under all three walls sits an identity problem that has nothing to do with hardware. Most enterprise software asks for an email address at sign-up. The frontline worker does not have a company one, not because they have no email at all, but because the organisation never issued one. The job never needed it: clock in, do physical work, clock out.

That covers agency temps, service-voucher workers, line operators, kitchen and floor staff and warehouse teams: the largest, most spread-out groups and the ones most exposed to the consequences of a procedure not being followed. A platform that requires email sign-in has excluded part of the workforce before the rollout starts. What that means in practice, and what the term covers, is set out under deskless worker.

The sign-in model decides who can be reached. If it needs a credential the frontline was never given, it excludes the people most exposed to non-compliance.

Can you require staff to use their own phone?

The obvious answer to the access problem is "everyone has a phone". In Belgium and the Netherlands that answer runs into consultation and data protection rules first.

Belgium. Collective Bargaining Agreement No. 81 of 26 April 2002 governs employer monitoring of electronic communications and requires finality, proportionality and transparency. A work system on a personal phone that processes work data sits within CBA 81 and the GDPR, and raises further questions under the well-being rules on work equipment and under tax law on reimbursing costs.

The Netherlands. Article 27(1)(k) of the Works Councils Act (WOR) requires the works council's consent for any arrangement that processes staff personal data, and 27(1)(l) for any system that can monitor attendance, behaviour or performance, as the Autoriteit Persoonsgegevens explains. A decision taken without consent can be nullified by the subdistrict court.

Neither rule was written for delivering procedures to the frontline, and neither forbids personal phones. Together they mean a consultation path before the decision can take effect. How to write a policy that holds is covered in the BYOD guide.

The rollout owner cannot see the floor

In the largest retail and hospitality networks, the person rolling out a new standard to a region sits at head office or a regional office. They adapt the procedure, schedule it and mark it as distributed to site managers. What happens between the site manager receiving it and the floor team carrying it out is a gap that neither the rollout owner nor the report measures.

The site manager has a different reporting line, different daily priorities and no obligation to report back on execution. The system records that the procedure was sent, and maybe that the manager opened it. It does not record whether the part-timer who started on Tuesday and works three shifts a week ever saw it. Across two hundred sites the rollout owner manages a distribution list and the site manager manages a floor, with no shared instrument for the third event: whether the procedure was carried out.

That gap is not a communication failure. It is how large multi-site organisations are built.

What access would have to mean

A system meant to close the gap between a published procedure and its execution, across every site and every group of workers, has to meet at least these requirements. Each traces back to a wall above.

Any requirement that fails is a gap that will surface at a site you cannot predict, on a day that matters. A procedure that cannot reach the worker cannot be carried out by the worker, and a report built on top of it measures the delivery channel, not the floor. What that report can and cannot prove is the subject of the delivery record is not the floor.