A Private 1:1 Meeting Notes Template

A strong one on one meeting template has five recurring parts: a quick check-in, wins since last time, current blockers, two-way feedback, and action items with clear owners and due dates. Keep one running note per direct report so context carries week to week, and keep it private by default — visible to no one but you until you deliberately share it.

A 1:1 is not a status meeting, so the template should not read like a stand-up. The point is to build trust, surface friction early, and leave with a short list of things that will actually get done. The best structures are the same every week, because sameness is what lets context accumulate and lets both people prepare in thirty seconds.

Across the many one on one meeting agenda templates you will find online, the durable ones converge on the same five parts. Use them in this order — the softer, human parts first, the accountability at the end.

• Check-in — a quick read on how the person is actually doing, before work talk starts.
• Wins since last time — what went well, what shipped, what they are proud of.
• Blockers — what is stuck, slow, or ambiguous, and what they need from you.
• Two-way feedback — feedback in both directions, not a one-way performance review.
• Action items — concrete follow-ups, each with an owner and a due date.

Here is the fillable 1 on 1 template for managers and individual contributors alike. Paste it into one running note per person and fill it in before and during the meeting. The left column is the fixed structure; the right column is what you write.

You do not need every row every week. Growth and career often belong to a monthly beat rather than every session. But keeping the row in the template is a quiet prompt to raise it, so the relationship does not shrink to task-tracking.

Open with a genuine check-in. A single question — how are you, really — signals the meeting is about the person, not just their tickets. Write down one line, not a transcript. You are noting mood and load so that a pattern is visible over a month: three weeks of quiet overwhelm reads very differently than one busy Tuesday.

Then wins. Ask what went well and what they are proud of. This is not filler. It surfaces work that would otherwise go unseen, gives you material for later recognition and reviews, and reminds a stressed report that progress is being made. Capture two or three specifics, not a vague good week.

Blockers are where a 1:1 earns its place on the calendar. Ask what is stuck and, more usefully, what they need from you specifically. Write the blocker and the ask as separate things — the problem, and the exact action that would move it. A blocker with no owner is just a complaint; a blocker with your name and a date attached is a commitment.

Feedback has to run both directions. Give your feedback plainly, and then ask for theirs — on your decisions, your clarity, the team. Most managers under-collect upward feedback because they never explicitly ask. Put a line in the template that prompts it every week, and note what you heard so you can act on it and close the loop next time.

End every 1:1 the same way: read back the action items. Each one needs an owner and a due date, even if the owner is you. Vague follow-ups die between meetings; owned, dated ones survive. This is also the single most re-readable part of the note — the first thing you both scan when the next 1:1 opens.

1. State the action in one concrete sentence — what will be done, not the topic it relates to.
2. Assign one owner. Shared ownership usually means no ownership.
3. Set a due date, even a rough one. A date turns intent into accountability.
4. Carry anything unfinished into the next note so nothing quietly disappears.

The template only compounds if you stop starting fresh each week. Keep one long-lived note per direct report and append to it — newest entry on top — rather than spawning a new file every meeting. Everything you need to prepare is then in one place: last week's action items, the open blocker, the feedback you promised to act on.

A running note also makes patterns legible over time. Scroll back a quarter and you can see whether the same blocker keeps resurfacing, whether wins have thinned out, whether a career conversation has been slipping for two months. That longitudinal view is impossible when each 1:1 lives in its own scattered doc.

On cadence: weekly is the default for most manager–report pairs, especially for newer or more junior reports who benefit from tighter feedback loops. Senior, autonomous reports can often move to every other week. The rule of thumb is simple — meet often enough that no problem waits more than a week or two to be raised, and protect the slot. A 1:1 that is routinely cancelled tells the report they are optional.

1:1 notes are among the most sensitive things you will write at work: candid feedback, career doubts, sometimes personal context. So the default should be simple — a 1:1 note is visible to no one but you until you choose to share it. Not your skip-level, not the workspace at large.

This is about access control, not encryption. In Reline the model is private by default: a workspace role on its own grants zero access to any note. Being an admin or owner does not silently open your 1:1 notes; every viewer needs an explicit, revocable grant that you make on purpose. We won't re-argue the whole permission model here — the linked post walks through exactly who can and cannot see a note, level by level.

Typing action items while staying present in a hard conversation is a real tax. This is where capture helps — if it does not change the tone of the room. Reline records the meeting without a bot joining the call. It captures your mic and the system audio locally on your machine, so nothing shows up in the participant list and the other person is not staring at a recorder that wandered into the room.

From that recording, the Action Items Lens reads the transcript and drafts the follow-ups — the owner-and-due-date list — so you can start from a draft instead of a blank line. Lenses are a library of reusable output formats; Action Items is the one built for exactly this. You review and correct it, because AI drafts are a starting point, not the final word.

Be clear-eyed about what runs where. Capture is local, but transcription, the AI summaries, and storage are cloud services, handled under a data-processing agreement, and your meetings are never used to train models. Our cloud transcription provider covers 60+ languages with automatic language detection. And bot-free removes the on-screen recorder — it does not remove your duty to tell people they are being recorded. Get consent as you normally would; then let the tooling do the note-taking.

Short answers to the questions managers and reports ask most about running and storing 1:1 notes.

A good template is only half the work; keeping one running, private note per person is what turns a weekly meeting into a real relationship you can look back on. Start with the five-part structure above, keep each note yours by default, and let the recording draft the action items so you can spend the meeting on the human in front of you.