NotebookLM prompts for meeting packets from your uploads

Build a timed agenda for [MEETING NAME] lasting [MEETING LENGTH] using only uploaded notes and the invite if present. Output a table: Block, Minutes, Goal, Source file. Minutes must add up to the length I gave. Pull block names from the files. If the files never give a length for a topic, write [VERIFY] in Minutes and do not invent a timebox. Do not invent a topic the files do not mention. End with the one block I should cut if we start late.

Split the uploaded packet for [MEETING NAME] into Must decide in the room and Inform only. For each item: 12 word statement, source cite, and why it is in that bucket in 10 words. Inform only means the files already record a decision or are FYI. If you cannot tell, write [VERIFY] and put it in Unclear. Do not invent a decision to shrink Must decide. Do not invent an FYI to protect someone's feelings. Cap each bucket at 6. Audience: [AUDIENCE].

Extract a parking lot for this meeting from uploaded notes of prior meetings on [TOPIC]. List each parked item with: first seen file, last seen file, last named owner if any, and whether this meeting's files pick it up. If an owner is unnamed, write [VERIFY]. Do not invent a future meeting to send it to. Do not invent a done state because it disappeared. Sort oldest first. Max 8 items. End with 2 items that belong on today's agenda if the files still call them open.

Write a chair opening card for [MEETING NAME] that the chair can read in 45 seconds. Use only uploaded sources. Include: purpose in 20 words, the decision we must leave with if the files name one, the timebox, and the one clash to name up front if the files show one. If the decision is not in the files, write [VERIFY] and open with the open question instead. Do not invent a joke. Do not invent attendance. Output as 4 labelled lines.

If [MEETING NAME] starts [MINUTES LATE] late, how should the chair cut the uploaded agenda? Using only the files, rank remaining items Must keep, Can move to notes, and Can drop. Give minutes that still fit the remaining slot. If the files never rank importance, write [VERIFY] on ranking and keep only items the files call a decision. Do not invent a new agenda. Do not invent extra time. Return a 6 line rescue plan the chair can follow without debate.

Using only uploaded memos, build an options table for [DECISION] at [MEETING NAME]. Columns: Option name as the files write it, What it is in 20 words, Who supports it if named, Risks the files name, Missing input. Cite the file in each cell. If a cell has no source, write [VERIFY]. Do not invent an option. Do not invent a score. Do not pick a winner unless a file already does, and then quote it. Max 4 options.

Compile a bring-in decision log from uploaded notes for [PROJECT] so [MEETING NAME] does not relitigate closed items. Table: Decision, Date if present, Decided by if named, Source file, Still open yes or no. Copy wording from the files. If a line sounds decided but no one is named, write [VERIFY] in Decided by and mark Still open yes. Do not invent a vote. Do not invent a date. Max 12 rows. End with 3 items this meeting should not reopen unless new files appear.

List risks the uploaded files already name for [DECISION] at [MEETING NAME]. For each: risk in 15 words, file cite, who the files say owns it if anyone, and the mitigation the files already wrote. If a risk has no owner or no mitigation, write [VERIFY] in that cell. Do not invent a new risk to look diligent. Do not invent a likelihood. Sort by how many files mention the risk. Max 8. Audience: [AUDIENCE].

Build a missing input checklist for [DECISION] from the uploaded packet. An input is missing if a file says we need it and it is not in any uploaded source. For each: input, which file asked for it, who the files say should bring it, and [VERIFY] if the person is unnamed. Do not invent an input the files never asked for. Do not invent a deadline. Output a checklist the chair can read at the start. If the packet already has every asked input, say so in one line.

Create a vote card for [DECISION GROUP] on [DECISION] using only options the uploaded files name. For each option: the name as written, a 12 word restatement, and a blank line for yes, no, or abstain. If the files name a voting rule, copy it. If they do not, write [VERIFY] and do not invent majority, consensus, or a chair break. Do not add an option. Do not add a voter who is not in the files. Output as a one page card.

Build a 2 page exec skim pack for [EXEC ROLE] joining [MEETING NAME]. Use only uploaded sources. Page 1: decision, options, ask, in 120 words with cites. Page 2: the three clashes or risks the files name. If the ask is not in the files, write [VERIFY] and lead with the open question. Do not invent a metric. Do not invent a recommendation. Keep file names visible so they can click through. This is a packet, not a stand-alone briefing they will never open the sources from.

Create a first time attendee pack for [NEW PERSON ROLE] at [MEETING NAME]. From uploaded sources only: 80 word context, glossary of terms used in more than one file, who usually attends if the files list them, and the decision on the table. If context before the uploads is needed, write [VERIFY] and do not invent history. Do not invent a seating chart. Do not invent nicknames. Keep the pack under 250 words plus the glossary. End with 3 questions they can ask without looking lost.

