Skip to main content

Meetings

One on One Meeting Template

A 1:1 belongs to the report, not the manager. This template gives the report the first word, carries last meeting's actions forward, and keeps a growth conversation on the calendar. Copy it, or start from the one on one notes example closest to your situation.

Updated 2026-10-27

Copy and adapt

The template

One on one meetingTemplate

1:1 [Report] and [Manager], {{date}}

Cadence: [weekly / every two weeks], [30 / 45 min]. Agenda owner: [report] Related: [[Report's name]]

Carried over

  • [Action from last time] (@[owner]) @due(YYYY-MM-DD)

Check-in (5 min)

  • [Energy, workload, anything outside work they choose to mention]

Their topics (15 min)

[Topic they added before the meeting]

  • [What they want from you: a decision, context, or just to be heard]

Priorities and blockers (10 min)

  • Top priority this week: [one thing]
  • Blocked on: [what, and who can unblock it]

Feedback (5 min)

  • From me: [one specific observation with the example it comes from]
  • From them: [one thing I could do differently]

Growth (every fourth meeting, or whenever they raise it)

  • [Skill or goal, and the next concrete step toward it]

Actions

  • [Action] (@[report]) @due(YYYY-MM-DD)
  • [Action] (@me) @due(YYYY-MM-DD)

Note to self: [patterns across meetings, things to watch. Not for sharing]

5 examples

Examples for different situations

The same structure, filled in for the situations people actually bring to it. Copy the one closest to yours.

1.First 1:1 with a new hire

When it fits: Use this in week one or two, when the report does not know what to bring yet, and the real job is to find the gap between what they were told and what the job is.

First 1:1 with a new hireExample 1

1:1 Amina and Sol, 2026-11-04

Cadence: weekly, 45 min for the first month, then 30. Agenda owner: Amina (from week 3) Related: [[Amina Yusuf]]

Carried over

  • None, first meeting.

Check-in

  • Day 8. Laptop and access sorted by day 3, which she said was faster than her last job. Commute is 50 minutes; she asked about the Wednesday work-from-home norm. Confirmed it is a norm, not a favor.

Her topics

Scope mismatch

  • The recruiter described the role as 70 percent data pipeline work. The onboarding plan is mostly dashboard maintenance. She wanted to know which is true.
  • Honest answer: the first two months are dashboards because that is where the team is behind. Pipeline work starts when the ingestion rewrite kicks off in January. She said that is fine if it is written down. It now is.

Priorities and blockers

  • Top priority this week: finish the onboarding tickets and ship one small dashboard fix end to end.
  • Blocked on: production read access, requested on day 2, still pending with IT.

Feedback

  • From me: her questions in the team channel are specific and easy to answer. Keep doing that.
  • From her: the onboarding doc lists a tool we stopped using in 2025. She will fix the doc.

Growth

  • Deferred to the 30-day meeting. She mentioned wanting to present at the data guild eventually.

Actions

  • Chase IT on production read access (@Sol) @due(2026-11-05)
  • Write the January pipeline plan into her onboarding note (@Sol) @due(2026-11-11)
  • Fix the stale tool reference in the onboarding doc (@Amina) @due(2026-11-07)
  • Add her first topics to next week's note (@Amina) @due(2026-11-10)

Note to self: She asks for things in writing. Good instinct. Make sure the scope promise survives if the January project slips.

2.Weekly 1:1 with a frustrated senior engineer

When it fits: Use this when a strong performer has gone quiet in meetings, the complaints are arriving sideways, and you need the real one on the table before it turns into a resignation.

Weekly 1:1 with a frustrated senior engineerExample 2

1:1 Rafael and Sol, 2026-11-11

Cadence: weekly, 30 min. Agenda owner: Rafael Related: [[Rafael Mendes]]

Carried over

  • Review the on-call rota for Q4 (@Sol) done 11-10
  • Pair with Amina on the dashboard fix (@Rafael) carried, moved to 11-14

Check-in

  • Said "fine" twice. Asked directly whether he is enjoying the work. Long pause, then: not for the last six weeks.

His topics

Code review latency

  • His PRs wait an average of two days for review. He measured it: 11 PRs since October, median 46 hours. Meanwhile he reviews others within the hour. He feels it is a one-way street.
  • I had not seen the numbers. They are bad. Agreed the team norm of "review within one working day" is not being kept, mostly by two people.

On-call load

  • He has been primary on-call 5 of the last 12 weeks. The rota review confirmed it: two people have skipped because of leave and the gaps landed on him.

Priorities and blockers

  • Top priority this week: the ingestion rewrite design doc, due 11-20.
  • Blocked on: the two reviewers above, for the design doc as well.

Feedback

  • From me: the PR latency data is exactly how to raise this. Numbers moved it from a complaint to a problem in ten seconds.
  • From him: I should have noticed the on-call imbalance without him raising it. He is right.

Growth

  • Not this week. He said he cannot think about growth while he is this annoyed. Revisit 12-02.

Actions

  • Raise review latency at Thursday's team meeting with his numbers, no names (@Sol) @due(2026-11-13)
  • Rebalance on-call: Rafael off primary until January, I take two of the gaps (@Sol) @due(2026-11-12)
  • Send the design doc to Priya for review instead of waiting on the usual two (@Rafael) @due(2026-11-14)

Note to self: Six weeks is a long time not to notice. Ask the direct question earlier. Check in on 11-18 whether review times moved.

3.1:1 about promotion timing

When it fits: Use this when a report asks for a promotion you do not think is ready yet, and the goal is to leave with a shared list of evidence rather than a disagreement about feelings.

1:1 about promotion timingExample 3

1:1 Jess and Marcus, 2026-11-13

Cadence: every two weeks, 45 min today by request. Agenda owner: Jess Related: [[Jess Okonkwo]]

Carried over

  • Send the senior-level expectations doc (@Marcus) done 11-03

Check-in

  • Skipped by agreement; she asked to use the full time on one topic.

Her topics

Promotion to Senior in the January cycle

  • Her case: she led the payments migration, it shipped on time, two people on the team now come to her first with questions. She has been at this level 2 years and 4 months.
  • My view: the migration was a strong project. The expectations doc also asks for influence beyond the team and for driving a piece of work nobody assigned. I have one example of each, and I would want two or three to make the case stick with the promo committee.
  • She pushed back: "nobody assigned" is vague, and the bar seems to move. Fair point about vagueness. We wrote down what would count.

What would count (agreed)

  • Leading the API deprecation she proposed in October, including the two other teams it affects. Not just proposing it.
  • One cross-team design review where she is the reviewer, not the author.
  • A written retro of the payments migration shared outside the team, so the committee sees the work directly.

Priorities and blockers

  • Top priority: the deprecation proposal, now with her as the named lead.
  • Blocked on: nothing yet. She needs the platform team's calendar.

Feedback

  • From me: she argued her case with specifics and stayed calm when I said not January. That is the influence skill, visibly.
  • From her: I should have told her in September that January was unlikely. Agreed. I waited for her to ask.

Growth

  • This was the growth conversation. Target: the April cycle, if the three items above are done by mid-March.

Actions

  • Write the three items into her growth note and share it with her (@Marcus) @due(2026-11-14)
  • Draft the migration retro (@Jess) @due(2026-11-27)
  • Introduce her to the platform lead for the deprecation (@Marcus) @due(2026-11-18)

Note to self: I owe people the honest timeline before they ask. Check the three items at every second 1:1 until March.

4.Skip-level 1:1

When it fits: Use this when a director meets an engineer two levels down, the report may not know what the meeting is for, and the risk is either saying nothing or undermining their manager.

Skip-level 1:1Example 4

Skip-level 1:1 Tomasz and Dana, 2026-11-19

Cadence: quarterly, 30 min. Agenda owner: Dana set the frame; Tomasz brought topics Related: [[Tomasz Nowak]]

Carried over

  • From August: Dana to clarify the mobile team's headcount plan in the org channel. Done 09-02

Check-in

  • Explained the purpose again: this is for me to learn how the team actually works, not a performance review and not a channel around his manager. What he says stays with me unless he asks me to act on it.

His topics

Release process

  • Releases take two days of one engineer's time every two weeks. Mostly manual checks that could be automated. He raised it with his manager twice; it is on the backlog behind feature work.
  • Asked whether he wants me to do anything. He said no, but he wanted someone above the team to know the cost. I will mention to his manager that I heard about release cost from "the team", without his name, and ask what would unblock it.

What is working

  • The new design review format. He said it is the first time he has seen designers and engineers disagree in the same room and resolve it.

Priorities and blockers

  • Skipped. Not the point of a skip-level.

Feedback

  • From me: his manager rates his mentoring of the two juniors highly. He did not know that. He should.
  • From him: the quarterly all-hands numbers are too high level; engineers cannot tell whether the mobile bet is working. I will bring one product-level metric to the next one.

Growth

  • He is curious about the staff engineer track but has not raised it with his manager. Encouraged him to; offered to tell his manager he is interested, which he accepted.

Actions

  • Raise release cost with his manager as a team-level observation, no name (@Dana) @due(2026-11-21)
  • Add one mobile product metric to the December all-hands (@Dana) @due(2026-12-10)
  • Tell his manager he is interested in the staff track (@Dana) @due(2026-11-21)

Note to self: Two skip-levels this quarter mentioned release cost. That is a pattern, not an opinion.

5.Remote 1:1 after a missed deadline

When it fits: Use this when a report in another time zone missed a date, the easy story is that they dropped the ball, and the actual cause is probably in the handoff.

Remote 1:1 after a missed deadlineExample 5

1:1 Yuki and Lena, 2026-11-25

Cadence: weekly, 30 min, 09:00 Berlin / 17:00 Tokyo. Agenda owner: Yuki Related: [[Yuki Tanaka]]

Carried over

  • Localization QA for the 2.3 release (@Yuki) was due 11-20, missed. Discussed below.

Check-in

  • She opened with an apology. Stopped her: we are here to find out what happened, not to apologize. She said she had been dreading this call since Friday.

Her topics

The missed QA date

  • Her account: the build she needed was published at 18:30 Berlin on 11-18, which is 02:30 Tokyo. She saw it 11-19 morning Tokyo, which was 11-18 evening Berlin, and had one working day instead of two. She asked in the channel whether the date could move; nobody answered before Berlin woke up, and by then the release manager had already marked QA as late.
  • The handoff assumed her day starts when ours does. It does not. The schedule was built in Berlin time with no Tokyo check.

Priorities and blockers

  • Top priority: finish the 2.3 QA by 11-27 (agreed with the release manager this morning).
  • Blocked on: nothing now. The build is there.

Feedback

  • From me: when the date was at risk, the channel message was right but it needed a name on it. Message the release manager directly next time, and me if no answer in two hours.
  • From her: the release calendar should show Tokyo time next to Berlin time. Obvious in hindsight.

Growth

  • Deferred. She asked to use next week's slot to talk about taking over the localization vendor relationship.

Actions

  • Add a Tokyo-time column to the release calendar and a rule that QA handoffs land before 15:00 Berlin (@Lena) @due(2026-11-27)
  • Tell the release manager the late mark was a scheduling failure, not a Yuki failure (@Lena) @due(2026-11-25)
  • Finish 2.3 localization QA (@Yuki) @due(2026-11-27)
  • Bring the vendor-relationship topic next week (@Yuki) @due(2026-12-02)

Note to self: She dreaded this for four days. Make the no-blame framing explicit in the invite next time, not just in the call.

What belongs in a one on one

A one on one meeting template has one job the group templates do not: it has to work across months, for one person, without turning into a status update. Each section in the template above exists because of a way 1:1s go wrong.

  • Carried over. Last meeting's actions, ticked or moved. This is what makes the meetings a thread. Without it, every 1:1 starts from zero and the same blocker gets raised in April and again in June.
  • Check-in. Five minutes, and it is optional for the report to say anything personal. The point is to notice when "fine" means something else, as it did in the second example.
  • Their topics first. The report's items go before yours, and get the biggest time box. If you consistently run out of time before their topics, the meeting is yours, not theirs.
  • Priorities and blockers. One line each. Not a ticket walk-through.
  • Feedback, both ways. One specific observation each, with the example it comes from. "Good job this week" is not feedback; "the PR latency numbers moved the conversation in ten seconds" is.
  • Growth, on a cadence. Every fourth meeting, or whenever they raise it. Otherwise it is always next time.
  • Actions for both people. The manager leaves with actions too. A 1:1 where only the report has homework is a review, not a conversation.
  • Note to self. Patterns you notice over time. Not shared, clearly marked.

Who owns the agenda

The report. Share the note or the structure before the meeting and ask them to fill Their topics. Your topics go into Feedback and, occasionally, into a section of your own. The order matters more than people expect: a 1:1 that opens with the manager's items trains the report to wait, and after a few months they stop bringing anything.

For a new hire this takes a few weeks. The first example on this page shows a manager setting the agenda for the first two meetings and handing it over in week three, with a written note that says so.

Keeping a running record over months

This is what most 1:1 templates skip. A good 1:1 note is not the meeting; it is the entry in a record that will be read at review time, at promotion time, and when the person moves teams.

  1. One note per meeting, linked to one note per person. The person's note is the index. Every 1:1 links to it, so the backlinks list is the history. You never search for "that conversation about on-call in the autumn."
  2. Actions carry forward explicitly. Copy last week's open actions into Carried over and tick them in the first minute. An action carried three times is a decision in disguise: drop it, or escalate it.
  3. Write the growth agreements down and date them. The third example shows the shape: not "work on influence" but three concrete items with a target cycle. Six months later the record either shows the items done or it does not, and the promotion conversation is about evidence instead of memory.
  4. Review the record before each quarter. Twenty minutes reading the last twelve notes for one person will show you the patterns the notes to self were pointing at.

Questions that work

The questions in the top-ranking 1:1 guides are mostly fine. The ones that get real answers share a shape: specific, about the recent past, and easy to answer honestly.

  • What was the most annoying part of your week?
  • What did you spend time on that you think was a waste?
  • Is there a decision you are waiting on from me?
  • What would you change about how the team runs if you could change one thing?
  • What have I done recently that made your work harder?

Ask one. Wait. The useful answer usually arrives after the pause.

Common mistakes

  • Cancelling when busy. The report reads it as "you are the lowest priority on my calendar." Shorten it to fifteen minutes instead.
  • Running it as a status meeting. Ticket progress is in the tracker. If the 1:1 is where you learn what someone did this week, the tracker is broken or the 1:1 is.
  • Feedback only in one direction. Ask what you could do differently, every time, and act on the answer visibly at least once. The fourth example shows what it sounds like when a report finally tells you.
  • No record. Twelve months of 1:1s with no notes means the promotion case is built from memory, and memory favors the last six weeks.
  • Promising timelines you have not checked. "Probably January" becomes a commitment in the report's mind. Say what would need to be true, and write it down.

When to use a different template

A formal review conversation with ratings and a written outcome belongs in the performance review template; a 1:1 is where the material for it accumulates. If you are coaching someone outside a reporting line, the coaching session notes template drops the priorities and blockers sections and spends the time on goals. For the report's own side of the growth conversation, the personal development plan template is the place to write the plan the 1:1 keeps referring to. And a group meeting with decisions is a different animal: use the meeting notes template.

Customization tips

  • The report writes the first section

    Share the note or the structure and ask them to add topics before the meeting. If the Their topics section is empty three meetings in a row, that is the topic: either the meetings are not safe enough to use, or the cadence is wrong.

  • Carry actions over at the top, every time

    Start by ticking or moving last meeting's actions. It takes one minute and it is what makes the 1:1 a thread instead of a series of conversations. Actions that get carried three times should be dropped or escalated, not carried a fourth.

  • Keep status out of it

    Progress on tickets belongs in the tracker. If the priorities section is becoming a status report, cut it to one line and give the time back to their topics. A 1:1 that could be an async update will be skipped the first busy week.

  • Put growth on a cadence so it happens

    Every fourth meeting, growth is the first topic instead of the last. Without a rule it gets pushed by whatever is urgent, and six months later nobody can remember when it was last discussed.

  • Separate your note to self

    Observations about patterns ("third time they mentioned being tired") are useful and are not for the report. Keep them in a clearly marked line at the bottom so you never share the wrong thing by accident. If you share the note itself, move this line to a private note about the person.

  • Shorter for weekly, longer for monthly

    A weekly 30-minute 1:1 can skip Growth and Feedback most weeks. A monthly 45-minute one should not skip either. Adjust the time boxes to the cadence rather than running the full template every time.

In the app

How to do this in Scribelet

  1. Open Desk Settings, then Templates, tap Add Template, paste the template above and set the category to Meeting. Keep {{date}} in the title and set #1on1 as a default tag so every 1:1 is one tap away.

  2. Create one note per person (Rafael Mendes, say) and link it from each meeting with [[Rafael Mendes]]. The person's note then shows every 1:1 in its backlinks panel, newest first, which is the running record most managers wish they had kept.

  3. Write actions as - [ ] Task (@Rafael) @due(2026-11-14). Both your actions and theirs appear in the Tasks view and on your daily note until ticked, so the Carried over section writes itself next week.

  4. Ask the AI chat "what has Rafael raised about on-call in the last three months?" It answers from your 1:1 notes with citations, and it remembers people and projects across conversations.

  5. Before a promotion or review conversation, ask "summarize the growth items Jess and I agreed to since September" rather than rereading six notes.

Templates, template variables and AI generation are documented in Note templates.

Frequently asked questions

How often should one on one meetings be?

Weekly for new hires, people in a new role, and anyone remote or struggling. Every two weeks for experienced people who are doing well and have other ways to reach you. Monthly is too rare for a direct report; problems like the review latency in the second example above take six weeks to surface even at weekly cadence.

What is the 10-10-10 rule for meetings?

For a 30-minute 1:1, one common version is ten minutes for the report's topics, ten for the manager's, and ten for the future (growth, career, what is coming). Versions vary and the split is a guide, not a rule. The template above follows the same idea but gives the report's topics the first and largest block.

Why do managers have 1:1 meetings?

Because the things that matter most (someone is frustrated, someone wants to leave, someone was promised a scope they are not getting) do not get raised in team meetings or in a ticket. A regular private slot is the only reliable place to hear them early. Every example on this page is a problem that would have cost more if it had been found later.

Should I share my one on one notes with the report?

Share the agenda, the actions and anything you said as feedback; the report should never be surprised by what is in the record. Keep your note to self separate, as the template does. Many managers share the whole note minus that line and let the report add their topics directly before the meeting.

What do I do when the report has nothing to talk about?

Do not cancel. Ask one open question ("what is the most annoying part of your week right now?") and let the silence sit. If nothing comes three meetings running, raise that as the topic: either the meeting is not useful in its current form or something is making it hard to speak. Both are worth knowing.

Is a one on one meeting template different from a regular meeting notes template?

Yes. A meeting notes template is organized around topics and decisions for a group. A 1:1 template is organized around one person over time: carried-over actions, their topics first, growth on a cadence, and a running record linked to the person. Using the group template for 1:1s is how they turn into status meetings.

One running record per person, not fifty scattered notes

Save this 1:1 template in Scribelet, link every meeting to the person's note, and let actions carry forward as tracked tasks. When the review cycle comes, ask your notes what you agreed in March. Encrypted, free to start.

Free plan, no credit card. See pricing

Meetings

Meeting Notes Template

One structure that captures the three things people come back for: what was decided, who owns what by when, and the context that made the decision make sense. Copy it as-is, or pick the example closest to your meeting.

Meetings

Meeting Agenda Template

An agenda is a promise about how the time will be spent: what the meeting must produce, which topics get how many minutes, and who owns each one. Copy the template, or start from the agenda example closest to your meeting.

Work

Performance Review Template

A performance review template is only as fair as its rating scale and its evidence. This one defines each rating level in the template itself, ties every goal to a result and a source, and leaves room for the employee to disagree in writing. Copy it, or start from the example closest to the review you have to write.

Work

Coaching Session Notes Template

Coaching and mentoring session notes (not therapy notes) follow one client toward one goal over several sessions. This template opens with last session's commitments, records what came up and what the client realized, and ends with new commitments and a private reflection.

Work

Personal Development Plan Template

A personal development plan names where you are, where you want to be in a year or so, and no more than three things you will work on to get there. This template adds what most plans skip: a monthly check, a quarterly rewrite, and a rule for plans that stall. Copy it, or start from the example closest to your situation.

Planning

Weekly Review Template

A weekly review is 45 minutes that stops small things from going stale: clear the inboxes, look back honestly, check every project has a next step, then choose three priorities for next week. Copy the template, or start from the weekly review example closest to your week.

We use cookies for analytics to improve your experience. Learn more