Back

flagship course · GL-15

Tele and Video Conferencing Operations

Run reliable, accessible online meetings and events: set up rooms, test audio and video, manage people and recording, and fix problems live.

about this course

What you will be able to do

L3 Foundation54 h of lessons plus practiceAbout 8 to 12 weeks part-time

Run reliable, accessible online meetings and events: set up rooms, test audio and video, manage people and recording, and fix problems live.

  • Understand Explain what makes a call clear: audio, light, network and etiquette.
  • Apply Set up a room, a camera and a microphone for a clean picture and sound.
  • Analyse Analyse call quality using simple tests and logs.
  • Create Create run sheets, joining guides and accessibility settings for a live session.
  • Evaluate Evaluate sessions with attendee feedback and technical measures.

Task, condition and standard

Task

Host and technically run three online sessions (small meeting, workshop, larger webinar) with run sheets, recordings where agreed, and feedback.

Condition

A computer or phone, a free conferencing tool, a headset or microphone, a second person to act as guest, a mentor and a peer circle. About 8 weeks part-time.

Standard

Test completed 30 minutes before each session; audio understood by every attendee; captions or notes offered; recording only with consent; attendee satisfaction 4 of 5 or better; any fault fixed or worked around within 3 minutes.

Who it is for: Office staff, teachers, event assistants, support staff, community hosts. Requirements: Basic computer skills. Materials: lesson text, worked examples, templates, rubric, 10-question check.

Safety and limits: Record only with clear consent. Protect meeting links and passcodes. Never share a screen with private tabs open.

lesson by lesson

8 modules with worked examples

Module 1 What makes a good call 4 hUnderstand

Sound matters more than picture. You will plan a call around one purpose, a decision and a short agenda sent in advance, so a half-hour meeting ends with named owners.

  • Audio first: a headset beats a laptop microphone.
  • Light from the front; camera at eye level.
  • Steady network: wire if you can; close heavy apps.
  • Quiet, tidy background and good manners.
  • Before any call, write a one-line purpose and a decision you need, such as choosing between two dates, and cap the agenda at three items so a 30-minute call ends with named owners.
  • Send the agenda at least 24 hours ahead with the join link and the time in two time zones. Then a team of ten does not lose five minutes to confusion at the start.
  • Test the microphone level by speaking at normal volume and watching the meter.
  • Place the camera at eye level using books if needed.
Worked example. Window behind the speaker makes a silhouette; turning the desk so light falls on the face fixes it in one minute.

Activity. Set up your space and record a 1-minute test.

Standard to meet. Test is clear in sound and face.

Common mistake. Relying on a laptop microphone.

Second worked example. A sales call looks dull because the speaker sits far from the camera. Moving the camera to eye level and one arm's length closer makes the face fill the frame, and attendees comment on the clarity.

Check yourself. What audio gear do you use?

Module 2 Tools and rooms 6 hUnderstand

Know the features before the day. You will compare platforms against a five-point checklist and prepare a backup route, so a failed room costs minutes rather than the session.

  • Waiting room, mute-all, chat, hand raise, breakout rooms.
  • Roles: host, co-host, presenter, attendee.
  • Passcodes and locked rooms for private meetings.
  • Open the tool on a phone as a guest to see what attendees see.
  • Compare two platforms on a checklist of five points: maximum people, recording, captions, breakout rooms and phone dial-in, then pick the one that meets all five for your usual group size.
  • Keep a backup route ready, such as a second link or a phone number, and share it in the invite so a failed room costs two minutes rather than the whole session.
  • Remove clutter from the background or use a plain wall.
  • Close your email and chat notifications before sharing.
Worked example. A webinar with 80 attendees uses a co-host for questions so the host can present.

Activity. List the features you will use and test each.

Standard to meet. Test all features with a guest.

Common mistake. Opening the tool for the first time as host on the day.

Second worked example. A 15-person team workshop uses breakout rooms of 3 people. The host sets 10 minutes, a shared notes page per room, and all five groups report back on time.

Check yourself. What did your guest test find?

