A 1:1 template for distributed teams is the structure of the agenda that makes a recurring manager-report meeting useful in a timezone-mismatched pair. The classic 1:1 advice — let the report drive the agenda, don't make it a status update — was written for co-located teams who see each other in the office. Distributed pairs need more structure because the conversation has to do more work in a shorter, sometimes inconvenient slot.
The template below is the version that consistently works. It is async-friendly: most of it is filled in before the synchronous slot, and the synchronous time is reserved for the topics that genuinely need real-time discussion. The format scales from weekly to biweekly without changing.
When to use it
- Manager-and-report pairs across two or more time zones.
- Pairs where the 1:1 has become a status update.
- Pairs where the report consistently has nothing to discuss.
- New manager-report relationships, where structure helps build the trust.
The template structure
This is the structure of the template. Copy it into a Notion page, a Linear doc, or a markdown file in your repo — it works in any of them.
1:1 — [report] and [manager]
Cadence: [weekly / biweekly] Next: [date]
BEFORE THE MEETING (REPORT FILLS IN)
Posted by: [N hours before the meeting]
WINS / WHAT I SHIPPED
- [...]
- [...]
WHAT IS HARD
- [topic, with as much or as little detail as you want]
- [topic]
THINGS I WANT YOUR INPUT ON
- [topic]
- [topic]
THINGS YOU SHOULD KNOW (FYI, NO ACTION NEEDED)
- [...]
GROWTH / CAREER
Touched on this week? [yes/no]
Topic to discuss (any cadence): [...]
AGENDA REQUESTS FROM MANAGER (manager fills in here)
- [topic]
- [topic]
DURING THE MEETING
Walk through the agenda in order. Stop the status portion early
if there's nothing live to discuss. Use the time saved for growth,
career, or harder questions.
AFTER THE MEETING
Action items, owner, date.
[ ] [action] — [owner] — [date]
[ ] [action] — [owner] — [date]
Manager notes (private, manager-only).
- [...]
CADENCE QUESTIONS (REVISIT QUARTERLY)
- Is the current cadence right?
- Are we using the slot well, or has it become status?
- Is this slot the right time of day for both of us?
ASYNC FALLBACK
If a meeting needs to be skipped, the report still posts the
"before" section. The manager replies in writing. The next live
slot picks up only what could not be handled in writing.
Governance, not a status channel
StandIn is async governance infrastructure. Engineers declare working state before they go offline. Representatives answer from the record, cite the source, and refuse when the answer is not there.
Request access →How to use it well
- The report fills in the agenda — not the manager. 1:1s are the report's meeting. The manager only adds to the "agenda requests from manager" section. This rule alone fixes most 1:1 failure modes.
- The "what is hard" section is the most important. Wins are easy to share. Hard things are the reason the 1:1 exists. A 1:1 where this section is empty for three weeks in a row is a 1:1 where the trust has eroded.
- Skip the meeting some weeks — but keep the written section. If both of you are heads-down and there is nothing live to discuss, skip the synchronous slot. The written section still gets filled in. The cadence is the conversation, not the calendar.
- Career touched on regularly, not just at review time. The quarterly "let's talk about growth" 1:1 is a dishonest convention; growth conversations are best in small doses, often. The "touched on this week" prompt makes it easy to surface a quick item.
- Revisit cadence quarterly. The right 1:1 cadence depends on what the report is working on and where the relationship is. A quarterly check ("is this slot working?") is enough to keep it tuned.
What to skip
Skip the "status update" portion entirely if the team has good async wraps or a status tool. The 1:1 is too expensive a slot to spend on what the manager could read elsewhere. Use it for the topics that need conversation.
Skip making it a fixed agenda. The template is a scaffold. Some weeks the entire 1:1 is one topic; some weeks it's six small items. Forcing every section to be filled in produces ceremony, not conversation.
Frequently asked questions
Is this template free?
Yes. The structure above is the template. Use it as a Notion page per pair, or a recurring Google Doc — whichever the pair already keeps.
Can I edit it?
Yes. Most edits are about cadence and the specific wording of the prompts. The pre-fill-then-meet pattern is the part that matters.
Do I need to give my email?
Not for the template. The download is just a formatted Notion version; the email is for our newsletter only.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.