How to run operations for a remote and distributed team.

Many tech startups are remote or hybrid from the start. It widens the pool of talent and cuts office costs, but the informal coordination of a shared office disappears. Questions that would take seconds across a desk become messages that wait hours. Remote teams therefore need clearer operations, not fewer.

Step by step

1. Default to writing. Decisions, plans and updates are written in a shared place, not just said in a call. A short decision log (what was decided, by whom, why, on what date) prevents repeated debates.
2. Agree which channel is for what. For example: chat for quick questions, the project tool for tasks, email for external contacts, documents for anything that needs thought, and calls for discussion and relationships. Write it down and include expected response times.
3. Set core hours and time zone rules. Agree a window of a few overlapping hours when everyone is reachable. Rotate meeting times fairly if your team spans several time zones.
4. Make ownership explicit. Every task, process and document has a named owner. Remote teams lose things in the gaps between people.
5. Onboard remotely with care. Prepare equipment and access before day one, give a written first-week plan, assign a buddy and schedule short daily check-ins for the first fortnight.
6. Secure every device. Company devices should be encrypted, updated and managed centrally where possible. If people use their own devices, set minimum standards. See the security guide in this playbook.
7. Build connection deliberately. Regular informal calls, occasional in-person meet-ups and visible recognition of good work help a remote team feel like a team.

Legal and practical points in the UK

Employers keep health and safety responsibilities for people working from home, including display screen equipment. Right to work checks apply to UK employees whether or not they are remote. If you employ people in other countries, local employment, tax and social security rules apply, and you may need local advice or an employer of record service. Contracts should state the place of work and any expectations about travel. Acas publishes guidance on hybrid and home working. This is general information, not advice; see the people playbook for more.

A remote operating handbook

A good remote handbook fits on a few pages. It sets out core hours and time zones; which channel to use for what, with expected response times; how meetings run and where notes go; how to request leave and report sickness; equipment and security standards; how expenses are claimed; and who to contact about what. New starters read it on day one.

A worked example

Clearwell Robotics, a fictional Bristol tech startup, had eight people across the UK and two contractors in other European countries. Decisions were made in calls, then forgotten or remembered differently.

It introduced a decision log, a channel guide with response times and a three-hour core window. Weekly meetings moved to a written update posted on Monday and a 30-minute call on Tuesday for discussion only. Within a quarter, the team spent less time in calls and reported fewer misunderstandings about who was doing what.

Common mistakes

• Recreating the office online. Back-to-back video calls exhaust remote teams.
• Expecting instant replies. It drives people to watch chat all day instead of doing focused work.
• Ignoring isolation. Quiet team members can struggle without anyone noticing.
• Overseas hiring without advice. Treating a long-term overseas employee as a contractor can create tax and employment risks.

What to measure

• Hours per person per week in meetings.
• Time for a new starter to have full access and equipment.
• Decisions logged per month.
• Team engagement, through a short regular pulse survey.