Remote work policy: the questions it has to answer

A remote work policy sets out who can work away from the office, from where, under what expectations, and who pays for what. Companies usually write one after the informal version produces its first awkward case: someone working from another country, an equipment claim nobody budgeted for, or a team that cannot find each other because everyone chose different hours.

The useful policy is short and specific. It is not a statement about flexibility being valued — it is a list of answers to questions that would otherwise be improvised.

What the policy must answer

• Who is eligible: all roles, some roles, after a probation period. Say it plainly, because the alternative is people inferring it from who was allowed.
• Where people may work from — home, anywhere in the country, anywhere at all — and whether working from another country needs approval. This last one has tax and employment-law consequences and is the most commonly missed clause.
• Hours: core hours when people must be reachable, and whether the rest is flexible.
• Equipment: what the company provides, what it will reimburse, and what happens to it when someone leaves.
• Home-office costs: internet, electricity, a desk — whether you contribute, and how.
• Data protection and security: devices, networks, screens in public places, and what may not leave a controlled environment.
• Health and safety: your obligations for a home workstation, which in many jurisdictions do not disappear because the desk is not yours.
• Meetings and communication: what happens in writing, what needs a call, and expected response times.
• How the arrangement changes — notice on both sides, and the grounds on which it can be withdrawn.

The working-from-another-country question deserves its own line. An employee spending months abroad can create a tax presence for the company, trigger local employment rights, and breach the terms of their own visa or your insurance. Requiring approval is not bureaucracy — it is the only way you find out in time. Take advice locally before writing the rule.

Writing one that survives

1. Decide eligibility first, and write the reason. "Roles that require handling physical stock are on site" is a rule people accept; unexplained exclusions are not.
2. Set core hours narrowly — a four-hour overlap is usually enough — and let the rest flex.
3. List equipment and the reimbursement route, with a figure. A policy that says "the company will provide suitable equipment" produces individual negotiations.
4. Write the security rules as behaviours rather than principles: lock the screen, no client data on personal devices, company VPN on public networks.
5. Cover health and safety concretely — a self-assessment checklist for the home workstation is the usual proportionate answer.
6. State the approval requirement for working abroad, with the notice period you need.
7. Say how the arrangement is reviewed and how either side ends it, so nobody is surprised.
8. Publish it, then check after three months which questions people are still asking — those are the clauses you did not write clearly.

What the policy cannot fix

Remote arrangements fail on management practice, not on policy wording. If one-to-ones get cancelled, decisions are made in rooms half the team is not in, and progress is judged by who is visible online, a policy will not help. The written rules remove ambiguity about hours, equipment and location; keeping a distributed team working requires a meeting rhythm people can rely on and a habit of writing decisions down where everyone can read them.

In Ettex, the policy lives in Ettex Docs with version history — useful when someone asks what the rule was in March — and threaded comments while it is being agreed. The equipment register, with who has what and when it was issued, fits Ettex Records as a table with typed fields and revision history. Core hours and the meeting rhythm sit in Ettex Calendar, day-to-day communication in Ettex Chat, and the home-workstation self-assessment works as a form in Ettex Forms, where each submission lands timestamped in one inbox — which is exactly the record a health-and-safety obligation asks for.

Said plainly: Ettex has no HR system. There is no employee record with contracts and absence, no policy acknowledgement tracking, no device management, no time or attendance monitoring, and nothing here tells you whether someone is working. It holds the document, a register you maintain, and a form for the checklist. For employment records at any scale, use an HR product. Where people work changes the tax and right-to-work position, so keep it consistent with the employment contract rather than the handbook alone.

Common gaps

• No rule about working from another country, discovered when it has already happened for four months.
• Core hours unstated, so a team spreads across a working day nobody shares.
• Equipment promised vaguely, producing a different deal for each person.
• Security written as principles, which cannot be followed or breached in any concrete way.
• Health and safety ignored on the assumption that a home desk is not the employer's concern — often untrue.
• No route back: a policy that grants remote work permanently with no stated review is hard to change later without it feeling like a punishment.
• Never revisited after the first three months, when the real questions have surfaced.

Two policies overlap with it and are better kept separate. A hybrid work policy sets the default pattern of office days, and a flexible working request is the statutory route an individual uses when they want something different from that default.

A remote work policy earns its place by answering the questions people would otherwise guess at: who, where, when, what equipment, what security. Write those, publish it, and fix the clauses people keep asking about.