A remote 1:1 is a structured recurring conversation between a manager and a direct report who are not in the same location, often with limited timezone overlap, conducted over video or async tools.
The in-office model assumes you can read body language, that side conversations happen naturally between meetings, and that context accumulates through proximity. None of those hold remotely. Remote 1:1s need a more explicit structure: a shared agenda built before the call, a written record updated after, and a cadence shorter but more frequent than most managers default to.
Key takeaways
- Shorter and more frequent beats long and monthly. Thirty minutes weekly outperforms 60 minutes biweekly for distributed teams.
- Build the agenda together in a shared doc before the call, not during it.
- Leave 10 minutes at the end for open discussion. The agenda items are not the whole meeting.
- When timezone overlap is limited, protect the 1:1 slot above everything else. It is the hardest meeting to reschedule.
Why it matters
Remote reports lose the ambient information that office workers take for granted. They do not know what conversations are happening around you, what mood the organization is in, or whether the product direction is shifting. Your 1:1 is often the primary channel through which they get that context. If you run the 1:1 purely as a status update on their work, you are wasting the channel that matters most.
Timezone constraints make the 1:1 structural rather than optional. If you have a two-hour overlap with a report and you do not use it for a regular 1:1, your conversations happen on an ad hoc basis at inconvenient times. The cadence decays. Issues surface late.
The written record of a remote 1:1 matters more than it does in-office because it is the only record. In an office, you can follow up in the corridor. Remotely, if the conversation is not documented and acted on, it did not happen.
How it works in practice
A format for a 30-minute remote 1:1 with a shared agenda doc
-
Set up a shared running notes doc before the first meeting
Each week, both parties add items to the doc before the meeting. The doc stays open during the call. After the call, decisions, commitments, and follow-ups are written there. Neither party should be scrambling to recall what was said.
-
Open every call with a two-minute calibration question
Ask: 'What is your energy level this week?' or 'What has been taking more time than you expected?' This is not small talk. It is calibration. Remote reports carry context you cannot see. The first two minutes surface it.
-
Cover their items first, not yours
The 1:1 is primarily their time. Your items are context and direction, not the agenda. If you are running out of time, your items can move to async. Theirs cannot.
-
Address blockers explicitly
Ask: 'Is there anything you need from me to move forward that you do not have yet?' If the answer is yes, write it in the doc with a due date. A remote blocker that is not written down will still be a blocker at the next 1:1.
-
End with a forward look
Ask: 'What are you planning to be done with by the next time we talk?' Write the answer in the doc. Start the next 1:1 by reviewing it. This creates continuity across the calls and a lightweight accountability structure that does not require a separate tracking system.
Common mistakes
Treating it as a status update
Status can go in a written update. The 1:1 is for the things that do not fit in a written update: concerns, context, friction, and growth.
Skipping it when you are busy
The times you are most tempted to skip a 1:1 are the times the report most needs it. Organizational busyness and churn are exactly when remote reports need anchoring.
Running it with no agenda doc
A spoken conversation without a shared record produces good intentions with no follow-through. The notes doc is not optional for remote 1:1s.
Defaulting to camera-off as the norm
Camera-off 1:1s over time create distance. If your report routinely declines video, that is worth addressing directly as a pattern rather than accommodating silently.
What it sounds like
Daniel and Merav are in a weekly 1:1. Merav is based in a timezone with a two-hour overlap.
Daniel: “I can see from the doc you added an item about the API review process. Can you walk me through what is not working?”
Merav: “The reviews are taking four to five days and I am blocked waiting for them. I only have two hours of overlap a day, so I cannot chase it in real time.”
Daniel: “I will move the API review SLA up in the backlog. Let me own getting that to 48 hours. I will update the doc with the target so we can track it together.”
Questions managers actually ask
What if my report is in a timezone with no overlap at all?
Move the 1:1 to an async format: they send a written update or a short recorded video 24 hours before the slot, you respond in writing or a short recording, and you have a live call once a month for the things that need real-time conversation.
How do I build trust without in-person interaction?
Trust is built through consistency: you show up for the 1:1, you follow through on what you said you would do, and you give honest feedback even when it is uncomfortable. One in-person meeting a quarter, if budget allows, accelerates this significantly.
How do I tell if a remote report is disengaged?
The signal is the agenda doc. If they stop adding items, they have either stopped investing in the relationship or have nothing to say because nothing is happening. Ask directly: 'I noticed you did not have items this week. Is everything fine or is something getting in the way?'
Should I share my own agenda items before the meeting too?
Yes. Anything you plan to bring up should be in the shared doc before the call. It lets them prepare and signals that the meeting is collaborative, not a debrief.
How do I handle a 1:1 where someone clearly wants to talk but cannot say what is wrong?
Ask: 'Is there anything going on at work or outside it that is affecting your focus right now? You do not have to tell me everything, but I want to make sure I am not missing something.' Then be quiet.
What tool should I use for the shared agenda doc?
Whatever you both already use. Notion, Google Docs, or even a shared Slack thread. The format matters less than the habit of adding to it before every meeting and keeping the record after.
See how Leap improves execution in your meetings
Leap sits in your meetings, captures decisions and owners in real time, and shows you where execution breaks down before the week is out.