Module 3 Audio and video setup 8 hApply

Test, adjust, test again. You will set up lighting, camera height and a recorded sound test, so participants hear you clearly and see you without distraction.

  • Choose microphone and speaker; check levels.
  • Use headphones to stop echo.
  • Check camera framing: head and shoulders.
  • Test screen sharing and audio sharing.
  • Place a light in front of your face, not behind you. Set the camera at eye level by stacking books under a laptop until the top third of the screen meets your eyes.
  • Do a two-minute test recording each time: speak a sentence, play it back, and check that your voice is clear, not echoing, and that the lowest background hum is gone.
  • Keep water and a spare charger within reach.
  • Open the joining link on a phone to see the guest view.
Worked example. Echo appears when two laptops in one room are open: mute one, use headphones.

Activity. Run a 15-minute test with a partner and fix three issues.

Standard to meet. Log three issues with fixes.

Common mistake. Testing alone.

Second worked example. A speaker's voice crackles on a phone microphone. Switching to a wired headset and moving away from the laptop fan clears the sound, and the check list records the headset as standard.

Check yourself. What did your partner hear?

Module 4 Network and quality 8 hApply

Know the numbers behind a bad call. You will test connection speed at the real meeting time and apply an ordered fix sequence, so freezing pictures are handled calmly.

  • Speed: a video call needs roughly 2 to 4 Mbit/s each way.
  • Delay above 150 ms feels awkward.
  • Lost data packets (small chunks of data) cause choppy sound.
  • Fallback: turn off video, then call in by phone.
  • Test your speed at the time of day you will meet, and aim for at least 3 Mbit/s up and down for one video call; if it falls below that, ask guests to turn cameras off.
  • If the picture freezes, switch off your own video first, then close other tabs and downloads, and only then move closer to the router or plug in a network cable.
  • Name your screen with your role, for example 'Host, your first name'.
  • Save the participants' names for the thank-you note.
Worked example. Link gives 1.5 Mbit/s up: turn off camera for non-speakers; speaker keeps video.

Activity. Run a speed and delay test three times and record.

Standard to meet. Record three readings in a table.

Common mistake. Ignoring upload speed.

Second worked example. Upload speed is 1.5 Mbit/s. Non-speakers turn off video; the speaker keeps video on; the session runs without freezing.

Check yourself. What are your three readings?

Module 5 Access and inclusion 8 hAnalyse

Everyone should be able to take part. You will use captions, advance files, spoken image descriptions and chat options, so people with different needs and connections can all contribute.

  • Captions on; share slides before the call.
  • Describe visuals aloud.
  • Allow chat as well as voice.
  • Time zones: offer two times or a recording.
  • Turn on live captions, share slides as a file ahead of time, and describe any image you show in one spoken sentence so people using screen readers or slow links are not left out.
  • Keep to a pace of one idea every two minutes, pause for five seconds after each question, and offer chat as well as voice so quieter or non-native speakers can join.
  • Practise muting and unmuting others politely.
  • Know where the chat save and attendance report are.
Worked example. A deaf attendee needs captions; check them before the session and offer notes afterwards.

Activity. Build an access checklist and use it.

Standard to meet. Apply the checklist to one session.

Common mistake. Adding captions at the end.

Second worked example. A learner with slow internet cannot watch video. You offer a phone dial-in, send the slides as a small file, and she follows the whole session at no extra cost.

Check yourself. Which access items did you set?

Module 6 Run the session 10 hCreate

A run sheet keeps the host calm. You will open early, set ground rules in the first minute and use a co-host for chat and time, so sessions finish as planned.

  • Run sheet: time, task, who, backup.
  • Open the room 10 minutes early; greet people as they arrive.
  • Set ground rules; manage questions.
  • Record only after announcing it and getting consent.
  • Open the room ten minutes early, greet people by name as they join, and give a rule in the first minute: mute when not talking, use the hand-raise button to speak.
  • Assign a co-host to watch the chat and the clock; when the planned time for an item is up, they signal you so a 60-minute session actually finishes in 60.
  • Keep the backup phone number in the invitation.
  • Offer a plain text summary of the session.
