TL;DR
Equipment during industrial action is something almost no handbook addresses, and the default in practice is that devices stay with the people who hold them. The questions that actually arise are about access rather than hardware, and about whether a position taken during a dispute looks like a position or like a reaction.
- This is legally sensitive. Take advice before adopting any position.
- Hardware usually stays. Access is the live question, not the laptop.
- A rule written during a dispute reads very differently from one written before.
- Rights and protections around industrial action vary widely by jurisdiction.
- Consistency matters more than the specific choice you make.
The moment this becomes real
Say a group of staff give notice of industrial action. Within a day somebody asks IT a reasonable sounding operational question: should we suspend their accounts for the duration.
IT has no basis to answer. There is no policy, nobody knows whether suspension would be appropriate or what it would signal, and the request has arrived with an implied urgency. Somebody suggests collecting the laptops too, since people are not working.
Best tools for HR Operations
At that point the company is one decision away from turning an employment dispute into a second, different dispute about property and access. The real issue is not what the right answer is. It is that the question arrived with no prepared answer, during the exact week when improvising is most expensive.
When this is lighter than you think
Four stages where this needs no preparation at all.
- No recognised union and no collective bargaining. For many small and mid sized companies this simply does not arise.
- Single jurisdiction with clear advice available. One call to an employment adviser covers it if it ever comes up.
- Office based teams. Devices stay in the building and the question of collecting from homes does not exist.
- You already have works council arrangements. Then there is an existing forum for exactly this kind of question.
It is worth thinking about in advance if you employ across several countries, if any part of your workforce is unionised, or if a dispute is foreseeable.
The five questions teams actually ask
Can we take the equipment back? This is a legal question before it is an operational one, and the answer depends on jurisdiction, on the nature of the action and on the employment relationship, which continues in many circumstances. Do not reason from your equipment policy. Take advice.
Should we suspend access? Treat this separately from hardware. There may be legitimate operational reasons to restrict particular systems, and there is a difference between a targeted control with a stated reason and a blanket lockout. The second is much harder to explain afterwards.
What about equipment still on order? A joiner whose start date falls during a dispute is a separate matter from existing staff, and usually the ordinary process continues. Confusing the two is a common way to create a problem that did not need to exist.
Does a refresh or collection already scheduled go ahead? If a device swap was planned before notice was given, carrying on as planned is usually easier to defend than pausing it. Pausing looks like a response. Continuing looks like a schedule.
Who decides? Not IT, and not a line manager under pressure. Name the decision owner in advance, which in most companies is a senior HR lead working with legal advice.
Three positions, and where each breaks
Change nothing. Devices stay, access stays, normal operations continue for everyone not taking action. Simplest and the most common. It breaks only where there is a genuine and specific operational risk, which is rarer than people assume in the moment.
Targeted access controls with stated reasons. Specific systems restricted for specific reasons, documented, applied consistently. Defensible and proportionate. It breaks if the reasons are thin, because a restriction without a real justification is just a blanket lockout with paperwork.
Collect devices. The most aggressive option and the one most likely to escalate. It breaks on several fronts at once: the legal position varies and may not support it, it reads as retaliation whatever the intent, and it creates a second dispute about property. If anybody proposes this, it needs legal advice before anything else.
Five questions to settle in advance
Preparing for equipment during industrial action takes one short conversation.
Who would decide? Name the person now. Under pressure, the decision falls to whoever is asked.
Have you taken advice on your jurisdictions? The answer differs by country and this is not a question to research in the moment.
Can you apply a position consistently? Inconsistent treatment between groups is where most of the risk sits.
What was already scheduled? Knowing what refreshes and collections are in the diary stops them becoming accidental statements.
What does your handbook currently say? Probably nothing, which is a fine answer if it is deliberate.
What is actually available
Five honest options, including ours.
Say nothing in the handbook. Best for most companies. A handbook clause about industrial action is a statement in itself and can create more problems than it solves. Struggles only in that the question still has to be answerable when asked.
A short internal decision note. Not published, just an agreed position with named owners and legal advice attached. Best preparation available. Struggles if nobody can find it when needed.
Existing works council or union consultation. Best where a forum already exists. The question gets discussed rather than imposed. Struggles where no such structure exists.
External employment advice on demand. Best for the specific moment. Definitive and current. Struggles on speed if you have no existing relationship, which is why the time to find an adviser is not during a dispute.
RemoAsset. Relevant only to one narrow part of this, which is knowing what is where. Asset tracking and retrieval mean that if a collection is ever agreed, it is a scheduled job rather than managers improvising. Where it struggles, and this is the important part: none of the hard questions here are logistics questions. They are legal and relational, and no vendor should be anywhere near them. 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 |
|---|---|---|---|---|
| No unionised workforce | Any | Single country | Unlikely to arise | No preparation needed beyond knowing who to call |
| Recognised union, one country | Any | Bargaining in place | No agreed position | Agree an internal note with legal advice |
| Several countries, mixed arrangements | Any | Varied jurisdictions | One policy cannot fit | Take advice per country before writing anything |
| Dispute foreseeable | Any | Notice not yet given | Decisions would be reactive | Settle the position while nothing is happening |
| Notice already given | Any | Any | Pressure to act quickly | Take advice before changing anything at all |
What the gap actually costs
Usually nothing, because most companies never face this and the ones that do find that leaving things alone was both the easiest and the correct answer.
The cost appears only when somebody acts quickly without advice. A device collection or a blanket access suspension during a dispute can convert a contained disagreement into a separate claim, a separate negotiation and a story that outlives the original issue. That is a large downside for a decision taken to feel decisive.
There is a smaller cost that is more common: inconsistency. Treating one group differently from another, or acting on one site and not another, is harder to explain than any single decision. So the question is not what your position should be. It is whether you have one at all, and whether it was written before anybody needed it.
When this is not an equipment question
Most topics in this space reward operational thinking. This one punishes it. The instinct to treat devices as company property to be managed is exactly the instinct that causes trouble here, because the context changes what an ordinary action means.
What is genuinely useful operationally is narrow: know what equipment each person holds, and know what was already scheduled. Both of those are register questions and both are worth having regardless. A laptop lifecycle management service keeps that record current, which is useful background rather than an answer.
Everything else belongs with employment advisers and senior HR. If you take one thing from this, make it the smallest one: decide in advance who answers the question, so that when IT is asked whether to suspend accounts, they have somebody to forward it to rather than a decision to make.
See how device records stay current across a distributed team
Read our guide to writing an asset management policy
Related reading
- Writing an asset management policy
- Equipment and works councils
- Equipment during suspension
- Writing an employee equipment policy
- Rights around industrial action differ by country. The UK government publishes guidance on industrial action, and the ILO covers collective bargaining. Take local advice.
Frequently Asked Questions
Can we collect equipment during industrial action?
This is a legal question rather than an operational one, and the answer depends on your jurisdiction, the nature of the action and the employment relationship, which continues in many circumstances. Do not reason from your equipment policy. Take employment advice before taking any step.
Should we suspend system access?
Treat access separately from hardware. Targeted restrictions on specific systems with a stated operational reason are easier to justify than a blanket lockout. A broad suspension applied because action is happening, rather than for a specific risk, is much harder to explain afterwards.
What about a new starter whose first day falls during a dispute?
Usually a separate matter from existing staff taking action, and the ordinary onboarding process continues. Conflating the two creates problems that did not need to exist. If there is genuine uncertainty, that is another question for your advisers rather than for IT.
Should we pause a scheduled device refresh?
Carrying on with something planned before notice was given is usually easier to defend than pausing it. A pause looks like a response to the dispute, while continuing looks like a schedule. If in doubt, ask whether you would be doing this anyway.
Who should make these decisions?
A senior HR owner working with legal advice, named in advance. Not IT, and not a line manager responding to a question in the moment. The most useful preparation is simply ensuring everyone knows where to forward the question.
Should our handbook say something about this?
For most companies, no. A handbook clause on industrial action is a statement in itself and can create difficulties rather than resolve them. An internal note recording an agreed position, with advice attached, is usually the better form.
What is the single most useful thing to prepare?
Know who decides, and know what each person currently holds. The first stops the question being answered by whoever happens to be asked. The second is worth having for entirely separate reasons and means any agreed action can be carried out accurately.
