Special Inspections Tracking Log

It is used to track the special inspections required by the project’s Statement of Special Inspections from start to closeout. The log keeps the inspection scope, schedule, report receipt, deficiencies, corrective actions, and final review in one place. That makes it easier to prove the required inspections were completed and resolved before project turnover.

Use it on projects where the code, permit conditions, or design documents require special inspections for items such as structural steel, concrete, masonry, fireproofing, or designated seismic systems. It is especially useful on permitted work where the AHJ expects a clear record of required inspections and their status. If the project has no Statement of Special Inspections, this template may be more than you need.

Update it whenever an inspection is scheduled, completed, reported, or reopened for corrective action. In practice, that means the log should be current after each field visit and again when the written report arrives. Waiting until the end of the job creates gaps that make closeout harder.

It is usually maintained by the project manager, construction administrator, quality manager, or inspection coordinator, with input from the special inspector or agency. The person maintaining it should be able to confirm dates, report references, deficiency status, and AHJ notifications. The inspector performs the inspection; the log owner keeps the record complete.

No. The log is an index and control record, not a substitute for the signed inspection reports or field notes. It should point to the report reference or file number so the underlying documentation can be retrieved quickly. If a deficiency is found, the log should also show how and when it was closed.

It creates a single view of what inspections were required, what was completed, and what still needs action before final approval. That supports compliance with building code special inspection requirements and helps answer AHJ questions without searching through scattered emails and PDFs. It also makes it easier to show that deficiencies were documented and resolved.

Common mistakes include leaving required inspection categories off the log, recording scheduled dates but not actual dates, and failing to link reports to the right inspection entry. Another frequent issue is marking an item complete before the deficiency is actually closed. The log works best when every row has a clear status and a traceable document reference.

Yes. You can add or remove inspection categories based on the project scope, such as post-installed anchors, spray-applied fireproofing, or seismic bracing. You can also add columns for subcontractor, location, phase, or permit revision if your team needs more control. The core structure should stay focused on scope, status, reports, deficiencies, and closeout.

Email and ad-hoc spreadsheets often lose the connection between the inspection, the report, and the corrective action. This template keeps those pieces in one controlled record so status is easier to verify. It also reduces the risk of missing a required inspection or closing out a deficiency without documentation.