Global HR 9 min read

What an Employee Relocation Policy Leaves Out

An employee relocation policy covers flights, housing and shipping. The desk, the chair and the laptop fall between the lines, and that is where disputes start.

Sarah Mitchell Sarah Mitchell • • 9 min read
What an Employee Relocation Policy Leaves Out

TL;DR

An employee relocation policy is strong on the expensive things and silent on the cheap ones. Flights, temporary accommodation, shipping allowance, immigration support. Then the person arrives, needs a desk, a chair and a second monitor, and discovers the document has nothing to say. The amounts are small. The number of arguments per pound is remarkably high.

  • Relocation documents cover moving, not working. The gap is the home office.
  • Say what is issued, what is reimbursed and what is not. Three numbers.
  • Decide whether a shipping allowance covers furniture, because people assume it does.
  • Treat self-initiated moves as the same question with a different trigger.
  • Name who approves an exception before the first one arrives.
  • Write the return condition for anything the company buys.

Why an employee relocation policy stops at the front door

A relocation policy is a moving document. It answers how the person and their belongings get from one place to another, and who pays for it.

It is almost never a working document. It does not answer what the person sits on, what they look at, or what they type on once they arrive.

For an office-based role that gap does not matter, because the office answers it. For anyone remote or hybrid, the gap is the entire question.

Why it produces disputes out of proportion to the money

Relocation is already stressful and already involves a lot of money moving around. A disagreement about a 300 pound desk lands on top of that, and it reads as the company being mean rather than the policy being incomplete.

The fix costs nothing. It is three sentences in a document that already exists.

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 →

The three numbers worth publishing

Every workable version of this answers the same three questions explicitly.

  • What the company issues. Usually the laptop, often a monitor and peripherals, sometimes a headset.
  • What the company reimburses, and up to how much. Desk, chair, and whatever else you choose to cover.
  • What the company does not cover. Say it plainly. Broadband upgrades, room renovations, anything bolted to a wall.

The third one does the most work and is the one usually omitted, because it feels unfriendly to write down. It is less unfriendly than refusing a claim after somebody has spent the money.

Item Common treatment Where it goes wrong
Laptop and peripherals Company issued Nobody arranges it for the new country
Desk and chair Reimbursed to a cap Cap unstated, so the first claim sets it
Second monitor Varies Issued at home, not at the destination
Connectivity Often excluded Assumed included by the employee
Shipping of existing furniture Inside the moving allowance Allowance runs out before the office kit

Row five is the quiet one. A shipping allowance is usually sized for personal belongings. When somebody uses it on a desk and a filing cabinet, something else does not travel, and they ask for more.

Setting the cap on something real

If you fund a workspace, set the number against what a working setup costs rather than a round figure somebody liked. the OSHA computer workstation guidance describes what a properly arranged workstation involves, which is a better basis than guessing.

Tax treatment also differs by country and is worth checking rather than assuming. the UK guidance on homeworking expenses and benefits sets out the UK position on homeworking expenses and benefits, and the equivalent rules elsewhere are often not the same shape.

Ownership and the return condition

If the company buys it, say who owns it and what happens when the person leaves.

For a laptop this is obvious and usually written down. For a 400 pound chair bought in another country it is almost never written down, and recovering it is rarely worth the cost of shipping it back.

Most companies land in one of two places, and either is defensible as long as it is stated.

Company property, recovered on exit. Honest, and it needs a realistic recovery plan for furniture, which usually means local disposal or sale rather than return.

Becomes the employee’s after a period. Simpler, avoids a logistics problem that costs more than the asset, and is easy to explain.

Why the second is often better for furniture

Shipping a desk back across a border costs more than the desk. Paying to recover an asset you will then scrap is a worse outcome than writing it off cleanly.

Laptops are different, because the data makes recovery necessary regardless of the residual value. We covered that split in what to do about unreturned equipment.

Self-initiated moves are the same question

The classic relocation is company-initiated. Increasingly the common case is an employee telling you they are moving and asking whether that is fine.

Mobility processes usually have nothing for this, because no assignment exists. But the equipment question is identical and arrives with less notice.

Three things to decide in advance.

  • Does the company fund anything at all for a move it did not ask for?
  • Who pays to get the existing equipment to the new address?
  • What happens if the new country cannot be supported?

The third one is the hard one, and it is a business decision rather than an equipment decision. A policy that quietly implies anywhere is fine will be tested.

The decision table

Match the row to the kind of move rather than the seniority of the person.

