The 2-Prompt Quick Win

Meeting notes are where decisions go to die. You leave the call with something agreed upon, someone types up a loose summary, it gets posted somewhere, and two weeks later half the team is working from different assumptions about what was actually decided.

The problem isn't the notes. It's the conversion step — turning a raw transcript or summary into a structured brief that everyone can actually execute from. That step requires judgment, formatting, and follow-through. All three are things AI handles well.

This workflow takes five minutes. You put in meeting notes, you get out a project brief. No interpretation gaps, no missing owners, no deadlines that were "mentioned" but not formally assigned.

Most meeting participants are either running the meeting or thinking about their contribution to it. Nobody is optimizing for downstream clarity. So what gets written down afterward is usually a combination of: what was said, what the note-taker found important, and whatever half-thoughts got added in the thirty minutes after the call.

That output is not a brief. A brief needs decision statements (not discussion summaries), explicit owners (not "the team"), deadlines (not "sometime next week"), and a clear scope boundary (what is NOT included). Raw notes have none of this structure. AI can apply the structure if you give it a clear conversion prompt.

What you need: meeting notes, transcript, or even a rough audio-to-text output. Format doesn't matter — the prompt handles normalization.

Paste your notes into Claude with this prompt:

"These are notes from a [meeting type] meeting on [date]. Extract only the following: (1) Decisions made — stated as clear declarative sentences, not discussion points. (2) Action items — each with an explicit owner and a deadline. If an owner wasn't specified, flag it as 'owner: unassigned.' If a deadline wasn't specified, flag it as 'deadline: unset.' (3) Open questions — things that came up but weren't resolved. Format as three separate lists."

The instruction to flag unassigned owners and unset deadlines is the important part. Most meeting notes skip this because it's uncomfortable to document what wasn't resolved. AI doesn't have that discomfort. It will dutifully flag every gap, which is exactly what you want — a project brief that makes gaps visible rather than hiding them in vague language.

Take the output from Prompt 1 and run this second prompt:

"Using the decisions, action items, and open questions you just extracted, write a project brief in this format: Project name, date, 2–3 sentence summary, bulleted decisions list, action items table (Task | Owner | Deadline | Status), open questions list with who needs to answer each, and an Out of Scope section. If Out of Scope was not discussed, write: 'Not discussed — recommend clarifying before kickoff.' Keep it under one page."

The Out of Scope section is what separates a working brief from a document that causes scope creep. If it wasn't discussed in the meeting, the brief says so explicitly and flags it for follow-up. That one line prevents weeks of drift.

Here's the difference between raw notes and brief output.

Raw meeting notes: "Talked about the website redesign. Sarah is going to handle the homepage. Need to get it done before the launch. Jake mentioned the mobile version might need extra time. Budget wasn't finalized. Asked about SEO — nobody sure whose responsibility that is."

After the two-prompt workflow, you get a structured project brief with: homepage redesign assigned to Sarah with a pre-launch deadline, mobile version scoped separately and flagged for Jake, budget marked as blocked with no owner, and SEO ownership flagged as an open question requiring leadership input. Out of Scope: not discussed — recommend clarifying before kickoff.

That output took two prompts and ninety seconds. The original notes would have produced two weeks of "wait, what did we decide?" emails.

This matters most for meetings that produce cross-functional work — anything with multiple owners, multiple deliverables, or a hard external deadline. Sales calls, client kickoffs, product planning sessions, hiring committee meetings. Anywhere that "we'll figure it out" is a phrase that gets said.

For internal team syncs with a single owner and no dependencies, a simpler summary is fine. The two-prompt brief is for the meetings that will create confusion if not structured correctly — which, in most organizations, is most of the meetings that matter.

If you want the full operator brief template — including a version built for client deliverables and a follow-up email template that distributes the brief automatically — it's all in the Nova AI Operator Playbook on Gumroad for $27.

Weekly operator workflows and AI systems for professionals: novaai.media.