The building permit approval process is the sequence by which an authority having jurisdiction — an AHJ, usually a city or county building department — reviews a construction project for code compliance and grants legal permission to build. It runs from a prepared application through intake, plan review, any correction cycles, and finally the issued permit, after which inspections govern the work on site. Nothing on a permitted project may legally start until this process reaches the "issued" step.
This template lays that process out as a living graph. It moves an application from Prepare application & docs to Submit to authority (AHJ), through the department's Intake & completeness check and Plan review, and then it forks. If reviewers approve, the application flows to Permit issued and on to Inspections during build. If they return comments, it drops into a correction loop — comments, resubmit, re-review — that repeats until the plans pass. That loop is where permits actually live or die.
It is built for architects, permit expediters, general contractors, and owner's reps who need to see where an application stands and why it stalled. Because it opens in FlowGraph as an editable graph, you can rename every review step to match your own jurisdiction, add the specific checks your AHJ demands, and track each correction cycle so a resubmittal turns around in days instead of weeks.
How this permit process template works
The graph follows one application from preparation to construction inspections. Each card is a step you can open, edit, assign, and time-stamp. Here is the flow in order.
- Prepare application & docs — Assemble the permit application and its supporting package: stamped drawings, structural and energy calculations, site plan, and the jurisdiction-specific forms. The completeness of this package is the single biggest predictor of how fast the permit clears, because most delays trace back to something missing here.
- Submit to authority (AHJ) — Lodge the application with the authority having jurisdiction, through its counter, portal, or electronic plan-review system. This step records the submittal date and the assigned application number — the clock that every downstream aging calculation runs against.
- Intake & completeness check — The department screens the submittal for completeness before it enters technical review. If a required document is missing, the application can be rejected at the counter before a reviewer ever opens it. Passing intake is what gets you into the actual queue.
- Plan review — Reviewers examine the plans against the building, fire, energy, accessibility, and zoning codes. Larger projects are split across disciplines, each with its own reviewer and its own comments. This is the technical heart of the process, and it is the node that branches: it either approves the plans or returns them with corrections.
- Comments / corrections — When the reviewer finds code issues, they issue a set of comments. The applicant must respond to each one — by revising a drawing, adding a detail, or providing a code justification. Tracking these comments individually, with an owner and a status, is what keeps a correction cycle from stalling on one forgotten item.
- Resubmit — The corrected package goes back to the department. Its re-review edge routes it straight back to Plan review, not to the front of the line — the same reviewer checks whether the comments were adequately addressed. This is the loop that can repeat several times, and each turn adds days, so its aging is worth watching closely.
- Permit issued — Once Plan review is satisfied, the approved edge leads here: fees are paid and the permit is issued. Construction may now legally begin. The issued permit carries conditions and the schedule of required inspections.
- Inspections during build — With the permit in hand, work proceeds through the mandated inspection milestones — footing, framing, rough-in, insulation, final — each of which must pass before the next phase or occupancy. This step is the bridge from the paper process into the physical build, and a natural place to link an inspection or ITP graph.
The branch out of Plan review — approved versus corrections — and the re-review loop back through it are the parts a linear checklist can never capture. A permit is rarely a straight line; it is a review with a feedback loop, and modelling that loop is what makes the process honest.
How to use it in FlowGraph
- Open the template. Click Open in FlowGraph to load the permit process as a live graph. Viewing, editing, and adapting it are free with no account — you only sign up when you want to save it to a vault or ask the AI to extend it.
- Adapt it to your AHJ. Rename the review steps to match your jurisdiction's real workflow and add its specific checks — a separate fire-department review, a health-department sign-off, a planning-commission hearing, or an electronic plan-review portal. Every AHJ is different, and every edit here is governed and carries a receipt.
- Assign owners and dates. Give each step an owner — the designer of record for corrections, the expediter for submittals, the plans examiner for review — and stamp the submittal and response dates. Now you can see how long the application has aged at each stage.
- Track corrections. On Comments / corrections, log each reviewer comment as its own item with a status, so nothing falls through the cracks. Follow the re-review edge on Resubmit and watch how many cycles a package takes — the aging of that loop is usually the difference between an on-time and a late permit.
- Schedule inspections. Extend Inspections during build into your real milestone list, or link it to a separate inspection graph, so the permit conditions flow straight into the construction quality checks.
- Extend it with AI or links. Bring your own API key and ask FlowGraph's AI to draft a corrections-response matrix, list the submittal documents a given jurisdiction requires, or split plan review into per-discipline lanes. The AI proposes; you decide what lands. You can also link cards to the drawing sets and code sections they concern.
Why a living graph beats a static permit checklist
A permit checklist tells you the steps once, in order, as if approval were a straight line. But the reason permits slip is precisely the part a checklist hides: the correction loop. Comments come back, corrections go out, the package re-enters review, and it may do that two or three times. On a static list all of that collapses into a single "plan review" box that quietly sits open for months.
A living graph shows the loop as a loop. You can see the application circling between Comments / corrections, Resubmit, and Plan review, see how long it has been on each turn, and see which comment is still unresolved. Every step has an owner and a date, so accountability for a stall is obvious rather than diffuse. And because it opens in FlowGraph, the same graph you use to plan the process is the one you use to track it — no separate tracker to keep in sync.
It is also honest about jurisdiction. FlowGraph doesn't pretend one permit process fits every city; it gives you an editable starting point that you rename, extend, and govern for your own AHJ, with a receipt on every change so the record of how your process evolved is never lost. AI can propose refinements, but you stay in control of what the process actually says.
Frequently asked questions
What is the building permit approval process?
It is the regulated sequence by which an authority having jurisdiction reviews a construction application for compliance with the building code and related regulations — intake, plan review, corrections, and issuance — before work may legally begin, and during which the schedule of construction inspections is established. It exists to confirm, on paper, that a proposed building is safe and lawful before anyone breaks ground.
This template models that sequence end to end, including the correction loop that most descriptions gloss over, so you can both understand the process and run a real application through it.
What is an AHJ?
The authority having jurisdiction is the office empowered to review plans, issue permits, and inspect the work — most often a municipal or county building department, though for some scopes it may be a fire marshal, a health department, or a state agency. The AHJ sets the local interpretation of the code and the specific submittal and inspection requirements you must meet.
This template routes the application through the AHJ's intake and plan-review steps, and because those steps are editable, you can reshape them to reflect exactly how your particular authority operates rather than a generic ideal.
Why do permits get delayed?
The overwhelming majority of permit delays come from two things: incomplete applications that fail or slow the intake and completeness check, and correction cycles that drag because comments are answered slowly or partially. Both are process problems, not code problems, which means both are fixable by managing the workflow better.
Tracking the permit as a graph makes the correction loop and its aging visible — you see how many cycles a package has taken and which comment is still open — so resubmittals turn around quickly and the application keeps moving instead of quietly aging in a reviewer's queue.