Glanz: aiMOOC über GPT aiMOOC Action erstellt

2026-08-09T14:35:19Z

aiMOOC über GPT aiMOOC Action erstellt

Neue Seite

{{T}}
[[Category:English]]
[[Category:Meeting Preparation and Follow-Up]]

{{BR}}
= Introduction =

Workplace meetings are common in companies, workshops, offices, laboratories, care settings, schools, service businesses, and training organizations. As an apprentice, trainee, or vocational student, you may be asked to prepare a meeting, take notes, contribute ideas, report progress, or follow up on decisions. Good meeting practice helps a team use time well, make clear decisions, assign responsibilities, and avoid misunderstandings.

This aiMOOC shows you how to prepare before a meeting, participate professionally, document outcomes, and complete the follow-up. You will practise practical workplace English for [[Business communication|business communication]], [[Active listening|active listening]], [[Agenda (meeting)|agendas]], [[Minutes|meeting minutes]], and [[Task management|action items]].

[[File:Simple illustration of a business meeting.png|500px|frameless|center]]

A useful meeting has a clear purpose. Before you invite people or reserve a room, ask: '''What should be different when this meeting ends?''' The answer might be a decision, a plan, a status update, a solved problem, or a list of next steps. If there is no clear purpose, another communication method such as an email, short message, shared document, or one-to-one conversation may be more efficient.

