The Allowance Is Not the Asset: Offboarding a Personal Handset Used for Work

A monthly allowance for mobile use has become an ordinary feature of many UK small and medium-sized business expense policies. It avoids a capital purchase, sidesteps handset administration and lets staff choose the device they actually want. The arrangement is usually recorded as a payroll item or a modest monthly reimbursement. What it does not do is create a company asset. At the point an employee resigns, that distinction matters more than the allowance itself.

When a business supplies a handset, the leaver checklist is relatively straightforward: collect the device, remove the SIM, confirm it has been returned and wipe it before reissue. A stipend phone has no such handover moment. The phone stays in the employee's pocket, and with it may go a working phone number, an authenticator app, saved call history, voicemail, customer message threads, photographs of job sites and a range of sessions that were never designed to be separated from the person holding the handset.

The gap in the standard leaver checklist

Most offboarding processes are built around systems the employer controls. Email is disabled, the directory account is suspended, the laptop is returned and building access is revoked. A personal handset used for work sits outside that perimeter. It is not an asset on the fixed-asset register, so it does not appear on a returns list. It is not covered by a device collection appointment, so nobody asks for it. Yet it may be the single most concentrated point of business communications in the employee's possession.

The practical exposure is rarely a dramatic data breach. It is more often a quiet loss of continuity. A customer continues to ring a number that now belongs to someone else. A finance workflow stalls because the departing employee was the enrolled authenticator for a payment platform. A colleague cannot find the WhatsApp thread that recorded a variation to a quote. The business has saved the cost of a handset but has not accounted for the cost of untangling one.

What actually leaves with the handset

It helps to separate the contents of a stipend phone into four groups. The first is identity: multi-factor authentication apps, saved passwords, authenticator enrolments and email sessions. These are access credentials and should be revoked or re-enrolled before the leaver's final day.

The second is communications records. Business calls made and received on the personal number, voicemail messages, text messages and messaging-app threads may contain commercial commitments, quotations or service history. Some of this can be exported; some cannot. The contract should make clear what the employer expects to receive and what the employee is permitted to retain.

The third is customer relationship data. If staff use a personal messaging account for customer conversations, the employer may have little practical control over the thread. The number belongs to the employee and the account belongs to the employee. The business may have a lawful basis for processing the messages, but it does not automatically have a right to take over the account.

The fourth is files and images: photographs of installations, scanned delivery notes, PDF quotations and screenshots of portal confirmations. These are easy to overlook because they sit in a camera roll or downloads folder rather than in a document management system.

Contract wording that earns its place

A phone allowance clause should not pretend the employer owns the handset. It should instead describe the business use, the separation of work data and the cooperation expected at exit. Useful provisions include a clear statement that the allowance is a contribution to business use rather than a transfer of the device; a requirement to use a work profile or managed container where the employer provides one; an obligation to keep business data within approved applications; and an exit clause requiring reasonable cooperation with deprovisioning during the notice period.

The clause should also address the awkward point of deletion. The employer can require the removal of business data, but it should not reserve a right to wipe a personal device wholesale. A blanket remote-wipe clause is likely to be unenforceable in practice and damaging to trust in any event. The sensible approach is a limited work profile that can be removed without touching personal photographs, messages or accounts.

Data protection wording matters too. The employer should state what business data may be processed on the device, how it will be handled at exit and what records will be kept of the deprovisioning. That is not legal theatre; it gives HR and IT a defensible sequence to follow when the leaver is no longer motivated to help.

A deprovisioning sequence that does not rely on goodwill

The trigger should come from HR, not from the line manager's memory. Once a resignation is accepted, the leaver process should generate a mobile-data task alongside the laptop return. The sequence can then run in a predictable order.

First, identify every business service tied to the personal number or handset. That includes the authenticated apps, the messaging accounts used for customer contact, call forwarding arrangements and any eSIM or secondary number. Second, revoke access to identity and productivity services and re-enrol the authenticator on a company-controlled device or a colleague's account. Third, agree how business message threads and call records will be exported or handed over, with a written record of what was transferred and what was deleted.

Fourth, remove the work profile through the mobile device management tool if one is in place. If there is no tool, provide a short written checklist and ask the leaver to confirm completion. Fifth, redirect the business number if it is being ported or replacement contact details have been issued to customers. Sixth, record the completion date and stop the allowance in the final payroll run.

The conversation about wiping someone else's phone

The most difficult part is rarely technical. It is asking an employee to remove business data from a device they own, often during a notice period that may not be entirely cordial. The conversation is easier when the policy was explained at the start, when the work profile is visibly separate from personal apps and when the request is specific rather than open-ended.

A practical approach is to schedule a short deprovisioning session during the exit interview or final week. The employee can see what is being removed, confirm that personal data is untouched and receive a written record. Where a work profile exists, removal is usually a single action. Where it does not, the employer is relying on cooperation and should document the request clearly. If cooperation is refused, the matter should go to HR and legal advice rather than to an improvised remote wipe.

Procurement starts before the leaver does

The leaver problem is really a procurement problem that has been deferred. A business choosing a stipend model should decide at the outset whether it will supply a managed work profile, how business numbers will be owned, which messaging channels are permitted for customer contact and what evidence of deletion it will accept. Those choices cost far less than reconstructing a customer relationship after the phone has left the building.

The allowance is not the asset. The business data on the handset is. Treating the two as separate from the first day of employment is what makes the last day manageable.