Produce a vendor-safe packet for [VENDOR NAME] attending [MEETING NAME]. Uploaded sources include internal notes. Shareable facts I allow you to treat as public: [PASTE SHAREABLE FACTS], plus any uploaded file labelled public. Strip costs, staff names not in the shareable list, and roadmap dates. If a remaining slide would be empty, write [VERIFY] and drop it. Do not invent a joint win. Do not invent a promise. Output a cover, 5 body sections, and a next step only if the files already record one with them.

Split the uploaded packet for [MEETING NAME] into an engineering cut and an ops cut. Each cut is 6 sections. Engineering gets constraints, incidents, and technical owners the files name. Ops gets process, staffing the files name, and customer-facing dates the files call public. Do not copy the same section into both. If a date is internal only, keep it out of the ops cut and write [VERIFY] if you cannot tell. Do not invent an owner. Do not invent an incident.

Build a catch-up packet for [ABSENT PERSON] who missed [MEETING NAME] and must act this week. Use only uploaded notes from that meeting and prior files they already had. Include: 3 decisions, 3 actions that name them if the files do, 2 items they can ignore, and 1 question to reply to. If they are not named as owner, write [VERIFY] and do not assign them work. Do not invent a tone of blame. Keep it under 200 words so they read it.

After [MEETING NAME], turn the uploaded notes into a decision and action packet. Sections: Decisions with cites, Actions with owner and date only if named, Open questions, and Links to source files. If an action has no owner, write [VERIFY] in Owner. Do not invent a decision that the notes only leaned toward. Do not invent a due date. Keep the packet under 250 words plus a table. End with a 40 word version I can paste into the calendar invite for next time.

From uploaded notes of [MEETING NAME], map who heard what. For each named speaker: topics they spoke on, commitments they made, and questions they asked, each with a short quote. If a name appears only in the attendee list and never speaks, put them under Silent and write [VERIFY] for any task later assigned to them. Do not invent a speaker. Do not invent a quote. This packet is for the chair, not for public shaming. Max 12 names.

Create a follow-up packet for [OWNER NAME] from uploaded notes of [MEETING NAME]. Include only actions the notes assign to them, each with the quote, any date, and the file cite. If the notes never assign them that task, write [VERIFY] and omit it. Do not invent extra work to make them look busy. Do not invent a status. Add a 30 word reply they can send to confirm. Keep the pack to one screen.

Rewrite uploaded internal notes of [MEETING NAME] as customer-safe minutes for [CUSTOMER NAME]. Public facts I allow: [PASTE PUBLIC FACTS], plus any upload labelled customer. About 120 words, 3 next steps only if they appear in the public set, and no staff debate. If a next step needs an internal date, write [VERIFY] and drop the date. Do not invent a promise. Do not invent a quote from the customer. Output a packet cover line plus the minutes.

From uploaded notes of [MEETING NAME], draft a stub packet for the next invite. Include: purpose in 20 words, 3 leftover decisions, 2 reading items that were skipped, and a proposed length only if the files say we need another slot. If no leftover decision exists, write [VERIFY] and recommend cancelling rather than inventing a meeting. Do not invent attendees. Do not invent a date. Output title, body, and required reading as three blocks the organiser can paste.

Look at uploaded packets from the last meetings of [RITUAL NAME]. Propose a standing packet template: cover fields, required files, agenda blocks, and recap fields. Copy labels from the files when they repeat. If a field appeared only once, write [VERIFY] and keep it optional. Do not invent a field the files never used. Do not invent a metric the ritual does not already record. Output as a checklist the organiser can duplicate each week. Audience: [AUDIENCE].

Diff this week's uploaded packet against last week's for [RITUAL NAME]. This week files versus last week files. Return: Still open, New, Resolved because a file marks it done, and Missing. If a disappeared item was never marked done, put it in Missing and tag [VERIFY]. Do not invent a resolved state. Do not invent a trend. Limit each list to 8. End with a 40 word opener the chair can read that names the oldest still open item.

From uploaded examples of [RITUAL NAME], list what should always be in the packet and what should never be. Always in: items that appear in every uploaded example. Never in: items the files call parking lot, confidential, or out of scope. If an item appears in some weeks only, write [VERIFY] and put it in Sometimes. Do not invent a never-in rule from taste. Do not invent a compliance requirement. Output three lists plus a one line rule for the organiser.

Find decisions that have stayed open across uploaded packets for [PROJECT]. For each: first file, last file, last named owner, and the question still open in 12 words. 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. End with a packet page the chair can print: three oldest questions, each with a 15 word yes or no the room can vote on if the files already frame it that way.

I run more than one ritual. Uploaded packets include [RITUAL A] and [RITUAL B]. Tell me which packet sections belong only in A, only in B, and in both. Use only the uploads. If a section would confuse guests if copied across, say so and cite the file that shows the mismatch. If you cannot tell, write [VERIFY]. Do not invent a third ritual. Do not invent a section to make the kits look even. Output as two checklists plus a shared core of at most 4 items.