Worked example. Minute 0 welcome, 2 rules, 5 content, 40 questions, 50 summary, 55 close.

Activity. Write a run sheet and host a 30-minute session.

Standard to meet. Run sheet followed; times kept within 5 minutes.

Common mistake. No run sheet, so time slips.

Second worked example. A 45-minute training run sheet: minute 0 check sound, 5 icebreaker poll, 10 demo, 30 practice, 40 questions, 45 close. A poll runs long, so the practice is cut to 8 minutes.

Check yourself. What did you cut?

Module 7 Fix problems live 6 hEvaluate

Problems will happen; calm fixes keep trust. You will keep a one-page fix list and a handover plan for a dropped presenter, so problems are resolved without losing the audience.

  • Common: no sound, frozen picture, wrong room, someone cannot join.
  • Say what you are doing; give a plan B.
  • Send the joining link again and a phone number.
  • Log the fault and cure.
  • Keep a one-page fix list: no sound means check the output device and mute switch; no video means check browser permissions; lag means turn off video. Tape it beside your screen.
  • If the main presenter drops out, the co-host should take over within 30 seconds by saying what happens next, such as a short break or sharing the next slide.
  • Check accessibility settings such as caption language.
  • Time each part against the run sheet.
Worked example. Presenter freezes; co-host reads the notes while the presenter rejoins; lost time 90 seconds.

Activity. Practise five fault drills and time each.

Standard to meet. Fix each drill in 3 minutes or less.

Common mistake. Panicking in a fault.

Second worked example. A guest's microphone is muted and she does not know. The host sends a private message with the unmute steps and she is heard within 40 seconds, so the session continues.

Check yourself. What is your plan B?

Module 8 Measure and improve 4 hCreate

Learn from every session. You will gather a short survey and a session log, then compare figures across sessions to learn which change actually improved quality.

  • Ask attendees for a score and one comment.
  • Check join success rate and drop-offs.
  • Update the joining guide.
  • Plan 90 days.
  • After each session, send a three-question survey: was the audio clear, was the time well used, what one thing would you change. Aim for a response rate above 40 percent.
  • Keep a simple log with date, number joined, number who stayed to the end, and problems; after five sessions, compare the figures to see which fix helped most.
  • Keep a note of any fault and its fix.
  • Write the lessons after each session in three lines.
Worked example. 38 of 40 joined without help = 95%; satisfaction 4.4.

Activity. Report on three sessions.

Standard to meet. Report compares sessions and lists three changes.

Common mistake. Not asking for feedback.

Second worked example. After a session 27 of 30 guests answered the survey: 22 of those answers rated clarity 4 or 5 (81%). The top comment asks for slides in advance, so the next invitation attaches them.

Check yourself. What did attendees say?

case cards and glossary

Practise on cases; learn the words

Case 1. The echo

Everyone hears themselves.

Question: Cause and fix?

Model answer: Two open microphones in a room; mute one, use headphones.

Case 2. The late guest speaker

The speaker has not joined at start time.

Question: What do you do?

Model answer: Start with the welcome, call the number you hold, move the slot if possible, and keep the time.

Glossary

Host
The person who controls the meeting.
Co-host
A helper with host controls.
Breakout room
A small group space.
Latency
Delay between speaking and hearing.
Bandwidth
Data speed.
Run sheet
A timed plan.

assessment

How you are checked

Your evidence: space test, tool test list, run sheets, fault drill log, access checklist, three-session report. A mentor and one peer mark it with this rubric. Pass: no criterion at 'Not yet', and at least 8 of 10 check answers right.

Marking rubric (Not yet, Meets, Exceeds)
CriterionNot yetMeetsExceeds
Set-upMissing, or claimed without a recordClear sound and pictureNetwork and fallback tested
Run sheetMissing, or claimed without a recordFollowed within 5 minutesBackup used smoothly
AccessMissing, or claimed without a recordChecklist appliedFeedback from a user needing support
Fault handlingMissing, or claimed without a recordDrills under 3 minutesFaults prevented by testing
EvaluationMissing, or claimed without a recordReport for three sessionsChanges made and re-measured

