Free template
Remote 1:1 Meeting Template
When you and your teammate work in the same room, a lot of the 1:1 happens before the meeting even starts. You read the body language, overhear the frustrated sigh, catch the quick “hey, got a sec?” on the way to coffee. Remote, all of that is gone, and the check-in has to do the work that proximity used to do for free.
So a remote 1:1 needs more intentional structure than an in-person one, not less. This is a copy-paste template built for distributed teams: async prep that travels ahead of the call, a few minutes of real connection, and a deliberate pass at the blockers and context you would never notice from a different time zone.
The template (copy this)
Remote 1:1: [Your name] & [Teammate name] Date: __________ | Time zone: __________ | Cadence: Weekly / Biweekly Submitted async, before the call: - How I'm doing (1 line): - Wins since last time: - Where I'm blocked or stuck: - Decisions I need from you: - Anything I'd flag that you might not see remotely: On the call: 1. Connect, camera on (5 min) - How are you really doing this week? 2. Their agenda from the async prep (12 min) - Walk through wins, blockers, decisions, questions. 3. Context & feedback (5 min) - Decisions and updates you might have missed: - Feedback (something that went well + one thing to adjust): 4. Career & growth (5 min) - What you're working toward + one step this month: 5. Follow-ups & close (3 min) - Action items (who / what / by when): - One thing to revisit next time:
Paste it into a shared doc and split it the way it’s written: your teammate fills the async section a day before the call, and you both spend the live time on the conversation. If you want the in-person version to adapt, start from the standard 1:1 agenda template.
A filled-in example
Here’s what it looks like once it’s real, between a manager in London and a teammate in New York. Notice how much got decided because the prep landed before the call: the blocker, the launch-date question, and the quiet flag about the new contractor were all there to talk about, not discovered live.
Remote 1:1: Priya & Marcus Date: Jun 9 | Time zone: Marcus is GMT+1, Priya is GMT-5 | Cadence: Weekly Submitted async, before the call: - How I'm doing: solid week, a little stretched on the migration. - Wins: shipped the export fix, unblocked the data team. - Blocked: waiting on design sign-off for the settings redesign, 3 days now. - Decisions I need: can we push the launch a week, or cut the second screen? - Flag: the new contractor seems lost in standup but won't say so on camera. On the call: 1. Connect: Marcus is heads-down before a long weekend, wants to wrap early. 2. Their agenda: agreed to cut the second screen and keep the date. Priya to nudge design directly instead of waiting. 3. Context: leadership moved the OKR review to next Thursday; Marcus pairs the contractor with him for an hour Friday. 4. Growth: Marcus wants more architecture ownership; first step is to draft the migration plan and review it next 1:1. 5. Follow-ups: - Priya: ping design lead today re: settings sign-off. - Marcus: pair with contractor Fri, share migration draft by next 1:1. - Revisit: did cutting the second screen actually unblock the date?
What makes a remote 1:1 work
Async prep, submitted ahead of time
The single biggest upgrade for remote teams. When the wins, blockers, and decisions arrive before the call, you stop spending live minutes on status and start spending them on the parts that need a real conversation. It also gives quieter teammates a way to raise something hard in writing first.
A few minutes of genuine, camera-on connection
Open with how they're really doing, cameras on, no agenda yet. This is the small talk you'd have had at a desk, and remotely it's the only reliable place to notice that someone sounds flat or worn down before it shows up in their work.
Deliberately surface the invisible blockers
In an office, you overhear the thing someone's stuck on. Remote, you have to ask for it on purpose. Keep a line in the prep for "anything I'd flag that you might not see," because the problems that stay hidden remotely are exactly the ones that grow.
Over-communicate context and decisions
People who aren't in the room miss the hallway version of every decision. Spend a few minutes each check-in catching them up on what changed, what got decided, and why. Assume they have less context than you think, and you'll usually be right.
Be fair across time zones
If your team spans zones, don't always make the same person take the early or late call. Rotate the inconvenient slot, keep the cadence predictable, and write down enough that a teammate three zones away never feels like decisions happened while they were asleep.
Write down every follow-up
Remote work runs on the written record. A follow-up that nobody wrote down is a follow-up that dies between calls. Capture who does what by when, and carry the open ones forward so nothing quietly slips when you're not sharing a room.
None of this is exotic, it’s the basics done more deliberately. For the full walkthrough of the conversation itself, read how to run a 1:1.
Remote 1:1 FAQ
How is a remote 1:1 different from an in-person one?
The structure is the same, but remote check-ins need more of it. In person you pick up tone, hesitation, and side conversations for free. Remote, you have to ask for those things on purpose: surface blockers people would have mentioned at a desk, over-communicate context, and write down every follow-up so nothing gets lost between calls.
Should remote 1:1s be async or live?
Both, in that order. Async prep submitted before the call does the status reporting, so the live time is spent on the conversation that actually needs two people: blockers, decisions, growth, and how someone is really doing. A live call with no prep usually becomes a verbal status update, which is the one thing remote 1:1s should not be.
How often should remote teams hold 1:1s?
Weekly is a safe default for remote and distributed teams, more often than you might run them in an office. When you are not co-located, a week is a long time for a small problem to grow quietly, and the regular cadence is what keeps you from only talking when something is already wrong.
How do I stay connected to a remote teammate without micromanaging?
Connection comes from consistency and genuine interest, not from checking up. Keep the cadence, start with a real personal check-in, and let their async agenda drive the call. Track follow-ups instead of asking for status, so the conversation stays about them and their work rather than your need to monitor it.
Built for teams that don't share a room
A doc gets you started. A shared workspace fits remote work better: your teammate adds their prep before the call, follow-ups carry forward on their own, and every past check-in stays put so nobody loses the thread across time zones.
That’s MeetFika. Free to start.