Web Only: the Arrangement That Needs No Device
If nothing is stored locally, most of this collection stops applying. The question is which work can actually be done that way.
Every difficulty in BYOD comes from company data resting on somebody else's hardware. Remove the resting and the difficulties go with it.
The practical lesson in “Web Only: the Arrangement That Needs No Device” is to connect every record to a named decision. Organisations exploring review the solution for productivity software for business can add structured workforce context, provided the use is disclosed and interpretation is reviewed with the people affected.
What changes
No data on the device means nothing to remove at exit, nothing to retain or disclose, nothing lost when a phone is stolen, and no container to manage.
For an independent reference relevant to “Web Only: the Arrangement That Needs No Device”, consult the CISA mobile-device security guidance; compare its principles with the proposed ownership model, access rules and real support process.
The device becomes a screen. What matters is the browser and the connection, and the hardware requirements collapse to almost nothing — which solves the too-old-device problem at the same time.
Enrolment becomes unnecessary. The employer manages access rather than devices, which is both less intrusive and considerably less work.
What it requires
Work that is genuinely reachable through a browser, which for mail, documents, messaging, most business systems and a great deal of office work it now is.
A connection, reliably, because without local copies an outage stops everything.
Access controls that do the work the device management was doing: strong authentication, session limits, and conditional rules about where and how somebody connects.
And discipline about downloads, because a browser can still save a file and a saved file is resident data.
Where it does not reach
Work needing local applications: design, engineering, development, video, large datasets.
Work in places without connectivity.
Anything requiring specialised hardware or peripherals.
And roles where the latency of working through a browser is itself a cost, which is real for some kinds of intensive work and overstated for most.
The download problem
This is the leak that undoes it. Somebody downloads a spreadsheet to work on it, and the arrangement's central property is gone.
Most access platforms can prevent or restrict downloads on unmanaged devices, which is the control that makes the whole thing hold. Without it the arrangement is browser-based in theory and resident in practice.
Worth checking whether yours is configured that way, because many are not.
The virtual desktop variant
A full desktop delivered to the browser, which extends the approach to work that needs applications.
More expensive per user and heavier on the connection, and it solves the same problem for a wider set of roles. For organisations with sensitive material and a BYOD population it is frequently the arrangement that resolves the tension.
Why it belongs in this section
Not because every organisation should adopt it, but because it is the alternative that removes the underlying problem rather than managing it.
An organisation reviewing a troubled BYOD arrangement should cost this alongside the others, and a surprising share of roles turn out to fit it.
The connection becomes critical
Without local copies, an outage stops work entirely rather than degrading it. That shifts the importance of the connection and makes the mobile fallback from the earlier note a requirement rather than a nicety. Organisations adopting access-only arrangements without considering this discover it on the first bad day.
Testing whether it actually fits
The question is answerable by trial rather than by argument: move one team to browser-only access for a month and record what they could not do. The list is usually shorter than expected and specific enough to act on, and it settles a debate that otherwise runs on assumptions about what people need locally.
The roles it fits better than expected
Occasional users, contractors, board members, anybody whose work is mail and documents. For these the arrangement requires nothing of the device at all, which removes enrolment, agreements, exits and allowances in a single decision.
The control that makes it work
Preventing or restricting downloads on unmanaged devices. Without it the arrangement is browser-based in theory and resident in practice, and every benefit described here quietly disappears while everybody believes it is in place.
Where the arrangement quietly fails
Downloads. Somebody saves a file to work on it and the central property of the arrangement is gone, invisibly, while everybody continues to believe nothing rests locally. The control exists in most access platforms and is frequently not switched on, which is worth checking before relying on the approach.