One-on-One Meeting Template
A one-on-one is a recurring private conversation between a manager and a team member, typically thirty minutes every two weeks. The notes template below covers commitment tracking from the previous session, question prompts by theme, and a filled-in example.
The biggest difference between a one-on-one and every other meeting is that it does not belong to the manager. This is the team member's time, and the manager only prepares the frame for the conversation. The template reflects that, which is why the employee's topics come before the manager's.
This page covers the structure, a set of question prompts for when the conversation goes flat, how to take notes without damaging trust, and a short FAQ.
A .docx file that opens in Word, Google Docs and LibreOffice.
When to use this template
Use it for recurring one-on-ones between a direct manager and a team member. The common cadence is every two weeks for thirty to forty-five minutes. New hires and newly formed teams often need a weekly rhythm for the first three months.
Do not use it for a formal performance review, which has a different structure and administrative consequences. Do not use it for feedback on a specific incident either, since that conversation needs to happen right after the event rather than waiting for the next scheduled slot.
If you are the person being managed rather than the manager, this template still works. Preparing three topics in advance is the most effective way to make the session useful for you.
One-on-one notes structure
The eight fields below follow the order the conversation should take. The employee's topics come first, deliberately, because placed last they routinely run out of time.
| Field | How to fill it in |
|---|---|
| Date and participants | The date and both names. Record cancelled sessions and the reason too, because a run of cancellations is a meaningful signal about the priority being demonstrated. |
| Review of previous commitments | What each side promised last time and where it stands. This field matters most for building trust, particularly the commitments made by the manager. |
| Employee's topics | What the team member wants to discuss, ideally sent in advance. Give this at least half the total time. It is the field that defines what a one-on-one is. |
| Current work | How current work is going, focused on obstacles and where support is needed rather than progress reporting, which already happens in other meetings. |
| Two-way feedback | Feedback from manager to employee and the reverse. Record the substance briefly, not the emotion. The upward feedback field is often left blank, which usually signals it does not yet feel safe to speak plainly. |
| Career development | Skills being built, direction wanted, opportunities being sought. Not needed every session, but it should appear at least monthly, otherwise it never gets discussed at all. |
| Commitments for next time | Concrete items from both sides with dates. The manager's commitments need recording just as clearly as the employee's, because those are the ones remembered longest. |
| Manager's private notes | An unshared section for tracking patterns over time. Keep it clearly separate from the shared part and never let it contain subjective judgements about the person. |
Filled-in example
A one-on-one between a manager and a member of a product team. Names and content are illustrative.
| Field | Example content |
|---|---|
| Date | Wednesday 22 July 2026, Anh and Linh |
| Previous commitments | Linh completed the automated testing course, done. Anh promised to ask about the training budget, not done, committed for this week. |
| Linh's topics | Wants to understand how feature priorities get decided, currently receives work without knowing the context. Wants to try leading a small area. |
| Current work | Search work is on track. The obstacle is waiting on design feedback several times a week, each wait costing half a day. |
| Two-way feedback | Anh: the technical document Linh wrote last week was clear, worth continuing. Linh: unscheduled meetings break up morning focus time. |
| Career development | Direction for the next six months is depth in data architecture. Agreed Linh will lead the bulk import area next quarter as a trial. |
| Commitments | Anh: share the prioritisation document before 25 July, ask about the training budget before 25 July, move unscheduled meetings to afternoons. Linh: write an approach proposal for bulk import before 5 August. |
| Private notes | Second time Linh has raised missing context when receiving work. Worth reviewing how priorities are communicated to the whole team, not just to Linh. |
Why the employee's topics come first
In most broken one-on-ones the order is: the manager asks about progress, then time runs out. Whatever the team member wanted to raise gets pushed to the end and cut every week, so by week five they stop preparing anything.
Reversing the order is a very small change that alters the nature of the meeting entirely. When the employee's section comes first and has real time, the one-on-one becomes a place where problems surface early rather than a place to re-report what was already reported elsewhere.
Practically, ask the team member to send two or three topics beforehand, even as bullet points. That also gives them thinking time, and the important issues rarely surface in the first thirty seconds of a conversation.
Question prompts for when the conversation goes flat
Some sessions start with both sides saying nothing much is going on. Sometimes that is true, but more often the question was too broad to answer. Specific questions consistently produce better answers.
A few that work in practice: was there any point this week where you spent time on something that should not have been necessary, has there been a recent decision you did not understand the reasoning behind, is anyone on the team doing good work that has gone unrecognised, and if you could change one thing about how we work, what would it be.
That last question is the most valuable, but only ask it when you are genuinely prepared to act on the answer. Asking repeatedly and doing nothing teaches people that speaking plainly has no effect.
Taking notes without damaging trust
Note taking in a one-on-one is more sensitive than in other meetings because the content is personal. If a team member watches their manager typing continuously, they will start filtering what they say.
A workable principle: record commitments and topics, not a detailed account of what was said. Tell the person in the first session what you record and who can read which part. That transparency matters more than the content of the notes.
The private section should hold patterns and things to follow up on, never character judgements. A line like second time context has come up is a useful observation. A line like tends to complain is a harmful judgement that cannot be used for anything.
The manager's commitments are the ones remembered longest
Two kinds of commitment come out of a one-on-one: what the team member will do, and what the manager will do. The second kind is remembered far more precisely, because for the team member it is evidence of whether a manager's word carries weight.
So manager commitments need clear recording and a review at the start of the next session, including when they were not completed. Saying plainly that you did not do what you promised and will do it this week is far better than passing over it in silence.
If one of your commitments slips three sessions running, the best move is to drop it and explain why rather than promise again. A permanently pending commitment corrodes the credibility of every other one.
Five mistakes that ruin a one-on-one
Progress is already covered in check-ins and on the task board. Using a one-on-one to re-ask it wastes the scarcest kind of time two people have together.
Every cancellation sends a message about priority whether or not anyone says so. When busy, shorten it to fifteen minutes rather than dropping it.
Leaving this out turns every commitment into talk. The review costs two minutes and is the most effective trust-building part of the session.
If a team member never gives upward feedback, it is not because they have nothing to say but because it does not yet feel safe. One specific question works far better than a general invitation to share thoughts.
This topic is always less urgent than immediate work, so it always gets deferred. A fixed monthly slot is the only reliable way to make sure it actually happens.
FAQ
How often should one-on-ones happen?
Every two weeks for thirty to forty-five minutes suits most teams. New hires and newly formed teams should keep a weekly rhythm for the first three months and then space it out.
Who should prepare the agenda?
Both, but the team member should send two or three topics beforehand. That keeps the session serving their needs and gives them thinking time, since important issues rarely appear in the first thirty seconds.
Should you take notes during a one-on-one?
Yes, but record commitments and topics rather than a detailed account. More important is telling the person up front what you record and who can read which part.
How is a one-on-one different from a performance review?
A one-on-one is a regular conversation with no administrative consequence, focused on removing obstacles and on development. A performance review runs on a cycle, produces a formal conclusion and usually connects to pay. Mixing them makes people feel unsafe speaking plainly in the one-on-one.
What if the team member has nothing to say?
Usually the question was too broad. Try something specific, such as was there any point this week where you spent time on something that should not have been necessary. If it persists across many sessions, that is a signal about safety in the relationship rather than about content.
Record the session so you are not listening and typing at once
In a one-on-one, continuous typing interrupts the conversation and makes the other person more guarded. Meco records the session and extracts the commitments and action items, so you can focus on listening.
Because one-on-one content is personal, ask the other person before recording and keep the notes private. Every set of minutes in Meco is private by default and only shared when you actively create a link.
Try it free