HR Operations 9 min read

The Reduction in Force Checklist Nobody Writes: Equipment

A reduction in force checklist covers selection, notification and pay. The equipment recovery runs for months afterwards and nobody plans for it.

James Carter James Carter • • 9 min read
The Reduction in Force Checklist Nobody Writes: Equipment

TL;DR

A reduction in force checklist is built around a single day. Selection, notification, documentation, final pay, communications. All of it converges on one date and then the project is considered closed. The equipment does not work like that. Forty laptops do not come back in a week, and the team that would chase them has usually just been reduced too.

  • Equipment recovery runs for months after a date everyone treats as the end.
  • Volume arrives all at once. Schedule collections across weeks, not days.
  • The people who would chase devices are often part of the reduction.
  • Do not tie recovery to final pay. It is a legal question and a bad relationship move.
  • Expect a long tail and budget for it instead of reporting failure.
  • Decide in advance whether recovered kit is reissued, stored or sold.

Why a reduction in force checklist ends too early

These projects are organised around a notification date, and that is right. Everything legally and ethically significant clusters there.

So the checklist is built as a countdown. Selection criteria, consultation where required, documentation, notification scripts, final pay calculations, internal and external communications. Then the date passes and the project closes.

Equipment is the one workstream that genuinely starts on that date rather than ending on it.

The resourcing trap

Worse, the capacity to handle it often shrinks at the same moment. IT and people operations teams are frequently part of the reduction, so the volume peaks exactly as the headcount to deal with it falls.

That combination is why devices from a reduction take longer to recover than devices from ordinary attrition, and why the recovery rate is usually worse.

Free Weekly Briefing Stay ahead of what's changing in HR and people ops.

Join 4,200+ leaders getting practical insights every week — no fluff, just signal.

Join Free →

Plan for volume, not for one leaver

Ordinary offboarding handles one device at a time. A reduction produces thirty or eighty at once, and the process built for one does not scale by repetition.

Constraint Fine for one leaver Breaks at volume
Packaging Order as needed Needs ordering in advance, in bulk
Collections Book individually Needs scheduling across weeks
Receiving Someone opens a box Needs space and a person assigned
Wiping Ad hoc Needs a queue and a record per device
Chasing An email Needs an owner and a tracker

The receiving row is the one people underestimate. Eighty laptops arriving at an office over three weeks need somewhere to go and somebody to log them, and if neither exists they sit in a pile and the asset records never get updated.

Stagger the collections deliberately

Booking everything for the same week is the obvious move and the wrong one. Spread collections across two to three weeks so receiving and wiping can keep pace, and so that a missed collection can be rebooked without the whole queue slipping.

Recovery from people who were let go

This is the part that deserves care rather than process optimisation.

Somebody who has just lost their job is being asked to do an administrative favour for the organisation that let them go. The request should be as close to zero effort as it is possible to make it.

That means packaging sent to them, collection booked at a time they choose, and no requirement to print anything. It also means the tone of the request matters, and it should come from a person rather than an automated sequence.

What not to do

Do not make final pay conditional on return. Whether that is even lawful depends on where the person is employed, and the Acas guidance on dismissals sets out the UK framework around dismissals while the position differs elsewhere. Beyond legality it converts a logistics task into a dispute, and disputes do not produce laptops faster.

Do not send chasing emails on a weekly cadence from a no-reply address. The recovery rate does not improve and the reputational cost is real, particularly for people who may be in contact with your remaining staff.

Budget for a long tail

Some devices take a long time. People move house, go travelling, start a new job and stop checking an old personal email, or simply put it off.

A process that assumes two weeks will record most of the batch as a failure, which is both inaccurate and demoralising for whoever owns it.

The more useful framing is three buckets, reported separately.

  • Recovered. In hand, wiped, dated.
  • In progress. Contact established, collection arranged or pending.
  • Unresolved. No contact, no collection, after a stated number of attempts.

Only the third is a loss, and it is normally far smaller than a single headline recovery percentage suggests at the four week mark.

When to stop

Decide the stopping rule in advance: a number of contact attempts over a set period, after which the device is written off and the asset record closed with a reason. An open row that nobody will ever close is worse than an honest write-off.

The decision table

The right approach depends on scale and geography more than anything else.

Situation Scale Setup Primary pain Recommended starting point
Under ten people, one country Any Office exists Minor Individual collections, normal process
Thirty or more, one country Series A+ Hybrid Receiving capacity Stagger collections, assign a receiver
Across several countries Series B+ No local presence No courier relationships Partner-managed, country by country
IT team also reduced Any Capacity cut Nobody owns the chase Name an owner outside the affected team
Office closing at the same time Any No destination Nowhere to send devices Arrange storage before notification day

