One-on-One Meeting Notes Template: A Useful Structure for Managers

What one-on-one notes are for

A recurring one-on-one is a place to discuss work that may not fit into a project status meeting: priorities, obstacles, feedback, decisions, development goals, and support. Notes can create continuity from one conversation to the next, especially when an issue needs a follow-up or a decision changes. They are not a transcript of everything said and should not be treated as a full record of a person’s performance.

The purpose is mutual. The report may want a record of manager commitments; the manager may need to remember a blocker or decision; both people may want to review an open topic. A template that is owned only by the manager can feel like unilateral monitoring. Agree on who can see and edit the notes, how the other person can correct them, and what is intentionally excluded.

Keep the 1:1 distinct from other systems. A project task should live in the project tracker; a formal performance or HR record should follow the organization’s approved process. The notes can point to those records without copying sensitive detail into a personal document or a meeting assistant.

A flexible 1:1 notes template

Meeting details: date; participants; intended duration; and whether the notes are shared. Do not record or transcribe automatically without checking the organization’s rules and telling participants as required. The title should be neutral and searchable without exposing sensitive information.

Check-in: What has changed since the last conversation? What is taking more or less attention than expected? Is there anything that should change the planned agenda? This is an invitation, not a mandatory personal disclosure. Allow the report to pass or redirect the topic.

Report-owned topics: What does the report want to discuss? What decisions, feedback, or support would be useful? Leave room for an agenda item to emerge during the meeting instead of forcing every conversation into a fixed script.

Manager support and decisions: What question needs a decision? What context or dependency is missing? What did the manager agree to do? State whether a decision is final, tentative, or waiting on another person. Add the source or related project link when it helps.

Growth and workload, when relevant: What is going well? What skill or opportunity would the report like to develop? Is workload sustainable for this period? Keep the conversation specific and work-related; do not infer motivation, health, or personal circumstances from silence or tone.

Follow-ups: action; one accountable owner; due date or review trigger; status; and where the work will be tracked. Add only agreed actions. If no task was agreed, do not manufacture one to fill the section.

Next conversation: open question; topic to revisit; preparation needed; and any note either person wants removed or corrected. A short reminder is often more useful than a complete narrative.

How to use the template in the conversation

Before the meeting, share the agenda in a place both people can edit. The report should have the first opportunity to add topics. The manager can add a brief work update or decision needed, but should avoid filling the agenda with a list of evaluations. If there is nothing important to discuss, shortening or cancelling the meeting can be a reasonable choice.

At the start, confirm the priority for that session and whether either person wants a topic kept out of the notes. During the conversation, write concise phrases rather than trying to capture every sentence. Ask before recording a sensitive detail or a personal disclosure. If a note could be interpreted as a commitment or judgment, read it back in plain language.

At the close, summarize decisions and actions together. For each action, confirm the owner and due date or trigger. Ask whether the written note reflects the conversation accurately. A brief correction at the meeting is easier than discovering later that an inference was written as a promise.

Afterward, send or share the note in the agreed place. Link to the official work item when one exists. Review access before sharing beyond the participants. For the next 1:1, bring forward only unresolved topics that are still relevant; mark completed or superseded items so old context does not appear current.

Example: turn an open concern into a clear next step

Suppose a report says a project dependency is delaying a design review. A weak note might say “project is blocked; needs to be more proactive.” That sentence mixes a status claim with a judgment and does not specify what help is needed. A clearer record might say: “Design review depends on updated API guidance. Jordan will ask the platform lead for an owner by Wednesday; Casey will revisit the timeline in Friday’s project sync.”

The clearer note names the dependency, separates the two actions, and provides a follow-up point. It does not claim that the report caused the delay or that the dependency is resolved. If the plan changes, update the status and preserve what changed rather than silently overwriting history.

This scenario is an illustrative example, not a ProfMe customer story. In a real team, record only what the participants agree belongs in the shared note and keep project execution in the system that owns the work. Sources: ProfMe Professional Memory

Keep the conversation supportive and balanced

A template can make a meeting predictable, but the manager’s behavior determines whether it feels safe and useful. Make room for the report’s agenda, follow through on manager-owned commitments, and avoid using notes as a substitute for listening. If feedback is difficult, describe specific work and impact rather than assigning a fixed trait to a person.

