Pre-Permit Review Built Around How Architects Actually Plan Check
Plan reviewers comment on the same families of issues every cycle. Helonic catches them first so your set goes in clean.
Architects don't fail plan review because the design is wrong. They fail because something on sheet A-301 contradicts something on sheet A-501, because the code summary references an edition the AHJ no longer accepts, or because a corridor narrows by an inch at a column enclosure nobody recomputed. Pre-permit review is the discipline of catching those issues before the plan reviewer does - and it's exactly where AI is at its strongest, because plan check comments follow patterns. Helonic was built around the most common pattern families we've collected from licensed architects across firms ranging from 8-person studios to 300-person practices.
Where pre-permit review actually breaks down for architects
The vulnerability isn't competence - it's coverage. A single CD set can run 250+ sheets, with code-relevant content scattered across the cover sheet, life-safety plan, building section, wall types, door schedule, hardware schedule, fire-rating notes, and specifications. Any one architect can hold a few hundred items in working memory; a set carries thousands. The architects we talked with consistently described the same failure mode: an early decision (say, adding a stair pressurization fan) propagates incompletely through the set, and the inconsistency only surfaces when the AHJ flags it three weeks later.
How Helonic helps
Pattern-matched against thousands of plan-check comments
Helonic's pre-permit checks are calibrated against the categories of comments that AHJs return most often - occupant load mismatches, fire-rating discontinuities, ADA route deficiencies, code-summary citations that don't match the adopted edition.
Reads the whole set as one document
A code-relevant decision is rarely on one sheet. Helonic cross-references the life-safety plan, schedules, sections, details, and specs so contradictions between sheets surface as a single finding with citations to each source.
Cites the specific code section and the sheet location
Every finding includes the page and coordinate where the issue lives plus the code section it implicates. Reviewers can land directly on the affected sheet instead of triangulating from a summary.
Reduces re-submittal cycles, not just comments
Most schedule slippage on permit isn't the first review - it's the second and third. Catching the issues that drive re-submittal correspondences is where pre-permit review repays itself.
Example issues Helonic catches
Real-world issues detected by AI analysis, specific to architects running pre-permit review:
Occupant load of 312 calculated on the life-safety sheet doesn't reconcile with 268 used for egress capacity on A-001 - egress width sized 0.15"/occupant for 268 leaves the actual load short on stair B
2-hour shaft enclosure detail S-712 terminates at the ceiling on plan A-201 but the wall section A-501 extends it to deck above - drawings are internally inconsistent
Code summary cites IBC 2018 but the AHJ adopted 2021 IBC last cycle - energy code references on A-001 still point to the previous IECC
Door D-204 listed in the door schedule as 3'-0" but shown as 2'-10" on the demolition / new plan overlay; ADA clear width may not be met on rebuild
Stair pressurization shown on M-201 but missing from A-001 life-safety narrative and stair detail A-602 - coordination gap that AHJs typically flag
Tactile exit signage scheduled but mounting height on A-902 shows 60" AFF - ADA requires 48"–60" to baseline
Key features for this workflow
Cross-sheet consistency checks across plans, schedules, sections, and specs
Adopted-edition aware code checks (IBC, IFC, IBC accessibility, IECC, NFPA 13/72)
Occupant load and egress capacity recompute from labeled rooms and corridors
Door, window, and finish schedule reconciliation
Fire-rating continuity tracing from wall types to penetration details
ADA route slope and clearance recalculation from dimensioned plans
How architects run pre-permit review with Helonic
Drop the current CD set in
Upload the most recent IFP-candidate set. Helonic indexes every sheet, schedule, and reference within minutes - no manual sheet tagging required.
Pick the adopted edition and amendments
Select the AHJ jurisdiction and adopted IBC/IFC/IECC editions. Helonic adjusts its rule set to the active code and known local amendments.
Triage the findings by severity
Hard code violations surface at the top. Cross-sheet inconsistencies, missing details, and ambiguous notes follow. Each finding includes page citations to every contradicting source.
Resolve, dismiss, or export
Resolve findings inside Helonic, dismiss with a written reason for the audit log, or export the open issues as a structured report you can hand to the team for revision.
What construction professionals told us
“The licensed architects we interviewed consistently said the highest-value pre-permit pass isn't checking individual sheets - it's verifying that decisions made at SD propagated all the way through CD. That's a coordination problem more than a code problem, and it's where they want help the most.”
Based on interviews with practicing architects at firms from 8 to 300 staff, including AIA-licensed principals and project architects who run their own internal plan checks.
FAQs
Does Helonic replace our internal QA/QC process?
No. The architects we work with use Helonic as the first pass before the internal QA reviewer takes the set. Helonic catches the high-volume, pattern-based issues; the internal reviewer focuses on judgment-heavy items like design intent, detailing quality, and specification consistency.
Can it check against my jurisdiction's specific amendments?
Yes for the most common local amendments. Helonic ships with a curated set of jurisdictional amendments and lets you upload custom amendment language for any AHJ. The rule engine then runs the amended sections instead of the base code.
What happens to findings the team disagrees with?
Every finding can be dismissed with a written reason. Those dismissals are logged and reviewable so the team can demonstrate that issues were considered and consciously closed - useful for both internal QA and E&O documentation.
Manas Gandhi
Co-founder & CTO, HelonicManas is the co-founder and CTO of Helonic, where he leads engineering and AI research for construction drawing analysis. He works directly with structural, MEP, civil, and fire protection engineers to translate the way they review drawings into AI systems that flag the issues that actually matter in the field. Before Helonic, he built machine learning pipelines for technical document understanding and has spent the last several years interviewing licensed design engineers and discipline leads to ground product decisions in real practice rather than industry assumptions.
- AI for technical document understanding
- Cross-discipline coordination workflows
- Code compliance automation (IBC, NEC, NFPA, IPC, IMC, ASCE)
- Structural and MEP drawing review systems
How this page was researched: Based on interviews with practicing architects at firms from 8 to 300 staff, including AIA-licensed principals and project architects who run their own internal plan checks.
Last reviewed by Manas Gandhi · May 2026
Other use cases for architects
Pre-Permit Review for other roles
Try Helonic on pre-permit review for your next project
See how Helonic catches the issues that matter most to architects. Upload your drawings for a free analysis.