Situation Scale Setup Primary pain Recommended starting point
Company-initiated, permanent Any Full relocation package Home office unfunded Add the three numbers to the existing pack
Company-initiated, short assignment Any Temporary accommodation Kit sized for a permanent move Issue a travel setup, recover at the end
Employee-initiated, same country Any Remote-first policy Policy silent One line: company does not fund a self-move
Employee-initiated, new country Any No entity there Support and payroll both unclear Decide the country list before the request
Several moves a year Series B+ Mobility function exists Every case negotiated separately Publish the caps, delegate approval

Row three saves more argument than any other line here. One sentence stating that self-initiated moves are not funded, published in advance, prevents the entire conversation.

Exceptions, and who signs them

Every policy here needs an exception route, because some of the requests are legitimate and specific.

An accessibility requirement is not an exception to be negotiated against a cap. Neither is a role that genuinely needs unusual hardware. Both should be routed somewhere other than the standard expense approval, and quickly.

The design error worth avoiding is sending an accessibility request through the same queue as a monitor upgrade. It is slower, and it asks somebody to justify a need they should not have to justify to a line manager.

Name the approver

Say who can approve above the cap, and keep it to one or two named roles. An exception process with no named owner becomes a negotiation with whoever answers first, which produces inconsistent outcomes and resentment.

For the standing version of this question outside relocation, see our piece on handling equipment accessibility requests.

What to actually add to the document

A short section, placed with the other allowances rather than in an IT annex nobody reads.

It should state the issued equipment list, the reimbursement cap for workspace items with a currency and a date, the exclusions, the ownership position, the return condition, and the named approver for exceptions.

That is six lines. It replaces an unbounded set of individual negotiations with a document, and it makes the answer the same for everybody, which is the part employees actually care about.

Those six lines are the whole of what an employee relocation policy needs to say about equipment. Anything longer tends to be read by nobody.

Review it when the country list changes

A cap written in one currency ages badly across markets. Review the figures when you add a country, not annually, because the annual review always lands after the awkward case.

For teams placing equipment in countries where they have no office, RemoAsset handles procurement and delivery in-market and recovery when someone leaves, which removes the hardest part of writing the return condition.

RemoAsset delivers and recovers equipment in markets where you have no local presence. More on equipment policy at HROpsLab.

Frequently asked questions

What should an employee relocation policy include about equipment?

Three numbers and three rules. What the company issues, what it reimburses and up to what cap, and what it does not cover at all. Then who owns anything purchased, what happens to it when the person leaves, and who can approve an exception. That is roughly six lines added to a document you already have, and it replaces an open-ended series of individual negotiations with a single published answer.

Does a relocation shipping allowance cover a desk and chair?

Usually it is not stated, which is why it causes trouble. The allowance is normally sized for personal belongings, so an employee who uses it on office furniture finds something else cannot travel and comes back asking for more. Decide explicitly whether workspace items sit inside the moving allowance or get their own line, and say which in the document rather than leaving it to be inferred.

Should we fund equipment for an employee who relocates by choice?

That is a business decision rather than a policy mechanic, and either answer works as long as it is published before the first request. A single sentence stating that self-initiated moves are not funded prevents more argument than any other line in this area. What does not work is silence, because the request arrives anyway, usually after the person has already moved and spent money.

Who owns a desk or chair bought for a relocated employee?

Pick a position and state it. Company property recovered on exit is honest but needs a realistic plan, which for furniture usually means local sale or disposal rather than shipping it back. Becoming the employee’s after a set period is simpler and often cheaper, because returning a desk across a border costs more than the desk. Laptops are the exception, since the data makes recovery necessary whatever the residual value is.

How do we handle accessibility requirements during a relocation?

Route them somewhere other than the standard expense approval, and do it quickly. An accessibility need is not an exception to be negotiated against a cap, and sending it through the same queue as a monitor upgrade is both slower and asks someone to justify a requirement to a line manager who should not be assessing it. Name one or two roles who can approve outside the normal route.

What if an employee moves to a country we cannot support?

Decide the country list before somebody asks rather than after. Support coverage, payroll, tax presence and equipment logistics all constrain where somebody can realistically work, and a policy that implies anywhere is acceptable will eventually be tested by a request you have to refuse. Publishing a list of approved locations is less comfortable to write and far easier to apply consistently.

How often should the equipment caps be reviewed?

When the country list changes, rather than on an annual cycle. A cap written in one currency ages badly across markets, and the annual review reliably lands just after the awkward case that exposed the gap. Tying the review to adding a market keeps the figures roughly honest and means the update happens before somebody relocates into a country where the number makes no sense.

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 →