Do not assume a quiet meeting means a person has nothing to say. Offer more than one way to contribute, including sharing an agenda item beforehand or following up in writing. Ask open questions and avoid turning every answer into a task. The note should reflect an agreed next step, not create an obligation simply because a topic was raised.

When the discussion concerns a sensitive health, family, discrimination, or conduct issue, pause before placing detail in routine meeting notes. Follow the organization’s relevant policy and support pathway. Keep only the minimum information needed for the next step, and use the appropriate confidential channel.

Access, privacy, and retention

Decide whether notes are private to each participant, shared between the two, or stored in a managed team space. There is no universal answer; organizational policy and the conversation’s purpose matter. Make the choice visible before the meeting and do not promise confidentiality that the system or policy cannot provide.

Use access controls that match the content. A shared notebook may sync to an account with broader administrators; a transcript may be visible to a vendor or workspace owner; a copied action may enter a project tool. Understand the full path before using a new app. Set a retention period that matches the actual need, and remove stale notes when they no longer help.

If an AI meeting assistant is involved, check capture method, participant notice, recording/transcription settings, data access, retention, model processing, sharing behavior, and deletion. ProfMe’s AI and recording notice explains that the user is responsible for appropriate notice and consent. Product availability, permissions, and data handling should be checked against the current release and policy. Sources: ProfMe AI and recording notice

What to avoid putting in routine 1:1 notes

Avoid speculative labels such as “not committed,” “difficult,” or “low potential” without a specific, relevant, reviewable basis. A note can follow a person across conversations and distort future interpretation. Describe an observable work event and its effect, then give the person a chance to add context.

Avoid personal details that are not needed for work continuity. A participant may volunteer a private explanation, but that does not mean it belongs in a shared notebook. Ask what, if anything, should be recorded and who needs access. Follow the organization’s policies for confidential or regulated information.

Avoid copying full transcripts into a personnel file by default. Transcripts capture tangents and speech errors that are easy to misread outside context. If an official record is required, use the approved process, inform participants, preserve source context, and limit access to appropriate reviewers.

Avoid using the note as a hidden scorecard. If you are evaluating work, make expectations and feedback explicit through the organization’s normal management practice. Routine one-on-one notes should support continuity, not surprise someone with an undocumented judgment later.

When AI can help—and where it should stop

AI can help prepare a short agenda from recent, permitted work context or suggest candidate action items from a meeting transcript. These suggestions need participant review. The system may assign a task to the wrong person, miss a condition, or make an exploratory idea sound agreed. Do not treat generated tone analysis or personality scoring as a substitute for conversation.

A practical prompt is: “Draft a shared recap with only explicitly agreed work decisions and actions. For each action include the owner and due date if stated; label missing details as unspecified; keep personal topics out; include source links.” Review the draft with the other participant before treating it as the record.

ProfMe describes meeting preparation and search across saved meeting context. A user may find those workflows useful for recalling an agreed open thread, but ProfMe does not replace a manager’s judgment, HR processes, or a shared 1:1 agreement. Verify product behavior and access settings before including sensitive conversations. Sources: ProfMe privacy policy

Make the template fit your working relationship

Try the template for a few meetings and ask both participants what helped, what felt intrusive, and what information was missing. Remove sections that produce busywork. Add a role-specific section only when it serves a recurring need—for example, coaching topics for a new manager or customer escalations for a support lead.

Keep a small set of shared conventions: how to mark an open question, how to signal a tentative decision, who confirms a follow-up, and how to correct or remove a note. These conventions reduce ambiguity more effectively than a long form with many required fields.

A good 1:1 note is short enough to use, clear enough to resume the work, and respectful enough that both people know what it contains. The template is a starting point; the participants should decide how it serves their relationship and team policy.

Frequently asked questions

Sources and further reading

Original research and product documentation are labeled separately.

• Official documentation Otter Meeting Types: tailored summaries for common meetings
• Official documentation Granola 101: meeting notes, templates, and settings
• ProfMe documentation ProfMe privacy policy
• ProfMe documentation ProfMe meeting capture
• ProfMe documentation ProfMe Professional Memory
• ProfMe documentation ProfMe AI and recording notice

Article ID: one-on-one-meeting-notes-template · Canonical publication URL: https://www.profme.in/blog/one-on-one-meeting-notes-template · Author: Satish Rajnale, Senior AI Product Engineer