Remote work policy: template, sections, example — and the one channel the policy lives in (2026)

A remote work policy is the written set of rules an organization applies to work done away from its office: who is allowed to work remotely and how often, from which places and countries, during which hours they must be reachable, how the team communicates and meets, who pays for the desk, the laptop and the connection, how company data is handled outside the building, and how the policy itself is changed. It is a short document — two to four pages for a company of ten to two hundred — and its purpose is not to permit remote work but to make it predictable: the same answer to "can I work from my parents' place in June?" whoever asks and whoever is asked.

This guide is the craft first — what a remote work policy is and isn't, the ten sections a usable one carries, how to write one that the team actually follows — then a template you can copy, a filled-in example for a company of forty across three countries, and the mechanics: where the policy and its review live in the tools your team already uses, and what happens to the questions it provokes. Because the policy's real test is not the day it is signed. It is the Tuesday a new colleague in another city, reading in another language, asks the one question the policy was supposed to answer.

What a remote work policy is — and what it isn't

Five documents surround remote work, and they are routinely confused:

The policy is the rule layer: short, rarely changed, approved by whoever can bind the company. The agreement is the policy applied to one person and signed; the guidelines are the team's habits and change whenever the work does. A policy that tries to be all three — the rule, the contract and the daily habits — gets long, goes stale in a month and stops being read.

A remote work policy is also not a statement that remote work is allowed. "Employees may work remotely with their manager's approval" is a sentence, not a policy. The policy is what follows: from where, when, with what, at whose cost, and what happens when it does not work.

What to include: the ten sections

A usable remote work policy carries ten sections. Most templates online are a subset of this list; the ones most often missing are the eighth, the ninth and the tenth.

1. Purpose and scope. Why the policy exists in one sentence, and who it covers: employees, contractors, both; which countries' contracts; whether it applies to the whole company or named teams.
2. Eligibility and arrangements. Which roles can work remotely, and in which of three arrangements — fully remote, hybrid with set office days, or occasional with manager approval. Say who decides and how a request is made and answered.
3. Place of work. The registered place of work for each person, the countries work may be done from and for how long, and the rule for working from a country other than the contract's — because tax, social security and insurance follow the place where the work is done, not where the company sits. This is the section to write with a lawyer or an accountant per country; the policy's job is to say what the rule is and who checks it.
4. Working hours and availability. Core hours when everyone is reachable, in which time zone; expected response times by channel; how working hours are recorded where the law requires it; the right to be unreachable outside them.
5. Communication and meetings. Which channel is for what — the team channel for work, direct messages for the personal, email for the outside world; which meetings are mandatory and how a person who could not attend reads what was decided; where the written record of the team lives. This is the section that decides whether the other nine are ever read again.
6. Equipment and expenses. What the company provides — laptop, screen, headset, chair — what it reimburses — connectivity, a coworking desk, part of a home office — at what rate and how often, and what happens to the equipment when the person leaves.
7. Security and data. The devices that may hold company data; the sign-in the company requires; what may not be done on public networks or shared computers; where documents are stored and where they are not; whom to call within what time when a device is lost.
8. Health, safety and workspace. The minimum the company expects of the place work is done — a desk, a chair, light, a door that closes for calls — what the company checks and how, and the insurance that applies when an accident happens at home.
9. Performance and presence. That work is judged by what is finished and written down, not by the hours a status light is green; how goals are set and reviewed for a person the manager rarely sees; which written updates replace the visibility an office gives for free.
10. Review and changes. The owner of the policy, the date it is next reviewed, how a change is proposed and approved, and where the current version lives and the old ones are kept. A policy without this section is the version somebody printed in 2023.

What stays out: the organization's leave policy, expense policy and code of conduct, each of which the remote policy links to rather than restates; the team's daily habits — stand-up time, status format — which belong in the working guidelines; and anything that applies to one person, which belongs in that person's agreement.

How to write one: before, during, after

Before you write, collect the questions. Post one message in the team's channel: "We are writing the remote work policy — reply with the question you most want it to answer." The questions that arrive are the policy's table of contents in the words of the people who will read it; a policy that answers them is read, a policy that answers the questions HR had is filed. Collect for a week. Then write the ten sections, each as short as the questions allow, and send the draft to the same channel with a date by which comments close.

While you write, decide, don't describe. Every section ends in a rule a stranger can apply: "reachable 10:00–15:00 CET", not "we expect reasonable availability"; "up to 30 days a year from another EU country, notified two weeks before", not "working abroad is possible by arrangement". A rule that depends on who is asked is not written yet. Where the answer genuinely differs by country — place of work, hours recording, home-office allowance — write the rule per country in a table rather than a paragraph that tries to cover all of them.

