Report template and format, condition documentation, violation documentation, and corrective action. Covers accuracy and legal sufficiency.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
Report template and format, condition documentation, violation documentation, and corrective action. Covers accuracy and legal sufficiency.
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 teamComplete inspection reports accurately and thoroughly
An inspection report is not a memo to the contractor — it is the permanent record of what a public official observed, when, where, and under what authority. Concrete gets poured, walls get closed, buildings get sold; months later, the report may be the only evidence of what existed on site that day. A defensible report answers five questions completely:
Who. The inspector's name (not just initials) and the responsible parties. Anonymous or unattributable entries are worthless in an enforcement action.
What. The type of inspection performed (footing, framing rough-in, plumbing top-out, final) and the specific scope covered. If the inspection was partial — only the second floor was ready — the report must say so; a report that reads as a full approval when only part of the work was reviewed exposes both the inspector and the jurisdiction.
When. The date, and where department practice supports it, the time. Sequence is often the disputed fact: whether the notice came before or after the drywall went up can decide who pays for the rework.
Where. The permit number and site address, plus a specific location for each finding. "Bedroom 2, north wall" or "girder G-4 at gridline C" can be verified by anyone who walks the site later. "Framing issues throughout" cannot.
Code basis. The adopted code, the edition, and the section that makes the observed condition a violation — developed fully in Module 2.
The second discipline of accurate reporting is separating observed facts from conclusions. "Observed 2x10 floor joist notched approximately 3 inches deep at midspan, bedroom 2" is a fact — anyone could go look and confirm it. "Bad framing" is a conclusion, and an opinionated one. Facts survive cross-examination; conclusions invite argument about the inspector's judgment and motives. The report records what was seen and measured; the code supplies the conclusion.
ICC's Inspector Skills text drives this home with a paired example: a framing report that reads like a critique — declaring the work the worst the inspector has seen and questioning whether anyone looked at the truss drawings — versus one that simply itemizes the corrections: lateral bracing on identified trusses, nailing at a specified spacing on identified girders, connectors at a specified rating, and a note to call for reinspection before covering. The first entry is judgmental and, as the book notes, brings the inspector's own skills into question. The second sticks to the facts. Both came from the same site visit; only one is professional documentation.
Inspector Skills also gives the standing test for everything an inspector writes: write every report, notice, and file note as though it might be read by anyone — an elected official, a judge, a manager, a reporter, the property owner, other contractors, or the public — and never write something you would regret hearing read aloud in a hearing. Its core structural advice applies too: state the point clearly and briefly up front, then give clear direction for any required action.
An inspector performs a framing inspection on a two-story addition, finds several deficiencies, and walks the job with the cooperative contractor explaining each item. Back in the truck, the tempting shortcut is a brief entry — "framing corrections discussed with contractor, reinspect" — trusting the verbal walkthrough to carry the details.
That entry fails every test in this module: no findings, no locations, no code basis, no corrective actions. If the crew misunderstands an item, or the superintendent leaves the company, the department has no record of what was required. The correct practice is to treat the conversation as a courtesy and the written report as the record: itemize each deficiency with its location, observed condition, code section, and required correction, then note "call for reinspection before covering." The conversation builds the working relationship; the report protects everyone in it.
The most common accuracy failures are omissions, not errors: documenting the worst violation and skipping the minor ones; approving "framing" when only part of it was inspected; writing conclusions ("substandard," "not workmanlike") instead of observations; leaving locations generic so no one can find the deficiency later. All are corrected by the same habit: before leaving the site, reread the report as a stranger would, and ask whether someone who was not present could find every deficiency, understand why it is a violation, and know what to do about it.
Document code violations with specific code references
A correction notice is an exercise of legal authority, and its power comes entirely from the adopted code. ICC's Inspector Skills is blunt about the language this requires: say "the code requires this," never "this is what I want done." Phrasing requirements as personal preferences implies the rules are being made up on the spot or applied arbitrarily. The inspector who cites the section, can open the book to it, and can explain the reason behind the requirement is enforcing the jurisdiction's law, not a personal standard. The same text warns against the mirror-image error: never ask for more than the code requires — a notice demanding work beyond the code minimum is as indefensible as one with no code basis at all.
A complete violation entry on a correction notice has four parts:
1. The code and edition. "IRC" is not a citation; jurisdictions adopt specific editions, often with local amendments, and section numbers move between editions. The governing code is the one applicable to the permit, not always the newest book on the shelf. Citing a section renumbered two editions ago hands the permit holder a ready-made appeal argument. 2. The section number. Specific enough to point to the actual requirement, not just a chapter. If the requirement lives in a table or an exception, cite that. 3. The requirement. A plain-language statement of what the code demands — what makes the notice usable by the tradesperson doing the correction and the file reviewer who was never on site. 4. The observed condition. The specific fact, with location, that fails the requirement — what makes the violation provable rather than asserted.
An entry missing any part is vulnerable: no section means no authority, no requirement means the contractor must guess, no observed condition means nothing to prove, no edition means an argument about which book governs.
Photo documentation extends the written record. Shoot in pairs: a context shot establishing where the condition exists — wide enough to recognize the room, elevation, or assembly — and a detail shot showing the deficiency itself, with a scale reference in frame when dimensions matter. A close-up of a notched joist proves nothing if no one can establish which joist, in which building, on which date; accurate timestamps matter because sequence is often the disputed fact. Photos must be named or logged to the permit number and inspection date and stored in the department's records system — not marooned on an inspector's personal phone. A photograph the department cannot retrieve when the dispute arrives functionally does not exist. BDA notes that when a violation case goes to court, the building official is expected to arrive with the evidence needed to prove the case — photographs, video, and the notices themselves.
Verbal and written communication on site serve different purposes. The conversation is where the inspector explains requirements, answers questions, and listens — Inspector Skills suggests spending twice as much time listening as talking. The written notice is where the requirements live: anything the contractor must act on appears in writing, and anything promised verbally that contradicts the written record creates exactly the ambiguity documentation exists to prevent. For follow-up after leaving the site, Inspector Skills notes that e-mail's advantages include creating documentation for the record and reinforcing previous verbal instructions the recipient can refer back to.
An inspector writes a correction notice reading: "Bathroom exhaust terminates in attic — correct and call for reinspection." Working from the notice alone, the superintendent cannot tell whether the fix is extending the duct to the exterior, adding a damper, or something else, and has no code provision to point to when the owner asks why the work is being redone. Compare the complete version: the adopted mechanical code and edition, the section requiring exhaust to terminate outdoors, the observed condition ("bath exhaust duct from second-floor hall bathroom terminates in attic space approximately 4 feet from ridge vent"), and the required correction ("extend duct to terminate at exterior per cited section; reinspect before insulation"). The second notice is two sentences longer and eliminates the callback, the argument, and the appeal risk.
Recurring citation defects: a chapter or code title with no section; sections from the wrong edition or the wrong code entirely (a residential project cited to the commercial code's parallel section); a code reference with no observed condition, asserting a violation without evidence; and padding notices with requirements the code does not contain. The correction discipline is to verify every citation against the adopted edition — from the book, not from memory — and to reread each entry confirming all four parts are present.
Specify corrective actions clearly
A violation entry tells the permit holder what is wrong; the corrective action tells them what compliance looks like. The standard is simple: the person performing the correction, who was not at the inspection, should be able to read the entry and do the work without calling the department. "Fix framing" fails that test; "install lateral bracing on trusses T-8 through T-16 per the truss design drawings; call for reinspection before covering" passes it. Where the code allows multiple compliance paths, state the requirement to be met rather than dictating one solution — the inspector enforces the standard; the designer and contractor choose among compliant means. Every corrective action should also state the next procedural step: reinspection before cover, resubmittal of revised drawings, or engineer's evaluation. A correction with no defined path back to approval strands the project and generates the phone calls good documentation is supposed to prevent.
Common report defects worth auditing for in any department:
Reports are public records. BDA's records-management chapter is unambiguous that building department project records are public records open to examination — and it observes that online access to permit records puts staff data entry on display, including mistakes, lack of clarity, and bad grammar. Three consequences follow. First, retention is not the inspector's call: BDA notes that permits are legal public records that cannot be summarily destroyed without consent of a higher authority, and that a retention policy approved by the legislative body is the best practice. Second, completed records must not be quietly altered: a record, once made, is a legal document, and an error discovered later is corrected with a dated "Memo to the Record" attached to the file — not by amending the original, which can be recognized as an unlawful alteration. Third, because any record may be produced in litigation or a public-records request, the Module 1 rule — write as though anyone may read it — is not a courtesy but a description of reality.
Two correction notices, two outcomes. In the first, an inspector fails a deck, writing: "Deck framing inadequate. Redo." The contractor appeals. The notice offers no observed condition, no code section, no specific correction. The inspector testifies from memory about undersized joists and a questionable ledger connection, but the contractor has since added blocking and disputes what existed at inspection. With no contemporaneous facts, photographs, or cited authority, the board finds the notice unenforceable as written. The department loses not because the deck was compliant, but because the record could not prove it was not.
In the second, a different inspector fails a similar deck with an itemized notice: each deficiency located ("ledger attached with nails only, no lag screws or through-bolts observed, full length of ledger"), tied to the adopted residential code's deck provisions by section, and paired with a corrective action and reinspection requirement — supported by a context photo and detail photos of the ledger fastening, filed under the permit number. The appeal collapses at the first meeting: the record answers every factual question before it is asked. Same department, same kind of deck, opposite outcomes — the only difference is the documentation.
The recurring failure is writing for the person who was there instead of the person who will read it later. Corrections that reference the on-site conversation ("as discussed"), assume knowledge of the location, or name a problem without a path to compliance all fail the stranger test. The fix is procedural: use the department's standard template so no field is skipped; write corrective actions executable by someone who never met you; state the next step; enter the report into the records system before the day ends; and correct later-discovered errors with a dated supplemental entry, never an alteration.
A defensible report answers who, what, when, where, and under what code authority; records observed facts rather than opinions; cites the adopted code by edition and section with the observed condition that fails it; specifies corrective actions a stranger could execute; and is supported by organized, retrievable photo documentation. Because inspection records are public records — retained under an adopted policy, discoverable in disputes, and correctable only by dated supplemental entries — every report is written for the unknown future reader as much as for today's contractor. These disciplines, drawn from ICC's Inspector Skills and Building Department Administration references, separate a correction notice that stands up under appeal from one that fails.