侠Liangshen AIailiangshen.com
AI Implementation Course · Short topic lessons · Lesson 6

Meeting Minutes and Action Items

Clarify conclusions, action items, responsible persons, and deadlines in one go

Freeabout 10 minNo experience neededWeb lesson + slides + video

This is a domain course suitable for all staff, especially administrative personnel, project managers, and product managers. The exercise involves organizing messy meeting notes into conclusions, action items, responsible persons, and deadlines.

By the end of this lesson, you can

  • Use the minutes template to organize meeting notes into conclusions, action items, and items pending confirmation
  • Action items must have a responsible person and a deadline; if missing, write 'pending confirmation'
  • Create a pending confirmation list, specifying who to confirm each item with
  • Prepare a question list before the meeting, and send a follow-up email of no more than 250 words after the meeting

Takeaway: a minutes template and a pending confirmation list

01

Opening

About 1 minutes

Let's look at a scenarioFictional example, numbers are illustrative

Administrative Specialist Lin Yue

For the weekly department meeting, she needs to organize the minutes and send them to twelve colleagues.

Common issues include: missing action items, incorrect responsible persons, and unspecified deadlines.

The Dragon Warrior might conveniently add a plausible-sounding deadline.

A guessed date in the minutes is more dangerous than a blank space.
02

Method

About 4 minutes

Four steps to organize minutes

First, anonymizeReplace client names, amounts, and undisclosed plans with code names; for audio recordings, first ask participants for consent.
→
The Four-Column FormatConclusion, Action Items, Responsible Person, Deadline
→
State the rules clearly.If information is missing, mark it as 'To Be Confirmed'; do not add anything not said in the meeting; do not include items that were only discussed in the conclusions.
→
You verify this.Check if the responsible persons match and if the deadlines accurately reflect the original statements, then send it out.
This is the final checkpoint, and you are the guardian.
Tip

Meeting Minutes Template

Suggested time
Template 1: Organizing Meeting Minutes
You are an administrative assistant with ten years of experience. Below is a meeting transcript. Please organize it into meeting minutes.
Output structure:
1. Basic Meeting Information (time, location, attendees; write 'To Be Confirmed' if not in the record)
2. Conclusions Reached (one sentence per item)
3. Action Items (in a table with columns: Item, Responsible Person, Deadline, Source Quote from the Record)
4. To-Be-Confirmed List: List missing responsible persons, missing deadlines, and ambiguous points one by one, with a suggestion on whom to confirm with.
Rules:
1. If the record does not explicitly state the responsible person or deadline, mark them as 'To Be Confirmed.' Do not guess.
2. Do not add anything not said in the meeting.
3. Distinguish between 'decided' and 'discussed' items; do not include discussed items in the conclusions.
Meeting transcript:
[Paste the de-identified transcript]
Discussed items do not go into the conclusions; missing responsible persons and deadlines go into the To-Be-Confirmed list.

Example: 'Let's see' is not a decisionFictional example, numbers are illustrative

Original Record

He Lei asked if the budget could be increased. President Zheng said, 'Let's see.'

How it appears in the minutes

Budget Increase: Discussed, no conclusion reached. Not included in conclusions. Added to the To-Be-Confirmed list with a suggestion to confirm with President Zheng.

Discussed items can only go into the To-Be-Confirmed list.

Check each item before sending

Action Items

Does each item have a responsible person and a deadline? Have vague terms like 'next week' or 'ASAP' been converted to specific dates?

Names

Is the responsible person actually that person? Verify if there are name duplicates or abbreviations.

Conclusions

Have any discussed items been mistakenly written as conclusions?

Sensitive Content

Amounts, client, and user data must be verified by a human before being sent.

03

Practice

About 3 minutes
Tip

Pre- and Post-Meeting

Suggested time
Template 4: Pre-Meeting Question Checklist
I am attending a meeting next week: [Meeting Name]. The topic is: [Topic, anonymized].
Please help me prepare:
1. The problem this meeting aims to solve, stated in one sentence.
2. The most likely positions of the other party (or all parties). Mark any assumptions with 'Assumption'.
3. Three questions I can ask. Ask one thing at a time. The final question must be 'What is your key takeaway from this discussion?'
4. One document I need to prepare in advance.
Use only the information I provide. If something is missing, write 'To be supplemented'. Do not fabricate information.
Template 5: Post-Meeting Follow-up Email
Write a post-meeting follow-up email based on the meeting minutes below.
Requirements: No more than 250 words; include only what was discussed in the meeting; do not add any suggestions not present in the minutes; end with a list of items to be confirmed and specify who needs to reply.
Minutes: [Paste here]
All assumptions are marked with 'Assumption', and the email contains no information not discussed in the meeting.

Tech Version Example: Four Traps in Requirements Review (Fictional)

Export in Batches

This is just Qiu Ziang's concern, not a decision, so do not include it in the conclusions.

Acceptance Criteria

The assigned owner is He Wenqing, but there is no deadline. Add this to 'To be Confirmed'.

Client's Urging

This is an expectation, not a commitment, and no one has responded. Add this to 'To be Confirmed'.

Whether Exports Include Usernames

This involves user data. Add this to 'To be Confirmed' and recommend consulting data compliance.

