How to manage remote employees: a practical operating manual

Managing someone remotely is the same job as managing them in an office, with the safety net taken away. In an office you can get away with vague expectations, because people pick up the real ones by watching. You notice someone looks stressed. A quick chat by the kettle fixes a misunderstanding before it turns into a week of wasted work.

Remote, all of that has to be done on purpose. The upside is that the things you’re forced to make explicit (what good work looks like, when people are expected to be around, how decisions get recorded) make you a better manager wherever your team sits.

This manual is written for team leads and managers of remote or mostly remote employees. It’s organised around the work, in roughly the order you’d set it up.

Why the manager matters more remotely

Gallup estimates that managers account for at least 70% of the variance in employee engagement scores across business units. That figure isn’t specific to remote work, but distance amplifies it. A remote employee’s experience of the company is mostly their manager, their immediate team and the tools. If the manager is disorganised, the job feels disorganised, and there’s no office buzz to compensate.

So the work below isn’t overhead. For a remote employee, it is the workplace.

Step 1: Write down what the job actually is

Start with a one-page role sheet for each person. Not the job advert: a working document you both agree on and revisit each quarter.

It should answer five things:

1. Outcomes. Three to five results the role exists to produce, phrased so you could tell at the end of a quarter whether they happened. “Support tickets in the billing queue answered within one working day” is an outcome. “Help customers” is not.
2. Decisions they own. What can they decide without asking? Where do they need to consult, and where do they need sign-off? Remote employees who don’t know their decision rights either wait (slow) or guess (risky).
3. Working hours and overlap. Their normal hours, in their own time zone, and the window when they’re expected to be reachable for real-time work.
4. Response times. How fast they should reply to chat, email and direct mentions, and how urgent things reach them.
5. How work is made visible. Where their status lives (project tool, weekly update, shared doc), so nobody needs to ask “what are you working on?”

A role sheet takes an hour to write. It removes most of the low-grade anxiety remote employees describe, which usually comes down to not knowing whether they’re doing enough.

Step 2: Set a weekly operating rhythm

Remote teams need a predictable rhythm, because there’s no physical routine to lean on. A small number of fixed touchpoints beats a calendar full of ad hoc calls.

Two notes on this. First, the written pieces carry more weight than the calls. People in other time zones, people who were off sick and people who join next year can all read a written update. Second, protect the 1:1 above almost everything. Cancelling it repeatedly tells a remote employee they’re low priority more clearly than anything you could say.

If your team is spread across time zones, the daily update should be asynchronous by default. The tools for that are covered in our guide to async communication tools.

Step 3: Make the 1:1 their meeting, not your status check

The most common way remote 1:1s go wrong is that they become a status update the manager could have read in the project tool. Thirty minutes a week, every week, spent recapping tickets.

Move status out of the 1:1 completely. If the daily written update and the project tool are working, you already know the status. Use the time for what text does badly:

• Blockers they haven’t mentioned. “Is anything slower than it should be?” gets a different answer from “Any blockers?”
• How they’re doing. Energy, workload, anything outside work they want you to know about. Ask directly and accept “fine” without pushing.
• Feedback, both ways. One piece of specific feedback from you; an open invitation for theirs.
• Development. What they want to get better at, and whether this month’s work is helping.

Keep a shared running doc for each person, newest date at the top. Either of you adds items during the week. That makes the 1:1 theirs to steer, and gives you both a record when review time comes round.

Step 4: Judge output, and be careful with monitoring

When you can’t see people working, the temptation is to measure activity instead: online status, hours logged, mouse movement. Activity data tells you whether a laptop is awake, not whether the work is good.

Use the outcomes from the role sheet instead. Each month, ask: did the agreed results happen, at the agreed quality? If not, what got in the way? That conversation is harder than glancing at a dashboard, but it’s the one that improves the work.

If your company does use monitoring software, be aware that it carries legal obligations in many places. In the UK, the Information Commissioner’s Office has published guidance on monitoring workers, which expects monitoring to be necessary, proportionate and transparent to the people being monitored, with an impact assessment for higher-risk methods. Check the rules where your employees are based before switching anything on, and tell people plainly what is collected and why.

There’s also a US wage-and-hour angle for non-exempt staff. The Department of Labor’s Field Assistance Bulletin 2023-1 says short breaks of 20 minutes or less count as hours worked whether the employee is at home or in the office, and that work the employer knows or has reason to believe is happening must be counted too. So a manager who quietly expects evening replies from hourly staff is creating paid time, whether or not anyone records it.

Step 5: Write decisions down where people will find them

In an office, a decision made in a corridor reaches most people by lunchtime. Remote, a decision made on a call reaches the people on the call, and everyone else finds out when they do the wrong thing.

