Notion AI prompts for meeting notes you actually pasted

Pull action items from these pasted notes into a Notion checklist for [PROJECT]. Notes: [PASTE MEETING NOTES]. One item per line in the form Owner, Task in 12 words, Due date. Copy owner names and dates only if they appear. If a task has no owner, write [VERIFY] in Owner. If a task has no date, write [VERIFY] in Due date. Do not invent a person or a Friday. Limit to 12 items. End with a count of items that still need an owner.

Hunt for commitments that have no owner in these notes. Notes: [PASTE MEETING NOTES]. A commitment is a will, I'll, we should, let's, or need to line. List each one with the exact phrase, the speaker if named, and a suggested owner only if that person already appears as doing similar work in the same paste. If you cannot suggest from the paste, write [VERIFY]. Do not invent a volunteer. Output a table with columns Phrase, Speaker, Suggested owner.

Sort the tasks in these notes into Ready to start and Blocked. Notes: [PASTE MEETING NOTES]. Project: [PROJECT]. A task is Blocked only if the notes name a dependency, a missing input, or a waiting-on person. Copy that blocker in 10 words. If the notes are silent on blockers, put the task in Ready and do not invent a blocker to sound careful. If a task is unclear, write [VERIFY] and leave it out of both lists. Max 8 per list.

Label each action in these notes as S, M or L using only cues in the paste such as this week, a quick ping, or a full rewrite. Notes: [PASTE MEETING NOTES]. Do not assign hours. If there is no size cue, write [VERIFY] instead of a letter. Inventing a day count would throw the sprint off. Return a table with columns Task, Size, Cue you used. Then list the three L items I should surface first in [NEXT MEETING].

I pasted notes from two meetings about [PROJECT]. Meeting A: [PASTE NOTES A]. Meeting B: [PASTE NOTES B]. Merge the action items into one Notion checklist. When the same task appears in both, keep the version with an owner and a date. When the wording conflicts, show both phrases and tag the row [VERIFY]. Do not invent a third wording to smooth them. Do not drop a task that appears in only one paste. End with a count of unique tasks.

Build a decision log from these notes for [MEETING NAME] on [DATE]. Notes: [PASTE MEETING NOTES]. Table columns: Decision in 15 words, Decided by, Date, Replaces if the notes say so, and Link to the triggering quote. Copy names and dates from the paste only. If a decision has no named decider, write [VERIFY] in Decided by. Do not invent a vote count. If something sounds like a leaning, put it under Leaning, not Decision. Max 10 decision rows.

For each decision in these notes, write a reversal risk note. Notes: [PASTE MEETING NOTES]. Decisions I see: [PASTE DECISIONS] or extract them if I left this blank, but only from the paste. For each, give: What we decided, What would reverse it according to the notes, and Who would have to change it if named. If the notes never say how to reverse it, write [VERIFY] and do not invent a governance step. Keep each note under 40 words.

Build an attendance block from these notes for [MEETING NAME]. Notes: [PASTE MEETING NOTES]. List Present, Mentioned but not present, and Unclear. Put a name in Present only if the notes show they spoke or were listed as attending. Put Unclear names under Unclear with [VERIFY]. Do not invent an attendee from a team name. Do not assume a Slack handle is a person unless the notes map it. Output as three Notion lists I can paste under the title.

Sort these notes into Explicit decisions and Implied decisions for [TOPIC]. Notes: [PASTE MEETING NOTES]. Explicit means someone said decide, go, approved, or we will. Implied means the group talked as if it were true. Copy a quote for each row. Tag every Implied row [VERIFY] because treating it as closed would invent a decision. Do not move an implied item to explicit. End with one question I should ask in the thread to turn the riskiest implied item into an explicit yes or no.

Find items in these notes that still need a vote or a written yes from [DECISION GROUP]. Notes: [PASTE MEETING NOTES]. List each item with the open question in 12 words, who already spoke, and who in the group has not spoken if the notes name the group. If the group roster is not in the paste, write [VERIFY] for missing names rather than inventing a voter. Do not invent a deadline. Output a short Notion callout I can drop at the top of the page.

Draft a recap email of about 120 words to [RECIPIENT GROUP] from these notes. Notes: [PASTE MEETING NOTES]. Include: 3 bullets of what we decided, 3 bullets of actions with owners if named, and 1 question. Keep the tone plain, no exclamation marks. If an owner or date is missing, write [VERIFY] in that bullet. Do not invent a decision to make the email feel finished. Put the subject line on its own first line, 8 words or fewer.

Write a channel post under 80 words for [CHANNEL NAME] based on these notes. Notes: [PASTE MEETING NOTES]. Lead with the one decision that changes work this week. Then two actions with owners if named. End with a link placeholder [PAGE LINK]. If there is no decision, lead with the open question and tag it [VERIFY]. Do not invent a win. Do not @ people who are not in the notes. Output only the post, ready to paste.

Draft a chase note of about 70 words to [PERSON NAME] about the task they took in these notes. Notes: [PASTE MEETING NOTES]. Task I think they own: [TASK]. Quote the line that assigns it. Ask one question: confirm owner, confirm date, or send the artefact. If the notes do not actually assign this person, stop, write [VERIFY], and do not invent an assignment. Keep it friendly and specific. No guilt. Output the note plus the quote on its own line.

