TL;DR
Equipment refresh communication is the difference between a rollout people welcome and one they resist. The three questions everybody has are what happens to my files, how long will I be without a machine, and do I have any choice. Answer those before the first laptop ships and most of the friction disappears.
- Data is the first question. Answer it before anybody asks.
- Give a date range per person, not a project timeline.
- Say plainly whether there is a choice. Fake consultation is worse than none.
- Explain what happens to the old machine. People genuinely want to know.
- One message too early beats three during the rollout.
The moment this becomes real
Say a refresh covers 140 machines over a quarter. The project is well planned, the hardware is ordered, and the first announcement goes out on a Monday saying that laptops will be replaced over the coming weeks.
By Wednesday IT has sixty questions, and they are all variants of three things. Will I lose my files. When exactly is mine happening, because I have a client presentation. Can I keep this one, it works fine.
Best tools for HR Operations
Each answer exists and none of them was in the message. The project team knew all three, because they had planned for them, and assumed people would ask if they wanted detail. The real issue is not the rollout. It is that a message about a change said what was happening to the company and not what was happening to the person reading it.
When this is lighter than you think
Four stages where this needs almost nothing.
- Replacing a broken machine. Nobody needs persuading. The communication is a date and a process.
- Small teams. Under about twenty people this is a conversation rather than a communications plan.
- Everything lives in the cloud. If nothing is stored locally the hardest question answers itself, and you should say so loudly.
- People are asking for new machines. A refresh that people want needs logistics, not persuasion.
It matters on large rollouts, where machines are being replaced on a schedule rather than on failure, and wherever people have local files they care about.
The five questions people actually ask
What happens to my files? The first question every time, and the one most announcements skip. Say exactly what transfers automatically, what the person needs to do themselves, and what will not come across. If the honest answer includes anything saved to the desktop, say that clearly and early rather than discovering it on swap day.
How long will I be without a machine? People plan around this. Give a realistic range rather than an optimistic number, and be explicit about whether they hand over the old machine before or after the new one arrives. Overlap is far less disruptive and worth the extra device for a few days.
Do I get a choice? Answer honestly. If the specification is fixed, say so. If there is a genuine choice between two models or an accessory budget, say what it is. Asking for preferences you cannot act on costs you more goodwill than never asking.
What happens to my old laptop? People ask this more than teams expect, partly from curiosity and partly from concern about their data. Say whether it is wiped, redeployed, sold or recycled. A clear answer here does a lot of quiet reassurance work.
Can I keep it? Some will ask. Have a position before the first message goes out, because answering differently to different people is worse than any single answer.
Three ways teams communicate it, and where each breaks
One announcement, then silence. A single message at the start covering the whole programme. Efficient and common. It breaks because a company wide message cannot tell any individual when their turn is, so everybody has to ask.
Per person notification only. Each individual gets a message a week before their swap. Highly relevant and nothing is wasted. It breaks on context: the first person contacted has no idea this is a programme, and rumour fills the gap.
Both, in that order. A short programme message explaining why and answering the three questions, then an individual message with a date. This works. It breaks only if the second message never arrives, which happens more often than you would think when a rollout slips.
Five questions before you send anything
Good equipment refresh communication is mostly about having answers ready.
What exactly happens to local files? If IT cannot state this in one sentence, do not announce yet.
Is there an overlap period? People need to know whether they hand over before or after.
Is the specification fixed? Decide before somebody asks, not after.
What happens to the old devices? Have the honest answer, including if it is resale.
Who answers questions? Name a route. Sixty people emailing whoever sent the message is not a route.
What is actually available
Five honest options for running the rollout behind the message.
Self service swap at an office. Best where people are on site. A booking slot and a desk. Fast and personal. Struggles for anyone remote, which is increasingly everyone.
Ship new, collect old afterwards. Best general approach for distributed teams. The overlap removes most anxiety about data. Struggles on recovery, since the old machine is now a leaver style collection problem.
Collect old, then ship new. Cheaper and tidier for the company. Struggles badly on experience, because the person is without a machine for the gap and will remember it.
Swap on a visit. Best where teams gather periodically. One day, many swaps, no shipping. Struggles on timing, since it ties the refresh to an events calendar.
RemoAsset. Best for distributed refreshes where both legs have to happen in markets you have no presence in, since delivery across 80+ countries and retrieval let you run the overlap approach without the old machines disappearing. Where it struggles: none of this is the hard part of a refresh. The hard part is the message, and no vendor writes that for you. Its published pricing starts with a pay as you go plan and a yearly subscription above it.
Where to start, by situation
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Replacing failed machines | Any | Any | None | A date and a process, no campaign |
| Small team, one office | Under 20 | On site | Minimal | Talk to people, book swap slots |
| Large office based rollout | 100 plus | On site IT | Question volume | Programme message then individual dates |
| Distributed rollout | Any | No offices | Shipping both ways | Ship new first, then collect, and say so |
| Fleet change across markets | Any | No local presence | Old machines never come back | A service such as RemoAsset for both legs |
What the gap actually costs
Communication costs an hour of writing. Not doing it costs IT a fortnight of answering the same three questions individually, which is the most visible and least interesting consequence.
The bigger cost is resistance. People who feel a working machine is being taken away without explanation delay their swap, miss their slot and escalate to their manager. A rollout planned over a quarter stretches to two, and the project team spends the difference chasing rather than deploying.
The third cost lands on the old devices. People who do not know what happens to their previous laptop, or who were not given a clear return route, keep it. A refresh that recovers eighty per cent of old machines rather than ninety five has quietly lost real value. So the question is not what to say. It is whether the message answers the questions people actually have.
When the logistics undermine the message
You can write a good message and still have a bad rollout, because the thing people judge is what happens to them rather than what they were told would happen. Promising an overlap and then collecting first destroys more trust than never promising it.
That is the real link between the communication and the operation. Every reassuring sentence in the announcement is a commitment somebody has to deliver, usually across several countries, often on dates that matter to individuals.
So the practical advice is to work out what you can actually deliver before writing what you will say. If collection in a given market takes three weeks, do not promise two. Where both legs run through one arrangement, as with a laptop lifecycle management service, the dates you give people are the dates somebody is accountable for, which is what makes the message survive contact with the rollout.
See how device swaps are delivered and collected across markets
Read our guide to setting a hardware refresh cycle
Related reading
- Setting a hardware refresh cycle
- Writing an employee equipment policy
- What to do about unreturned equipment
- Device spend per role
- Handling of data during a device change touches data protection duties. The UK ICO publishes guidance for organisations, and the NCSC publishes device security guidance.
Frequently Asked Questions
What should equipment refresh communication say first?
What happens to the person’s files. It is the first question everybody has and the one most announcements omit. State what transfers automatically, what they need to move themselves and what will not come across, before explaining anything about the programme.
Should people hand over the old laptop before or after the new one arrives?
After, wherever you can afford it. A short overlap removes almost all anxiety about data and lets people move anything the migration missed. Collecting first is tidier for the company and is the version people remember badly.
Should we ask people what specification they want?
Only if you can act on the answer. A genuine choice between options is good. Asking for preferences when the specification is already fixed costs more goodwill than never asking, because people notice when their input changed nothing.
How far ahead should we tell people?
Send a short programme message early explaining why and answering the main questions, then an individual message with a specific date about a week before each swap. The second message is the one people act on, and it is the one most likely to be forgotten when a rollout slips.
What should we say about the old devices?
The truth, including if they are being sold or recycled. People ask partly from curiosity and partly because they want to know their data is handled properly. A clear sentence about wiping and what happens next does a lot of quiet reassurance work.
What if someone wants to keep their old laptop?
Decide your position before the first message rather than per request. Whatever you choose, applying it consistently matters more than the answer itself, because different answers to different people is the version that generates complaints.
How do we stop old machines going missing during a refresh?
Give everybody a specific return route at the same time as their swap date, with packaging if they are remote. Recovery rates fall sharply when collection is treated as something to arrange later, because by then the person has a working new machine and no reason to think about it.
