HelonicHelonic
Industry Research

Most Common Construction Code Violations: A Frequency Report

Helonic has analyzed more than 100,000 pages of construction drawings across 1,000+ project reviews, surfacing over 150,000 issues. This report ranks the code sections that get flagged most often at the drawing stage — before a permit set is submitted or a drawing set is issued for construction — so teams know where to look first.

Last reviewed by Manas Gandhi · June 2026Industry Research

The most-flagged code sections, ranked

The table below ranks the code categories Helonic flags most often by relative frequency within all code-related findings. We report the ranking and rough tiers rather than precise percentages — exact shares move with project type and code edition — but the ordering is stable across our corpus.

RankCode section / categoryRelative frequency
1NEC 110.26 — electrical working space & clearancesMost flagged (~1 in 5)
2IBC Ch. 10 — egress width, door swing, travel distanceVery high
3ADA / ICC A117.1 §703 — signage & 305 clear floor spaceVery high
4NFPA 13 — sprinkler obstruction & clearance to deflectorHigh
5IBC Ch. 7 / 707–708 — fire-rated assembly continuityHigh
6IBC Ch. 11 / A117.1 §404 — accessible doors & maneuveringModerate
7IMC / IBC — ventilation & equipment access clearancesModerate
8IPC — fixture count & accessible fixture clearancesModerate

The pattern that holds across the list: the violations that recur most are the geometric and cross-sheet ones — a clearance, a width, or a count that is correct on one sheet and wrong on another. These are exactly the findings that pair with the broader categories in our most common drawing errors report.

Why NEC 110.26 tops the list

Electrical working-space clearance is the most-flagged single code section because it sits at the intersection of two disciplines that rarely draw the same room at the same scale. The electrical engineer places a panel on the power plan; the architect lays out the room on the floor plan; neither sheet shows the 36-inch depth, 30-inch width, and 6.5-foot headroom that NEC 110.26 requires in front of the equipment. The violation is invisible on either sheet alone and only appears when the two are reconciled.

Our deep dive on NEC panel clearance requirements walks through the working-space, dedicated-equipment-space, and illumination rules in detail, and NEC electrical code checking shows how Helonic flags them automatically.

Egress and accessibility: the two categories on every project

Egress and accessibility rank second and third because they appear on every occupied building regardless of type, and because both require counting and measuring against an occupant load that is itself derived elsewhere in the set. The most common egress findings are doors that swing into required width, corridor widths that don’t satisfy the calculated occupant load, and travel distances that exceed the limit for the occupancy and sprinkler condition. See our reference on IBC egress width requirements for the underlying calculation.

Accessibility findings under ADA and ICC A117.1 cluster around clear floor space at fixtures and doors (Sections 305 and 404), maneuvering clearances, and signage mounting under Section 703. These are catchable on the drawings, which is why accessibility checking and egress compliance are among the most-used checks in the platform.

The wrong-edition trap

A frequency ranking only matters if the review runs against the code edition the authority having jurisdiction actually enforces. Jurisdictions adopt the IBC and NEC/NFPA on their own schedules, often with state amendments, so a set checked against the 2026 NEC can still fail a jurisdiction enforcing an earlier adopted edition. Confirming the adopted edition and local amendments before review is the highest-leverage step in code checking — the same point we make in is AI plan review reliable enough to catch code violations.

How Helonic helps

Helonic reads every sheet of a 2D PDF set and cross-checks the measurable code categories — working-space clearances, egress widths, accessible clearances, fixture counts, and rated-assembly continuity — against the conditions shown on adjacent disciplines. Each finding includes the exact page location and the governing code reference, and can be turned into a draft RFI or plan-review comment. Confirm the adopted edition first, run the set, and let the platform handle consistent first-pass coverage of the categories that recur most.

Practitioner insight