Ten-question check, with model answers

Q1. Why audio first?

Model answer: People tolerate poor picture but not poor sound. (Covered in module 1: What makes a good call. To pass that module: Test is clear in sound and face.)

Q2. Where should light come from?

Model answer: In front of you. (Covered in module 1: What makes a good call. To pass that module: Test is clear in sound and face.)

Q3. What stops echo?

Model answer: Headphones and one open microphone per room. (Covered in module 3: Audio and video setup. To pass that module: Log three issues with fixes.)

Q4. Bandwidth needed per video participant?

Model answer: Roughly 2 to 4 Mbit/s each way. (Covered in module 4: Network and quality. To pass that module: Record three readings in a table.)

Q5. Why use captions?

Model answer: They help people who cannot hear well and anyone in a noisy place. (Covered in module 5: Access and inclusion. To pass that module: Apply the checklist to one session.)

Q6. When may you record?

Model answer: After announcing and with consent. (Covered in module 6: Run the session. To pass that module: Run sheet followed; times kept within 5 minutes.)

Q7. What is in a run sheet?

Model answer: Time, task, who and backup. (Covered in module 6: Run the session. To pass that module: Run sheet followed; times kept within 5 minutes.)

Q8. Plan B when video fails?

Model answer: Turn off cameras or join by phone. (Covered in module 7: Fix problems live. To pass that module: Fix each drill in 3 minutes or less.)

Q9. Why open as a guest?

Model answer: To see what attendees see. (Covered in module 2: Tools and rooms. To pass that module: Test all features with a guest.)

Q10. How do you compute join success?

Model answer: Joined without help divided by invited, times 100. (Covered in module 8: Measure and improve. To pass that module: Report compares sessions and lists three changes.)

jobs this leads to

Where this takes you

  • Webinar producer. Runs large online events.
  • Meeting room technician. Sets up rooms and tools.
  • Virtual classroom assistant. Supports teachers online.
  • Event support assistant. Handles chat and questions.

Next courses: Virtual Event Planning; IT Service and Support; Online Tutoring Platform.

ten locations and global

Your place

Recording and cross-border calls may need consent and notices; check your place and your attendees' places. Check your local rules with an adviser before you act for real.

India (Bengaluru)

Currency: write INR next to every number. Language: English, Hindi, Kannada. Personal data law to check: Digital Personal Data Protection Act 2023. Level frame: National Skills Qualifications Framework (NSQF) and the national credit framework. Partner to practise with: an industrial-training institute, a polytechnic, a small-business cluster or a Bengaluru incubator.

Netherlands (Eindhoven area)

Currency: write EUR next to every number. Language: Dutch, English. Personal data law to check: EU GDPR (Dutch: AVG), supervised by the Autoriteit Persoonsgegevens. Level frame: the Dutch qualification framework (NLQF) linked to the European Qualifications Framework. Partner to practise with: a regional college (MBO), a maker space or a small firm in the region.

UAE (Dubai and Abu Dhabi)

Currency: write AED next to every number. Language: Arabic, English. Personal data law to check: Federal Decree-Law No. 45 of 2021 (personal data protection). Level frame: the emirate education and training regulators (for example KHDA in Dubai) and the national qualifications framework. Partner to practise with: a free-zone business centre, a training institute or a municipality-licensed operator.

Brazil (Sao Paulo)

Currency: write BRL next to every number. Language: Portuguese (Spanish and English support). Personal data law to check: LGPD (Lei Geral de Protecao de Dados). Level frame: the national technical-education catalogue and the national S-system training bodies. Partner to practise with: a small-business support agency, a technical school or a local cooperative.

Canada (Toronto)

Currency: write CAD next to every number. Language: English, French. Personal data law to check: PIPEDA, with provincial rules where they apply. Level frame: the provincial colleges framework and the national credential-recognition guidance. Partner to practise with: a community college, a settlement agency or a Toronto business hub.

