Presentation skills, public speaking techniques, visual aids, and audience engagement. Covers presenting to city councils, community groups, and professional organizations.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
Presentation skills, public speaking techniques, visual aids, and audience engagement. Covers presenting to city councils, community groups, and professional organizations.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamPrepare and deliver effective presentations to diverse audiences
Building department professionals speak in public far more often than most expected when they took the job. The venues are specific and recurring: presenting the budget, fee schedule, or annual permit activity to the council or commission; testifying before the board of appeals; explaining an enforcement action or a proposed code adoption at a neighborhood meeting; briefing a homebuilders association on new requirements; making a media statement after an incident; and training junior staff. Each venue has its own rules, but in all of them the speaker represents the department, and the audience judges the whole building safety program by how clearly and credibly that one person communicates. Building Department Administration makes the point directly: the law is behind the building safety program, but the law is not enough — the building official must win over public opinion, and much of that work happens in these rooms.
Preparation starts with the audience, not the content. Before assembling a single slide, answer three questions. Who is in the room — elected officials, appeal board members, angry neighbors, contractors, reporters? What do they already know — almost never the code? What decision or action do you want from them? Every choice about structure, vocabulary, visuals, and length follows from those answers. A presentation that would impress a code-development committee will lose a city council in ninety seconds.
For decision-making bodies — councils, commissions, boards — structure the presentation conclusion-first. State the bottom line in the opening sentence: what you are asking for and why it matters. Support it with no more than three points, each backed by a fact the audience can verify. Then state the ask explicitly: "I am requesting adoption of the fee schedule as presented." This mirrors the point-up-front principle the Basic Inspection Skills text applies to written communication: the point stated clearly and briefly right up front, followed by clear direction on the action requested. Decision-makers are impatient with narrative buildup; a presenter who spends eight minutes on background before revealing the request gets interrupted or asked "what exactly do you want from us?" — and at that moment control is lost.
Time discipline is part of respect for the body. If the agenda allots ten minutes, prepare eight and leave the rest for questions — councils cut off rambling presenters, and being cut off mid-argument is worse than never making the argument. Rehearse aloud, time it, and cut until it fits. Prepare a one-page handout that carries the detail so the oral presentation stays at the level of conclusions while the record still contains the support. When a councilmember asks a detailed question, "that's line four of the handout in front of you" beats a fumbled recollection.
A building official must present a proposed permit fee increase to the city council. Costs have outrun revenue and the fee schedule has not changed in years. The official opens with the conclusion: "I'm asking the council to adopt the updated fee schedule. It restores cost recovery for the permit program, keeps plan review times where builders need them, and requires no general-fund support." Three supporting points follow: what the program costs, what current fees recover, and what comparable jurisdictions charge. Each councilmember has a one-page handout with the numbers. When a member asks the predictable hostile question — "Why should builders pay more for the same service?" — the official answers calmly and factually: the fee buys plan review and inspection, current fees no longer cover that work, and without the adjustment either service slows down or taxpayers subsidize private construction. No defensiveness, no jargon, no filibuster. The measure survives pointed questioning because the structure did the work: the ask was heard in the first sentence, the support was on one page, and the answers were direct. The alternative — ten minutes of budget history before any request, no handout, improvised answers — is how fee proposals die.
The most common failure is presenting to decision-makers the way one would present to peers: leading with background, burying the request at the end, and assuming code literacy. The correction is conclusion-first structure, three points, explicit ask. A second failure is overrunning the time slot; the correction is rehearsing against a timer and cutting content, not talking faster. A third is bringing no leave-behind; the correction is the one-page handout. A fourth is failing to anticipate questions — the pointed questions at a fee hearing or appeal are predictable, and Building Department Administration's media-interview guidance applies here too: get the concerns in advance where possible, research, and rehearse answers until they can be delivered casually yet thoroughly. Finally, the building official should cultivate allies among elected officials through ongoing education — field trips, ride-alongs, association meetings — long before needing their votes, while staying at arm's length from political debate and avoiding anything that looks like favoritism.
Use visual aids and technology to enhance presentations
The audiences building department staff address almost never speak code. Building Department Administration is blunt about this in the media context: neither the reporter nor the general public knows enough about the code to understand it, so the official must simplify the problem with thoughtful answers — and the same holds for councilmembers, appeal boards, and neighbors. Translation into plain language is the core presentation skill. Replace terms of art with ordinary words: "tear down" rather than "abate," "community" rather than "jurisdiction," "escape window" rather than "emergency escape and rescue opening." Prefer concrete examples, and frame every requirement by its consequence for the listener — the "what this means for a homeowner" test. "This is what keeps a bedroom survivable in a fire" lands; the same requirement recited by section number does not. The Basic Inspection Skills face-to-face guidance compresses it: keep it simple; do not use jargon or make speeches.
Visual aids should follow the same translation principle. Show buildings, not spreadsheets. A photograph of a deck collapse explains ledger attachment better than any table; a diagram of a house with inspection points labeled explains what inspectors do better than a process flowchart; photos of storm damage in code-built versus pre-code construction make the case for adoption better than statistics. When numbers are unavoidable — budgets, fees, permit volumes — reduce them to one chart with one message and put the full detail in the handout. If a slide must be studied to be understood, it belongs in the leave-behind, not on the screen.
Slide discipline matters as much as slide content. The count must fit the time: a thirty-minute talk does not support forty-five slides, because racing through material loses the audience and eliminates discussion. Slides are visual support, not the script — a presenter reading dense bullets aloud has converted the audience into proofreaders. One idea per slide, minimal text, a visual where possible. And verify the technology: arrive early, test everything, and be prepared to present with none at all, because equipment fails and the meeting proceeds anyway. The handout doubles as the failure plan.
The same plain-language and visual standards apply in every outreach venue Building Department Administration recommends for putting the department's best foot forward — home shows, Building Safety Month displays, an "Ask the Building Official" newspaper column, department open houses and tours.
A plans examiner is asked to brief the local homebuilders association on newly adopted energy provisions. The first draft is forty-five slides walking through the changes section by section for a thirty-minute slot. The examiner rebuilds it around the audience's actual question — "what do I have to build differently, and what will it cost me?" The final deck is twelve slides: the three changes that affect most local projects, each shown with a photo or detail drawing of the compliant installation and a plain-language explanation of what changed and why, plus one slide on how plans already in review will be handled. Section-by-section detail moves to a handout. The briefing finishes in twenty minutes, leaves ten for questions, and the questions are specific and productive because the audience understood the material — builders heard the reasons, saw the details, and had their objections answered face to face.
The classic mistake is the code-recitation presentation — section numbers, defined terms, and exception language delivered verbatim to an audience that cannot parse them. The correction is ruthless translation: plain words, concrete examples, consequences for the listener. A second mistake is data-dense visuals — spreadsheet screenshots and unreadable tables; the correction is one message per slide, buildings and photographs over numbers, detail in the handout. A third is too many slides for the time, which forces rushing and kills engagement; the correction is cutting the deck to fit comfortably with room for questions. A fourth is reading slides aloud; slides support the speaker, not the reverse. A fifth is trusting the technology; the correction is arriving early, testing everything, and carrying a no-technology fallback.
Manage presentation anxiety and engage audience questions
Delivery rests on fundamentals that are learnable, not innate. The first is nonverbal communication: by most estimates it — posture, gestures, eye contact, facial expression, physical positioning — accounts for greater than 50 percent of communication, and audiences read it whether or not the speaker knows it is being sent. The practical guidance from the Basic Inspection Skills text transfers directly from the jobsite to the podium: make eye contact, keep hands open and arms uncrossed, and let body language signal openness to discussion and questions; avoid anything that conveys boredom, anger, ridicule, superiority, or intimidation. The second fundamental is pace: nervous speakers rush, and rushed delivery reads as uncertainty, while deliberate pace and pauses read as command of the material. The third is working from notes, not a script — a read speech loses eye contact, and with it most of the nonverbal channel, while an outline of key points keeps the speaker connected to the room.
Anxiety itself is managed primarily through preparation. Fear of public speaking is mostly fear of the unknown — the unanticipated question, the lost train of thought, the failed projector. Preparation removes the unknowns: rehearse aloud, time the talk, rehearse answers to the hard questions, check the room and equipment early, and keep the handout as a safety net. Speakers who know their opening cold get through the highest-anxiety minute on autopilot, and momentum carries from there. Experience does the rest — every presentation makes the next one easier.
Then there are the hard rooms. At a hostile neighborhood meeting about an enforcement action, the pattern is acknowledge, facts, boundaries: acknowledge the concern respectfully and let people be heard; respond with facts about what the code requires and what the department did; and hold the line on scope — the meeting is about the enforcement action, not every grievance against city hall. Losing composure is losing the meeting; the inspector-skills guidance for difficult conversations applies — tact, empathy, and firm resolve, without apologizing for the code or for doing the job. When a questioner cannot be satisfied in the room, offer a specific follow-up afterward. For loaded questions from a council dais, answer the question actually asked — directly, briefly, factually; restating the question as understood confirms the target and buys a moment to think. When the answer is not known, "I don't know, and I'll get you an answer by Friday" beats a guess every time — a wrong guess on the record can undo years of credibility, while a prompt, accurate follow-up builds it.
Media discipline is its own category. The department speaks with one voice: inform the jurisdiction's public information officer before any media contact and follow the PIO's direction on message. After an incident, stay in your lane — describe the department's role and process; do not speculate on causes under investigation. Nothing is off the record. Be honest and to the point; do not sugarcoat or hide behind waffle language, and never ask to review a story before it runs. Ask for questions in advance when possible, rehearse, and treat the interview as a chance to educate the public through the reporter.
Board-of-appeals testimony calls for a different register again: facts and records, not advocacy. The official explains what the code requires, what was observed, and how the determination was reached — supported by the file, the photographs, and the correspondence. The inspector-skills principle that every record should be written as if an elected official, judge, or reporter might read it becomes literal in a hearing. Argue nothing the record does not support, concede uncertainty honestly, and let the board weigh the evidence. Passion reads as bias in a quasi-judicial setting; measured factual testimony reads as credibility.
Finally, supervisors should deliberately build these skills in junior staff. Start small — a five-minute staff-meeting briefing, then a contractor-breakfast presentation, then a supporting role at a council session — and pair each opportunity with a dry run in front of colleagues who ask the hard questions first. A department where only one person can speak in public has a single point of failure.
A building official faces a packed, angry neighborhood meeting over an enforcement action on an unsafe vacant structure. Half the room wants the building demolished yesterday; the owner's supporters call the department heavy-handed. The official acknowledges both concerns as legitimate, then walks through the facts in plain language with photographs: what the inspection found, what the code requires, what notices were issued, and what happens next, with dates. When a resident launches a broader attack on city permitting, the official sets the boundary — tonight is about this building; other concerns get a direct phone number and an offer to meet. When another asks a technical question the official cannot answer precisely: "I don't want to guess on that — I'll have the answer to you this week." The meeting stays tense but productive, and nothing said tonight will read badly in the newspaper or a courtroom later, which is the standard every public statement should meet.
The most damaging mistakes in hard rooms are emotional: arguing with a hostile questioner, losing composure, or matching aggression with aggression — all of which surrender the professional high ground. The correction is acknowledge-facts-boundaries delivered with calm body language. A second mistake is guessing under pressure rather than saying "I'll find out"; guesses become commitments. A third is speculating to media about causes or blame, or speaking to reporters without looping in the PIO; the correction is one voice, known facts only, nothing off the record. A fourth is scripted, head-down delivery; the correction is notes, rehearsal, and a cold-memorized opening. A fifth is advocacy in appeals testimony; the correction is facts and records, delivered without heat.
This course provides comprehensive professional development in public speaking and presenting for building department staff. Presentation skills, public speaking techniques, visual aids, and audience engagement. Covers presenting to city councils, community groups, and professional organizations. Participants learn to prepare audience-first presentations for the venues that define the job; to structure requests for decision-makers with conclusion-first organization, three supporting points, and an explicit ask; to translate code language into plain language supported by visuals of buildings rather than spreadsheets; to command the nonverbal channel that carries most of the message; and to navigate hostile meetings, loaded questions, media interviews, and appeals testimony with composure, facts, and discipline — the communication judgment that determines whether the public, elected officials, and the industry trust the building safety program.