Your remote report shouldn't have to wait for the next 1:1 to get help
When the 1:1 is a remote report's only contact, blockers wait and the meeting turns into status. Agree where urgent questions go in between.

If your weekly 1:1 is the only reliable time your remote report talks to you, two things go wrong. Questions that block today's work wait for days, and the meeting fills up with status. Agree a route for blocking questions, using channels your team already has, and keep the 1:1 for what needs a real conversation.
What it looks like from the other side
In a February 2025 developer thread, one person wrote: “I'm a solo remote dev across the world. It's the only time I actually talk with someone from the company I work for. It's a weekly status update for my case.”
Another remote developer, u/Stubbby, replied in the same thread on 17 February 2025 that their manager works 60+ hour weeks, and “outside of the 1-on-1 we rarely speak so its 100% status and update.” Reddit sometimes blocks access to the page, so we checked the comment's full text in an archived copy on Arctic Shift.
These are two accounts, not a survey. Larger data points in the same direction, though. In a study of 61,182 Microsoft employees, firm-wide remote work made collaboration networks “more static and siloed, with fewer bridges”, with less real-time conversation and more asynchronous messages. The authors note this may make it harder to get new information.
Some people won't ask anyway. Lighthouse observes that remote employees may hesitate to raise a concern “for fear of their job, or of being imposing.” A route you've agreed in advance removes the guesswork about whether a question is worth interrupting you.
Sort the question before it waits
Ask one thing: if this waits for the next 1:1, does work stop or go in the wrong direction?
- Yes: route it now. A decision only you can make, an approval, missing access, two priorities that conflict this week.
- No: bring it to the 1:1. Career, feedback, a recurring friction with another team, how the role is going.
Agree the route in three answers
Settle these together in your next 1:1:
- Where. Which existing channel a blocking question goes to: a direct message, a team thread, a call. Agree how to mark it, for example a message that starts with “Blocked:”.
- When. The reply time you can actually keep, given your calendar and their time zone. There's no universal number. If you can't answer within their working day, say so.
- Who else. Who can decide when you're unavailable, and on what. A tech lead may settle technical scope while deadlines still wait for you.
An invented example of the written result:
Blocking questions: a direct message that starts with “Blocked:”. I answer within four of my working hours.
If I'm off: Maya decides technical scope. Dates wait for me.
At each 1:1: what got blocked, and did this route work?
Give the 1:1 its own job back
Once blockers have a route, the meeting no longer has to carry them. Start with the third line: what got stuck since last time, and why? A one-off is solved. A pattern, such as access that keeps missing or decisions that keep waiting on another team, is a 1:1 topic.
That's where a written record helps. 1on1 brings the agenda, written conversation record, action items and prior-session context into one workflow for a manager and direct report, and carries action items and written context into the next conversation. The question you fixed by message on Tuesday can return as an action or a topic, instead of being forgotten.
1on1 is built for the recurring conversation, not as a chat or on-call channel. Keep the urgent route in the tools your team uses every day.
At your next 1:1, agree the three answers and write them down. See how 1on1 carries the written record from one 1:1 to the next.
Next step
Test it with one manager and one direct report
Start free and keep this article context through the registration step.
Start free