Short answer
A one on one meeting template is a shared agenda for a regular private meeting between a manager and one team member. A good remote version runs about 30 minutes and covers a quick check-in, the employee's topics first, blockers, feedback both ways, growth, and agreed next steps, with notes kept in one shared document.
Astrolinks gives each person a daily report written from their own private log. No screenshots. Get it free →
In an office, a lot of management happens by accident: a chat at the coffee machine, a quick question after a meeting, a look at someone's face that says the week is going badly. On a remote team none of that happens unless you plan it. The one on one meeting is where you plan it.
This page gives you a one on one meeting template you can copy into a shared doc, a 30-minute agenda for remote teams, questions to ask, a version for the employee, and how to keep status updates out of the meeting so there's time for what matters.
One on one meeting template (copy and paste)
Create one shared document per person. Add a new block at the top for each meeting, so the history reads from newest to oldest.
1:1: [Manager] and [Team member], [Date]
Check-in (5 min)
- How are you doing, really? (1 to 5, and why)
Your topics (10 to 15 min)
- [Added by the team member during the week]
Blockers (5 min)
- What's slowing you down? What do you need from me?
Feedback (5 min)
- From me: [one specific thing that went well, one thing to change]
- For me: What should I start, stop or keep doing?
Growth (once a month, 10 min)
- [Skill, project or goal they're working toward]
Next steps
Action Owner By when Carried over from last time: [Open actions from the previous meeting]
The order matters. The team member's topics come before the manager's, so the meeting stays theirs.
What is a one on one meeting?
A one on one is a regular, private meeting between a manager and one person on their team. It is not a status meeting and not a performance review. Its job is to keep the working relationship healthy: to hear problems early, remove blockers, give and receive feedback, and talk about where the person wants to go.
For remote teams it matters more, because it's often the only time a manager and an employee talk without other people in the room. Our guide on how to manage remote teams calls it the most important meeting a remote manager has.
How do you run a 30-minute remote one on one?
Here's a simple flow that fits in 30 minutes on a video call.
- Open with a real check-in (5 minutes). Ask how they are and wait for the answer. A quick 1 to 5 score helps people who don't like talking about feelings at work.
- Their topics first (10 to 15 minutes). Work through what they added to the doc. If nothing is there, ask what's on their mind this week.
- Blockers (5 minutes). Ask what's slowing them down and what you can do about it. Write down what you'll do.
- Feedback both ways (5 minutes). Give one specific piece of praise and, if needed, one specific change. Then ask for feedback on yourself.
- Agree next steps (2 minutes). Read the actions back with an owner and a date.
Keep the camera on if you both can, but don't insist. Turn off notifications and don't type other messages during the call. On a remote team, people notice.
Questions to ask in a one on one meeting
Rotate these. Asking the same three every week makes the meeting feel like a form.
Check-in
- What's on your mind this week?
- How's your energy compared to last week?
- How are your working hours? Is anything spilling into your evenings?
Work and blockers
- What's slowing you down right now?
- Is anything unclear about what's expected of you?
- Which meetings could you drop?
Feedback
- What's one thing I could do to make your work easier?
- Is there anything I've done recently that didn't help?
- What should we change about how the team works?
Growth
- What would you like to be doing more of in six months?
- Which skill would you like to build next?
- Is there a project you'd like to be part of?
Remote-specific
- Do you feel connected to the rest of the team?
- Is the time zone overlap working for you?
- Do you have what you need at home to work well?

One on one meeting template for employees
If your manager doesn't run one on ones well, you can bring the structure yourself. Before each meeting, fill in this short prep note in the shared doc:
My prep for [Date]
- Wins since last time: [one or two]
- What I need help with: [blocker, decision, resource]
- A question I have: [about priorities, the team, the company]
- Feedback I'd like: [on a specific piece of work]
- Something I'd like to grow in: [optional]
Managers almost always appreciate a team member who arrives with an agenda. It also makes sure your topics get time before the meeting runs out.
How do you keep status updates out of the one on one?
The most common way one on ones go wrong is that they turn into status meetings. "So what did you work on this week?" fills twenty minutes, and the real topics never come up.
The fix is to move status into writing. When each person sends a short daily or weekly update, the manager already knows what happened before the call starts. The one on one is then free for the things writing does badly: worries, ideas, feedback and careers.
Some options:
- A short end-of-day report with what's finished, what's in progress and any blockers. See our daily standup vs EOD report comparison.
- Async check-ins a few times a week, covered in async check-ins for remote teams.
- A weekly written update the employee drops into the one on one doc before the meeting.
Written updates also take the pressure off monitoring. A manager who reads a clear report every day has no need to watch anyone's screen. More on that in remote team updates without micromanaging.
This is the idea behind Astrolinks, the desktop app we make for Mac and Windows. It keeps a private log of each person's workday on their own computer, with no screenshots and no keystrokes, and writes their end-of-day report at clock-out. They mark items as Finished, Sent, Drafted, Replied or In progress and choose whether to send it. Nothing leaves their computer unless they press a button. See how it works for remote teams.
How often should you hold one on ones?
There is no single right answer, but these rules of thumb work for most remote teams:
| Situation | Frequency | Length |
|---|---|---|
| New hire, first 3 months | Weekly | 30 minutes |
| Settled team member | Weekly or every two weeks | 30 minutes |
| Senior, very independent person | Every two weeks | 30 to 45 minutes |
| Person going through a hard time | Weekly, plus ad hoc | As needed |
Whatever you choose, keep the slot fixed. If you have to miss one, move it within the same week instead of cancelling. Cancelled one on ones tell a remote employee they're the first thing to go when you're busy.
What are the most common one on one mistakes?
- Talking more than listening. Aim for the employee speaking most of the time.
- Using it for status updates. Read their written updates before the call instead.
- No notes. Without a shared doc, actions are forgotten and the same problems come back.
- Cancelling often. It sends a stronger message than anything you say in the meeting.
- Saving all the feedback for reviews. Small, timely feedback in one on ones means reviews hold no surprises.
- Ignoring time zones. Don't schedule someone's one on one at the edge of their day every week. Share the awkward hours.
Remote one on one meeting example
Here's a filled-in example block for a developer and her manager.
1:1: Tom and Aisha, Dec 9
Check-in: 3 out of 5. Tired after the release, slept badly.
Aisha's topics
- The release went out Thursday, but on-call was rough. Wants to rotate on-call more evenly.
- Interested in the payments project starting in January.
Blockers: Waiting two days for design review on the settings page.
Feedback: Tom: the release notes were clear, the support team used them directly. Aisha: asks Tom to share priorities on Monday instead of Wednesday.
Next steps
- Tom: propose a new on-call rotation at Friday's team meeting.
- Tom: ask the design lead about the review backlog, by Wednesday.
- Aisha: write a short note on what she'd like to own in the payments project.
Each action has an owner. Next week's meeting starts by checking them.
The short version
Keep one shared doc per person, put their topics first, and run a 30-minute flow: check-in, their topics, blockers, feedback both ways, next steps. Move status updates into written reports so the meeting is free for people. Hold it weekly or every two weeks, keep the slot fixed, and end every meeting with actions that have an owner and a date.