Common Biases and Remedies

04

Quiz and Wrap-up

About 2 minutes

Three quick questions to check yourself

Question 1: The notes don't specify a deadline. How should I record this in the minutes?

Answer B.For any unspecified deadlines, always write 'To Be Confirmed' and add it to the list. Someone needs to follow up. Leaving it blank means overlooking the issue.
Show the full transcript (video narration)
Meeting Minutes and Action Items

This is a domain course suitable for all staff, especially administrative personnel, project managers, and product managers. The exercise involves organizing messy meeting notes into conclusions, action items, responsible persons, and deadlines. We will complete this in ten minutes.

After completing this course, you will be able to

After completing this course, you will be able to do four things. First, use the minutes template to organize meeting notes into conclusions, action items, and items pending confirmation. Second, action items must have a responsible person and a deadline; if missing, write 'pending confirmation'. Third, create a pending confirmation list, specifying who to confirm each item with. Fourth, prepare a question list before the meeting, and send a follow-up email of no more than 250 words after the meeting.

Let's look at a scenario

Let's look at a fictional scenario, with numbers for illustration. Administrative Specialist Lin Yue organizes the department meeting notes into minutes every week and sends them to twelve colleagues. Common issues include missing action items, incorrect responsible persons, and unspecified deadlines. The Dragon Warrior is good at organizing text, but it might conveniently add a plausible-sounding deadline. A guessed date in the minutes is more dangerous than a blank space.

Four steps to organize minutes

There are four steps to organizing meeting minutes. First, de-identify the data: replace client names, amounts, and undisclosed plans with code names. If using an audio recording, first ask participants for consent and check company policies. Second, paste the transcript and specify the four columns: Conclusion, Action Items, Responsible Person, and Deadline. Third, state the rules: mark missing information as 'To Be Confirmed,' do not add anything not said in the meeting, and do not include items that were only discussed in the conclusions. Fourth, you verify the responsible persons and deadlines before sending. This final checkpoint is your responsibility.

Meeting Minutes Template

This is a meeting minutes template—a single prompt that yields a consistent structure. Note three rules: if the responsible person or deadline is not explicitly stated, mark it as 'To Be Confirmed'; do not add anything not said in the meeting; do not include discussed items in the conclusions. Save this prompt for reuse in future meetings.

Example: 'Let's see' is not a decision

Consider a fictional weekly meeting. In the original record, He Lei asked if the budget could be increased, and President Zheng said, 'Let's see.' The minutes cannot write this as a conclusion. It is merely a discussed item and should be placed in the To-Be-Confirmed list, with a note suggesting confirmation with President Zheng. 'Let's see' is not a decision.

Check each item before sending

Review each item before sending. Check if the to-do list has an assigned owner and a deadline, and whether the deadline accurately reflects the original wording (e.g., whether 'next week' or 'ASAP' has been converted to specific dates). Verify that the assigned owner is indeed the correct person. Check if discussion points have been mistakenly recorded as conclusions. For any content involving amounts, clients, or user data, a human must verify it before sending.

Pre- and Post-Meeting

Before the meeting, you can have it prepare a question checklist. It will list the problems to be solved, mark assumptions, and provide three questions, each addressing only one issue. After the meeting, have it draft a follow-up email based on the minutes. The requirements are clear: no more than 250 words, include only what was discussed, end with a list of items to be confirmed, and specify who needs to reply. Before sending, you must still review it yourself.

Tech Version Example: Four Traps in Requirements Review (Fictional)

The tech version example is a fictional requirements review meeting, with feature names replaced by codes. This record contains four traps. 'Export in Batches' is just a concern, not a decision. 'Acceptance Criteria' lists He Wenqing as the owner, but there is no deadline, so it must be added to 'To be Confirmed'. 'Client's Urging' is an expectation, not a commitment, and no one has responded. 'Whether Exports Include Usernames' involves user data, so it must be handled by a human and checked for data compliance. Run these through the minutes template to see if it correctly places these items in 'To be Confirmed' rather than 'Conclusions'.

Common Biases and Remedies

Several common biases. If it unilaterally adds deadlines, reiterate the rules and ask it to list the changes it made. If the owner is listed as 'relevant colleagues', require specific names. If the same item is listed twice, ensure conclusions only record decisions and actions go into the To-do list. If it only records the opinions of the person who spoke the most, create a separate section for 'Points where reservations were raised'. If speech-to-text results contain homophone errors, list suspicious words first, confirm them, and then create the minutes.

Quiz

Here's a quick quiz. The notes don't specify a deadline. How should I record this in the minutes? A: Write 'Next Friday,' since it's common knowledge. B: Write 'To Be Confirmed' and add it to the 'To Be Confirmed' list. Don't guess. C: Leave it blank to avoid errors. The answer is B. For any unspecified deadlines, always write 'To Be Confirmed' and add it to the list. Someone needs to follow up. Leaving it blank means overlooking the issue.

End of lesson

End of lesson. Bring a copy of your own meeting notes. After removing sensitive information, use the minutes template to draft the minutes. The 'To Be Confirmed' list must include at least three items, specifying who needs to be consulted for each. Remember: If something is missing, write 'To Be Confirmed.' Don't guess. Thanks for watching. This video's narration is AI-generated.