After it is approved, put it where the team reads — and keep it there. The policy goes to the channel the team already works in, pinned, with the three decisions people asked about most quoted in the message that announces it. The same day: the review date goes in the calendar, the agreement template goes to the people who need one, and the old version, if there was one, is marked superseded and kept. A policy that lives in one HR folder is a policy the team does not have; the questions keep coming, and each one is answered from memory, differently.

How a distributed team then runs its week — the written status by a set time, the meetings that stay and the ones that go — is in how to improve team productivity; the rhythm of the meetings themselves is in meeting cadence.

A remote work policy template

[Company] — Remote work policy
Version: [1.0] · Owner: [name, role] · Approved: [date] · Next review: [date]
Applies to: [employees / contractors / both], under [country] contracts, in [all teams / named teams]

1. Purpose and scope
[One sentence: why the policy exists.] This policy covers work done away from [office address]. It links to the [leave policy], [expense policy], [data protection policy] and [code of conduct], which apply unchanged.

2. Eligibility and arrangements
Roles eligible: [list, or "all roles except …"]. Arrangements: fully remote — [who]; hybrid — [office days per week, which days, set by whom]; occasional — [up to N days a month, approved by the manager in the channel]. A request is made [where] and answered within [N] working days.

3. Place of work
Each person's registered place of work is the one in their agreement. Work from another place in the same country: [allowed / notify manager]. Work from another country: [up to N days per calendar year, notified N weeks ahead, only from countries listed here]; longer stays require [a new agreement]. [Name] confirms the tax and insurance position before approval.

4. Working hours and availability
Core hours: [10:00–15:00] [time zone], working days. Response time: team channel [within 2 hours in core hours]; direct message [same day]; email [next working day]. Hours are recorded [how, where the law requires]. Outside working hours nobody is expected to read or answer.

5. Communication and meetings
The team channel is where work happens; [the written status is posted by [day, time]]. Mandatory meetings: [list, cadence]. A person who cannot attend reads the meeting's recap in the channel [by when]. Decisions not written in the channel were not made.

6. Equipment and expenses
The company provides: [laptop, screen, headset, …]. The company reimburses: [connectivity N per month / coworking desk up to N / home-office allowance N per year], claimed [how, how often]. Equipment is returned within [N] days of leaving.

7. Security and data
Company data lives only on [company-managed devices], signed in with [the company sign-in]. Not allowed: [shared computers, public networks without VPN, storing files outside [the named tools]]. A lost or stolen device is reported to [name / address] within [N] hours.

8. Health, safety and workspace
The minimum workspace: [a desk, a chair, daylight, a quiet place for calls]. The company [checks how: a self-assessment once a year / on request]. Accidents during working hours at the registered place of work are covered by [insurer / scheme].

9. Performance and presence
Work is assessed on [outcomes agreed in writing, reviewed every N weeks], not on hours online. [The written status] replaces the status meeting. Presence indicators are not a measure of work.

10. Review and changes
This policy is reviewed by [owner] on [date] and after [a change in law, a new country, an incident]. Changes are proposed [in the channel], approved by [who] and announced [where]. The current version is [pinned in the team channel]; previous versions are kept [where].

Revision history: [date — version — what changed — approved by]

A filled-in example: forty people, three countries

An illustrative policy for a design and localization agency of forty, headquartered in Milan, with a studio of twelve in Bucharest and nine people working from home in Portugal and Spain. The numbers are examples; the shape is the point.

Studio Alba — Remote work policy · v2.1 · Owner: Chiara R., COO · Approved: 6 Oct 2026 · Next review: 6 Apr 2027
Applies to: employees on Italian, Romanian, Portuguese and Spanish contracts; contractors by their agreement.

1. The policy exists so that a person in any of our four countries knows the same rules as a person in Milan. It covers work done away from Via Torino 12, Milan, and from Strada Lipscani 4, Bucharest.

2. All roles are eligible except reception. Hybrid for Milan and Bucharest staff: Tuesday and Thursday are studio days, set per team by the team lead each quarter. Fully remote for Portugal and Spain. Occasional extra remote days are asked for in the team channel and answered by the lead the same day.

3. Registered place of work: the address in each agreement. Work from another EU country: up to 30 calendar days a year, notified in the channel two weeks ahead; longer than 30 days needs a new agreement. Outside the EU: not permitted. Chiara confirms the position with the accountant for each country before approving a stay over 14 days.