Write text I can paste into a calendar hold for the follow-up of [MEETING NAME]. Notes: [PASTE MEETING NOTES]. Length I can book: [HOLD LENGTH]. Include purpose in 20 words, required people only if named as owners of open items, and the two questions we must answer. If the notes never asked for a follow-up, write [VERIFY] and do not invent a meeting. Do not add optional attendees from thin air. Output title, body, and required list as three blocks.

Rewrite these internal notes as a customer-safe recap for [CUSTOMER NAME] at [CUSTOMER ROLE]. Notes: [PASTE MEETING NOTES]. Public facts I may share: [PASTE PUBLIC FACTS]. About 100 words, plus 3 next steps if they appear in the public list. Strip staff debate, cost, and any name not on the public list. If a next step would need an internal date, write [VERIFY] and drop that step. Do not invent a promise. Inventing a delivery date they did not hear would break trust.

Diff this week's notes against last week's notes for [STANDUP OR RITUAL]. This week: [PASTE THIS WEEK]. Last week: [PASTE LAST WEEK]. Return three lists: Still open from last week, New this week, and Done because it disappeared and last week marked it done. If a disappeared item was never marked done, put it in Missing and tag [VERIFY]. Do not invent a done state. Do not assume silence means shipped. Limit each list to 8 lines.

Compare these notes to our standing agenda for [MEETING NAME]. Standing agenda: [PASTE AGENDA]. Notes: [PASTE MEETING NOTES]. Mark each agenda item Covered, Skipped, or Unclear. For Skipped, copy the nearest line that shows we moved on, or write [VERIFY] if the notes never mention it. Do not invent a reason we skipped. End with a suggested agenda for next time that drops two items we never cover and adds one open question from the notes.

Find issues that repeat across these pasted notes from several meetings about [TOPIC]. Notes pack: [PASTE SEVERAL MEETINGS]. List each repeating issue with: phrase variants, how many pastes it appears in, and the last owner named if any. If a count is unclear because the paste is messy, write [VERIFY] rather than inventing a frequency. Do not invent a root cause. Output a table sorted by how often the issue appears, max 8 rows, plus one question for the next meeting.

From these pasted attendance rolls for [MEETING NAME], build a pattern table. Rolls: [PASTE ATTENDANCE LINES]. Columns: Name, Meetings present as written, Meetings listed absent as written, and Unclear. Copy only what the rolls say. If a name appears once with no present or absent mark, write [VERIFY]. Do not invent a percentage. Do not recommend firing or replacing anyone. End with two names whose status is Unclear so I can check the invite.

Find carry-over items that have aged across these dated notes for [PROJECT]. Notes: [PASTE DATED NOTES]. An item is aged if it appears in more than one dated paste and is still open. For each, give first seen date, last seen date, and last named owner. If a date is missing, write [VERIFY] and do not invent a week. Do not invent a reason it stalled. Sort oldest first. Max 10 items. End with one line I can paste as a meeting opener.

Turn these notes into a one screen recap for [EXEC ROLE]. Notes: [PASTE MEETING NOTES]. Sections: What changed, Decision we need, Risk if we wait, and Ask in one sentence. Max 120 words total. Use only facts in the paste. If the ask is not in the notes, write [VERIFY] in Ask and do not invent a budget or a headcount. Do not add a metric the notes lack. Output as Notion headings I can pin at the top of the page.

Rewrite these notes so a new hire on [TEAM NAME] can follow [PROJECT] without the backstory. Notes: [PASTE MEETING NOTES]. Add a 40 word context blurb using only terms defined in the paste. Then a glossary of acronyms that appear, with a plain phrase if the notes define them, or [VERIFY] if they do not. Then the summary. Do not invent a definition. Do not invent history from before the paste. Keep the whole page under 250 words.

Create a partner-safe version of these notes for [PARTNER NAME]. Notes: [PASTE MEETING NOTES]. Shareable facts: [PASTE SHAREABLE FACTS]. 8 bullets max, plus 2 joint next steps only if they appear in the shareable list. Strip roadmap dates, costs, and third parties. If a joint step has no date in the shareable list, write [VERIFY] and keep the step without a date. Do not invent a joint win. Output a Notion page body I can duplicate into a shared workspace.

Split these notes into an engineering cut and a sales cut for [LAUNCH OR TOPIC]. Notes: [PASTE MEETING NOTES]. Each cut is 6 bullets. Engineering gets constraints, bugs, and owners of technical next steps. Sales gets customer-facing changes, dates we can say, and open questions from buyers if the notes include them. If a date is internal only, write [VERIFY] and keep it out of the sales cut. Do not invent a customer quote. Do not copy the same bullet into both cuts.

Build an FAQ from questions in these notes that nobody answered. Notes: [PASTE MEETING NOTES]. Meeting: [MEETING NAME]. List up to 7 questions copied as asked. Under each, write Answer not in notes and [VERIFY], unless the same paste later answers it, in which case copy the answer in 25 words. Do not invent an answer to look helpful. End with a suggested owner for collecting answers only if that person is named as following up in the notes.