TL;DR
Company phone contracts bundle two different things: a piece of hardware and a connectivity contract with a minimum term. Treating them as one purchase is why offboarding goes wrong, why nobody can answer what the fleet costs, and why equipment platforms do not touch this category.
- Two purchases, not one. Separate the handset from the line.
- The line is the one with a minimum term, and it outlives the employee.
- Offboarding has two actions, and the line is the forgotten one.
- Personal use is normal, which changes what you can wipe.
- Number portability is a real decision, and it is made at the wrong moment.
- No equipment platform covers the carrier side, and none claims to.
Company phone contracts are two things
Separating them is most of the work, and almost nobody does it at the point of purchase because the bundle is how it is sold.
The handset. A device. It can be bought outright, it has a resale value, it belongs in the asset register, and it can be recovered and reissued like any other piece of hardware.
The line. A contract with a carrier, a number, a billing account and usually a minimum term. It is not a device, it cannot be recovered, and it continues whether or not anybody is using it.
| Handset | Line | |
|---|---|---|
| Recoverable | Yes | No |
| Has a term | No | Usually |
| In the asset register | Yes | Should be in a contract register |
| Transfers between people | Easily | With effort, sometimes |
| Cost after somebody leaves | Zero | Continues |
The last row is the whole argument. A recovered handset stops costing money the day it comes back. A line keeps billing until somebody cancels or reassigns it, and that somebody has to know it exists.
Offboarding has two actions and one gets forgotten
The handset comes back because it is a physical object somebody notices. The line continues because nothing visible happens when it does.
That asymmetry is why companies find themselves paying for numbers belonging to people who left two years ago, and it is usually discovered during a cost review rather than by any process.
It compounds quietly. Each individual line is small enough that nobody queries it, and the total only becomes visible when somebody adds them up, which tends to happen once every few years and never on a schedule.
Three things to build in.
A contract register, separate from the asset register. Number, carrier, term end date, assigned person. It does not need to be sophisticated, it needs to exist.
A leaver step for the line, not just the device. Cancel, suspend or reassign, decided explicitly rather than by default.
A quarterly reconciliation of active lines against current employees. This is the one that finds the accumulated drift, and the first run is usually uncomfortable.
The number question
Whether somebody keeps their number when they leave is a decision worth making in advance rather than during a departure.
If the number was issued by the company and has been given to customers, you may want to keep it. If it is effectively the person’s number and has been for years, taking it is both hard and harsh. The answer differs by role, and the time to decide is when the line is issued, not when somebody resigns. Write it into whatever the person signs when they receive the phone, because a rule agreed in advance is a rule, while the same rule produced during a resignation is a negotiating position and will be treated as one.
Personal use changes what you can wipe
Disclosure: RemoAsset, named below, is owned by the same people who publish PeopleOpsHQ. It is described with its limitations stated, on the same terms as every other supplier. This site takes no vendor money.
A phone gets used personally in a way a laptop does not, and that is the normal state rather than a policy failure. It changes what is reasonable to do at the end.
A full device wipe on a phone carrying somebody’s photographs and personal messages is a different act from wiping a company laptop, and doing it without warning is the kind of thing that produces a complaint with substance behind it.
The workable approach is a work profile or container: company data lives in a defined space, that space can be removed, and the rest of the device is untouched. NIST Special Publication 800-124 on managing the security of mobile devices treats the enrolment and configuration state as the core control on a mobile device, which is the right frame, and it is what makes a selective wipe possible.
What to say in advance
Three sentences at issue, not at exit. What the company can see, what it cannot, and what happens to the device when somebody leaves.
Where personal data belonging to the individual sits on a device the company manages, the consolidated text of the General Data Protection Regulation is relevant to both directions: the company’s data on their device, and their data on the company’s. Saying plainly which is which at the start removes nearly all of the difficulty later.
Worth noting where equipment platforms stand. RemoAsset’s procurement and delivery is built around laptops and similar computing devices. It does not manage carrier contracts, numbers or billing accounts, and this post exists partly to say so: the connectivity half is a separate supplier, usually local to each market, and planning for two suppliers from the start is better than discovering it at the first international hire.
The decision table
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Bundled handset and line | Any | Carrier deal | Cannot separate costs | Buy handsets outright, lines separately |
| Paying for unknown numbers | 100 plus | No contract register | Accumulated drift | Reconcile lines against employees |
| Hiring in a new country | Any | One carrier deal | Does not extend | Local line, handset from your supplier |
| Heavy personal use | Any | No work profile | Cannot wipe safely | Container or profile, stated at issue |
| Phones not really needed | Any | Legacy policy | Paying from habit | Allowance instead of a fleet |
The option worth considering first
Before any of the above, the question worth asking is whether you need a phone fleet at all.
For a lot of roles the answer is now no. People have phones. What the company actually needs is for them to be reachable and for work data to be handled properly, and neither requires issuing hardware.
An allowance plus a managed work profile on the person’s own device achieves both for most roles, with less administration and no contract register.
Where a company phone is still right
Three cases, and they are genuine.
Roles where the number belongs to the company. Sales lines, support lines, anything a customer calls back.
Regulated contexts where communications must be recorded or retained, which is not reasonable to impose on somebody’s personal device.
Field roles with real wear, where expecting somebody to use their own phone on a building site is not fair.
The thing to avoid
Do it at a fixed point in the year so that it happens at all. A review depending on somebody noticing the cost is a review that occurs roughly never, which is how most fleets reached their current size.
Run the comparison with the real total rather than the handset cost, since that is the number people reach for and it is roughly half the answer.
Issuing phones because you always have. It is the most common reason a fleet exists, it is expensive, and the cost is split across two budgets in a way that makes the total hard to see, which is precisely why nobody revisits it.
The split across two budgets is what hides it. The handsets sit in equipment spend and the lines sit in telecoms or facilities, so no single report shows the total and nobody has a reason to question a number they only ever see half of.
Count the lines, total the monthly cost, and compare it with an allowance. Do that once a year, and either the fleet is justified or it is not. For the adjacent spending decision, see our piece on connectivity stipends, and control frameworks such as ISO/IEC 27001, the information security management standard expect the devices to be in the inventory either way.
See what an equipment platform does cover at configured device procurement and delivery, or read our piece on connectivity stipends.
Frequently asked questions
Why separate the handset from the line?
Because they behave completely differently. A handset is a device: recoverable, resaleable, reissuable, and it stops costing money the day it comes back. A line is a contract with a term, a number and a billing account that continues whether or not anybody is using it. Bundling them hides that difference.
What gets forgotten at offboarding?
The line. The handset comes back because it is a physical object somebody notices, while the line continues because nothing visible happens when it does. That is why companies find themselves paying for numbers belonging to people who left two years ago, usually discovered in a cost review rather than by any process.
What should we put in place?
A contract register separate from the asset register, holding number, carrier, term end date and assigned person. A leaver step for the line as well as the device, decided explicitly rather than by default. And a quarterly reconciliation of active lines against current employees, whose first run is usually uncomfortable.
Who keeps the number when somebody leaves?
Decide at issue rather than at departure. If the number was issued by the company and has been given to customers you will want to keep it. If it is effectively the person’s number and has been for years, taking it is both difficult and harsh. The answer differs by role, which is why it belongs in the policy.
Can we wipe a phone the way we wipe a laptop?
Not reasonably, because personal use of a phone is normal rather than a policy failure. A full wipe on a device carrying somebody’s photographs and messages is a different act, and doing it without warning produces a complaint with substance. A work profile or container lets you remove company data and leave the rest.
Do we need a phone fleet at all?
Often no. People have phones, and what the company needs is for them to be reachable and for work data to be handled properly, neither of which requires issuing hardware. An allowance plus a managed work profile covers most roles with less administration and no contract register.
When is a company phone still right?
Three genuine cases. Roles where the number belongs to the company, such as sales or support lines a customer calls back. Regulated contexts where communications must be recorded or retained, which is not reasonable on a personal device. And field roles with real physical wear, where using somebody’s own phone is not fair.
PeopleOpsHQ covers the operational side of distributed work. We describe suppliers with their limitations stated, and we take no vendor money.