Authority having jurisdiction (AHJ)

"The authority" is grammatically singular and practically plural. A single project answers to a building authority, a fire authority, environmental regulators, utility companies with connection requirements, labour and technical-safety inspectorates, and — depending on the facility — industry-specific supervisory bodies, each an AHJ for its own domain, each with its own submissions, review cycles, inspections and approvals. The term itself comes from code language: the codes name the role abstractly precisely because who fills it varies by place and subject.

Two properties of AHJs shape project planning. First, interpretation is part of their authority: the same code clause can be read differently by different offices, and the local reading is the operative one — which is why experienced teams engage AHJs early rather than discovering interpretations at review. Second, AHJs do not coordinate with each other; requirements can conflict, and reconciling them is the project's job, not theirs.

The planning failure is the uncounted authority: an AHJ discovered late, with its own submission requirements and its own clock, inserted into a schedule that assumed the permit path was already fully enumerated. Enumerating the authorities is the first permitting deliverable, and the cheapest.