Row five is more common than it sounds, because reductions and office closures often happen together. If there is no office to return equipment to, that has to be solved before anybody is told, not after the first collection fails.

Decide where the equipment goes

Recovered devices need a destination decided in advance, because a pile with no decision attached becomes a cupboard problem.

Reissue. The best outcome where the fleet is standardised and the devices are recent. It also removes near-term purchasing, which matters in the circumstances.

Store. Sensible if hiring is expected to resume, and only if the storage is real rather than a corner of a room.

Sell or recycle. Appropriate for older machines. Anything leaving needs documented sanitisation first, and NIST Special Publication 800-88 on media sanitization sets out what that actually involves.

For distributed teams the practical constraint is that devices come back to no single place. RemoAsset handles recovery across markets and storage of recovered stock, which is what allows reissue to be a real option rather than a theoretical one.

Our note on equipment during a redundancy process covers the people-side sequencing in more detail.

Reissue is worth more than it looks

A reduction usually arrives alongside a spending freeze, which makes recovered hardware the only source of machines for the roles that remain. Forty recovered laptops can cover a year of replacements for the people still there.

That only works if the devices are logged on arrival rather than stacked. A pile of unlogged laptops is indistinguishable from no laptops when somebody needs one in March.

Tell the remaining team what happened

People notice equipment disappearing and they draw conclusions. A short note explaining that recovered machines are being reused rather than disposed of costs nothing and prevents a rumour that the company is quietly selling off assets.

It also makes the reissue practical. Somebody receiving a colleague’s former laptop should know that is what it is, and that it was wiped, rather than finding out from a sticker on the lid.

RemoAsset recovers and stores equipment at volume across markets, including where you have no office. More at HROpsLab.

Frequently asked questions

What does a reduction in force checklist usually leave out?

The equipment workstream, because the whole project is organised around a notification date and equipment is the one thread that starts on that date rather than finishing on it. Forty laptops do not come back in a week, and the recovery runs for months. Worse, the IT and people operations capacity that would normally chase them is frequently part of the reduction itself, so volume peaks exactly as headcount falls.

How should equipment collections be scheduled after a layoff?

Spread across two to three weeks rather than booked for a single week. Everything arriving at once overwhelms receiving and wiping, so devices sit in a pile and asset records never get updated. Staggering also means a missed collection can be rebooked without the entire queue slipping. Order packaging in bulk ahead of notification day, because ordering as needed does not scale past a handful.

Can we withhold final pay until equipment is returned?

Treat that as a legal question rather than a policy choice, because whether it is permissible depends on where the person is employed and the answer is not uniform. Separately from legality it is a poor move, since it converts a logistics task into a dispute and disputes do not produce laptops any faster. Make returning the equipment as close to zero effort as possible instead.

What recovery rate should we expect?

Report it in three buckets rather than as one percentage, because a single number at four weeks will look like failure regardless of how well the process ran. Recovered means in hand, wiped and dated. In progress means contact established and a collection arranged or pending. Unresolved means no contact after a stated number of attempts. Only the third is genuinely a loss, and it is usually much smaller than the headline suggests.

When should we stop chasing an unreturned device?

Decide the stopping rule before the process starts: a set number of contact attempts across a defined period, after which the device is written off and the asset record is closed with a stated reason. An open row nobody will ever close is worse than an honest write-off, because it quietly corrupts both the asset register and the refresh forecast built on top of it.

What should happen to recovered equipment?

Decide the destination before the devices arrive, or the pile becomes a cupboard problem. Reissue is the best outcome for recent, standardised machines and removes near-term purchasing, which matters in these circumstances. Storage works if hiring is expected to resume and the storage is real rather than a corner of a room. Older machines should be sold or recycled, with documented sanitisation first.

What if we are closing an office at the same time?

Solve the destination before anybody is notified. Reductions and office closures frequently happen together, and if there is no office for equipment to return to then the first collection has nowhere to go. Arranging storage or a partner-managed receiving point in advance is a small piece of work that prevents the recovery stalling in its first week, which is the point at which momentum matters most.

Share on X Share on LinkedIn

What to do next?

Explore More Articles

Dig deeper into HR Ops strategy, tools, and workflows built for real teams.

Browse the blog →
Join the HROpsLab Community

Connect with People Ops practitioners sharing real workflows, tools, and challenges.

Join now →