4. Core hours 10:00–15:00 CET; Lisbon colleagues 09:00–14:00 local. Team channel: answered within two hours in core hours. Direct messages: same day. Client email: next working day. Hours are recorded in the time tool where the contract's law requires it (Italy, Spain). Nobody reads the channel after 18:00 their time.

5. Each team's channel is where its work happens. Friday status by 16:00 CET in the shape posted in the channel. Mandatory: the Monday team meeting (30 min) and the monthly all-hands; everyone else reads the recap in the channel by the next morning. A decision that is not in the channel was not made.

6. Provided: laptop, screen, headset; a chair on request. Reimbursed: €40 a month for connectivity; a coworking desk up to €150 a month for fully remote staff who ask; both claimed quarterly through the expense tool. Equipment is returned within 10 days of leaving.

7. Company data on company laptops only, signed in with the company Google account; client files in the project's channel or the client's shared drive, nowhere else. No public Wi-Fi without the VPN. A lost device is reported to Chiara within 4 hours, by any means.

8. Minimum: a desk, a chair with back support, daylight, a door that closes for calls. A self-assessment form once a year; the company pays for a chair where the form says the one at home will not do. Accidents at the registered place of work in working hours are covered by the national scheme of the contract's country.

9. Goals are set in writing every six weeks with the lead and reviewed in the one-on-one. The Friday status is the visibility; the green dot is not.

10. Reviewed by Chiara every six months and after any new country or incident. Changes proposed in the #studio channel, approved by the two directors, announced in the same channel with the changed lines quoted. Current version pinned in #studio; previous versions in the policy folder.

Revision history: 6 Oct 2026 — v2.1 — section 3: 30 days abroad, was 20 — directors.

Notice what the example has that most policies lack: a time zone next to every hour, a named person next to every approval, a number next to every allowance, and a section 10 that says where the policy is and who will change it. That is the whole craft.

Where the policy lives in the tools you already use

The policy itself is a document, and it lives wherever the team's documents live — a Word file in a shared library, a Google Doc, a page in a wiki, a canvas. The questions it provokes and the review that changes it are a meeting, and each platform has a place for what that meeting leaves behind, and each stops at a different point. Documented behaviour only, from the vendors' own pages, with the month each page was checked:

Two things are the same everywhere. The policy is a document in the one language it was written in, and the colleague who reads another language reads that one or a copy someone made; and what the review changed gets into the document only if a person types it in afterwards, in that same language. For a team in one office, in one language, the table is the whole answer. The next section is one way the job gets done where it is not.

The one channel the policy lives in

InterMIND is a communication space where a team's work lives in a channel, so the remote work policy has an obvious home: the channel of the team it covers. Posted as a note — a rich-text message with headings and numbered sections, editable later from its own menu — it is read by each member in their own language, with the original and a diff of what changed a toggle away, and pinned so the current version is the first thing a new colleague finds. Uploaded as a file instead — a PDF or a Word document from the HR folder — it opens for each reader translated into their language on paid plans, and on every plan its card carries an AI summary in the reader's language, each point linked to the paragraph it came from, so the two-minute version exists before anyone has written it. If the master copy stays in a document tool, its updates land in the channel by email: the channel's host gives it an address of its own, and a message sent there appears as a regular message with the sender named and attachments kept.

The questions the policy provokes stay with it. A member in Bucharest asks in Romanian under the pinned note; the lead in Milan reads it in Italian and answers in Italian; the colleague in Lisbon reads both in Portuguese — the channel's chat is translated per reader, and the thread of questions and answers becomes the policy's own commentary, searchable later. A question from the road is a voice note from the phone, up to ten minutes, transcribed within seconds and read by each teammate as text in their own language. The "occasional remote day" request of section 2, the "30 days abroad" notice of section 3, the Friday status of section 5 — all of them are messages in the same channel, with an author and a time.

The review meeting starts from that channel. During the call, the current version goes on everyone's screen next to the video tiles with Share to conference — a note, or a Google Docs or OneDrive document linked in the chat — and each participant scrolls it independently and reads it in their own language; a shared note is edited live by the sharer while the room watches the changed section take shape. When the call ends, the recap is written from the meeting itself — a summary, the points marked agreed, open or disputed, the action items with owners, each line keeping its timestamp — and the documents shared during the session contribute their summaries alongside what was said. It arrives by email, as a message in the channel and as a link in the calendar event, and every signed-in member reads it in their own language: the record is translated per reader, not written once in the language the room happened to use. Any member can edit it, every edit keeps author and revision history, and the channel keeps the recap of every past session — so the review that produced v2.1 is one click from the note that is v2.1. An ad-hoc meeting by link leaves only its recap, in each participant's Inbox, and its chat is wiped when the call ends; a policy and its history belong in a channel.

