Code Enforcement Administration and Program Management
Domain 1, Code Enforcement Administration and Program Management, tests whether you can run a code department as a system: legal authority, permit and inspection workflow, records, appeals interface, and performance measurement. The exam favors operational judgment over reciting code sections.
Authority and workflow
The code official's power comes from an enabling statute and local ordinance, not from the code book alone. Know the adopted edition and local amendments, who may approve permits, and what must be inspected. A complete submittal triggers plan review; approved plans authorize construction; inspections verify milestones; a certificate of occupancy is issued only after required inspections and approvals. Temporary certificates need explicit conditions and an expiration.
Managing performance
Measure cycle time, completeness rate, inspections per inspector-day, re-inspection rate, and appeal volume. Use root-cause analysis before adding staff. Standard operating procedures should cover screening, correction notices, stop-work orders, and records retention.
Worked example: A department misses a 10-day residential plan-review target; average is 15 days and 30 percent of submittals are incomplete. Adding an inspector is premature. Screening data shows incomplete submittals consume review time. A completeness checklist and pre-submittal meeting reduce rework; only residual backlog justifies staffing.
Traps
Do not treat plan approval as a guarantee of compliance, issue a CO before finals, let a board of appeals waive code requirements beyond its authority, or rely on memory instead of inspection records. Fee schedules are not enforcement leverage.