Prepare meeting notes for a new user by giving them one dependable place to find the agenda, decisions, and follow-up work. The goal is not to document every sentence. It is to make the result of the meeting understandable to someone who returns later.
Build one small template
Use a shared document with these sections: meeting purpose, date and attendees, agenda, key facts, decisions, action items, parking lot, and links to supporting material. Give every action an owner, a due date or review date, and a status. If a decision replaces an earlier one, link to the earlier record instead of silently overwriting it.
Keep the template short enough that the new user can complete it during a real meeting. Optional fields can live below the main sections. A complicated form usually encourages people to take private notes and copy them later, which creates delay and competing versions.
Set access before the meeting
Decide who can edit, comment, or only view the notes. Microsoft Teams meeting notes can hold an agenda, notes, and tasks, and can be edited collaboratively; Microsoft also warns that people who were not directly invited, including external attendees in some situations, can have limited access. That makes an access check part of preparation, not an afterthought.
If the notes live in Google Docs, use sharing roles deliberately. Google's documentation distinguishes editor, commenter, and viewer access, and its version history can show earlier versions and who changed a file. These controls are useful for correcting an error without turning the notes into an untraceable replacement document.
Demonstrate the whole cycle
Before handing the process over, run one sample meeting. Show the new user how to open the note, capture a decision in neutral language, create an action with an owner, add a source link, and close the meeting. Then show how to find the note from the calendar or project space, how to review comments, and how to inspect version history.
Close and archive consistently
At the end, read back decisions and actions. Mark unresolved questions instead of guessing. After the meeting, correct obvious formatting, notify action owners through the agreed channel, and move the note to the expected folder or workspace. Do not duplicate it into several systems unless one is clearly the authoritative record.
A good handoff leaves the new user able to answer four questions without help: Where are the notes? Who can change them? What was decided? What happens next?
Sources used
- Microsoft Support: Take meeting notes in Microsoft Teams
- Google Workspace Learning Center: Google Docs cheat sheet
Sources
- Take meeting notes in Microsoft Teams — Microsoft Support
- Google Docs cheat sheet — Google Workspace Learning Center