Writing down how a remote team works: a team handbook
What to put in a short handbook for a remote team: hours, channels, decisions, devices and time off, with public guidance on security and flexible working.
General information, not legal advice. Written October 10, 2026. A handbook can create obligations under local employment law, and those rules differ by country, so have an adviser licensed where your people work review anything you plan to call policy.
In an office, a lot of how the company works is learned by watching. Where to ask a question, when it is fine to be away, who decides what: a new person absorbs it in a week. On a remote team, none of that is visible. If it is not written down, each person invents their own version, and the differences surface as friction months later. A founder who works alone, or with one other person, tends to put this off because everything is in their head. The first hire is the moment it stops being enough.
This article describes a short handbook for a small remote team: what to put in it, what to leave out, how public guidance on security and flexible working bears on it, and how to keep it alive. It is a writing guide, not a policy template, and it is not legal review.
What a handbook is for
A handbook answers the questions a new person would otherwise ask you one by one, and the questions a person on the other side of the world cannot ask at the moment they need the answer. It has three jobs. It tells people how the team works so they can act without waiting. It gives you something to point to when two people remember an arrangement differently. And it forces you to decide things you have only been assuming.
It is not a rulebook, and it is not the contract. An offer letter and any employment agreement carry the legal terms, as offer letters describes. The handbook describes habits. If a handbook sentence and a contract disagree, the disagreement is a problem, so write habits and not promises.
Keep it short and in one place
Aim for a document a person can read in one sitting, kept somewhere every teammate can find without asking you. A dozen pages is more than a small team needs. People who must search through a long document to find the answer will ask you instead, and the handbook has failed.
Write it in plain sentences about what happens, not in the language of regulation. “Post a short update in the team channel at the end of your day” is better than “employees shall provide daily status communications.”
What to put in it
Six topics cover most of what a small remote team needs. The table lists them with the question each one answers.
| Section | Question it answers | What to decide first |
|---|---|---|
| Hours and availability | When can I expect to reach people, and when are they away? | Whether there is a window of shared hours, and what happens outside it |
| Channels and replies | Where do I post what, and how fast should I expect an answer? | Which channel is for what, and what counts as urgent |
| Decisions | Who decides, and how do I find out what was decided? | Where decisions are recorded and who may make them alone |
| Devices and access | What may I use, and how must I protect it? | Whether people use their own devices, and what is required of them |
| Time off and flexibility | How do I ask, and who is told? | How requests are made and who answers them |
| Working with customers | What may I say, and who speaks for the company? | Who owns each customer relationship |
Hours, channels and replies
For a team spread across time zones, availability is the section that prevents the most friction. State the hours when a person is generally reachable, in each person’s own time zone, and state what the team does with the hours that do not overlap. Say which channel carries which kind of message, and what a reasonable reply time looks like for each. A reply expected by the end of the next working day is a different request from one needed within the hour, and people cannot tell which you mean unless you say.
An operating rhythm for a remote offshore team describes the recurring meetings and written updates that carry this across time zones. The handbook is where the result of those choices is written down so a newcomer does not have to infer it.
Decisions
Write down who decides what, in a sentence each. “Product priorities are set by the founder after the weekly review” is enough. Add where a decision is recorded, for example a dated note in a shared folder. A remote team without a place for decisions finds that the same question is answered twice in two channels.
Devices and access
If people work from home, the handbook is the natural place to say what they must do to protect company data. Public guidance gives a sense of what such a section addresses. NIST, the US standards agency, says in its guide to enterprise telework, remote access and bring your own device security that all components of these technologies, including organization-issued and bring your own device (BYOD) client devices, should be secured against expected threats as identified through threat models. The publication also gives advice on creating related security policies. It is written for large organizations, and a small team does not need its full detail, but it shows that device policy is something to decide deliberately.
Data protection regulators publish guidance on home working as well, and the rules differ by country. If your people handle other people’s personal data, ask your adviser what your obligations are where you and they operate, and write the practical result into the handbook.
At a minimum, a short section can say which accounts people use for company work, whether personal devices are allowed, what must be switched on to protect a device, and whom to tell if one is lost.
Time off and flexible working
Rules about leave and flexible working differ widely. As an example of one national rule, the UK government says all employees have the legal right to request flexible working, and that employees can make a request for flexible working from their first day in a job. Its page describes flexible working as including having flexible start and finish times, or working from home. That is a UK rule and an example of how a legal right can shape a handbook. If you employ someone there, or anywhere else, ask your adviser what applies and how requests must be handled.
Write down how a person asks for time away, whom they tell, and how the calendar shows it. Keep the statement of what the law requires out of the handbook unless an adviser has reviewed it, since a wrong statement is worse than none.
What to leave out
A handbook should not repeat the law, promise outcomes or set rules you do not plan to follow. It should not list consequences you have not thought through. It should not contain anything you would be uncomfortable showing a person who was upset with you. If you are unsure whether a sentence belongs, ask whether it describes how the team actually works. If not, cut it or change the behavior.
A handbook grows in passes. No team writes a complete handbook on day one. A pass-based approach lets the document follow the work.
-
Write the first page
Hours, channels, reply times and who decides what. One page is enough.
-
Add after the first surprise
Each time a misunderstanding costs the team a day, add the sentence that would have prevented it.
-
Prune on a schedule
Every quarter, delete what nobody has used and fix what has changed.
-
Hand it to the next person
Ask each new team member what was unclear and edit while the confusion is fresh.
How to keep it alive
A handbook that is never updated becomes a document nobody trusts. Give it an owner, put a review date on the first page, and change it whenever a habit changes. Invite the team to correct it. People who work remotely often see gaps before you do, because they are the ones who hit them. Keep a list of changes at the top so the team can see what moved.
The best test is a new person’s first week. Onboarding a new team member describes what to prepare, and the handbook should be the first thing they read. Note every question they ask that it should have answered, and add it. If you are still deciding on a first hire, your first hire covers what to settle before you write the job, and if the person will work abroad, hiring across borders lists the questions to ask an adviser. The glossary defines shared terms.
Where this fits in a long effort
A handbook is a record of how a team has agreed to work, and it matters more the longer the team stays together. Teams that expect to last years benefit from a document that a new person can read in an hour. The research on coworking and community describes why shared norms and regular contact matter to people who work alone, and the longevity paradox article explains why a team that writes things down is easier to sustain over a decade.
Founder communities and coworking spaces, listed in the ecosystem directory, are good places to compare handbooks with other small teams before writing your own.
What this article cannot tell you
This article cannot tell you what your handbook must say, which rules apply to your people, or whether a particular sentence creates a legal obligation. It draws on two public pages read on October 10, 2026: a US standards publication on telework security and a UK government page on flexible working. The UK page describes a UK rule and is an example, not guidance for other countries. It does not cover monitoring of employees, disciplinary procedures, expenses, data protection law in your jurisdiction, or the security controls your own systems need. Ask a qualified adviser before you adopt any rule as policy.
In the data
These figures describe U.S. businesses in general, not WE’s results. Each one names its source.
Show the data as a table
| Age group | Median tenure |
|---|---|
| Ages 20 to 24 | 1.5 years |
| Ages 25 to 34 | 3.0 years |
| Ages 35 to 44 | 4.7 years |
| Ages 45 to 54 | 7.0 years |
| Ages 55 to 64 | 9.6 years |
| Ages 65 and over | 9.9 years |
| All workers 16 and over | 4.1 years |
Wage and salary workers only; tenure is time with the current employer, not in the current job.
Source: U.S. Bureau of Labor Statistics, Employee Tenure, Table 1 , January 2026
Retrieved 2026-10-16. Values are the published medians for both sexes, copied as printed.
Sources
- SP 800-46 Rev. 2, Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security, National Institute of Standards and Technology . Accessed October 10, 2026.
- Flexible working, GOV.UK . Accessed October 10, 2026.
Spotted an error? Read how we handle corrections in our editorial policy.