12 AI Meeting Notes Examples You Can Adapt Today

Blank pages are hard, and examples make AI meeting notes easier to start. This post gives twelve example setups for different kinds of calls: what to ask for, what the notes might look like, and why that shape works. They are illustrative samples written for this post, with invented names. They are not real client notes.

Take the ones that match your work and change the words. Most of them follow the same base instruction: use only the transcript, mark what you are unsure about, and give owners and dates for tasks.

The best notes layout depends on what happens after the call. Pick the example whose follow up matches yours.

1. Client project call

Ask for: summary, decisions, tasks with owner and date, open questions. Sample: "Decision: use the single column page. Task: Sam sends photos by the 14th." Why it works: projects fail on unclear owners, and this puts names and dates first.

2. Sales discovery call

Ask for: the person's main problem, what they have tried, budget if mentioned, decision process, next step. Sample: "Problem: late invoices. Tried: spreadsheets. Next step: send a proposal by Monday." Why it works: it records the buyer's own words, which you can use in the proposal.

3. Coaching session

Ask for: goals mentioned, obstacles, the client's own commitments for the week. Sample: "Commitment: two outreach messages a day, reviewed next session." Why it works: it puts the commitments in the client's words, which makes them more likely to be kept.

4. Team check in

Ask for: done last week, plans this week, blockers, who needs help. Sample: "Blocker: waiting for logo files from Dana." Why it works: blockers surface early and appear in one place.

5. Supplier or vendor call

Ask for: prices quoted, delivery dates, conditions, what was promised. Sample: "Quoted: delivery in the second week. Condition: payment on order." Why it works: it gives you a record to point to if a promise changes. Check figures by hand.

6. Interview with a candidate

Ask for: answers to each question, strengths, concerns, your own follow up questions. Sample: "Strength: clear examples of handling complaints." Why it works: it keeps your comparison consistent. Be careful with privacy and fairness rules for hiring, and check what you may record and keep.

7. Podcast or content planning call

Ask for: topics agreed, guest ideas, deadlines, who writes what. Sample: "Topic: pricing mistakes. Draft: Lee, next Wednesday." Why it works: ideas from a creative talk get captured while still fresh.

8. Customer support escalation

Ask for: the problem in the customer's words, what has been tried, what was promised, the next contact time. Sample: "Promised: reply by Thursday afternoon." Why it works: it protects you and the customer from forgotten promises.

9. Board or partner meeting

Ask for: decisions, votes if any, responsibilities, items for next time. Sample: "Decision: delay the launch to the spring. Owner: Amira to update the plan." Why it works: formal groups need a clear record of who decided what.

10. Workshop or training session

Ask for: main points, questions raised, exercises given, follow up material. Sample: "Question: how do we price a pilot? Answer to send by email." Why it works: attendees get an outline plus the questions that were left open.

11. In person meeting with a voice memo

Ask for: summary and next steps from your own spoken recap after the meeting. Sample: "Recap: we agreed the order. I will send the invoice Tuesday." Why it works: speaking a two minute recap into your phone avoids recording others and still gives AI something to structure.

12. Quick phone call

Ask for: two sentences and one list of next steps. Sample: "Called the printer. Proofs arrive Friday. I confirm the artwork by Thursday." Why it works: short calls need short notes, or you will stop writing them.

Choosing and adapting

1. Match the callPick the example nearest to the kind of call you run most often.
2. Copy the askPut the "ask for" line into your standard instruction.
3. Run it on one callCheck the output against your memory.
4. EditRemove sections you never use and add one you keep wishing for.
5. SaveKeep the final version as your standing instruction.

What the examples have in common

Every example gives the assistant a shape, asks for owners and dates, and ends with something you can act on. They also avoid asking the AI to judge people or predict outcomes, which it cannot do reliably. The notes describe what was said. Decisions about what to do stay with you.

Privacy reminders

Some of these calls involve sensitive details: hiring, customer problems and money. Check what you are allowed to record, tell people you are recording, and check how your tool stores data. If in doubt, take handwritten notes instead.

Keep going

If you want a full template to start with, see the free template post. If you want a process to keep every set consistent, see the Note Framework. And the lesson Notes and next steps from every call teaches the full routine behind all of these examples.

Turning an example into your own standing instruction

Take example 2, the sales discovery call, as a case. Start from the ask: the person's main problem, what they have tried, budget if mentioned, decision process, next step. Turn it into a single instruction you can paste: "Write the person's main problem in their own words, what they have tried so far, any budget they mentioned, who else is involved in the decision, and the agreed next step with a date. Use only the transcript, and mark anything you are unsure about."

Now test it on a recent call you remember well. If the output matches your memory, keep it. If it misses something, such as how urgent the problem is, add a line asking for that. Two or three rounds of this give you an instruction that fits your calls better than any example here.

The full routine is taught in the lesson Notes and next steps from every call.

Questions people ask

Can I use these for any AI assistant?

Yes. They are plain instructions and work with any assistant that accepts pasted text.

Which example should I start with?

The one for the call type you run most often. Run it on one call and adjust.

Are the sample lines real?

No. They are invented examples to show how notes might look.

Can I combine two examples?

Yes, but keep the result short. Notes with too many sections are not read.