Flownote resourcesTemplates
One-on-One Meeting Notes Template for Managers and Reports
Published Reviewed
By Flownote EditorialOriginal Flownote template
Flownote resourcesTemplates
Published Reviewed
By Flownote EditorialOriginal Flownote template
Short answer
A good 1:1 note has five parts: a check-in, the report’s priorities, the manager’s topics, decisions or commitments, and questions for next time. Keep the shared record concise, agree on what is documented, and separate sensitive manager-only records from collaborative notes.
| Usually useful in shared notes | Use care or a separate approved process |
|---|---|
| Agreed priorities and support | Medical, family, or other deeply personal information |
| Specific commitments and dates | Unverified allegations or speculative judgments |
| Feedback both people agreed to revisit | Formal performance or employee-relations records |
| Growth goals and opportunities | Information the employee expected to remain off the record |
Shared notes should not become a hidden dossier. If the company requires performance, accommodation, investigation, or HR documentation, use its authorized system and policy rather than improvising inside a meeting-notes document.
Copy and edit
Check-in — Morgan wants more uninterrupted time for the launch brief.
Win — Stakeholders approved the first prototype.
Blocker — Two review meetings overlap with writing time.
Decision — Avery will consolidate the reviews into one session next week.
Commitment — Morgan will share the launch-brief outline by Aug. 19.
Growth — Morgan will present the next research readout; Avery will review the draft.
Next time — Discuss feedback on the presentation outline.
Note — The names and situation are fictional.
Both people add topics. The manager reviews prior commitments and prepares context or feedback.
Start with the report’s priorities, spend time on the highest-value issue, and state commitments clearly.
Read back decisions, actions, owners, and dates. Confirm what will be included in the shared note.
Review the draft, remove unnecessary sensitive detail, and give both people access to the agreed record.
Begin with open commitments and questions instead of rebuilding context from memory.
If both people are comfortable and policy allows it, select Flownote’s 1:1 output style before capturing. Review the transcript and generated note together, especially any sensitive or evaluative language, and edit the shared version down to what is useful.
A durable agenda has recurring prompts but leaves room for what matters this week. Invite both people to add topics before the meeting, and do not use the template as a checklist that forces a personal conversation into every category.
| Theme | Useful prompt | What the note should preserve |
|---|---|---|
| Priorities | What deserves your attention before our next 1:1? | The report’s actual priorities and any tradeoff the manager approved |
| Blockers | Where are you waiting on a decision, resource, or relationship? | The obstacle, support needed, and named follow-up |
| Feedback | What should I continue, change, or explain better as your manager? | Specific agreed feedback and the next behavior to revisit |
| Growth | Which skill or responsibility would you like to practice next? | An opportunity, support, and a realistic checkpoint |
| Sustainability | What is making the work harder than it needs to be? | Work-related changes the pair agreed, without unnecessary personal detail |
Review only commitments and topics intentionally carried forward, not the full history.
Mark work complete, change the date with context, or explicitly drop an item that no longer matters.
Add the decisions, support, and follow-ups from the current conversation.
Carry unresolved questions and future topics into the next agenda so they do not disappear.
Archive older notes according to policy and keep the current working view focused on active context.
Copying every prior note into the next document creates a long record nobody reads. Continuity comes from deliberately carrying forward open work, not preserving every sentence in the active agenda.
Explain what the tool captures, what output you want, who can access it, and the manual alternative.
Use the recording to reduce note-taking burden and preserve agreed follow-up—not to silently evaluate tone, emotion, or employee sentiment.
Correct speaker attribution and remove generated language that adds judgment or certainty the conversation did not contain.
Keep commitments, support, and context both people need. Move any required formal record through the approved channel.
Give the report access to the shared note and a straightforward way to change anything that misstates the conversation.
Put the guide to work
Flownote creates a transcript, structured notes, decisions, and follow-ups for you to review. Move the approved details into the template instead of rewriting the meeting from scratch.
A concise shared record of topics and commitments is often useful. Private reflections or records governed by HR policy should live in the appropriate separate system.
No. Consider consent, power dynamics, sensitivity, policy, and whether a recording is necessary. Manual shared notes are a valid default.
Long enough to preserve decisions, commitments, and the context needed next time. It should not be a transcript unless there is a specific authorized reason to keep one.
Both people should be able to add topics, with meaningful space for the report’s priorities. The manager remains responsible for bringing needed context, feedback, and follow-through.
This template does not recommend doing so. Use AI, if agreed and approved, to draft factual notes and follow-ups. Avoid inferring emotion or performance from a recording without a legitimate, governed process.
Try Flownote with your next meeting. It's free to get started.