Skip to the lesson
ChalkLineclear audio for people who teach online

The column

After the Bell

Margin notes from the teaching day — shorter than our guides, more honest than our lesson plans. One page, newest first, written between bookings. When an entry grows up into a full guide, we link it.

Written by the ChalkLine team · The column lives on this one page, by design — like a staffroom noticeboard, you read it top to bottom

The construction-site semester

In June, a crew began renovating the flat next to one of our editors' — the one who teaches conversation classes at 8 a.m. The naive plan was apologizing daily and hoping. The actual solution ended up being three boring moves executed together: shifting two regulars to 7 a.m. (they turned out to be larks and were delighted), a suppression layer that ate the angle grinder's midrange astonishingly well, and — this is the one nobody does — a one-line message to every student at the start of the month: "There's construction next door until October; my noise filter handles most of it, tell me if anything slips through."

The interesting result wasn't the audio. It was that zero students complained all summer, while colleagues in the same building with quieter flats and no announcement fielded weekly comments. Expectation-setting did work the software couldn't. The generalized version of all three moves is in the home-noise guide, filed under "the schedule is a noise tool" and "the scripts."

Beginners hear your noise louder than you do

A pedagogical observation that audio advice never makes: noise tolerance scales with proficiency. Your C1 student reconstructs a syllable the traffic ate — their brain autocompletes from context, same as yours does. Your A2 student cannot. For them, that syllable was the whole data point, and the sentence collapses without it. The cruel arithmetic: the students who most need your clean consonants are precisely the ones least equipped to tell you something's wrong, because "there was a noise artifact around your dental fricatives" is a C2 sentence.

Practical consequences we've adopted: judge your audio by your lowest-level student's experience, not your average review score; watch beginners' faces when a motorbike passes — the flinch-and-reread look is your real audio meter; and if you must schedule lessons in your building's loud hours, give beginners the quiet ones. The software half of the answer is the main guide; this note is the half about who pays when you skip it.

The kettle confession

An embarrassing discovery from reviewing our own lesson recordings (we preach the baseline-recording habit; occasionally we obey it): a kettle, boiled mid-lesson roughly every second morning class, clearly audible in the file — and completely inaudible to the teacher who boiled it. Household noise you produce yourself gets edited out by your own brain with remarkable efficiency. The student's brain extends no such courtesy.

This is the case for recording yourself even when nothing seems wrong: your ears are the least reliable witness to your own noise. The 60-second baseline recording — described in the setup guide's ritual — caught in one morning what months of live teaching hadn't. The kettle now boils before class. The suppression layer catches the fridge we also didn't know we could hear.

A replay humbled me

One of us hosted a webinar in August — good turnout, warm chat, felt great. Then came the VOD. Live adrenaline is a generous audio engineer: it mixes out the air conditioner, forgives the two notification chimes (we teach this! we wrote the checklist!), and rounds every fumbled transition up to charm. The replay, watched cold three days later on headphones, extended none of that credit. The chimes were mortifying. The air conditioner was a co-host.

Two rules came home with us: the replay is the real event — more people watched the file than the live room, which the recording guide now says in its first paragraph — and the pre-flight checklist gets executed by a human who assumes they're above it, so put "notifications off, system-wide" first, where even the confident can't miss it. The full host-side routine is in the webinar guide, freshly humbled.

The mute button is a classroom skill, not a setting

Watching a brilliant kids' educator run a full class of nine-year-olds with pristine audio, we expected to find exotic software. We found choreography. Minute one of week one, she teaches the mute button the way you'd teach a hand-raise: everybody mutes, everybody unmutes, everybody mutes — "microphone on means you're on stage." From then on it's a game mechanic the kids enforce on each other, which is the only enforcement that scales to twelve households you can't visit.

We stole the whole approach for the Outschool playbook. The wider lesson generalizes past kids: every audio problem that lives on the far side of other people's microphones is a norms problem wearing a technical costume. Software cleans your side; culture cleans the grid. You need both, and only one of them costs money.

Two filters walked into a signal chain

A tutor wrote to us with a puzzle: she'd bought the right software, followed a setup guide (not ours, we checked, with relief), and her students still said she sounded "like talking through water." Diagnosis took one question: what else is processing your microphone? The answer was everything. Her operating system's voice mode was on. Her suppression app was on. Her browser's processing was on default. Three well-meaning filters, each receiving the previous one's output and confidently "improving" it — by the third pass, her consonants had been enhanced into soup.

The counterintuitive fix for bad audio after installing good software is almost always subtraction: one dedicated suppression stage, everything else switched off, and suddenly the expensive tool sounds like its own marketing. We wrote the rule into the setup chain — one filter, chosen deliberately — but the general form deserves its own line in the column: when stacking help makes things worse, it isn't a paradox, it's signal processing. Also, arguably, a lesson about committees.


About this column. Entries are working notes from the ChalkLine team, not vendor-fact pages — when an entry mentions prices or platform features, the load-bearing verification lives in the linked guides, where dates are printed. The bell rings, we go back to class.