Back to Insights
Best Practice2026-07-169 min read

The 1:1 Meeting Template Every Manager Needs (+ Examples)

The 1:1 Meeting Template Every Manager Needs (+ Examples)
TL
Team Laxis
Laxis Team @ Laxis

You block 30 minutes every week. Your report shows up, rattles off what they shipped, you nod, you say "great, keep me posted," and you both close your laptops feeling like you did the responsible manager thing. You didn't. You had a status meeting wearing a nicer name.

That drift is the reason most 1:1s quietly fail, and it's why a good 1:1 meeting template matters more than people think. A template isn't bureaucracy. It's a guardrail that keeps the one recurring conversation you have with each person from collapsing into the thing a Slack update could have handled. Below is a real, copy-paste one on one meeting template, a filled example of an actual week, a bank of questions worth stealing, and variations for skip-levels, new hires, remote reports, and someone who's struggling.

Why most 1:1s devolve into status updates

Status is the path of least resistance. It's concrete, it's safe, and it makes both people feel productive. The report performs progress, the manager collects it, and the harder conversation — the one about the blocker they're embarrassed about, the project they're bored by, the feedback they've been sitting on — never happens. Research on 1:1 patterns is blunt about it: without a set structure, one-on-ones drift into status updates within weeks.

And when a 1:1 is just a status meeting, cancelling it feels free, because the status already lives in the dashboard. That's the real cost. You're not just wasting 30 minutes; you're training yourself to treat the meeting as skippable. Then trust erodes, and you don't notice until someone resigns "out of nowhere."

The stakes are higher than most managers assume. Employees whose managers hold regular 1:1s are almost three times as likely to be engaged at work, and weekly cadences correlate with roughly 20% lower anxiety and about 12% higher self-reported success versus meeting less often. The meeting is one of the most valuable half hours on your calendar. It just doesn't feel that way when you spend it reciting a to-do list.

What a good 1:1 actually covers

A 1:1 is the report's meeting, not yours. That single design choice is the difference between a coaching conversation and a check-the-box ritual. When managers set the agenda, 1:1s become status meetings. When the report sets it, they become the place where real problems surface. So the structure below front-loads their topics and keeps yours short.

Across the research, the same six ingredients show up. A quick personal check-in and wins (3–5 minutes). A review of last week's action items (3–5 minutes). The report's topics — blockers, decisions, whatever's on their mind — which should take the biggest single chunk (10–20 minutes). Your topics, kept tight (5–10 minutes). Feedback in both directions (about 5 minutes). And clear next steps written down before you leave (2–5 minutes). Growth and career don't need to appear every single week, but they should show up on a predictable rotation so they never get crowded out by whatever's on fire.

The best split I've seen recommended is aggressive on purpose: five minutes maximum on status, with the detail moved to writing beforehand, fifteen minutes on growing the person with one deep question, and the rest of the time solving exactly one problem together. You won't hit that ratio every week. But aim there, and even a messy 1:1 lands somewhere useful.

Tip: the report drives the agenda. Share a running doc and ask your report to add their topics before the meeting. If it's empty when you sit down, don't fill the silence with status questions — ask "what's the one thing you most want to talk through today?" and let them lead. Your job is to react well, not to run the show.

The copy-paste 1:1 meeting template

Here's the template. Keep it as a shared doc, one entry per week, newest at the top. The report fills their sections first; you add yours. The prompt questions are there to break a blank page, not to be answered in order every time.

1. Check-in & wins (3–5 min)

  • How are you doing this week — honestly, on a scale you'd defend?
  • What's a win, big or small, since we last talked?
  • Anything outside work I should know about that's affecting your week?

2. Follow-up on last week's action items (3–5 min)

  • What did we each say we'd do? What actually happened?
  • What's still open, and is it still worth doing?

3. Your topics — you drive this (10–20 min)

  • What's blocking you that I could clear today?
  • What decision are you stuck on where a second opinion would help?
  • What's frustrating you about how we work right now?

