Code compliance for
licensed professionals.
Ask the NEC, IBC, or NFPA 70E. Get the exact article, table, and exception — with citation trail and jurisdiction context. Built for engineers, contractors, and plan reviewers.
Sample output ↓
Code Text
“...overcurrent protection shall not exceed 30 amperes for 10 AWG copper and 40 amperes for 8 AWG copper...”
Sections indexed
NEC · NFPA 70E · IBC · IFC · ASCE
Citation format
Section, table, exception — not paraphrase
Jurisdiction layer
State amendments and local code adoptions

Platform capabilities
Built for the AEC workflow,
not the general public.
Every feature maps to a real task: pre-app meetings, submittal review, design review, AHJ coordination, and field verification.
Full Code Coverage
NEC, NFPA 70E, IBC, IFC, and ASCE 7 indexed at the article level. Ask about any section, table, or exception — including amendments.
Plan Compliance Review
Upload plan sets, panel schedules, or spec sections as PDF or image. Get numbered compliance findings with code basis and corrective action.
Exact Citations
Every answer cites the specific article, table, and exception. Not a summary — the actual code language, with edition and section number.
Jurisdiction Layer
State adoption tables and local amendments surfaced alongside base code. Know which NEC cycle your AHJ has adopted before the pre-app meeting.
PE-Ready Reports
Export compliance findings to PDF or Word with cover page, finding numbers, code basis, and action items — formatted for submittal packages.
Field-Ready
Optimized for mobile and tablet. Voice input for hands-free code lookup on the jobsite. Installs as a PWA for low-signal environments.

See PocketPE
In Action
Watch real demos of PocketPE.ai in action – from simple queries to advanced file analysis.
Simple Chat Demo – Ask questions, get instant answers
Advanced Demo – File Upload & Code Reference Table View

How It Works
Get expert electrical code answers in seconds, not hours of manual research.
Whether you're asking about NEC 210.20(A), motor sizing tables, or grounding requirements, simply ask naturally.
