Copy a meeting recap, request an owner, correct a detail or share promised material. Separate decisions from proposals before sending.
These are plain-text examples. Replace bracketed labels yourself, or add real fields with PhraseShelf’s visual editor. They are not executable template syntax.
Record a decision and its owner.
Subject: [project] — decisions and next steps Hello [name], Our decision was [agreed decision]. Next action: [action] — [agreed owner] — [agreed date]. Still open: [question]. Please flag anything I have misunderstood.
Remove the date if none was agreed. Keep open questions separate from decisions.
Resolve an unassigned action.
Hello [name], We discussed [action] in the meeting, but did not settle who would take it forward. Could you confirm the owner and suggest a realistic date? I’ll update the recap once that is clear.
Ask for ownership; do not assign a person who has not agreed.
Make a specific correction easy to find.
Hello [name], A correction to my recap of [meeting]: [old detail] should read [correct detail]. This changes [affected next step]. The other points remain as recorded. Thank you for checking this.
State whether the correction changes an action. Do not silently resend a different summary.
Connect a resource to the discussion.
Hello [name], Here is the [resource] we discussed: [link]. The relevant part is [section]. Could you review [specific point] and let me know [question]? Thank you.
Check permissions and identify the exact section, rather than sending an unexplained link.
Read your notes once for decisions and once for unfinished questions. A useful recap names the action, the person who agreed to it and the agreed date. If no date or owner was agreed, ask instead of inventing one.
Use a subject such as “Cedar project — decisions and next steps”. Keep the summary short enough for the recipient to spot a correction. A sales check-in without meeting decisions belongs in the sales collection.
Start with the recap below and save it as ;recap. Create fields for the project and action summary only when the same structure recurs. Keep a proposed date visibly separate from a confirmed date.
Before sending, verify file access, recipients and the wording of decisions. PhraseShelf prepares your words; it does not record a meeting, assign work or send invitations.
Copy an example, choose New snippet, give it a title and enter its suggested alias in Shortcuts and aliases. Paste into Plain text, edit the details, then choose Save snippet. Test it in Help & practice with the alias followed by Space.
For changing details, replace each bracketed label with a real field in the visual editor. Keep punctuation in the adjacent text segments. Preview a short and a long answer, then review the final message before using it. Choose a different alias if the suggestion already exists in your library.