Code Administration
The regulatory frame
Code administration covers permitting, plan review, inspections, variances, and enforcement. Know the sequence: application, site evaluation, design, permit issuance, installation inspections, and final approval. Each stage has documentation requirements, and skipping a stage is a common failure point.
Concepts to master
- Permit conditions: what must be verified before, during, and after installation.
- Variances and appeals: when a site cannot meet standards, the process for relief and the evidence required.
- Inspector authority: what the inspector may approve, reject, or require to be corrected, and the duty to document.
- Recordkeeping: inspection reports, test data, and correspondence form the legal record.
Traps in questions
Examiners test whether you know an inspector cannot waive a code requirement informally, and that verbal approvals are not substitutes for written documentation. Another trap: confusing a variance (relief from a standard) with an administrative approval (procedural sign-off). Also watch for questions implying the installer, not the inspector, determines compliance.
Worked example / rule of thumb
A contractor asks to proceed because the soil "looks fine" despite a failed percolation test. The correct response is to deny approval, document the failed test, and require a compliant design or a formal variance. Rule of thumb: if it is not in the record, it did not happen.
Inspection and Reporting
Inspecting the work
Inspection verifies that installed conditions match the approved design and the site evaluation. Check setbacks, separation distances, tank and field dimensions, pipe elevations, and the absence of construction damage such as compaction or smearing. Compare field conditions to the approved plan, not to the contractor's description.
Writing the report
A defensible report states what was observed, where, when, and by whom; what standard applies; and the resulting determination. Include test data, photographs, and any deviations. Use objective language - describe conditions rather than conclusions alone.
Traps in questions
Questions test whether you document deviations even when the overall installation is acceptable, and whether you distinguish a minor correction from a stop-work condition. Another trap: relying on memory rather than field notes, or writing conclusions without supporting observations. Watch for scenarios where the inspector is asked to approve work not yet visible - approval must follow verification.
Worked example / rule of thumb
During a final inspection, the field is 1 m shorter than the approved plan. The correct action is to document the discrepancy, determine whether it affects capacity or setbacks, and require correction or an amended approval. Rule of thumb: observe, record, compare to the approved plan, then determine.