United States

Currency: write USD next to every number. Language: English, Spanish. Personal data law to check: state privacy laws (for example California), and COPPA for children under 13. Level frame: state and community-college credit systems. Partner to practise with: a community college, a workforce board or a small-business development centre.

Singapore

Currency: write SGD next to every number. Language: English, Mandarin, Malay, Tamil. Personal data law to check: Personal Data Protection Act (PDPA). Level frame: the Singapore national skills frameworks and the national credit system. Partner to practise with: a channel partner, a polytechnic or an approved training provider.

Australia

Currency: write AUD next to every number. Language: English. Personal data law to check: the Privacy Act 1988 and the Australian Privacy Principles. Level frame: the Australian Qualifications Framework (AQF) levels. Partner to practise with: a vocational college or registered training organisation, or a regional business chamber.

Hong Kong (Eastern Asia)

Currency: write HKD next to every number. Language: Chinese (Cantonese, Mandarin), English. Personal data law to check: the Personal Data (Privacy) Ordinance. Level frame: the Hong Kong Qualifications Framework. Partner to practise with: a college, training body or business chamber.

Georgia and Israel (Western Asia)

Currency: write GEL or ILS next to every number. Language: Georgian, Hebrew, Arabic, English. Personal data law to check: the personal data law of the country where the learner lives. Level frame: the national qualifications framework of that country. Partner to practise with: a local college, chamber or training body.

Cayman Islands (Caribbean)

Currency: write KYD next to every number. Language: English. Personal data law to check: the Data Protection Act. Level frame: the local education and training framework. Partner to practise with: a local training body or business chamber.

Mexico

Currency: write MXN next to every number. Language: Spanish, English. Personal data law to check: the federal law on personal data held by private parties. Level frame: the national competency certification system and the education ministry levels. Partner to practise with: a technical college or business chamber.

ladder L1 to L7

Slide by slide, with notes

Seven slides, one for each level. Step in at your level and move up; credits stack.

Slide 1. L1 Basic: Basics of calling

On the slide: L1 Basic · Basics of calling

Notes: Join an online meeting with camera, sound and your name set up properly. Notes: test your set-up with a friend before the call. Standard: you are heard and seen clearly in the first minute.

Slide 2. L2 Awareness: Awareness

On the slide: L2 Awareness · Awareness

Notes: Explain the main parts of a conference session (audio, video, sharing, chat) and the usual faults. Notes: make a one-page fault card for a participant. Standard: five faults, each with a fix.

Slide 3. L3 Foundation: Foundation

On the slide: L3 Foundation · Foundation

Notes: Host a small meeting with a run sheet, muted guests, shared screen and a chat monitor. Notes: use a free tool with three friends. Standard: starts on time, agenda kept and notes sent.

Slide 4. L4 Practitioner: Practitioner

On the slide: L4 Practitioner · Practitioner

Notes: Run a workshop with breakout rooms, polls and a recording where everyone agrees. Notes: consent is taken at the start and in writing. Standard: recording only with consent, and feedback from at least five attendees.

Slide 5. L5 Specialist: Specialist

On the slide: L5 Specialist · Specialist

Notes: Host and technically run three online sessions (small meeting, workshop, larger webinar) with run sheets, recordings where agreed, and feedback. Notes: each run sheet has a back-up plan for audio failure. Standard: all three sessions run to time, with a fault log and a ratings summary.

Slide 6. L6 Advanced: Advanced

On the slide: L6 Advanced · Advanced

Notes: Run large events with a producer, moderators and an accessibility plan. Notes: add captions, a support line and a rehearsal checklist. Standard: rehearsal completed, accessibility checked, drop-out rate reported.

Slide 7. L7 Super expert: Super expert

On the slide: L7 Super expert · Super expert

Notes: Set the meeting-quality standard (audio, camera, access, recording consent) and teach the hosts who use it. Notes: review call-quality logs and complaints every quarter.

next

Draft

Draft flagship. Own wording; no outside brand, school or person names. Not live.

All courses Join