Building relationships with city councils, county boards, and planning bodies. Covers presentation skills, political awareness, and advocacy for code compliance and resource needs.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
Building relationships with city councils, county boards, and planning bodies. Covers presentation skills, political awareness, and advocacy for code compliance and resource needs.
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 teamPresent building department issues and needs to elected officials
Before a building official can present an issue to elected officials effectively, they have to understand who is actually in the room and what each body is empowered to do — a jurisdiction's governance is a layered structure, not a single audience. The governing body — the city council or county board of commissioners — is the legislative authority: it adopts codes, sets the budget, approves the fee schedule, and hires the executive manager. The executive manager (city manager, county administrator, or department head) is the building official's direct supervisor in most jurisdictions; Building Department Administration is explicit that building officials are hired by executive managers, working directly for the elected leadership, who want certain results. Alongside the council sit appointed bodies with narrower charges: the planning commission and zoning board, which act on land use and development approvals, and the board of appeals, a quasi-judicial body that hears challenges to the building official's technical determinations. Presenting to the wrong body, or asking a body to act outside its jurisdiction, wastes credibility the official cannot easily rebuild.
The most important thing to understand about the building official's place in this structure is that the building official is professional staff, not a politician — the role is to administer and enforce the adopted codes and advise the elected leadership with technical facts, not to campaign, take sides in political debates, or trade on relationships. Building Department Administration lists recommending final actions on code amendments to the governing body among the official's duties, always in an advisory capacity: staff recommends, the elected body decides. An official seen as a technician earns durable credibility across the political spectrum and through changes of administration; one seen as a player loses it the moment the political winds shift.
Serving the governing body well is mostly a matter of discipline in how information is delivered. Elected officials are time-pressed generalists juggling dozens of issues, almost none of whom know the code; they need conclusions first, support second, and detail available but not forced on them. A decisions-first briefing states the bottom line in the opening sentence — the problem, what you recommend, and what you need from the body — then backs it with a few verifiable facts. Its written companion is the one-page memo: the request and its justification on a single page the official can leave behind, so the record carries the detail while the oral briefing stays at the level of conclusions. Building Department Administration frames the underlying relationship as one built on trust and quality of work, achieved through persistence and time — and nothing erodes that trust faster than a surprise. Bad news delivered early and privately, before a public meeting, lets elected officials prepare and preserves the relationship; the same news breaking in front of cameras, with the council caught flat-footed, does lasting damage. The governing rule is simple: no surprises at public meetings.
A building official discovers that a long-delayed permit for a controversial development — a project several council members have publicly championed — has a structural deficiency that will push approval back at least two months. Rather than say nothing and hope the delay goes unnoticed, the official applies the no-surprises principle. Before the item can surface at a public meeting, the official sends the executive manager a one-page memo: the bottom line (roughly two months' delay), the reason in plain language (a structural detail must be redesigned and re-reviewed to meet the code), and what the department is doing about it (expedited re-review the moment corrected drawings arrive). It goes up the chain so the council members most invested hear it privately first. When the delay comes up at the meeting, the council is already briefed, the questions are informed rather than blindsided, and the official's answer is a calm restatement of facts the members already have on paper — the official protected the leadership from an ambush rather than becoming the source of one.
The most common mistake is presenting to elected officials the way one would brief a peer inspector — leading with background, burying the request, and assuming code literacy. The correction is the decisions-first structure: conclusion first, a few verifiable points, an explicit ask, and a one-page leave-behind. A second mistake is confusing the roles of the various bodies — asking the council to overturn a determination that belongs to the board of appeals, or the planning commission to resolve a code interpretation; the correction is routing each issue to the body empowered to act. A third mistake is letting bad news reach elected officials in public for the first time, corrected by early, private notice up the chain of command. A fourth is drifting out of the staff lane into advocacy — the correction is to stay a technical advisor, recommend rather than decide, and let the elected body own the policy call.
Manage political relationships while maintaining code objectivity
The central discipline of this work is apolitical enforcement: the code is applied uniformly, to every applicant, regardless of who they are or who they know. Building Department Administration is candid that the pressure to bend this is constant — some elected leaders build and therefore require permits, some owe political favors for support, and some will simply ask for special consideration. The text warns that acceding to such a request may appear to be favoritism to mollify a politician, and that appearance is corrosive whether or not any rule is actually broken. Uniform enforcement is what makes the department credible and legally defensible: the moment a contractor can point to a connected applicant who got a faster or softer review, the department's authority over everyone else weakens.
The recurring test is the political-pressure-on-a-permit problem: an elected official asks — sometimes gently, sometimes not — to expedite, approve, or overlook something for a favored applicant. The building official should expect these requests, no matter the size of the jurisdiction, and should have a response ready that holds the line without turning the relationship adversarial. The script has three moves. First, acknowledge the person and the interest genuinely: "I understand this project matters and I want to see it succeed." Second, state what the code and process require, plainly and without apology: "Every permit goes through the same plan review so we can certify it's safe; I can't move one ahead of the queue." Third, offer the legitimate paths that remain: a status update, a pre-submittal meeting to clear obstacles faster, the reviewer's name, or — where a genuine equivalency or hardship exists — the formal appeal. The official never simply says "no" and hangs up; Building Department Administration warns that an official who develops a reputation for always saying "no" is regarded as too inflexible. The art is to be helpful about everything except the one thing that would compromise objectivity. Where a legitimate community interest genuinely justifies acceleration — a project crucial to a large number of jobs, for instance — the official may seek a balance that serves the majority, but through transparent means applied to like projects, never as a private favor.
The board of appeals relationship demands a related discipline. The board is a quasi-judicial body with authority the official must respect even when it rules against the department. At a hearing, the official's job is to present facts, not to advocate for an outcome: the applicable code requirement, the specific deviation requested, and any safety implications — then let the board decide. Building Department Administration notes the board's authority is bounded — under the adopted code it determines whether the code was incorrectly interpreted, does not fully apply, or whether an equivalent or better form of construction is proposed, and it cannot simply waive requirements — and the official's testimony should help the board stay within those bounds by keeping the discussion technical. When the board reverses the official, the professional response is to accept the decision, document it, and apply it going forward, rather than treating it as a personal defeat.
A council member calls the building official directly about a commercial permit for a campaign donor. The project has stalled in plan review over unresolved code issues, and the member asks the official to "just push it through" as a personal favor. The official runs the script. The acknowledgment: "I hear you — I know this project is important to you and the applicant, and I'd like to see it get built." The boundary, plainly and without defensiveness: "Every project goes through the same review so we can certify it meets the code, and I can't move one ahead of that or approve it before the open issues are resolved." The open paths: "Here's where it stands, here's what the applicant needs to submit to clear the last items, and I'll set up a meeting with our reviewer this week so it moves as fast as it legitimately can." The member gets no favoritism but no cold rejection either; the applicant gets a faster legitimate route, and the official keeps both integrity and the relationship.
The first mistake is treating a request for a favor as either a simple yes or a flat no; the correction is the acknowledge-explain-offer script that holds the code line while keeping the person on side. A second is drifting toward favoritism to smooth a relationship — the correction is uniform enforcement, applied and documented the same for everyone. A third is arguing for an outcome at a board of appeals hearing instead of presenting facts, corrected by technical testimony that respects the board's authority. A fourth is reacting badly to a reversal by relitigating or slow-walking compliance; the correction is to accept and apply the board's decision professionally. Underlying all of them, Building Department Administration's standing instruction is to remain at arm's length from the political debate and avoid commitments that demonstrate political favoritism.
Advocate effectively for resources and policy changes
Advocating for budget and staff is where the building official most often stands before the governing body asking for something, and the durable rule is data over anecdote. A story about a stressed inspector moves no council; defensible facts do. Building Department Administration describes this dynamic around fees: the extent to which the department should be self-supporting is a question that must be answered by the political body, and the official will ordinarily be called upon to make a presentation acquainting that body with the need. The same holds for staffing: to justify additional inspectors, the official assembles the workload data — permit volumes, inspection demand, turnaround times against targets, the capacity gap — and pairs it with comparisons to similarly sized jurisdictions and the fee revenue the added positions would generate. That evidence turns "we're busy" into a fiscal argument an elected body can defend to its constituents. The companion course on strategic planning for building departments develops the longer-horizon side of this — tying resource requests to a multi-year plan the governing body has already endorsed — and the companion course on performance dashboards and data analytics covers how to capture and present the workload metrics that make the case objective.
Advocating for policy — new code editions and local amendments — runs on a different track: the code-adoption cycle, where the division of labor between staff and the elected body is the whole game. The building official's role is technical: recommending which edition to adopt and which local amendments to carry, explaining in plain terms what changes and why it protects the community, and answering the leadership's questions. Building Department Administration lists recommending final actions on code amendments to the governing body among the official's duties — recommending, not deciding. The elected body owns the policy call, because a model code has no legal force until it is properly adopted; regardless of whether the official believes it is a good idea, it must be passed into law by the governing body. The mechanism is a public hearing, where the proposed adoption is aired, the public can comment, and the body votes; the official's job there is to supply the facts, frame the choice, and let the leadership decide. Part of doing this well is long-term education, not last-minute persuasion. Building Department Administration recommends that officials make allies of elected leaders well before they need their votes — inspection field trips one at a time, invitations to code-group and homebuilder association meetings, and showing them building-safety failures in the community and asking for their input — all while remaining at arm's length from political favoritism. An elected body that already understands what the department does is far easier to move when the ask finally comes.
A building official has to persuade the county board of commissioners to adopt the newest code edition and fund two additional inspector positions, after six months of missed turnaround targets. Rather than pleading understaffing, the official builds two evidence-based cases. For the positions: a chart of permit volume against inspection capacity, turnaround times slipping past the department's published targets, a comparison with three similarly sized counties that staff at higher ratios, and the projected permit revenue the new inspectors would support — much of it self-funding. For the adoption: a plain-language summary of what the new edition changes for typical local projects, why those changes matter for safety, and how projects already in the pipeline will be handled, presented at the required public hearing. Neither presentation asks the board to take the official's word for it; both hand it defensible facts and an explicit recommendation. The board approves the adoption and funds one position, agreeing to revisit the second at mid-year review — an outcome the anecdote-driven version would not have produced.
The first mistake is advocating with anecdote — "we're overwhelmed" — instead of workload data, peer comparisons, and revenue projections; the correction is the evidence-based case an elected body can defend publicly. A second is blurring the staff/policy line by pushing a code edition or amendment as though the choice were the official's to make; the correction is to recommend and inform, and let the governing body own the adoption through its public hearing and vote. A third is treating adoption as automatic — enforcing an edition or amendment that was never properly passed into law; the correction is confirming that what is enforced is exactly what the governing body adopted. A fourth is waiting until a vote is imminent to build support, corrected by continuous education of elected leaders so allies are in place long before the ask.
This course provides comprehensive professional development in working with elected officials and appointed boards. Building relationships with city councils, county boards, and planning bodies. Covers presentation skills, political awareness, and advocacy for code compliance and resource needs. Through structured learning modules, practical scenarios, and code reference integration, participants develop the competencies needed for effective professional practice. The content emphasizes real-world application, systematic approaches to compliance verification, and the critical thinking skills required for sound professional judgment in building safety and code enforcement.