At most one email a week. Unfollow anytime with one click.
Transcript
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Show transcript
Introduction
Hi, and welcome back. In the previous episode we built a weekly plan. One thing that almost always shows up in that schedule is meetings. Today we learn to turn messy meeting notes into tidy minutes, then follow up with an email, a task table, and reminders.
Step 1: Prepare the meeting material
The first step is preparing the material. The most common source is quick notes typed during the meeting: short, full of abbreviations, and out of order. That's fine. The second source is a photo of handwriting or a whiteboard. As we saw in the Working with Files session, Claude can read images, so even a photo of your notes works. The third source is a transcript from an online meeting app. It's complete, but long and rambling. That's exactly where Claude helps most, by picking out what matters. Two rules before you paste anything. If the meeting was recorded, ask the participants for permission. Then remove sensitive information such as salaries, personal data, or customer secrets. Dewi has just finished leading the weekly Maju Bersama Co. meeting. She pastes her quick notes into Claude: the list of participants, then four short, untidy points. Notice that Dewi's notes have two gaps. There are question marks on the A4 stock point, and the brochure point just says, when? Claude doesn't make anything up. It first asks when the brochure is due and when Wulan has to report. It asks because the notes really are incomplete. Dewi answers: the brochure is due Thursday, and the budget report Wednesday. If you don't know the answer, just say it hasn't been decided. That's better than guessing.
Step 2: Write structured minutes
Step two is writing the minutes. Dewi uses a prompt with four parts. First, the role: a careful minute-taker who never adds information. Second, the data: the meeting notes, plus Dewi's answers about the deadlines. Third, the format. The minutes are split into meeting info, decisions, a task table with who, what, and deadline, and a list of items not yet decided. Fourth, the constraints, and this is the most important part. Claude must not add anything that isn't in the notes, and must mark doubtful parts with the words, needs checking. Save this prompt in your notes. After every meeting, you only need to replace the data part with the new meeting notes. Dewi asks for the minutes as an Artifact. Claude immediately tells her that one part is marked as needing a check: the remaining A4 stock. In the right panel, the minutes are tidy. There's the meeting info and participants, one main decision about the school promo, then a task table for Andi, Wulan, and Bayu. Look at Andi's row. The deadline says not set, because it really wasn't discussed in the meeting. Claude doesn't invent a date, and the item goes into the not-yet-decided list at the bottom. Because it's an Artifact, these minutes can be copied in full, downloaded, or revised with a short request, without rebuilding them from scratch.
Step 3: Check before sharing
Step three: check before sharing. The minutes become the shared record, so there are five things you must check. First, the participants' names and job titles are correct. Second, every task has exactly one owner. A task that everyone shares usually ends up done by no one. Third, the dates and deadlines match what was agreed in the meeting. Fourth, numbers such as the discount and stock amounts haven't changed. A ten percent discount must never turn into fifteen. Fifth, proposals aren't written as decisions. This is the mistake that most often causes misunderstandings after a meeting. Besides checking herself, Dewi asks Claude to point out the parts most likely to be wrong because the notes were unclear. Claude names three. The A4 stock with the question marks, the backup courier that may be approved or just proposed, and the scope of the promo discount. A question like this reveals the weak spots in our notes. The answers don't come from Claude; we ask the meeting participants. Dewi sends a short message to Andi and Bayu to confirm. Five minutes of asking now is far cheaper than a week of work based on wrong minutes. Once the answers come in, the minutes are updated to version two.
Step 4: Send the follow-up
Step four: send the follow-up. Dewi's inbox already has replies from Bayu and Andi: the discount is only for school packages, and the backup courier is still a proposal. Above them is the draft minutes email. Claude wrote this draft from the corrected minutes. The summary of decisions and tasks sits at the top, because many people only read the first few lines. Notice the last sentence: please send any corrections before Tuesday noon. It gives participants a chance to fix the record before the minutes are considered final. Claude writes the draft, but Dewi still reads it again and presses send herself. An email in your name is your responsibility. So tasks don't get lost in a pile of emails, Dewi moves them into a shared tracking table. Claude writes the rows, and Dewi just pastes them in. Row one: Andi, two backup courier options, due Wednesday. Row two: Wulan, the A4 stock budget report, also Wednesday. Row three: Bayu, the school promo brochure, due Thursday. Each person updates the status column themselves. At the next meeting, this table is opened first. Unfinished tasks are discussed before any new tasks are added.
Step 5: Reminders and the next meeting
The last step is the reminder. On Tuesday morning, Dewi asks Claude to write a polite reminder for the operations group. It names the tasks and deadlines, and offers help if anything gets in the way. Andi replies that he has found one courier option, and the other will follow this afternoon. Wulan also reports that the budget is done. With a reminder the day before, problems surface early, not after the deadline has already passed. You can adjust the minutes format to the type of meeting. For a client meeting, ask Claude to focus on agreements, prices, and deadlines, because those are the parts most often disputed later. For a teachers' meeting, for example at Cerdas Tutoring, Mr. Hendra records the class evaluation results. Student names don't need to be written. Just mention the class and the pattern. For a small business like Sunset Coffee, a quick chat between Laras and Dimas can be summed up as three decision points, then sent to the WhatsApp group. For a long online meeting, ask Claude to summarize the transcript first, then pull out only the task list. The principle stays the same: add nothing, and mark what's uncertain. Let's sum up the flow. First, take notes during the meeting as they are, without sensitive data. Second, write the minutes with a standard prompt that forbids Claude from adding content. Third, check. Doubtful parts are put to the participants, not guessed. Fourth, send the follow-up email and move the tasks into the tracking table. Fifth, track with reminders before the deadlines. If the meeting is a regular one, you can save this minutes prompt in a Project, as we learned in the Projects session, so you never have to rewrite it.
Done!
We've turned messy meeting notes into structured minutes, checked the doubtful parts, then followed up with an email, a task table, and reminders. In the next episode we use Claude to find ideas: focused brainstorming, not just a list of random ideas. See you there!
Practice exercises
Try these on your own after watching to lock in what you learned.
Turn the notes from your last meeting into minutes with four parts: info, decisions, tasks, and open items
Ask Claude to point out the parts of the notes it's unsure about, then fill them in yourself
Write a follow-up email and a task table from the same minutes
Ask the class material
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
My notes
Notes are saved with the current video time and are only visible to you.
Questions & answers
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.
Your instructor
Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
52 video classes1,277 episodes
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