Fix this with a habit rather than a tool. Every decision that changes what someone else will do gets a short written record: what was decided, why, who decided, and the date. Post it where the work lives (the project, the ticket, the team’s decision log), not in a private chat. Link to it from your weekly update.

Three side effects make this worth the effort. People in other time zones can disagree in writing before the decision hardens. New joiners can read why things are the way they are instead of asking. And when a decision turns out badly, you can see what you knew at the time, which makes the review about the reasoning rather than about blame.

A simple test for whether something needs a record: if a person who was absent this week would act differently once they knew, write it down.

Step 6: Give feedback that survives the distance

Written feedback loses tone. A comment that would sound neutral across a desk can read as cold in a chat message, and the reader can’t see your face to check.

A few rules make this easier:

• Praise in public, in writing. A specific thank-you in the team channel is visible, permanent and costs nothing. Name what they did and why it mattered.
• Correct on a call, then confirm in writing. Difficult feedback goes on video, where tone carries. Follow with a short written note of what you agreed, so nothing gets lost in translation.
• Be specific and recent. “The client summary on Tuesday missed the pricing change” is usable. “Your summaries need work” isn’t.
• Don’t save it up. Remote managers often hold feedback for the quarterly review because there’s no natural moment. The weekly 1:1 is the natural moment.

Step 7: Spot trouble early

Problems surface more slowly remotely. People who are struggling tend to go quiet rather than ask for help, and quiet is easy to miss when you don’t share a room.

Watch for changes from a person’s normal pattern rather than absolute levels:

None of these is proof of anything. Each is a reason for a conversation.

Step 8: Protect working hours, including yours

Remote work blurs the end of the day. The laptop is always within reach, chat follows you onto your phone, and a manager who replies at 11pm teaches the whole team that 11pm is a working hour.

Set the norm deliberately. Use scheduled send for anything written outside the recipient’s hours. Put your own working hours in your calendar and stick to them visibly. Say out loud, more than once, that evening messages can wait until morning.

Some countries now put this into law. In Australia, for example, the right to disconnect lets employees refuse to monitor, read or respond to out-of-hours contact unless refusing is unreasonable; it has covered small business employers since 26 August 2025, a year after larger ones. Check what applies where your people live.

Step 9: Look after the setup and the person

Two practical things remote managers own that office managers don’t think about.

The workstation. In Great Britain, HSE says employers have the same health and safety duties for home workers as for other workers, including stress and the safe use of computers. A short self-assessment when someone starts, and a budget to fix what it finds, covers most of it. Our remote employee onboarding checklist includes this step.

Visibility for development. Remote employees can lose out to people who are physically closer to decision-makers. Counter it on purpose: send stretch projects round the whole team rather than to whoever happens to be in the room, share credit by name in written updates, and base promotion cases on documented outcomes, which is another reason the role sheet matters.

Questions managers ask

How often should I check in with a remote employee? A weekly 30-minute 1:1 plus a written daily or near-daily update works for most teams. New starters need more in the first few weeks: a short daily check-in that tapers off as they settle.

Should cameras be on? For 1:1s and difficult conversations, cameras help. For large meetings, a camera-optional norm is reasonable. Whatever you choose, write it down so people aren’t guessing.

What if someone just isn’t delivering? Go back to the role sheet. If the outcomes were clear and agreed, have a direct conversation about the gap, agree specific next steps with dates, and record them in writing. If the outcomes weren’t clear, that’s the first fix.

Your remote management manual (copy and adapt)

REMOTE MANAGEMENT MANUAL: [Team name]  (owner: [manager], reviewed quarterly)

ROLE SHEETS
- Every person has a one-page role sheet: outcomes, decision rights,
  working hours + overlap window, response times, where status lives.
- Reviewed together every quarter.

RHYTHM
- Daily: written status update in [channel] by [time, their local time].
- Weekly: 30-min 1:1 per person, shared running doc, newest first.
- Weekly: team sync, agenda posted 24h ahead; notes posted within 24h.
- Weekly: manager's written update (priorities, decisions, changes).
- Quarterly: role sheet + development conversation (60 min).

1:1 RULES
- No status recaps. Status lives in [project tool].
- Agenda belongs to the report; manager adds items too.
- Cover: blockers, wellbeing, feedback both ways, development.
- Do not cancel; move it if you must.

PERFORMANCE
- Judged on role-sheet outcomes, not online status or hours visible.
- Any monitoring tool: legal check first, then tell the team in writing.

FEEDBACK
- Praise: public, written, specific.
- Correction: on video, then a short written follow-up.

HOURS
- Use scheduled send outside the recipient's working hours.
- Urgent = [named route, e.g. phone call]. Everything else waits.

DECISIONS
- Any decision that changes someone else's work gets a written record:
  what, why, who, date. Posted where the work lives; linked weekly.

EARLY WARNING
- Watch for changes from each person's normal pattern.
- Any change = a private conversation, not a conclusion.