Clear writing for inspection reports, violation notices, memoranda, and emails. Covers professional tone, accuracy, and legal sufficiency of written enforcement documents.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
Clear writing for inspection reports, violation notices, memoranda, and emails. Covers professional tone, accuracy, and legal sufficiency of written enforcement documents.
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 teamWrite clear and legally sufficient violation notices
Every piece of writing produced in a building department — a correction notice, a plan review letter, a memo, a two-line email — starts from the same premise: it is a government record, and the writer does not control who reads it. ICC's inspector-skills training makes the point bluntly: notes and notices should be written as if they might be read by anyone — an elected official, a judge, a manager, a reporter, a property owner, other contractors, or the public. Open-records laws make that audience real, not hypothetical, and many departments now deliver correction lists and inspection results to customers in real time through online portals, so the words a plans examiner types in the office appear on an applicant's screen essentially as typed. The discipline this imposes is simple: never write anything you would regret seeing quoted at an appeal hearing or in a news story. That single test — write for the judge and the reporter, not just the recipient — settles most questions of tone and content before they arise.
The second discipline is structure: put the point up front. The inspector-skills guidance is explicit that the point of the message must be stated clearly and briefly at the beginning, followed by clear direction for any required actions. Busy readers — contractors on ladders, council members with thick agenda packets — read the first two sentences and skim the rest; a letter that opens with three paragraphs of procedural history before revealing that the application is incomplete buries the one fact the reader needs. State the conclusion first, then support it. A related habit keeps correspondence usable as a record: one topic per letter. A letter mixing a plan review correction, a fee question, and a scheduling issue is hard to answer, hard to route, and hard to find in the file later.
The third discipline is plain language. The same keep-it-simple, no-jargon rule that ICC training applies to face-to-face communication applies doubly on paper, where there is no chance to read the listener's face and re-explain. Use short sentences. Prefer the common word to the bureaucratic one — "send," not "transmit herewith"; "before," not "prior to the commencement of." Strings of undefined abbreviations turn a report into a puzzle. Code terminology is different from jargon — terms like "dwelling unit" or "means of egress" carry precise legal meanings and should be used — but explain a technical term on first use when writing to a homeowner who cannot be assumed to know it. Plain language is not dumbed-down language; it is language that cannot be misunderstood.
These disciplines converge in the correction or denial letter, the most consequential document most code professionals write. A complete letter tells the reader five things: what was reviewed (project, address, permit or application number, and which submittal or revision); what does not comply, item by item, described specifically enough that the reader can find each condition; the code basis for each item — the specific adopted code and edition, since numbering and requirements change between editions and ambiguity invites challenge; the path forward — what must be corrected or submitted, any deadline, and how to request reconsideration or appeal; and who to contact, with a name, phone number, and email address. The tone throughout is firm and respectful: the letter states what the code requires and never apologizes for it, but never scolds, speculates about motives, or editorializes about the work. A denial without a path forward reads as a wall; with one, it reads as a map.
A plans examiner reviews a tenant-improvement submittal and finds four deficiencies. Her first draft opens: "Pursuant to the review of the aforementioned submittal, it has been determined that said documents fail to demonstrate compliance." Three dense paragraphs later, the actual corrections appear, mixed with a note about an unpaid fee. Before sending, she applies the course's tests. Point first: the opening becomes "The plans for Suite 210 cannot be approved as submitted. Four corrections are required; each is listed below with its code basis." One topic per letter: the fee issue moves to a separate note. Plain language: "fail to demonstrate compliance" becomes "do not show." Path forward: the letter closes with what to resubmit, the expected review time, and her direct phone line. The revised letter is shorter, and the architect calls once — to confirm the resubmittal date, not to ask what the letter meant.
The recurring failures mirror the incorrect examples in ICC's inspector-skills training. Editorializing — a notice ridiculing the workmanship — is judgmental, potentially defamatory, and calls the writer's own professionalism into question; the correction is clear, concise, factual information and no judgment. Vagueness — "framing violations: fireblocking" — identifies neither location, required action, nor follow-up; the correction is a notice that lists each item specifically, states any conditions for proceeding, and directs the reader to call for reinspection. Personal framing — "this is what I want done" — implies the rules are the writer's preferences; the defensible framing is "the code requires," with the section available on request. Buried conclusions, mixed topics, undefined abbreviations, and denial letters with no path forward round out the list.
Prepare detailed inspection reports with photographic evidence
Inspection reports and correction notices are the daily core of department writing, and this platform devotes a companion course — Inspection Report Writing and Documentation — to their structure, photographic evidence standards, and defensibility in depth. This module covers the pieces that course does not: the document as a permanent record, and the memos and staff reports that carry the department's work upward and inward.
Start with the record. Building department administration guidance draws a sharp line between transitory records — an inspection request has no validity once the inspection is made — and permanent ones: permits and plan review notes document legally consummated actions and may be needed decades later to evaluate a structure for a remodel, addition, or change of use, so they are retained indefinitely. The writing consequence is that a report or file note must stand on its own without its author. The person retrieving it may be a different inspector performing the next inspection, a coworker answering a counter question, or an attorney in discovery. A note that says "discussed the issue with the contractor; he'll take care of it" is worthless in ten years — or ten weeks. A note that identifies the issue, the direction given, the code basis, the date, and the agreed follow-up is a record. Good record keeping is also how a department demonstrates due process: the file shows notice was given, requirements stated, and opportunities to comply provided, in sequence.
Memos and staff reports serve a different master, and the controlling skill is audience calibration. A memo to inspection staff implementing a new procedure should lead with the procedure: what changes, when it takes effect, exactly what to do differently, and who to ask — operational specifics staff can follow in the field tomorrow, with background kept brief at the end. A staff report to a city council or board runs the opposite direction: elected officials want the decision — what is recommended, what it costs, and why — in the opening lines, with analysis beneath but not blocking the recommendation. Both documents obey the point-up-front rule; what changes is which point the audience came for. Writing for the wrong audience — procedural minutiae to the council, policy philosophy to field staff — is among the most common and most avoidable memo failures.
Finally, choose the medium deliberately. A file note memorializes; a memo directs internally; a letter carries formal positions to external parties; email moves quick, low-stakes information. Formal enforcement positions, appealable decisions, and legal notices belong in letters — dated, on letterhead, delivered verifiably — not in email threads. The medium is part of the message: a stop-work notice by casual email undercuts its own seriousness.
A building official must brief the city council on adopting the next code edition and simultaneously prepare staff for the transition. She writes two documents from the same material. The council staff report opens: "Staff recommends adoption of the updated building code with the local amendments listed in Exhibit A. The primary impacts are three changed requirements affecting residential construction and no change in permit fees." Two pages of analysis follow for those who want it. The staff memo opens differently: "Effective January 1, inspections on permits issued under the new code will use the updated checklists. Here is what changes in the field" — followed by the specific procedural differences and who to contact with questions. Same facts, opposite structures, because the council needed a decision and the staff needed procedures. Both documents go in the files, the permanent explanation of what was decided and how it was implemented.
The characteristic mistakes here are records that depend on memory and documents aimed at the wrong audience. Notes recording conclusions without observations, directions without code basis, or conversations without dates cannot support the department later; the correction is to write every file entry so a stranger could reconstruct the event from the page alone. Memos that bury the operative instruction under background lose the field reader; staff reports that open with methodology lose the council. Formal positions delivered by casual email create disputes about whether notice was given. And treating any of it as disposable is its own error: plan review notes and permit records are permanent, and the standards of specificity and professionalism apply for the full life of the record. Purge the transitory, preserve the permanent, and write the permanent accordingly.
Compose professional emails and internal communications
Email is the highest-volume writing most code professionals do, and ICC's inspector-skills guidance opens with the fact that governs everything else: email is not private. Messages belong to the jurisdiction, may be viewed by it at any time, are typically part of the public record subject to open-records laws, and can be introduced as evidence in litigation — an inspector subpoenaed in a contractor-owner dispute may watch the whole thread read into the record. The operating rules follow directly: never assume privacy exists in email, and never say in an email what you would not say in person. Deleting messages to avoid disclosure is not an option; records-retention laws reach email like any other record.
Within that frame, craft is mostly a handful of habits. Write the subject line so it says the thing — the guidance is to capture the message's objective in the subject line, so the recipient knows the purpose before opening it; a subject like "Guard height requirement for 123 Main St." works, "phone tag" does not, and a permit number in the subject line files the message for everyone downstream. Keep the body brief, state any required action explicitly, and format like a business letter: greeting, complete sentences, proper capitalization and punctuation, signature with contact information. Skip the attention-grabbing devices — all capitals read as shouting, and emoticons, colored text, and decorative fonts have no place in department communication. Fill in the recipient line last: the inspector-skills material recommends this specifically, because a message that cannot be sent cannot be sent half-written, unproofread, or to the wrong person. Copy additional recipients only when necessary — and the same restraint applies to reply-all: before including everyone on a thread, ask who actually needs the message. On response time, email's advantage is that the recipient can respond at a reasonable opportunity rather than instantly — but contractors and owners judge the department by follow-through, so establish and meet a consistent standard for returning messages rather than letting inquiries age silently.
Just as important is knowing when email is the wrong tool. The inspector-skills advice is to ask whether the communication would be easier by phone or in person — and to treat a message running long as a strong clue to switch channels. Bad news, contested positions, and anything with legal consequence deserve better than email: sensitive matters lose nuance in text, tone is invisible, and a hasty message becomes a permanent exhibit. Deliver difficult findings in conversation where questions can be answered, then confirm in a formal letter; email's legitimate role afterward is the one the guidance highlights — documenting and reinforcing what was already said, so the recipient has a reference and the file has a record.
Tone is where email fails most often, because messages read harsher than the writer intended — the recipient cannot see facial expressions or hear tone of voice, so wording that felt neutral at the keyboard lands as cold or hostile on screen. Sarcasm fares worst of all: stripped of the smile that softened it, it reads in print as contempt — and reads that way again at the appeal hearing. The cardinal rule is never to write angry. When a message provokes you, draft nothing while provoked; a widely used discipline is the twenty-four-hour rule — let a heated reply sit a day, or at minimum until you can reread it as the judge and reporter would. The inspector-skills guidance adds two checks for sensitive messages: read the draft aloud, and have a coworker or manager read it before it goes out. Finally, proofread as if your credibility depends on it, because it does: spell-check on, then a human pass over what spell-check cannot judge — the recipient's name, the project address, the permit number, and the code edition cited. A misspelled name suggests carelessness; a wrong address or edition can invalidate the point of the message.
Two versions of the same bad news. In the first, a plans examiner denies a revision by email late on a frustrating Friday: subject line "your plans," body reading "As I already explained, this doesn't come close to complying. Resubmit when it's right." The applicant, reading contempt between the lines and finding no specifics to act on, files an appeal — and the email, now an exhibit, makes the department look arbitrary regardless of the technical merits. In the second version, the examiner drafts the same denial, recognizes the heat in it, and lets it sit overnight. Monday's product is a formal letter: what was reviewed, the three items that do not comply and where each appears in the submittal, what a successful resubmittal must show, the procedure and review timeline, and a direct phone number. The applicant calls, asks two questions, resubmits, and is approved. Same denial, same code basis — but the first document created an adversary and an appeal, and the second created a path forward. The difference was never the decision; it was the writing.
The classic email failures cluster into privacy blindness, tone, and channel choice. Privacy blindness: venting, sarcasm, or unguarded commentary in a message that open-records laws can put in front of anyone — corrected by the rule that nothing goes in email the writer would not say publicly. Tone: messages sent hot, or dressed in capital letters and exclamation points — corrected by the twenty-four-hour rule, reading aloud, colleague review, and business-letter formatting. Channel choice: delivering denials or enforcement positions by quick email instead of conversation plus formal letter — corrected by asking, before sending, whether the message is carrying more weight than email should bear. Add the mechanical errors — vague subject lines, premature sends, reply-all sprawl, unproofread names and permit numbers — and the corrections are all habits, cheap to adopt and expensive to skip.
This course develops the written communication skills that building department work runs on: correction notices and denial letters that are specific, code-based, firm, and respectful; file notes, memos, and staff reports written for their real audiences and for the permanent record; and email handled with the discipline its public-record status demands. The through-lines are few — put the point up front, use plain language, write for the judge and the reporter as well as the recipient, match the medium to the message, and never send anything in anger. Documents built on those habits give customers a clear path to compliance, give the department a defensible record, and give the public a reason to trust the professionals who wrote them.