Managing a Remote Team: 12 Practices That Actually Work
The Coavon team · · 22 min read
Managing a remote team well comes down to replacing what an office gives you for free with things you do on purpose. In an office, people overhear decisions, see who is busy and ask quick questions across a desk. Remotely, none of that happens unless you build it in. So write down how the team works, agree on clear goals and judge results rather than hours online, choose which tool is for what, default to written and asynchronous communication, keep a few well-run meetings, make all work visible in one shared place, meet each person one-to-one regularly, and look after workload and connection deliberately.
This guide covers each of those practices in detail, with the questions to answer, examples and templates you can copy. It also covers working across time zones, running remote meetings, measuring performance without micromanaging, onboarding new remote hires, the most common mistakes, and the tools a remote team needs. There is a checklist at the end.
Short on time? Jump to the 12 practices, time zones, remote meetings, measuring performance, the templates or the checklist.
What is remote team management?
Remote team management is leading a team whose members do most of their work away from a shared office: from home, a coworking space or anywhere else, often in different cities or time zones. The manager's job is the same as in any team (set direction, remove obstacles, develop people and deliver results), but the tools and habits are different, because almost everything that happens by accident in an office has to happen on purpose online.
The words used for different setups are easy to mix up:
| Setup | What it means | The main thing to manage |
|---|---|---|
| Fully remote | Everyone works away from an office, all the time | Communication and connection, since nobody meets by default |
| Hybrid | People split their time between an office and home, or some are in an office and some are not | Fairness: making sure remote people are not left out of decisions made in the room |
| Distributed | The team is spread across cities, countries or time zones (it may or may not have offices) | Time zones and hand-offs between people who are rarely online together |
| Remote-first | The company runs as if everyone is remote, even if some offices exist | Keeping decisions and information written down and online, never only in the office |
Most of the advice in this guide applies to all four. Where something matters more for hybrid or distributed teams, it says so.
What makes managing a remote team different?
Remote work removes a few things that offices provide without anyone noticing. Each one has a deliberate replacement:
| What the office gave you for free | What happens remotely | What to do instead |
|---|---|---|
| Overhearing decisions and news | People miss context and work from old information | Write decisions down in one place everyone reads |
| Seeing who is busy or stuck | Overload and blockers stay hidden until a deadline slips | Keep all work, owners and dates in a shared project tool; ask about blockers every week |
| Quick questions across a desk | Small questions wait hours, or turn into meetings | Agree response times and which channel is for what |
| Casual chats and lunches | People feel isolated and trust builds slowly | Make time for informal contact on purpose |
| Being seen working | Managers worry about effort, people feel they must look “online” | Judge outcomes, not hours or green status dots |
| A clear start and end to the day | Work spills into evenings and weekends | Set working hours and notification rules as a team |
The good news is that every one of these fixes also makes in-office teams better. Remote teams simply cannot get away without them.
How to manage a remote team: 12 practices
You do not need all twelve on day one. If you are starting from scratch, begin with the first four: a written working agreement, clear goals, a rule for which channel is for what, and one place where all work lives. Add the rest as the team grows.
1. Write down how your team works
The single most useful document for a remote team is a short team working agreement (sometimes called a team charter or a “how we work” page). It turns unspoken office habits into rules everyone can read. Keep it to a page or two and cover:
- Working hours and availability: each person's normal hours and time zone, and the hours the whole team overlaps.
- Response times: for example, chat messages within four working hours, emails within one working day, urgent issues by phone.
- Which tool is for what: where tasks live, where discussion happens, where documents are kept (see practice 3).
- Meetings: which regular meetings exist, who attends, and the rule that every meeting has an agenda.
- Decisions: how decisions are made and where they are written down.
- Time off and being unavailable: how to show you are away, and who covers what.
- Camera and call etiquette: whether cameras are expected, and that it is fine to turn them off sometimes.
Write it with the team, not for them, and review it every few months. Put it somewhere everyone can find it, and link to it from the onboarding checklist.
2. Set clear goals and judge outcomes, not hours
Remote managers who try to manage by watching activity end up anxious, and their teams end up exhausted from performing “being online”. Manage by results instead. Every person should be able to answer three questions at any time: what am I responsible for, what does good look like, and by when?
- Set a small number of team goals for the quarter (three to five), each with a measurable result, such as “cut the average time to answer a support ticket from two days to one”.
- Break each goal into projects and tasks with one named owner and a due date.
- Agree what “done” means before work starts: a finished, reviewed, published piece, not “I worked on it”.
- Review progress against goals every week or two, not activity.
If a person delivers what was agreed, to the agreed standard, on time, it does not matter whether they worked nine to five or split their day around school pick-up. If they do not, you have a concrete conversation to have, which is far easier than a vague worry about whether they are working hard enough.
3. Decide which tool is for what
Remote teams drown when the same kind of message can arrive anywhere: a task in chat, a decision in an email thread, feedback in a document comment, a deadline in someone's head. Pick one home for each kind of information and write it in the working agreement:
| Kind of information | Where it lives | Why |
|---|---|---|
| Tasks, owners and due dates | Your project management tool | So everyone can see who is doing what, and nothing depends on memory |
| Discussion about a specific task | Comments on that task | So the history stays with the work, not lost in a chat feed |
| Quick questions and team conversation | Team chat, in channels by topic or project | Fast, searchable, and visible to the people who need it |
| Decisions and how-to knowledge | A shared document or team wiki | So new people can find out why things are the way they are |
| Files and assets | Shared file storage, linked from the task | One latest version, not five attachments |
| Urgent problems | A phone call or a named urgent channel | So urgent really means urgent |
| Messages to clients and outside people | Email, or guest access to the project | Clear records, and clients see only what they should |
The exact choice matters less than everyone following it. When someone puts information in the wrong place, move it gently (“let's put this on the task so we don't lose it”) rather than answering it where it landed.
4. Default to asynchronous communication
Asynchronous (async) communication means messages people can read and answer in their own time: written updates, task comments, documents, recorded walkthroughs. Synchronous communication happens live: calls, meetings, instant back-and-forth. Remote teams work best when async is the default and live time is saved for what really needs it.
| Use async for | Use a live call for |
|---|---|
| Status updates and progress reports | Sensitive conversations: feedback, performance, personal matters |
| Sharing information and decisions already made | Complex problems with lots of unknowns |
| Feedback on a draft or design | Brainstorming and early creative work |
| Questions that are not blocking anyone today | Conflicts or misunderstandings that writing has made worse |
| Planning documents that need careful thought | Building relationships, especially with new people |
Good async messages take a little more effort to write, and save everyone time to read. A useful structure is context, request, deadline: what this is about and why it matters, exactly what you need from the reader, and by when. “Can we chat?” with no context is the opposite: it interrupts someone and tells them nothing.
Async does not mean slow. With agreed response times, most questions are still answered within a few hours, and people get long, uninterrupted stretches for focused work, which is one of the main advantages remote work has over the office.
5. Run fewer, better meetings
Remote teams often replace every corridor conversation with a meeting and end up with a calendar full of video calls. Keep a small set of regular meetings with a clear purpose each, and cancel any that no longer earn their time. Every meeting should have:
- An agenda shared in advance, so people can prepare or decide they are not needed.
- An owner who runs it and keeps time.
- Written notes with decisions and actions, posted where the team keeps decisions, so people who could not attend are not left behind.
- Actions turned into tasks with an owner and a due date, not left in the notes.
- One person, one screen in hybrid meetings: if anyone joins remotely, everyone joins from their own laptop, so remote people are not watching a room.
There is a suggested meeting rhythm further down.
6. Make all work visible in one place
The quickest way to lower stress on a remote team, for the manager and for everyone else, is a shared place where every piece of work is visible: what is being done, by whom, by when, and what is stuck. When work is visible:
- You do not need to ask “where are we with this?”, because the answer is already there.
- People can see when a colleague is overloaded and offer help.
- Blockers show up early, while there is still time to fix them.
- Status meetings get shorter, or disappear.
Use a project management tool with boards or lists, owners, due dates and statuses, and agree a few habits: every piece of work is a task, every task has one owner and a due date, status is updated when it changes (not only before a meeting), and anything blocked is marked as blocked with a comment saying why.
7. Hold regular one-to-ones
One-to-ones matter more remotely than in an office, because they are often the only time a person talks to their manager about anything other than tasks. Hold them every week or every two weeks, for 30 minutes, on video if possible, and treat them as the employee's meeting, not a status update.
A simple agenda that works:
- How are you doing? Really ask, and listen. Remote isolation and overwork are easy to miss.
- What is on your mind? Anything they want to raise first.
- Blockers: anything slowing them down that you can remove.
- Feedback both ways: one thing that went well, one thing to try differently, and what you could do better as their manager.
- Growth: progress towards a skill or goal they care about (every few sessions, not every time).
- Actions: what each of you will do before next time.
Keep a shared running document of notes for each person, so nothing is forgotten between sessions. Do not cancel one-to-ones when you are busy: to a remote employee, a cancelled one-to-one sounds like “you are not a priority”.
8. Give feedback and recognition more often
In an office, a lot of feedback happens in passing: a nod in a meeting, a quick “nice work” at someone's desk. Remotely, people can go weeks without hearing how they are doing, and silence is easily read as disapproval.
- Give specific praise in public: “The way you rewrote the onboarding emails cut the questions we get in half” beats “great job”. A team channel for thanks makes good work visible.
- Give corrective feedback in private, and soon: on a call, not in writing, while the details are fresh.
- Be clear in writing: text loses tone, so be more explicit and warmer than feels necessary.
- Run regular reviews: short quarterly check-ins are easier than one big annual review. Our performance review template is a good starting point.
9. Onboard remote hires deliberately
A new person in an office learns by watching. A new remote hire can sit alone with a laptop and no idea who to ask. Plan their first weeks in detail:
| When | What to do |
|---|---|
| Before day one | Send equipment and accounts; share the working agreement; assign a buddy who is not their manager |
| Day one | A welcome call with the team, a one-to-one with the manager, a tour of the tools and where information lives |
| Week one | A short list of small, real tasks with clear owners; 20-minute introductions with the people they will work with most |
| Weeks two to four | Gradually larger work; daily or every-other-day check-ins with the buddy; weekly one-to-ones |
| End of month one | A review of how it is going, in both directions; agree goals for the next two months |
| End of month three | A fuller review; ask what was confusing so the next person has an easier start |
Keep the onboarding checklist as a reusable project or task template, so every new hire gets the same good start and you do not rebuild it each time.
10. Build trust and connection on purpose
Trust in remote teams comes from two things: reliability (people do what they say, when they say) and familiarity (people know each other as humans, not just names in a chat). Clear goals and visible work take care of the first. The second needs a little deliberate effort:
- A few minutes of non-work talk at the start of team meetings.
- Random pairings for a short informal call every week or two, across teams.
- A social channel for photos, pets, hobbies and wins outside work, and a channel for thanking each other.
- Occasional in-person time if the budget allows: even once or twice a year makes the rest of the year's remote work easier.
- Assume good intent in writing: a short reply is usually a busy person, not an angry one. Managers set the tone by doing this first.
For dozens of ideas, see our list of team building activities for work, which has a section for virtual and remote teams.
11. Watch workload and protect wellbeing
Remote work makes it easier to overwork, not harder. The laptop is always there, notifications follow people into the evening, and nobody sees someone working at eleven at night. Managers need to look for overload actively:
- Check workload, not just deadlines: look at how much each person has on this week and next, and rebalance before someone is underwater.
- Model good habits: do not send messages late at night (schedule them for the morning), take your holidays, and log off visibly.
- Agree notification rules: for example, nobody is expected to answer outside their working hours unless something is marked urgent.
- Watch for warning signs: slower replies, missed deadlines from a usually reliable person, cameras always off when they used to be on, short or flat messages. Ask privately and kindly.
- Respect focus time: encourage people to block time for deep work and to mute chat during it.
12. Measure what matters and keep improving
Review how the team is working, not just what it delivers. Every month or quarter, run a short retrospective: what is working, what is not, and one or two things to change. Look at a few simple signals over time, such as work finished on time, how long work waits for review, and how people answer a quick anonymous pulse survey (“How manageable was your workload this month?”). Then update the working agreement. A remote team's way of working is never finished; it should improve a little every quarter.
Managing a remote team across time zones
Time zones are the hardest part of managing a distributed team, because they limit how much live time you can have. A few rules make them manageable:
- Know everyone's hours. Put each person's time zone and normal working hours in the working agreement and in their profile.
- Find and protect the overlap. Identify the hours when everyone (or most people) are online and use them for the meetings that must be live. Keep them short.
- Rotate inconvenient meeting times. If someone always has to join at 7 a.m. or 9 p.m., share the pain by rotating the time.
- Write everything down. Decisions made on a call must be posted in writing for the people who were asleep.
- Plan hand-offs. When work passes between time zones, the person finishing their day leaves a short note on the task: what was done, what is next, and any open questions.
- Write dates and times clearly. Say “Thursday 3 p.m. UK time (10 a.m. New York)” rather than “tomorrow afternoon”, and use due dates on tasks.
- Allow a full working day for replies across large gaps, and plan deadlines around it.
Here is an example of finding an overlap for a team spread across three time zones:
| Team member | Location | Working hours (local) | The same hours in UTC |
|---|---|---|---|
| Ana | New York (UTC−5 in winter) | 9 a.m. – 5 p.m. | 14:00 – 22:00 |
| Ben | London (UTC+0 in winter) | 9 a.m. – 5 p.m. | 09:00 – 17:00 |
| Chloe | Berlin (UTC+1 in winter) | 9 a.m. – 5 p.m. | 08:00 – 16:00 |
| Overlap for all three | 14:00 – 16:00 UTC (9–11 a.m. in New York, 2–4 p.m. in London, 3–5 p.m. in Berlin) |
That two-hour window is where this team's stand-up or weekly meeting belongs. Everything else happens asynchronously. Remember that daylight saving changes on different dates in different countries, so check the overlap again in March, April, October and November.
Remote team meetings: what to run and how often
This rhythm suits most remote teams of three to fifteen people. Adjust it to your size and how fast your work moves, and replace any meeting with a written update where you can.
| Meeting | How often | Length | Purpose | Can it be async? |
|---|---|---|---|---|
| Daily check-in | Daily or 3 times a week | 10–15 min | What I did, what I am doing, what is blocking me | Yes, often better as a written check-in |
| Weekly team meeting | Weekly | 30–45 min | Priorities for the week, decisions, blockers, a few minutes of social time | Partly: share updates in writing beforehand, use the call for decisions |
| One-to-ones | Weekly or every 2 weeks | 30 min | Wellbeing, blockers, feedback, growth | No |
| Project status update | Weekly | — | Is each project on track, at risk or off track, and why | Yes, a short written update |
| Retrospective | Monthly or each quarter | 45–60 min | How we work: what to keep, stop and start | Collect ideas in writing first, discuss live |
| Planning | Monthly or each quarter | 60–90 min | Goals and priorities for the next period | Prepare in writing, decide live |
| All-hands or company update | Monthly | 30–45 min | Company news, wins, questions for leaders | Record it for other time zones |
| Social time | Every 1–2 weeks | 15–30 min | Get to know each other | Partly: a social channel helps |
How to measure remote team performance without micromanaging
Measuring a remote team is about results and the flow of work, not about watching people. Tools that track keystrokes, take screenshots or score “active time” tend to destroy trust, push people to perform busyness rather than do good work, and in some places raise legal and privacy questions. Measure these instead:
| What to measure | How | What it tells you |
|---|---|---|
| Goals met | Progress against the quarter's goals | Whether the team is achieving what matters |
| Work finished on time | Share of tasks done by their due date | Whether plans are realistic and work is flowing |
| Work that waits | How long tasks sit in review, or blocked | Where hand-offs and approvals slow things down |
| Workload balance | Open work and estimated hours per person, per week | Who is overloaded and who has room |
| Estimates against actual time | Time logged on tasks compared with their estimates | How accurate your planning is (useful for the team, not for judging individuals) |
| Quality | Rework, bugs, client changes, customer satisfaction | Whether speed is costing quality |
| How people feel | A short anonymous pulse survey each month | Early warning of overload, confusion or isolation |
Look at trends over weeks and months, not single days, and use the numbers to start conversations (“reviews are taking three days; what is getting in the way?”), never as a scoreboard.
Templates for managing a remote team
Copy these into your chat, documents or project tool and adapt them.
Written daily check-in
Post in the team channel at the start of each person's day:
- Yesterday: what I finished.
- Today: what I plan to finish.
- Blockers: anything I need from someone, with their name.
- Away: any time I will be offline today.
Weekly project status update
- Status: On track, At risk or Off track.
- What was done this week: two to five lines.
- What is next: the most important work for next week.
- Risks and decisions needed: anything that could slip, and who needs to decide what, by when.
Async request
- Context: what this is about, with a link to the task or document.
- Request: exactly what you need (a decision, a review, an answer).
- Deadline: when you need it by, and why.
Hand-off note between time zones
- Done today: what I finished and where it is.
- Next step: what should happen next, and who is doing it.
- Open questions: anything unresolved.
- Back online: when I will be working again.
Common mistakes when managing a remote team
- Managing by presence. Judging people by how quickly they reply or how often their status is green, instead of by what they deliver.
- Too many meetings. Replacing every corridor chat with a call, until nobody has time to do the work.
- Information in too many places. Tasks in chat, decisions in email, files in attachments: people waste hours looking and still work from old information.
- Decisions made in private. A quick call between two people that changes the plan, with nobody else told. Always post the outcome.
- Unclear ownership. “The team” is responsible, so nobody is. Every task needs one named owner.
- Cancelling one-to-ones. It is the first thing to go when you are busy, and the most noticed by remote staff.
- Ignoring time zones. Always scheduling at the times that suit the manager or head office.
- Treating hybrid people unequally. The people in the office get the decisions, the promotions and the context; the remote people get the leftovers.
- Surveillance software. Monitoring tools signal distrust and measure the wrong thing.
- Forgetting the social side. A team that only ever talks about tasks stops being a team.
Tools for managing a remote team
A remote team needs tools for a handful of jobs. You can use one tool for each, or a suite that covers several, which means fewer logins and less copying information between apps.
| Job | What to look for |
|---|---|
| Project and task management | Boards, lists and a calendar; owners, due dates and statuses; comments and @mentions on tasks; templates; workload views |
| Team chat | Channels by team or project, direct and group messages, threads, search, file sharing and notification controls |
| Video calls | Reliable calls with screen sharing and recording for other time zones |
| Documents and a team wiki | Shared editing, comments and suggestions, and a structured place for how-to knowledge and decisions |
| File storage | One shared place for files with permissions and sharing links, linked to the work |
| Calendar | Shared calendars that show time zones and connect to your other tools |
| Time and workload | Time tracking on tasks, timesheets, and a view of how much each person has on |
| Goals and reporting | Goals linked to projects, project status updates and dashboards |
Whichever tools you choose, choose fewer than you think you need, decide what each is for, and write it in the working agreement. For a wider comparison of project tools, see our guide to the best project management software.
How Coavon helps you manage a remote team
Coavon puts most of the tools above on one account, so a remote team has one place to plan, talk and keep its work. Here is what it covers today:
- The work: Flow shows projects as boards, lists, a calendar and (from Pro) a Gantt chart, with owners, due dates, statuses, comments, @mentions, followers and approvals on every task.
- Workload and time: a Workload page showing how much each person has on, week by week, against their weekly hours; time tracking on tasks; and a Timesheets page with estimates compared with actual time.
- Status and goals: project status updates with weekly reminders from Pro, dashboards from Pro, and goals and portfolios on Business.
- Conversation: Chat has channels for teams and projects, direct and group messages, threads, reactions, file sharing, and a choice per conversation of every message, only @mentions or muted.
- Docs, Drive and a team wiki: write together in Docs with comments and suggested edits, keep files in Drive, and from Pro keep a team wiki (the Library) in Flow for your working agreement and how-to pages.
- Calendar: events with guests and repeats, Flow tasks shown on the calendar, and events copied to Google Calendar.
- Free guests for clients and freelancers, who see only the projects they are invited to.
Coavon does not include video calls yet, so pair it with the video tool you already use. It also has no phone apps yet; it works in the browser on any device. See pricing for what each plan includes, or try Flow in your browser without signing up.
Remote team management checklist
Use this to check your setup, or as a plan for your first month managing a remote team:
| Area | Done when |
|---|---|
| Working agreement | A written page covering hours, time zones, response times, tools, meetings and decisions, agreed with the team |
| Goals | Three to five team goals for the quarter, each with a measurable result and an owner |
| Visible work | All work in one project tool; every task has one owner, a due date and a status |
| Tools | One agreed home for tasks, discussion, documents, files and urgent issues |
| Async habits | Written check-ins or updates; requests use context, request and deadline |
| Meetings | A short list of regular meetings, each with an owner, agenda and written notes |
| Time zones | Everyone's hours known; the overlap protected; hand-off notes on tasks |
| One-to-ones | Weekly or fortnightly with every person, with a shared notes document |
| Feedback | Public, specific recognition; private, prompt corrective feedback; quarterly reviews |
| Onboarding | A reusable first-month plan with a buddy and early, small tasks |
| Connection | Regular informal time, a social channel, and in-person time if possible |
| Workload | Workload checked every week; notification and working-hours rules agreed |
| Improvement | A retrospective every month or quarter, and the working agreement updated |
Frequently asked questions
How do you manage a remote team effectively?
Write down how the team works, set clear goals and judge results rather than hours online, decide which tool is for what, default to written and asynchronous communication, keep a few well-run meetings, make all work visible in one shared project tool, hold regular one-to-ones, give frequent feedback, and look after workload and connection on purpose.
What are the biggest challenges of managing a remote team?
The most common challenges are communication gaps (people miss decisions and context), hidden workload and blockers, time zone differences, isolation and weaker trust, unclear ownership, too many meetings, and overwork because the laptop is always there. Each one has a deliberate fix: written decisions, a shared project tool, protected overlap hours, informal time, named owners, fewer meetings and agreed working hours.
How often should you meet with a remote team?
Most remote teams do well with a short daily or thrice-weekly check-in (often written), a weekly team meeting of 30 to 45 minutes, one-to-ones every week or two, and a monthly or quarterly retrospective and planning session. Replace any meeting with a written update when the meeting is only sharing information.
How do you keep a remote team engaged?
Give people clear goals and real ownership, recognize good work specifically and publicly, hold regular one-to-ones that focus on the person, make time for informal conversation, involve the team in decisions about how it works, and protect their time and wellbeing. Engagement comes from meaningful work and good relationships, not from more meetings.
How do you track a remote team's productivity without micromanaging?
Measure outcomes and the flow of work rather than activity: goals met, work finished on time, how long work waits for review, workload balance and quality. Keep all work visible in a shared project tool so progress is clear without asking, and avoid surveillance software that tracks keystrokes or screenshots, which damages trust.
How do you manage a remote team across different time zones?
Record everyone's working hours, find the hours when most people overlap and use them only for meetings that must be live, rotate inconvenient meeting times, write down every decision, leave hand-off notes on tasks at the end of the day, and always state dates and times with a time zone.
What tools do you need to manage a remote team?
Most remote teams need a project management tool, team chat, video calls, shared documents or a wiki, file storage, a shared calendar, and a way to see workload and time. Using fewer tools, or one suite that covers several jobs, reduces confusion. Coavon covers projects, chat, documents, files, a wiki and calendar on one account; pair it with a video tool.
What is the difference between managing a remote team and a hybrid team?
A remote team works away from an office all the time, so the main task is building communication and connection that would otherwise not happen. A hybrid team mixes office and remote work, so the main task is fairness: making sure decisions, information and opportunities reach remote people as well as those in the room, for example by having everyone join meetings from their own screen.
How do you build trust in a remote team?
Trust comes from reliability and familiarity. Build reliability with clear goals, named owners and visible work, so people can see each other deliver. Build familiarity with informal conversations, random pairings, a social channel and occasional in-person time. Managers help most by assuming good intent and by keeping their own promises.
What should a remote team working agreement include?
Each person's working hours and time zone, the team's overlap hours, expected response times, which tool is used for what, the regular meetings and their rules, how decisions are made and recorded, how to show time off, and camera and call etiquette. Keep it to a page or two and review it every few months.