Writing a Remote Work Policy People Actually Follow

A remote work policy exists to answer questions before they are asked. Most instead read as a legal disclaimer wrapped around a vague aspiration, and the questions get answered informally, differently, by each manager.

What a usable policy answers

Work backwards from what people actually ask.

Where can I work from? Anywhere in the country? Anywhere you are already registered as an employer? Anywhere with an overlap requirement? Can I work from another country temporarily, and for how long? This last one causes more trouble than any other and is almost never addressed.

When am I expected to be available? Core hours, response time expectations, and whether those differ for urgent matters.

How much notice do I need to change my arrangement? For a temporary move, a permanent relocation, a change of days.

Who decides? Named role, not "management".

What equipment do I get, and what happens to it when I leave?

What is reimbursed? Internet, phone, desk, chair, coworking space. With amounts.

What happens if it isn't working? The process for changing an arrangement, in both directions, and the notice involved.

A policy that answers those seven questions in plain language is more useful than twenty pages that answer none of them.

Write it for the reader who is anxious

The person reading your remote work policy most carefully is usually deciding whether they can accept a job, move house, or arrange childcare. They are looking for certainty and they will read ambiguity as bad news.

Vague language does not preserve flexibility; it transfers risk to the employee, who then either asks their manager for an informal assurance you cannot honour, or leaves.

The parts organisations get wrong

Location approval without a list. "Subject to approval" with no criteria means every request is a negotiation and outcomes vary by manager confidence. Publish the list of locations where you can employ people. It is a finite list and you already know it.

Silence on international work. Employees will work from abroad — visiting family, extended trips. Saying nothing does not prevent it; it prevents you knowing about it. Set a limit in days, require notice, and explain plainly that permanent tax residence elsewhere is a different matter requiring a different conversation.

Equipment rules with no exit process. Say who owns the laptop, how it comes back, and what happens to the chair you bought.

Reimbursement described as "reasonable expenses". Reasonable to whom? Give numbers.

No review date. Policies without a stated review date are either permanent by accident or revised by surprise. Both damage trust.

Length

Two to four pages. If it is longer, it is doing something other than answering questions.

Split anything genuinely long — tax guidance for international work, security requirements — into linked annexes so the main document stays readable.

Involve managers before publishing

The policy will be enforced by line managers who were not consulted and do not agree with it. Ask a handful to read the draft and tell you which clause they would quietly ignore. Their answers tell you where the policy will actually fail.

Say what you will not do

A policy that only grants is read as marketing. One that also states limits reads as honest.

"We cannot employ people outside these countries." "We cannot support permanent relocation to a jurisdiction where we have no entity." "We will not reimburse home office furniture beyond this amount."

Constraints stated plainly are far better received than constraints discovered later.

Review it on a schedule

Put the date in the document. An annual review with a published outcome — even "no change" — signals that the arrangement is managed rather than drifting.