1. Preserve the starting version
When changing meeting notes, first preserve the version that participants previously received or approved. Record its date, location, owner, and meeting identifier. If the tool supports named versions, create one before editing. A downloaded copy can be useful when platform history is limited, but it should be stored with the same access controls as the notes.
2. Capture the reason for the change
Write a short change request that identifies the disputed or incomplete passage, the requested correction, the requester, and the evidence supporting it. Useful evidence can include the agenda, an approved decision record, an assigned action, or a follow-up message from the decision owner. Avoid retaining unrelated chat or a full recording merely to support a narrow correction.
3. Use platform history carefully
Google Docs version history can show who updated a file and what changed, and it allows an editor to name, copy, or restore an earlier version. Microsoft 365 version history can display, compare, and restore earlier versions of files stored in OneDrive or SharePoint. Record which history feature was checked and when. Do not assume every file type or storage location has identical history.
4. Separate corrections from reinterpretations
A spelling fix, corrected date, or missing attendee is different from changing a decision or action owner. For a substantive change, preserve the prior wording, proposed wording, approver, approval date, and rationale. If participants disagree, mark the point unresolved rather than silently choosing one account.
5. Protect the authoritative record
Name the person allowed to approve substantive edits and the location of the current approved notes. Restrict editing after approval when the tool and workflow allow it. If a new version supersedes the old one, add a visible revision note and keep the previous approved version available under the applicable retention policy.
6. Notify the right participants
Send a concise notice when a change affects a decision, deadline, owner, commitment, or compliance record. Include the meeting date, changed section, approval source, and link to the current version. Routine punctuation fixes usually do not require broad redistribution unless local policy says otherwise.
7. Minimize sensitive evidence
Keep only the material needed to support the change. Redact unrelated personal information from an attachment when permitted, and do not copy private side conversations into the notes. Access to the change evidence should be no broader than access to the underlying meeting record.
8. Close with a verification check
Confirm that the current notes contain the approved wording, the old version remains recoverable where required, links point to the authoritative file, and affected action owners received the update. A useful change entry contains the timestamp, editor, approver, before-and-after summary, supporting evidence, and verification result.
Sources
- See changes to your files in Drive and Docs — Google Docs Editors Help
- View previous versions of Office files — Microsoft Support