4. My topics (5–10 min)

  • One priority I want to make sure we're aligned on this week.
  • Context from the wider org you should have.

5. Growth & career — rotate, not every week (10–15 min when it comes up)

  • What did you learn recently that you want to do more of?
  • Where do you want to be in a year, and is this role moving you there?
  • What's one skill you'd like more reps or coaching on?

6. Feedback, both ways (5 min)

  • One thing I noticed you did well — specifics.
  • One thing I'd like to see you try differently.
  • What could I do differently to make your work easier?

7. Action items (2–5 min)

  • What are we each committing to before next time? Who owns what, by when?

A filled example: one week's 1:1

Templates read as abstract until you see one used. Here's a manager, Dana, and a report, Marcus, a mid-level product designer. This is roughly what their shared doc looked like after a single Tuesday session.

Marcus × Dana — Tuesday, July 14

Check-in & wins: "A solid 7. Tired but good. Win: the onboarding redesign shipped and support tickets about the first-run screen dropped noticeably this week."

Follow-up: Marcus did send the research summary to the growth team (done). Dana had promised to get him time with the data analyst — didn't happen, Dana owns it again.

Marcus's topics: Blocked on the settings redesign — engineering keeps deprioritizing it and he doesn't know if he should keep pushing or drop it. Also feeling stretched across three projects and wants help saying no to one.

Dana's topics: Heads-up that Q3 planning starts in two weeks; wants Marcus to think about which project he'd want to own end-to-end.

Growth: Marcus wants more reps presenting to leadership. Agreed he'll run the design review readout at the next Q3 kickoff, with Dana giving feedback after.

Feedback: Dana: "Your onboarding writeup was the clearest doc I've read from the team all month — do more of that." Marcus to Dana: "I'd love faster answers when I'm blocked; sometimes I wait days."

Action items: (1) Dana books the data analyst intro by Thursday. (2) Dana takes the settings priority to eng lead this week. (3) Marcus drops the third project after this sprint and confirms with the PM. (4) Marcus preps the Q3 readout.

Notice what that session did that a status update never would: it surfaced an overload problem, gave Marcus a concrete growth rep, and generated four owned action items. Notice also that the meeting is only useful next week if someone actually remembers those four items. That's where most 1:1s quietly break.

Where 1:1s really fall apart: the week in between

The template isn't the hard part. The follow-through is. Dana promised Marcus an intro to the data analyst last week and forgot — and when a manager forgets their own action item two weeks running, the report stops believing the meeting changes anything. Multiply that across six reports and the whole practice rots. The single most common failure mode of 1:1s isn't a bad agenda; it's that the action items and agreements evaporate by the next session, so every meeting starts from a blank page instead of from what you decided.

This is the one place I'll make a tooling suggestion, because it maps exactly to the failure. If your 1:1s happen over Zoom, Google Meet, or Teams, an AI meeting assistant like Laxis records and transcribes the call, then auto-extracts the action items, decisions, and next steps into a summary you can drop straight into your shared doc. The next 1:1 opens with "here's what we agreed last week" already written, so you spend the live time on the conversation instead of reconstructing it from memory. Laxis supports 100+ languages, works botlessly, and syncs notes to HubSpot or Salesforce if you track people conversations there — and there's a free plan to test it on your own recurring meetings.

Honest caveat: the template works with any tool. A shared Google Doc and the discipline to write action items down at the end of every session will get you 90% of the way there. The point isn't the software — it's that the agreements have to live somewhere both of you trust, or the meeting becomes theater.

Variations for different situations

The core template flexes. Here's how to bend it for four common cases without rebuilding it from scratch.