The people a remote work policy covers are not always employees. A contractor in Spain, a freelancer who works two days a week, a distributor's project manager who follows the same communication rules: an external member of the channel joins by email onto a free account and reads the policy and its history like everyone else; a person without an account is a guest of one meeting — a candidate, a supplier for one review — who joins by link, from a phone, at no cost, hears the meeting live in their own language, and gets no record afterwards. The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days — joined a meeting, wrote in a chat or asked the assistant; members who go quiet keep their access at no cost, and people from outside the team in a channel or a meeting are not counted.

• Open a complete recap — a real record rendered by the same code that writes yours.
• Try the live demo — no signup; speak, and hear the room translated per listener.

Remote work policies as a craft survive every tool: somebody still has to decide the hours, name the countries, put a number next to the allowance and write down who changes the rule. What doesn't have to survive is the second job — keeping a translated copy of every version by hand, and answering the same question from memory, in one language, for people who read others.

FAQ

What is a remote work policy?

A remote work policy is the written set of rules an organization applies to work done away from its office: who may work remotely and in which arrangement, from which places and countries, during which hours they must be reachable, how the team communicates and meets, what equipment and expenses the company covers, how company data is handled outside the office, what the workspace at home must provide, how performance is assessed, and how the policy itself is reviewed and changed.

What should be included in a remote work policy?

Ten sections: purpose and scope; eligibility and the arrangements offered; place of work, including the rule for other countries; working hours, availability and response times; communication and meetings, including where the written record lives; equipment and expenses; security and data; health, safety and workspace; performance and presence; and review and changes, with the owner, the next review date and where the current version is kept.

How do you write a remote work policy?

Collect the questions the team wants answered, in the channel where it already talks, for a week. Write the ten sections so that each ends in a rule a stranger can apply — hours with a time zone, allowances with a number, approvals with a name — and put country-specific rules in a table. Send the draft to the same channel with a date for comments, get it approved by whoever can bind the company, then pin it where the team reads, put the review date in the calendar, and keep the old version marked superseded.

What is the difference between a remote work policy and a work from home policy?

A work from home policy covers one place — the employee's home, usually in the same city and country as the office. A remote work policy covers any place away from the office: home, a coworking space, another city, another country, each with its own rules on hours, tax and insurance. Most organizations that started with a work-from-home policy end up rewriting it as a remote work policy once the first person moves.

What is a hybrid work policy?

A remote work policy in which the default arrangement is a split between the office and elsewhere: set office days per week or per team, who sets them, and how the remote days follow the same rules as fully remote work. It is usually a section inside the remote work policy rather than a separate document, because the rules on hours, data and equipment are the same for both.

Is there a remote work policy template in Word or Google Docs?

The template in this guide is plain text with bold labels, so it pastes into a Word document, a Google Doc, a Notion page, a Slack canvas or a chat note without reformatting. The format matters more than the file: whatever holds the policy needs the owner and the review date in the header, a rule a stranger can apply in each section, and a tenth section that says where the current version lives and who changes it.

How often should a remote work policy be reviewed?

On a date written in the header — every six or twelve months is usual — and earlier when one of four things happens: a person starts working from a new country, a law on remote work or hours recording changes in a country the policy covers, an incident the policy did not prevent, or three exceptions to the same rule in a row. The review is a short meeting with the team leads, and it ends in a new version with one line in the history or a confirmation with a new review date.

Does a small company need a remote work policy?

A company of ten with two people working from another country needs one more than a company of a thousand in one building: the questions — which country's rules apply, when is everyone reachable, who pays for the desk — arrive on day one, and without a policy each is answered from memory, differently. For a small company the policy is two pages, written in a week, and it lives in the team's channel rather than in a handbook.

Sources: Microsoft — Take meeting notes in Microsoft Teams; Zoom — Using Meeting Summary with AI Companion; Google — Calendar & Meet settings for "Take notes for me"; Google Meet — "Take notes for me" in Google Meet; Slack — Use huddles in Slack; Slack — Meeting agenda template (canvas). Microsoft, Google and Slack pages checked October 2026; the Zoom meeting-summary page checked August 2026. Vendors change plans, features and language lists over time; check their pages for the current state. The policy sections and the example are illustrative, not legal advice; the rules on place of work, hours recording and insurance differ by country.