- Inspectors enforce the code; they don't negotiate it. Arguments end at the code section — so bring the section, not an opinion.
- Most failed inspections trace to work that was covered before it was verified, or corrections called 'done' that weren't.
- Self-inspection against the actual code checklist before you call for inspection is the highest-leverage QA habit a GC can build.
- Documentation — photos, code references, timestamps — turns re-inspections from debates into formalities.
The inspector is not your adversary
After two decades of running job sites, here's the thing I wish every contractor internalized early: the inspector's function is to enforce code, not to exercise opinion. When an inspection goes sideways, it's almost never because the inspector was unreasonable — it's because the conversation happened without the code section on the table.
Most code is black and white. When an issue is addressed on factual evidence — the section, the measurement, the photo — there's no gray area left to argue about. Inspectors want that as much as you do. Their day is easier when your documentation is better.
What they consistently wish you'd done first
Talk to inspectors — and we build alongside them constantly at Black Rock Construction — and the same requests come up over and over:
- Self-inspect before you call. Walk the work against the same checklist the inspector will use. If you'd fail yourself, don't schedule.
- Don't cover unverified work. The most expensive failures are the ones behind drywall. If it wasn't verified, it isn't done.
- Have the documents on site and current. The approved set, the revisions, the engineering letters. 'It's in the office' reads as 'it doesn't exist.'
- Cite the section, not the argument. If you believe a condition complies, show the code path that makes it comply.
- Make corrections completely, once. A re-inspection that fails on the same item burns the relationship and the schedule.
Make every inspection boring
The pattern behind all five: inspections fail when verification happens too late and documentation happens never. Flip both and inspections become formalities — the inspector confirms what your own record already shows.
This is exactly the workflow we built Corevis around. The glasses check work against the applicable code as it's installed, attach the code reference to every flagged issue, and keep a timestamped, tamper-evident record of what was found and what was corrected. When the inspector arrives, the walk is a review of evidence, not a search for surprises.
Every violation documented, every code referenced, zero guesswork — that's not just our line for inspectors. It's what makes a contractor the kind an AHJ trusts, and trusted contractors get smoother inspections for the life of the relationship.
“If it wasn't verified, it isn't done. If it wasn't documented, it didn't happen.”