{{#ev:youtube|https://www.youtube.com/watch?v=iQsw3cdJbbM|500|center}}

{{BR}}
= Learning Goals =

After working through this aiMOOC, you should be able to prepare a meeting systematically, create a focused agenda, organize practical details, participate with professional language, take useful notes, distinguish decisions from discussion, write action items with owners and deadlines, produce concise minutes, and follow up so that agreed work is actually completed.

You should also be able to adapt these skills to face-to-face, hybrid, and online meetings in different vocational fields.

{{BR}}
= Before the Meeting =

{{BR}}
== Define the Purpose and Expected Result ==

Start with the purpose. A vague purpose such as "talk about the project" gives participants little guidance. A stronger purpose states the desired result, for example: "decide which supplier to recommend", "agree the work schedule for next week", or "identify the cause of repeated customer complaints".

A clear expected result helps you decide who needs to attend, what information is needed, how much time to reserve, and which agenda items belong in the meeting. It also gives the facilitator a basis for closing the meeting: the group can check whether the intended result was achieved.

Before scheduling the meeting, ask yourself these questions:

# [[Meeting objective|Objective]]: What result should the meeting produce?
# [[Participants|Participants]]: Who has information, responsibility, expertise, or decision authority?
# [[Preparation|Preparation]]: What must participants read, calculate, check, or bring?
# [[Timing|Timing]]: How much time is realistically needed?
# [[Meeting format|Format]]: Is face-to-face, online, or hybrid participation most suitable?

{{BR}}
== Choose the Right Participants ==

Invite people because they have a clear role, not simply because they might be interested. Too many participants can slow discussion, while missing a key decision-maker can prevent progress. Depending on the meeting, people may attend to provide technical knowledge, report progress, approve a decision, coordinate work, represent a customer need, or record outcomes.

For vocational learners, this may include a trainer, supervisor, team leader, technician, office administrator, customer-service colleague, safety representative, or project partner. If someone only needs the result, they may not need to attend; they can receive the minutes or a short follow-up message.

{{BR}}
== Create a Clear Agenda ==

An '''agenda''' is the planned sequence of topics for a meeting. A useful agenda tells participants why the meeting is taking place, what will be discussed, who will lead each item, and how much time is available.

[[File:Meeting Agenda - Page 1 of 2.jpg|500px|frameless|center]]

A practical agenda can include the following information:

{| class="wikitable"
! Element
! Example
! Why it matters
|-
| Purpose
| Agree the installation plan for a new machine
| Keeps the meeting focused on an outcome
|-
| Date and time
| Tuesday, 10:00 to 10:40
| Helps participants plan their work
|-
| Place or online link
| Training room B or secure video link
| Prevents access problems
|-
| Participants
| Supervisor, apprentice, maintenance technician
| Clarifies who is expected
|-
| Agenda item
| Review installation requirements
| Shows what will be discussed
|-
| Item owner
| Maintenance technician
| Identifies who will introduce the topic
|-
| Time box
| Ten minutes
| Protects the overall schedule
|-
| Expected result
| Confirm required tools and safety checks
| Makes the purpose of the item measurable
|}

Order agenda items logically. You might begin with a short check-in or approval of previous actions, then move to decision items, problem-solving, information updates, and final next steps. Put the most important items early enough that they are not rushed.

Send the agenda and preparation material early enough for participants to read and prepare. The exact timing depends on the workplace and the complexity of the topic, but participants should have a realistic opportunity to review what you send.

{{BR}}
== Prepare Documents, Data, and Questions ==

Do not enter a meeting hoping that the group will discover all the necessary facts together. Check what evidence is needed beforehand. Depending on the job, this might include a quotation, drawing, production figure, customer complaint, stock level, risk assessment, maintenance record, timetable, budget, or progress report.

Separate '''facts''' from '''assumptions'''. If a number is important, know where it came from. If you are unsure, mark it as something to verify rather than presenting it as certain.

Prepare questions that help the group move forward. Useful question types include clarification questions, comparison questions, risk questions, and decision questions. For example: "What information is still missing?", "Which option meets the customer requirement best?", "What could delay this step?", or "Who has authority to approve the change?"

{{BR}}
== Organize the Practical Setup ==

A well-prepared meeting also needs a reliable setting. Check the room, seating, accessibility, display equipment, whiteboard, power supply, required tools, and any materials participants need. For online meetings, test the platform, microphone, camera, screen sharing, permissions, and link before the start.

[[File:Modern Meeting Room.jpg|500px|frameless|center]]

For hybrid meetings, avoid treating remote participants as observers. Make sure they can hear, speak, see shared material, and join the discussion. If confidential information is involved, use the communication and data-protection procedures required by your workplace.

{{BR}}
== Prepare Your Professional Language ==

If English is used at work, prepare short phrases before the meeting. This reduces stress and helps you contribute clearly.

Useful phrases include:

{| class="wikitable"
! Situation
! Example phrase
|-
| Opening
| "The aim of today's meeting is to agree the next steps."
|-
| Asking for clarification
| "Could you explain what you mean by that?"
|-
| Checking understanding
| "So, if I understand correctly, the delivery moves to Thursday."
|-
| Adding a point
| "I'd like to add one practical concern."
|-
| Disagreeing professionally
| "I see the advantage, but I am concerned about the safety risk."
|-
| Returning to the agenda
| "Can we return to the question we need to decide?"
|-
| Confirming an action
| "I'll update the checklist by Friday."
|-
| Closing
| "Before we finish, let's confirm the decisions and responsibilities."
|}

{{#ev:youtube|https://www.youtube.com/watch?v=Wb6Oc1_SdJw|500|center}}

{{BR}}
= During the Meeting =

{{BR}}
== Start with Purpose, Roles, and Time ==

At the beginning, the facilitator should make the purpose clear, confirm the main agenda, and identify any important roles. Typical roles include a chair or facilitator, a note-taker, subject specialists, and participants responsible for decisions or actions.

If the meeting is short, role assignment can be simple. In a formal meeting, roles may be defined by workplace rules. In either case, everyone should understand what outcome is expected.

{{BR}}
== Listen Actively and Contribute Clearly ==

Active listening means paying attention to the speaker, checking meaning, asking useful questions, and responding to what was actually said. It is not simply waiting for your turn to speak.

[[File:Taking Notes.JPG|500px|frameless|center]]

Useful listening behaviours include summarizing a point in your own words, asking for an example, noticing disagreement, and separating the person from the problem. If you disagree, focus on evidence, requirements, consequences, or alternatives rather than attacking the speaker.

{{#ev:youtube|https://www.youtube.com/watch?v=aDMtx5ivKK0|500|center}}

A clear contribution is usually short and structured. State the point, give the reason or evidence, and explain what you recommend. For example: "The current delivery time is too short because the supplier needs two working days. I recommend moving installation to Friday."

{{BR}}
== Keep Discussion Connected to the Agenda ==

Meetings often lose time when discussion becomes repetitive or moves to a topic that only concerns a few people. A facilitator can protect the meeting by summarizing, parking unrelated issues for later, and asking decision-focused questions.

A useful pattern is: '''issue → evidence → options → decision → action'''. This sequence is not mandatory for every item, but it helps teams move from discussion to a practical result.

If a topic cannot be resolved because information is missing, record exactly what must be checked, who will check it, and when the team will revisit the issue.

{{BR}}
== Take Notes for Outcomes, Not a Transcript ==

Meeting notes should help people remember what matters after the meeting. They normally focus on decisions, action items, deadlines, unresolved questions, key reasons, and information that affects future work. A word-for-word transcript is usually unnecessary unless a specific formal procedure requires one.

Useful note-taking headings are:

{| class="wikitable"
! Topic
! Decision
! Action
! Owner
! Deadline
! Open question
|-
| Tool delivery
| Use supplier B
| Confirm delivery slot
| Sam
| Thursday
| Does the loading bay need to be reserved?
|-
| Safety briefing
| Add a short induction
| Prepare briefing sheet
| Lina
| Friday
| None
|}

The names above are only examples. In a real workplace record, use the correct names, roles, dates, and confidentiality rules.

{{BR}}
== Include Remote Participants ==

Online and hybrid meetings need deliberate communication. Use names when inviting contributions, pause after asking a question, avoid several people speaking at once, and describe visual information that remote participants may not be able to see clearly.

[[File:Virtual Meeting.png|500px|frameless|center]]

When sharing a document, make sure everyone has access to the correct version. Do not assume that a screen share is enough; important decisions and actions should still be recorded in a form that participants can review later.

{{BR}}
= After the Meeting =

{{BR}}
== Confirm Decisions and Action Items ==

Before the meeting ends, repeat the main decisions and actions aloud. This is the easiest time to correct misunderstandings.

A strong action item answers three questions: '''What will be done? Who owns it? By when?''' If necessary, also record the expected result or acceptance criterion.

Compare these examples:

{| class="wikitable"
! Weak action
! Stronger action
|-
| "Check the machine."
| "Maya will inspect the emergency-stop function and report the result by Wednesday."
|-
| "Contact supplier."
| "Jon will ask supplier B to confirm the delivery window by 15:00 on Tuesday."
|-
| "Update document."
| "Aisha will add the revised process steps to the shared work instruction before the next shift briefing."
|}

An action should have one clear owner, even when several people help. Shared responsibility without ownership can make follow-up difficult.

{{BR}}
== Write Useful Minutes ==

'''Meeting minutes''' are a concise record of what the meeting produced. The exact format depends on the organization, but useful minutes commonly include the meeting purpose, date, participants, important decisions, action items, deadlines, and unresolved issues.

Minutes should be accurate, neutral, and easy to scan. Avoid adding opinions that were not agreed. If a decision is provisional, say so. If a point still needs approval, record that status clearly.

{{#ev:youtube|https://www.youtube.com/watch?v=JJIiHeEd4ww|500|center}}

A simple structure is:

{| class="wikitable"
! Section
! What to record
|-
| Meeting details
| Purpose, date, time, format, participants
|-
| Decisions
| What the group agreed or approved
|-
| Actions
| Task, owner, deadline
|-
| Open issues
| Questions, missing information, pending approvals
|-
| Next meeting
| Date or trigger, if needed
|}

{{BR}}
== Send the Follow-Up Promptly ==

Follow-up turns meeting talk into coordinated work. Send the approved or agreed record through the workplace's normal communication channel. The message should make the outcome easy to understand without forcing recipients to read a long narrative.

A practical follow-up usually includes a short summary of the result, the decisions, action items with owners and deadlines, links or attachments to relevant documents, and any next meeting date.

Before sending, check names, dates, numbers, attachments, document versions, and access permissions. If the content is confidential, send it only to authorized people.

{{BR}}
== Track Actions to Completion ==

Follow-up does not end when the minutes are sent. Actions need to be tracked until they are completed, changed, or formally cancelled.

[[File:Clipboard check.svg|500px|frameless|center]]

Teams may use a shared task board, spreadsheet, ticketing system, project tool, maintenance system, or action log. The tool matters less than the clarity of the information. Each action should be visible, owned, dated, and updated.

If a deadline cannot be met, communicate early. Explain the problem, its effect, and the new proposal. Professional follow-up is proactive rather than silent.

{{BR}}
== Review Meeting Quality ==

A short review helps improve future meetings. Ask whether the purpose was achieved, whether the right people attended, whether preparation was sufficient, whether discussion stayed focused, whether decisions were clear, and whether follow-up actions were realistic.

For repeated team meetings, even a two-minute review can reveal useful patterns. If the same problems continue, change the meeting design rather than accepting wasted time as normal.

{{BR}}
= A Practical Meeting Workflow =

You can use the following cycle in many vocational settings:

{| class="wikitable"
! Stage
! Main question
! Typical output
|-
| Purpose
| Why are we meeting?
| Clear objective
|-
| Preparation
| What do people need before the meeting?
| Agenda, documents, data, questions
|-
| Setup
| How will everyone participate?
| Room or online access ready
|-
| Discussion
| What evidence and options matter?
| Shared understanding
|-
| Decision
| What has been agreed?
| Clear decision
|-
| Action
| Who does what by when?
| Owned action items
|-
| Record
| What must be remembered?
| Minutes or action log
|-
| Follow-up
| Is the agreed work completed?
| Updated status and next steps
|}

The cycle is especially useful when you are new to workplace meetings because it gives you a checklist for both preparation and follow-up.

{{BR}}
= Vocational Examples =

{{BR}}
== Workshop or Technical Team ==

A maintenance team meets because a machine has repeated stoppages. Before the meeting, the apprentice collects error codes and maintenance records. During the meeting, the team distinguishes confirmed facts from guesses, compares possible causes, and agrees on a test. The minutes record who will run the test, when it will happen, and what result must be reported.

{{BR}}
== Office or Commercial Team ==

A purchasing team meets to compare two supplier offers. Before the meeting, participants receive the quotations and evaluation criteria. During the meeting, they compare price, lead time, quality requirements, and service conditions. The follow-up records the selected option, any approval still required, and the person responsible for contacting the supplier.

{{BR}}
== Customer Service Team ==

A team sees an increase in customer complaints about delayed responses. The meeting objective is not simply to discuss the complaints; it is to identify the main causes and agree two improvements. After the meeting, each improvement has an owner, deadline, and measure of success.

{{BR}}
== Training or Project Group ==

Trainees plan a project presentation. The agenda includes responsibilities, missing content, rehearsal timing, and final quality checks. The follow-up message confirms who updates each section and when the group will review the complete version.

{{BR}}
= Interactive Tasks =

{{BR}}
== Quiz: Test Your Knowledge ==

{{MC}}

'''What should be defined before deciding who needs to attend a meeting?'''
(The purpose and expected result)
(!The decoration of the meeting room)
(!The order of names in the minutes)
(!The font used in the follow-up message)

{{E}}
<br>

{{MC}}

'''Which agenda element makes responsibility for introducing a topic clear?'''
(The item owner)
(!The room number)
(!The meeting title)
(!The file format)

{{E}}
<br>

{{MC}}

'''Which action item is the clearest?'''
(Mina will send the revised quotation by Friday)
(!Someone should check the quotation)
(!The quotation needs attention)
(!We can discuss the quotation later)

{{E}}
<br>

{{MC}}

'''What is the main purpose of active listening in a meeting?'''
(To understand and respond to the speaker accurately)
(!To prepare a longer speech than everyone else)
(!To avoid asking any questions)
(!To agree with every statement)

{{E}}
<br>

{{MC}}

'''What should meeting notes normally emphasize?'''
(Decisions actions deadlines and open issues)
(!Every sentence spoken by every person)
(!Only the names of participants)
(!Only the meeting room and date)

{{E}}
<br>

{{MC}}

'''What is a useful way to handle an unresolved issue?'''
(Record what must be checked who will check it and when)
(!Delete the issue from the notes)
(!Assign it to everyone without a deadline)
(!Assume it will solve itself)

{{E}}
<br>

{{MC}}

'''What should a facilitator do when discussion moves far away from the agenda?'''
(Summarize and guide the group back to the required decision)
(!Extend every unrelated discussion)
(!End the meeting without recording anything)
(!Ignore the meeting objective)

{{E}}
<br>

{{MC}}

'''What is especially important in a hybrid meeting?'''
(Making sure remote participants can hear speak and access shared material)
(!Giving remote participants no speaking time)
(!Using different document versions for each location)
(!Keeping decisions only on a physical whiteboard)

{{E}}
<br>

{{MC}}

'''What should be checked before sending a follow-up message?'''
(Names dates numbers attachments versions and permissions)
(!Only the color of the email background)
(!Only the first sentence)
(!Only the number of participants)

{{E}}
<br>

{{MC}}

'''When is meeting follow-up complete?'''
(When agreed actions are tracked to completion or formally changed)
(!As soon as the meeting room is empty)
(!As soon as the agenda is created)
(!As soon as the first person leaves)

{{E}}
<br>

{{BR}}
== Memory Game ==

<div class="memo-quiz">
{|
|-
| Agenda || Planned sequence of topics for discussion
|-
| Minutes || Concise written record of outcomes
|-
| Facilitator || Person who guides the discussion and protects the process
|-
| Deadline || Agreed latest time for completing work
|-
| Action item || Specific task with clear responsibility
|-
| Objective || Result the group is expected to achieve
|}
{{E}}
<br>

{{BR}}
== Drag and Drop ==

<div class="lueckentext-quiz">

{| class="wikitable"
! Match the correct terms.
! Topic
|-
| '''Agenda'''
| Ordered plan of meeting topics
|-
| '''Minutes'''
| Record of decisions and agreed work
|-
| '''Action item'''
| Task assigned for completion
|-
| '''Facilitator'''
| Person guiding the meeting process
|-
| '''Deadline'''
| Agreed completion point
|}
{{E}}

<br>
...
<br />

{{BR}}
== Crossword Puzzle ==

<div class="kreuzwort-quiz">
{|
|-
| Agenda || What document lists the planned topics for a meeting?
|-
| Minutes || What record summarizes decisions and agreed actions?
|-
| Facilitator || Who guides discussion and helps the group stay on process?
|-
| Deadline || What word means the agreed latest completion time?
|-
| Listening || What skill helps you understand and respond accurately to speakers?
|-
| Summary || What short account can communicate the main result after a meeting?
|}
{{E}}
<br>

{{BR}}
== LearningApps ==

<iframe> https://learningapps.org/index.php?s=Meeting+Preparation+and+Follow-Up </iframe>

{{BR}}
== Cloze Text ==

<quiz display=simple>
{'''Complete the text.'''<br>
|type="{}"}
A useful meeting begins with a clear { purpose }. The planned sequence of topics is called an { agenda }. Participants should receive the information they need for effective { preparation }. During the meeting, careful { listening } helps you understand other viewpoints. Important outcomes should be captured in concise { notes }. A clear action identifies the task and its { owner }. Each time-sensitive action should also have a { deadline }. A concise formal record of outcomes may be written as meeting { minutes }. After the meeting, participants need timely { follow-up }. Agreed work should be tracked until { completion }.
</quiz>

<br>

{{BR}}
= Open-Ended Tasks =

{{BR}}
=== Easy ===
# [[Meeting checklist]]: Create a one-page checklist for preparing a 30-minute workplace meeting and include purpose, participants, documents, room or link, equipment, and follow-up.
# [[Agenda drafting]]: Write an agenda for a short team meeting about a realistic training or workplace issue and give each item a purpose and time box.
# [[Participation phrases]]: Record yourself using six professional English phrases for opening, clarifying, disagreeing, confirming an action, returning to the agenda, and closing.
# [[Action item practice]]: Rewrite five vague workplace tasks so that each one states a clear task, one owner, and a deadline.

{{BR}}
=== Standard ===
# [[Meeting observation]]: Observe a real or simulated meeting with permission and analyse how clearly the purpose, agenda, decisions, and actions are handled.
# [[Minutes writing]]: Watch a short approved meeting video or role-play and produce concise minutes that separate decisions, actions, deadlines, and open questions.
# [[Follow-up message]]: Draft a professional follow-up message for a simulated workplace meeting, including a short outcome summary and a clear action table.
# [[Hybrid meeting plan]]: Design a plan for a hybrid meeting that explains how remote and in-room participants will access documents, speak, hear, and contribute equally.

{{BR}}
=== Advanced ===
# [[Facilitation project]]: Plan and facilitate a 20-minute meeting on a vocational problem, then collect participant feedback on focus, inclusion, and decision quality.
# [[Meeting process audit]]: Interview a supervisor or experienced colleague about meeting practices, compare the answers with this course, and propose two realistic improvements.
# [[Decision record]]: Create a structured decision log for a multi-step project and show how it connects decisions, evidence, responsible people, and later actions.
# [[Meeting improvement experiment]]: Compare two versions of the same simulated meeting, one with weak preparation and one with a clear agenda and assigned roles, then evaluate differences in time use and outcomes.

{{:Open Task - Create a MOOC}}

{{BR}}
= Learning Assessment =

# [[Preparation scenario]]: You are asked to organize a meeting about a delayed customer order; create the objective, participant list, preparation request, agenda, and setup, and justify each choice.
# [[Minutes evaluation]]: Compare two sets of meeting minutes and explain which one better supports accountability, accuracy, and follow-up.
# [[Action quality analysis]]: Diagnose five weak action items, rewrite them, and explain how ownership and deadlines change the chance of completion.
# [[Hybrid meeting transfer]]: Adapt a face-to-face meeting plan for a hybrid team and explain how your changes support equal participation and reliable documentation.
# [[Follow-up problem solving]]: A critical action is overdue and affects another department; prepare a professional response that explains the impact, requests an update, and proposes a next step.
# [[Meeting redesign]]: Review a recurring meeting that often runs over time and design a new format using objectives, time boxes, decision points, and action tracking.

<br>
<br>

{{BR}}
= Evidence of Learning =

Evidence of learning can include the following:

{| class="wikitable"
! Area
! Evidence
|-
| Knowledge
| You can explain the purpose of agendas, minutes, action items, deadlines, facilitation, and follow-up.
|-
| Preparation skill
| You can define an objective, choose relevant participants, prepare documents, and organize a suitable meeting setup.
|-
| Communication skill
| You can listen actively, ask for clarification, contribute concisely, disagree professionally, and confirm understanding.
|-
| Documentation skill
| You can distinguish decisions, actions, open issues, and background discussion in your notes.
|-
| Product
| You can produce a usable agenda, action log, minutes document, or follow-up message for a realistic workplace situation.
|-
| Transfer
| You can adapt meeting practice to technical, commercial, service, project, face-to-face, online, or hybrid settings.
|-
| Reflection
| You can evaluate meeting quality and suggest practical improvements based on evidence.
|}

<br>
<br>

{{BR}}
= OERs on the Topic =

<iframe> https://en.m.wikipedia.org/wiki/Meeting </iframe>

<br>

{{BR}}
= Linked Learning Areas =

{| align=center
{{:D-Tab}}
'''[[Meeting Preparation and Follow-Up]]'''
# [[Agenda (meeting)|Meeting agenda]]
# [[Minutes|Meeting minutes]]
# [[Active listening]]
# [[Business communication]]
# [[Facilitation]]
# [[Task management|Action tracking]]
# [[Videotelephony|Online meetings]]
|}

[[Category:English]]
[[Category:Vocational Education]]
[[Category:Business Communication]]
[[Category:Workplace Skills]]
[[Category:Professional Communication]]
[[Category:Project Management]]

{{BR}}
= aiMOOC Projects =
[[Category:English]]
[[Category:Meeting Preparation and Follow-Up]]
[[Category:Vocational Education]]
[[Category:Business Communication]]
[[Category:Workplace Skills]]
[[Category:Professional Communication]]
[[Category:Project Management]]
[[Category:AI_MOOC]]
[[Category:GPT aiMOOC]]
{{MT}}

English:Meeting Preparation and Follow-Up - Versionsgeschichte

Glanz: aiMOOC über GPT aiMOOC Action erstellt