Upgrade Cycles You Do Not Control
The employee decides when to replace the device, and their reasons have nothing to do with the work it is doing.
An organisation replacing its own equipment chooses the moment. Under BYOD somebody else chooses it, on a different basis, and both directions of that cause problems.
The operational issue in “Upgrade Cycles You Do Not Control” is easier to diagnose when device state and work evidence remain separate. A team reviewing open the provider page for how to calculate idle time can make time and project context visible, while endpoint tools remain the source of truth for security, software and hardware condition.
Replacing later than the work needs
The commonest case. A household keeps a laptop until it stops working or until there is money, which may be several years past the point at which it became inadequate for the job.
For an independent reference relevant to “Upgrade Cycles You Do Not Control”, consult the CISA mobile-device security guidance; compare its principles with the proposed ownership model, access rules and real support process.
The employer sees the consequence as slowness, support tickets and occasional incompatibility, and usually attributes it to something else.
The employee frequently will not say. Admitting your equipment is holding you back sounds like making excuses, so people absorb it and work around it.
Replacing sooner than you expected
Less discussed and genuinely disruptive. Somebody buys a new phone, the work profile space does not move across automatically, access breaks, and nobody told the service desk it was coming.
Or they upgrade the operating system on release day, before the company applications support it, and discover the problem at nine the following morning.
Both are avoidable with a line in the arrangement: tell us before you change device or make a major operating system change, and here is what happens.
The operating system version problem specifically
Vendors release major versions annually, and company software frequently lags by weeks or months.
On a managed fleet the organisation controls when the update happens. On a personal device it cannot, and people update because the notification is insistent.
Which means the organisation must either keep its software current enough to tolerate day-one upgrades, or ask people to delay, which works for a while and not reliably.
The first is the real answer and it is a cost of the arrangement that belongs in the honest saving calculation.
What can reasonably be asked
Notice of a device change, with a short process for moving the work profile space.
Notice before a major operating system upgrade, with a stated position on whether to wait.
Keeping the current version patched, which is the security minimum and is a different thing from taking a new major version.
Each of these is free for the employee to comply with, which is the test the minimum-standards note sets.
What the organisation should do on its own side
Track the version spread of connecting devices. Most access systems report it, and the distribution tells you when a compatibility problem is coming.
Test company applications against new major versions before release rather than after, which vendors make possible through preview programmes and which almost nobody does.
Telling people what to tell you
Nobody thinks to announce a phone upgrade to their employer, because it is a personal purchase. A single line in the arrangement — let us know before you change device, here is what happens — is all that is required, and it converts a recurring support surprise into a scheduled task. It is also the moment to check the old device was cleared.
The upgrade that was not optional
Vendors occasionally force a major version or withdraw support for an older one at short notice. The organisation has no control over the timing and neither does the employee. Keeping company software current enough to absorb this is the only defence, and treating it as a cost of the arrangement rather than as an unlucky event is the honest accounting.
Testing before the release
Vendor preview programmes exist and are free. Running company applications against a forthcoming major version before it reaches employees converts an annual surprise into a planned piece of work, and it is the only control available over a timing the organisation does not own. The replacement decision belongs to somebody whose household budget is the deciding factor. Plan for that rather than for an orderly cycle.