Planning & documentation
Preparing an AHJ Preapplication Meeting for a Steel Building
Prepare a US steel building preapplication discussion with property information, intended use, review pathways, and a written questions record.
Define the condition and its scope
An early meeting identifies review pathways and information gaps before detailed package development.
US construction requirements depend on the project location, proposed use, and the authority having jurisdiction. A model code title or a state-level map is an initial research aid rather than a complete permit decision. Identify the building department, planning or zoning contact, fire authority, and any separate floodplain or environmental review. Record the adopted editions, local amendments, and submission instructions obtained for the actual property. Keep the owner's intended operations clear so that reviewers are evaluating the building that will really be used.
References: Code adoption resources · Project Planning Guide
Gather the inputs before deciding
Prepare a concise property and operations description, preliminary site concept, anticipated alterations, and questions grouped by reviewing authority. Ask about submission pathways, required authors, separate approvals, and known information gaps. Bring the responsible design representative when technical interpretation is needed. Keep a tentative concept clearly labeled. The meeting should clarify how to obtain decisions rather than seek an informal promise that an undefined building will be approved.
- Property and site concept
- Proposed operational use
- Questions by reviewing authority
- Written meeting follow-up
References: Code adoption resources · Project Planning Guide
Set observable handoff deliverables
Informal meeting guidance should not be represented as a permit approval.
| Input | Evidence to keep with it | Review status |
|---|---|---|
| Property and site concept | Marked preliminary site concept | Identify reviewer and written decision |
| Proposed operational use | Operations and future-use narrative | Identify reviewer and written decision |
| Questions by reviewing authority | Authority response and pending questions | Identify reviewer and written decision |
Sequence review and release
Send the agenda and supporting concept through the authority's stated process. During the discussion, record the scope of each response and unresolved requests for information. Follow up with the written record and ask for corrections where appropriate. Assign preparation of formal submissions to the responsible team. Distribute procedural guidance to affected suppliers while retaining technical questions for professional and authority review.
- Locate property and site concept in the current record.
- Compare proposed operational use with the table's evidence.
- Document the decision: Confirm the actual review pathway and unresolved questions in writing.
Worked project coordination example
An owner proposes storage with a future office area. The meeting questions separate current occupancy, future conversion, zoning, and fire review so the design team can define the initial submission accurately.
Apply the stated release decision to the case: Confirm the actual review pathway and unresolved questions in writing. The responsible team determines acceptance for the actual project and records any condition that still requires resolution.
Keep a closeout record another team can use
Keep the meeting date, participants, materials discussed, response limits, and follow-up actions in the jurisdiction register. Link later formal decisions separately so the preliminary conversation is not mistaken for a permit. Record changed concepts that make earlier guidance incomplete. Before purchasing, reconcile the actual design with unresolved questions. A useful preapplication record helps the team prepare a complete package without overstating what the authority decided.
For this issue, include authority response and pending questions in the handoff. If review remains pending, identify the dependent work and its owner; do not present the record as a completed technical acceptance.
Common questions
Is a preapplication meeting always required?
Confirm local procedures; availability and requirements vary by jurisdiction.
How should property and site concept be documented?
Confirm the actual review pathway and unresolved questions in writing. Retain marked preliminary site concept and check that the decision reached the team performing the dependent work.
Sources & further reading
Use the current documentation for the exact product and project. Source links do not imply a partnership or endorsement.
- Code adoption resources International Code Council
- Project Planning Guide U.S. General Services Administration / WBDG
Prepared with AI assistance. Linked references require current project-specific review. How these guides are prepared.
Prepare a supply inquiry
- Record the project drawing or detail and the specified product, profile, or system.
- List the complete configuration, physical units, quantities, and cuts per piece.
- Request current manufacturer documents; confirm compatibility, price, and availability before ordering.
- Obtain the responsible professional's review for loads, code requirements, or installation.