How to summarize meeting notes before sharing them with your team
Select the rough notes in an editable field, open the Lightphrase wheel with Win+Ctrl+R, and choose Summarize. Keep a copy of the original first. Review the shortened version before sharing, especially where the notes distinguish a decision from a proposal or identify who agreed to do something.
Keep the source notes before you shorten them
Make a separate copy of the rough notes so that you can compare the summary after replacement. Select the agenda section or passage you want summarized. If you select only part of the meeting, keep the scope clear when you share it; a summary of one topic is not a record of the entire discussion.
Hold Win+Ctrl+R, or your configured shortcut, choose Summarize, and complete the action. Summarize normally replaces the selection in an editable field and restores the previous clipboard. If the target cannot be edited reliably, the result may be copied instead. Inspect a reported copied result in an editable draft before using it.
The action shortens the selection; it does not establish what the participants agreed to. Keep the original names, dates, and qualifications available as you decide what belongs in the shareable summary.
Preserve who said what and what remains undecided
A proposal can be important without being a decision. Keep the proposer’s name when attribution matters, and retain an explicit statement that no decision was made. A confirmed owner belongs with the action they accepted, including any date attached to that action.
In this example, Priya reports a missing review, Dev proposes a new date, and Marcus accepts a follow-up task. The summary retains those different roles instead of assigning every item to the person who mentioned it.
Before
Rough notes: Priya said the launch checklist is missing the accessibility review. Dev proposed moving the beta to the 14th, but no decision was made. Marcus will ask support to list the top five setup issues by Friday. Open question: do we need a separate sign-off for the help center?
After
Priya: accessibility review missing from the launch checklist. Dev proposed moving the beta to the 14th; no decision was made. Marcus will ask support for the top five setup issues by Friday. Open question: is a separate sign-off needed for the help center?
Separate the record into useful categories
After checking the shortened text, organize it into decisions, proposals, confirmed actions, and open questions where those categories help. You do not need every category for every meeting. An empty category is preferable to inventing a decision just to fill out a template.
A scheduled review is different from a decision about the subject being reviewed. Likewise, an unanswered question is different from a question that someone has already been asked to investigate. Preserve that distinction so a teammate does not assume an inquiry is underway.
Use a person’s name only for the role supported by the notes. Someone who suggests a change has not necessarily agreed to implement it. When an owner or deadline is missing, leave it unassigned until the team confirms it.
Before
Rough notes: The budget review is set for the 3rd. Sam proposed cutting the training line. The team did not decide. No one has asked finance whether the cut is allowed.
After
Budget review: set for the 3rd. Proposal: Sam suggested cutting the training line; the team did not decide. Open issue: No one has asked finance whether the cut is allowed.
Check what the shorter version leaves out
Compare the summary with the original notes item by item. Check numbers, dates, names, conditions, negations, and commitments. Then look for omissions: a sentence can be accurate while the summary as a whole leaves out a blocker that affects the team’s next step.
Pay particular attention to not approved, proposed, pending, and similar qualifiers. If a summary drops one, restore it from the notes. If the notes themselves are unclear, mark the uncertainty or ask the participants for clarification rather than writing a definite outcome.
Keep the summary’s purpose in mind. A brief update may omit conversational detail, but it should retain the information that changes what the team can do next. Put confirmed actions where readers can find them and keep unresolved items visibly unresolved.
Share the reviewed summary with the right scope
Read the edited summary once without the original beside it. Check whether a teammate could mistake a suggestion for an instruction, or interpret an open question as a completed task. Add a clear label when the summary covers only one agenda topic.
Keep the source notes with your meeting record according to your team’s process. The selected text is processed remotely when you use an action, so follow your organization’s rules for meeting material before submitting it. Neither a shorter format nor a polished sentence substitutes for checking what was actually recorded.
Take it into your next draft
Keep the original notes, summarize the intended selection, and compare the result before sharing. Preserve attribution, dates, undecided proposals, and confirmed actions. Leave missing owners and unresolved questions open rather than filling them in during the edit.