The clearance violations are never on the electrical sheet or the architectural sheet — they're in the gap between them. Once we started reviewing the panel against the room instead of reviewing each sheet on its own, NEC 110.26 went from our most common field surprise to something we caught in precon.

— Source: Conversations with electrical engineers and MEP coordination leads at design firms and design-build contractors, synthesized from Helonic's discipline-side interviews, Q1–Q2 2026.

Construction Code Violation FAQ

What is the most common construction code violation found in drawing review?
Across the drawing sets Helonic has analyzed, the single most frequently flagged code issue is electrical working-space clearance under NEC 110.26 — panels, switchboards, and disconnects drawn without the required 36-inch depth, 30-inch width, or 6.5-foot headroom in front of the equipment. Egress width and door-related issues under IBC Chapter 10 and accessibility violations under ADA/ICC A117.1 Section 703 follow closely behind. These three categories alone account for a large share of all code findings because they recur on almost every project type.
How often do construction drawings contain code violations?
Nearly every drawing set contains at least one code-related issue at the document stage. The reason is structural, not a reflection of design competence: code compliance is distributed across architectural, MEP, structural, and life-safety sheets that are drawn by different people at different times, so clearances, ratings, and counts drift out of agreement between disciplines. Helonic's review corpus shows code and accessibility findings on the overwhelming majority of sets reviewed before issue-for-construction.
Which building codes generate the most drawing-review findings?
The International Building Code (IBC), the National Electrical Code (NEC), the ADA Standards / ICC A117.1, and NFPA 13 and NFPA 101 together drive most code findings on commercial work. IBC dominates by volume because it governs egress, occupancy separation, and fire-rated construction across every sheet. NEC and NFPA findings concentrate on the MEP and fire-protection sheets, while ADA/A117.1 issues are spread across architectural plans, details, and signage.
Why are code violations missed during manual plan review?
Code compliance requires reconciling information that lives on different sheets — a panel on the electrical plan against the clear floor space on the architectural plan, or a rated wall on the life-safety plan against the penetrations on the mechanical plan. Manual reviewers run out of time and attention before they can cross-check every clearance, rating, and count across a full set, so the cross-discipline violations are the ones that survive to the field. AI review reads every sheet at consistent depth, which is why it surfaces the cross-sheet violations human review tends to miss.
What is the wrong-edition trap in code compliance?
Jurisdictions adopt code editions on their own timelines, so a drawing set can be reviewed against the 2024 IBC or 2026 NEC while the authority having jurisdiction is still enforcing an earlier adopted edition (or a state-amended version). When the set is checked against the wrong edition, the review passes findings that the AHJ will later reject. Confirming the adopted edition and local amendments before review is one of the highest-value steps in code checking.
Can AI catch code violations reliably on construction drawings?
AI reliably surfaces the geometric and cross-reference categories of code findings — working-space clearances, egress widths, accessible clearances, fixture counts, and rated-assembly continuity — because those are checkable against measurable conditions on the sheets. Judgment-heavy determinations, such as alternative means-and-methods or performance-based code paths, still require a licensed professional. The practical model is AI for consistent first-pass coverage of the measurable categories, with a professional resolving the rest.
MG

Manas Gandhi

Co-founder & CTO, Helonic

Manas 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.

Areas of focus
  • 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: Code-violation frequency rankings derived from Helonic's internal review corpus (1,000+ project reviews, 100,000+ pages analyzed, 150,000+ issues identified) through Q2 2026. Results are reported as a relative ranking with rough frequency tiers within the code-and-accessibility category rather than precise shares, cross-referenced with the published structure of the IBC, NEC, NFPA 13/101, and ADA Standards / ICC A117.1. Editions enforced vary by jurisdiction; confirm the adopted edition before relying on any specific finding.

Last reviewed by Manas Gandhi · June 2026

Keep exploring

See which code issues are hiding in your set

Upload your PDF drawings and we'll walk you through every clearance, egress, and accessibility violation our AI flags — with the page location and code reference for each.