Webinar Script: What to Say Without Assuming Too Much

Open your webinar script with a situation, not a verdict

An opening becomes intrusive when it diagnoses the viewer before you have earned their trust. “You’re overwhelmed because you don’t have a proper process” contains several untested assumptions: how they feel, what caused it, and what they lack.

Start with something they can recognise or reject without having to defend themselves. For a manuscript-revision webinar, you could say: “You open your draft to improve a chapter. Before long, you’re changing individual sentences, moving paragraphs, and wondering whether the chapter belongs in the book at all.”

Then name what the session will examine: “Today, we’ll look at how to separate different kinds of revision, so you can decide what deserves your attention before you start rewriting.” This is a statement about your teaching, not a prediction about their eventual success.

You can acknowledge variation without making the opening cumbersome: “Your draft may be nearly finished, or you may still be working through an early version. The distinction we’re discussing is between changing what a chapter does and changing how its sentences read.” You have established relevance without pretending everyone arrived at the same point.

Describe friction without assigning feelings or motives

Pain-focused copy often moves too quickly from an observable difficulty to a personal judgment. A viewer who keeps revising a chapter might be unsure about its purpose. They might also be responding to thoughtful editorial feedback. Calling that behaviour procrastination collapses different circumstances into one accusation.

Write about the friction before interpreting it. “When structural decisions remain open, a polished paragraph may still need to move or disappear” explains a cost. “You’re hiding behind perfectionism” assigns a motive. You do not need the second sentence to make the first useful.

Conditional language helps when it identifies a real situation. “If you keep returning to the same chapter without knowing what you’re trying to change, start by naming the revision question.” That is more actionable than “If you’re ready to finally take yourself seriously.” One offers a practical starting point; the other makes a judgment about character.

During drafting, look especially closely at phrases beginning with “you feel,” “you always,” and “you’re afraid.” Sometimes they will reflect language your audience genuinely uses. Even then, present the experience as a possibility rather than a universal truth.

• Instead of “You’re frustrated with your draft,” try “Your draft may contain several unresolved decisions.”
• Instead of “You lack confidence,” try “You may want a clearer basis for choosing what to revise.”
• Instead of “You keep making excuses,” try “The next revision task may still be too vague to begin.”

Make your explanations independent of insider knowledge

Your script can unintentionally assume that viewers share your vocabulary, professional background, or familiarity with your previous work. Phrases such as “as everyone knows” and “obviously” make that assumption audible. They can leave someone feeling behind before you have explained anything.

Introduce specialised language at the point where it becomes useful. Rather than “Start with a developmental pass,” write: “First, review the manuscript’s structure: what each chapter contributes, what order the chapters need, and what is missing. I’ll call that a structural review.” You can then use the shorter term without repeatedly defining it.

Give examples enough local context to stand alone. “Look at your chapter map” presumes the viewer already has one. “Write a short description of what each chapter is there to do; those descriptions become your chapter map” makes the reference understandable without a separate lesson.

This does not mean explaining every familiar word or treating experienced viewers as beginners. It means removing unnecessary entry requirements. Your viewer should need attention and relevant interest—not membership in your professional circle—to follow the reasoning.

Match the strength of each sentence to what you know

A script often becomes less credible when a sensible recommendation turns into an absolute rule. “Never edit sentences before reviewing structure” is broader than “For this exercise, leave sentence-level edits until you have decided what the chapter needs to do.” The second sentence is still decisive. Its scope is simply clearer.

Separate definitions, recommendations, and predictions. A definition can be direct: “Here, structural revision means changing the organisation or substance of the manuscript.” A recommendation should carry a reason: “Review structure first when sentence polishing would distract you from unresolved chapter decisions.” A prediction about the viewer’s results deserves more caution.

You do not have to soften every line with “perhaps” or “maybe.” Place uncertainty where it actually belongs. “This question helps you identify the purpose of a chapter” explains the function of a question. “This question will make your manuscript compelling” promises an outcome that depends on much more than your script.

Also remove declarations about what your audience has just understood. Replace “Now you know exactly what to do” with a concise restatement: “The distinction is between deciding what needs to change and making that change.” The viewer retains the freedom to understand, reconsider, or return to the explanation.

Write an invitation that does not manufacture agreement

Near the end of a webinar, scripts sometimes begin treating attention as consent. “You’ve stayed this long, so you must be ready” turns viewing behaviour into a buying signal. “If you’re serious about your book” makes a purchase sound like evidence of commitment. Neither is necessary to make a clear invitation.

Use language that owns your intention instead. You can say, “I’d like to tell you about the revision workshop I offer.” There is no need to disguise the commercial part of the session or present it as the viewer’s inevitable next move.

For a hypothetical workshop invitation, your draft might read: “You can use the distinction we covered when you next review your manuscript. I also offer a workshop focused on revision. If you’d like to consider it, the workshop page explains what is included and how it works.” Use wording like this only when the referenced page actually contains that information.

Finish with the action itself: “Open the workshop details using the link beside this recording.” Adjust the instruction to match the published experience. Avoid adding a final emotional test such as “Are you finally ready to back yourself?” The invitation can be direct without making the viewer prove anything about who they are.

Run an audience-assumption edit before you record

Once the full draft exists, give it a dedicated review for assumptions. This is different from checking grammar or trimming length. You are examining the relationship the language creates between you and someone you cannot observe.

Search the document for “you,” “your,” “everyone,” “always,” “never,” “obviously,” and “by now.” These words are not forbidden. They are useful inspection points. For each occurrence, ask whether the sentence offers information, gives an instruction, or claims knowledge of the viewer.

Mark each questionable sentence with the assumption it contains. “You already know this” assumes knowledge. “You’re relieved to hear that” assumes emotion. “You can’t afford to wait” assumes circumstances. Then decide whether to remove the claim, make it conditional, or replace it with something concrete.

Finally, read the invitation separately from the teaching. Without the momentum of the full presentation, does it still sound reasonable and respectful? If it depends on guilt, flattery, or presumed agreement, rewrite it. A sound invitation should survive without emotional leverage.

• Check knowledge assumptions: have you explained the terms the sentence relies on?
• Check emotional assumptions: are you describing a possible feeling as a fact?
• Check motive assumptions: are you interpreting behaviour without enough context?
• Check agreement assumptions: are you treating attendance or attention as a decision?
• Check action instructions: does the wording match what viewers can actually do?