Skip-level (your report's report)

This isn't a status meeting and it's not a review — it's a listening tour. Drop your topics almost entirely. Ask about the team's health, whether they have what they need, and how their own manager is doing from their side. Make it explicit that you won't repeat specifics back without permission, or you'll get nothing real.

New hire (first 90 days)

Meet weekly, no exceptions, and skew toward onboarding. Swap the growth section for "what's confusing?" and "who haven't you met yet that you should?" Ask every week what would have made their first weeks smoother — that feedback is gold and it expires fast once they acclimate.

Remote or distributed report

Protect the personal check-in harder, since you lose all the hallway signal. Turn cameras on, and resist the urge to jump straight to work. Because you can't read the room in passing, put more feedback in the meeting rather than saving it for "sometime." And write everything down, since time zones make follow-up chat harder.

Underperformer

Keep it a 1:1, not a disciplinary hearing — but be specific and documented. Replace vague encouragement with clear expectations, examples, and a written recap of what "back on track" looks like. Keep asking what's getting in their way; sometimes underperformance is an unremoved blocker, not a capability gap. If it's a formal performance plan, loop in your HR partner — this isn't legal or HR advice.

Tip: never cancel — reschedule. When the week explodes, the 1:1 is the easiest thing to drop and the most expensive. Move it to Thursday, shorten it to 15 minutes, do it as a walk-and-talk if you must — but keep the signal that this person's time with you is non-negotiable. A 1:1 that never gets cancelled builds more trust than a longer one that slips.

A short bank of good 1:1 questions

When the doc is empty and you need a better prompt than "how's it going," pull from these. Rotate them — asking the same one every week trains a scripted answer.

To surface the truth

  • What's something you've been meaning to bring up but haven't?
  • What's frustrating you right now that you've stopped mentioning because it feels normal?
  • If you were me, what would you change about how the team works?

To find blockers

  • What's the slowest part of your week, and why?
  • What are you waiting on from someone else right now?
  • Where are you spending time that doesn't feel worth it?

To grow the person

  • What part of your job do you wish you were better at?
  • When did you last feel genuinely proud of your work here?
  • What would make the next six months a great stretch for you?

To get feedback on yourself

  • What's one thing I could do to make your work easier?
  • Where am I not giving you enough — direction, context, or space?

The bottom line

The best 1:1 template is the one you'll actually keep using for a year, not the most elaborate one you download this week. Start with the seven sections above, let your report drive, and protect the slot like rent. The managers people remember aren't the ones with the cleverest agenda — they're the ones who showed up every week, remembered what you said last time, and did what they promised. A template just makes that easier to pull off when you're managing six people and forgetting most of it.

Frequently asked questions

How often should 1:1 meetings happen?

For most manager-report pairs, weekly or every other week for 30 to 60 minutes is the sweet spot. A biweekly 1:1 that never gets cancelled builds more trust than a weekly one that slips every other week, so pick the cadence you can actually keep. New hires and struggling reports often need weekly time; senior, steady performers can sometimes go biweekly.

Who should own the 1:1 agenda, the manager or the report?

The report should own most of it. When managers set the agenda, 1:1s drift into status meetings; when the report sets it, they become coaching conversations. A practical split is the report brings the first block of topics, the manager adds one or two items at the end, and both add items to a shared doc before the meeting so nothing gets missed.

What should a 1:1 meeting actually cover?

A good 1:1 covers a short personal check-in and wins, blockers you can remove today, current priorities, growth and career, feedback in both directions, and clear action items. Keep status to about five minutes and move the detail to writing before the meeting so the live time goes to problems and growth.

Why do 1:1s turn into status updates?

Without structure, 1:1s drift into status updates within weeks because status is the easiest thing to talk about. The report performs progress, the manager collects it, and the harder conversation about blockers, morale, and growth never happens. The fix is to cap status at five minutes, move detail to a written update, and reserve the rest for one real problem and one growth topic.

Should you cancel a 1:1 when things get busy?

Reschedule, don't cancel. Employees whose managers hold regular 1:1s are almost three times as likely to be engaged, and each cancellation signals the conversation isn't a priority. Trust takes weeks to rebuild after it slips, so if the slot truly can't happen, move it to another day that same week rather than skipping it.