Architecture & Design · Advanced
Draft a zoning and code research memo for verification
A new project lands: a four-storey building with shops on the ground floor and apartments above, on a corner lot in a city you haven't worked in before. Before anyone sketches, someone has to work out what the zoning allows and what the building code will demand. That research usually starts from a blank page and an afternoon of PDFs. This guide starts it from an organized set of questions, and keeps every interpretation where it belongs: with the licensed professional.
What AI is for here, and what it isn't
Code research is a structured search. For a given site and building, you need to know the zoning limits (use, height, floor area, setbacks, parking) and the building code consequences of what you're proposing (occupancy classification, construction type, allowable height and area, fire protection, means of egress, accessibility). The questions are similar on every project. The answers depend entirely on the jurisdiction: which code editions it has adopted, which local amendments it has made, and how its officials read them.
AI is useful for the parts that are the same every time. It can turn project parameters into a complete list of questions, organize the provisions you've pulled under each question, and summarize them in plain language with section references. It's also good at spotting what's missing from your research.
It is not a code consultant, and it can be confidently wrong in ways that matter. It may quote a different edition from the one your jurisdiction adopted, miss a local amendment, or present a provision from memory as if it came from your excerpts. Code interpretation is a professional responsibility, and in most places so is the seal on the drawings. In this workflow the AI works only from text you supply, every statement cites the section it came from, and anything uncertain becomes a question for the authority having jurisdiction (AHJ).
Gather the text and the parameters
Pull the provisions yourself, from the official sources for the jurisdiction:
- Zoning: the district for the parcel (from the zoning map), the district's use table, dimensional standards (height, floor area ratio, lot coverage, setbacks), parking requirements, and any overlay districts.
- Building code: the adopted edition of the building code and the local amendments. For a typical project, the chapters you'll need first are occupancy classification (in the International Building Code, Chapter 3), building heights and areas (Chapter 5), types of construction (Chapter 6), fire protection systems (Chapter 9), means of egress (Chapter 10) and accessibility (Chapter 11). Your jurisdiction's equivalents may be numbered differently.
- Other adopted codes and standards that the project triggers: fire code, energy code, accessibility standards.
Write the project parameters in one place: site address and parcel, proposed uses and their areas by floor, number of storeys and height, intended construction type if known, sprinklered or not, and anything unusual (a rooftop amenity, a parking garage, a change of use in an existing building).
Turn parameters into questions
I'm starting zoning and building code research for a project. Produce a
structured list of the questions this research must answer. Do not
answer any of them.
JURISDICTION: [city/county, state]
ADOPTED CODES (as confirmed): [e.g., building code edition + local
amendments; zoning ordinance date]
PROJECT: [uses and areas by floor; storeys; height; construction type
if known; sprinklers; site constraints]
GROUP THE QUESTIONS:
1. Zoning: use permissions, dimensional limits, parking, overlays,
approvals required (by-right vs special permit).
2. Occupancy: classification of each use; mixed-occupancy approach.
3. Height, area and construction type.
4. Fire protection: sprinklers, alarms, standpipes, fire separations.
5. Means of egress: occupant load, number of exits, travel distance.
6. Accessibility: which standards apply and what they trigger.
7. Other adopted codes the project likely triggers.
For each question, name the kind of provision that would answer it
(e.g., "zoning use table", "building code chapter on occupancy").
You'll get a checklist that's more complete than most first passes. Edit it: delete what doesn't apply, add what you know from experience about this kind of project or this jurisdiction.
Summarize only the provisions you supply
Work one question group at a time, pasting in the provisions you pulled for it.
Answer the questions below using ONLY the provisions I've pasted. You
are organizing my research, not interpreting the code.
QUESTIONS: [paste one group from Step 2]
PROVISIONS (with source, edition and section numbers):
[paste]
FOR EACH QUESTION:
- WHAT THE TEXT SAYS: a plain-language summary, with the exact section
reference for every statement.
- APPLIES IF: the project facts the provision depends on.
- OPEN: anything the supplied text doesn't settle: exceptions that may
or may not apply, terms that need a definition, cross-references to
sections I haven't supplied.
RULES:
- If a question can't be answered from the supplied text, say NOT IN
SUPPLIED TEXT. Do not fill the gap from your own knowledge.
- Never state that something is "permitted", "compliant" or "not
required" as a conclusion. Report what the text says and what it
depends on.
- Quote numbers (heights, areas, distances, ratios) exactly, with units.
The rule against conclusions is the one that protects you. "Section X allows Y where Z" is research. "The building complies" is an opinion that only a licensed professional should give.
Verify and list what goes to the AHJ
Check every section reference against the source text. Check every number. Then read the "open" items carefully. They're the substance of your next call with the building department or zoning office.
Turn them into a short list of written questions for the AHJ, each one specific enough to get a clear answer: the provision, the project fact, and the reading you're asking them to confirm. Record the answers, who gave them and when. Many jurisdictions offer pre-application or preliminary plan review meetings for exactly this.
Worked example: the corner lot
Fictional example; the jurisdiction, ordinance and figures are invented, apart from the model code section noted. A designer is researching a four-storey building in a city that adopted an earlier edition of the International Building Code with local amendments. Ground floor: retail. Floors 2–4: apartments. The zoning district is a mixed-use commercial district.
The question prompt produces 31 questions in seven groups. The designer cuts four that don't apply and adds one from experience: whether the corner lot triggers a visibility setback.
The provision summaries surface three useful findings and one problem:
- Zoning height: the district allows 50 feet, measured to the midpoint of a pitched roof or the top of a flat roof parapet (zoning ordinance, dimensional table, as supplied). The summary flags the measurement definition as OPEN, because the definition of "building height" sits in a section the designer hadn't pulled.
- Parking: the use table requires parking per dwelling unit, with a reduction near transit. The summary lists the reduction's distance condition as OPEN.
- Corner visibility: NOT IN SUPPLIED TEXT. The designer pulls the right section and adds it.
- The problem: in the fire protection group, the summary says residential occupancies "must be sprinklered in accordance with Section 903.2.8". That provision exists in the current model code, but it wasn't in the text the designer supplied. The designer's excerpts were from the city's adopted edition and amendments. When they check, the city's amendment adds a local requirement on top of the model provision. The AI's sentence wasn't wrong, but it came from the AI's own knowledge, not the adopted text, and it missed the local amendment entirely.
The designer deletes the unsupported sentence, rewrites the summary from the city's text, and adds the amendment to the AHJ question list. The memo goes to the project architect with nine questions for a pre-application meeting.
Record the research
[Project] — Zoning and code research memo v[number], [date]
Prepared by: [name] For review by: [licensed professional]
Status: RESEARCH FOR PROFESSIONAL VERIFICATION, NOT A CODE ANALYSIS
JURISDICTION AND ADOPTED CODES (confirmed [date], source [URL])
- Zoning ordinance: [date/version] District: [ ] Overlays: [ ]
- Building code: [edition] + local amendments [reference]
- Other: [fire, energy, accessibility]
PROJECT PARAMETERS
[uses and areas by floor; storeys; height; construction type; sprinklers]
FINDINGS (each with section reference)
Question | What the text says | Section | Applies if | Open
QUESTIONS FOR THE AHJ
# Provision | Project facts | Proposed reading | Answer | By whom, date
AI assistance: questions and summaries drafted with [tool] from the
excerpts listed; every reference checked against source by [name], [date]
What stays with you: every code interpretation. The stamp stays with the licensed professional.