Codecheck is a municipal compliance platform built by a VDC professional who felt the pain of manual ordinance research firsthand — and decided to fix it. Now live across 10 states — Illinois, Missouri, Kansas, Nebraska, Indiana, Wyoming, Iowa, South Dakota, Kentucky, and Montana — and scaling nationally.
I'm a full-time VDC Technician at an MEP mechanical contractor in the Chicago metro, where I spend my days coordinating BIM models, building Revit automation tools, and navigating the intersection of construction technology and municipal regulation.
I hold an M.S. in Building Science from Auburn University and a B.Eng. in Civil Engineering from FUNAAB, Nigeria. I've spent years building production Revit plugins in C#/WPF, running systematic literature reviews on AI in construction, and doing the manual compliance research that Codecheck is designed to replace.
Codecheck started as a question: what if the compliance system just showed you the sentence in the ordinance? It has grown into a production platform covering 505+ jurisdictions — and that's just the beginning.
Every VDC professional who has worked on a permit set knows the moment: you need to know whether an AC condenser can go in the side yard, or whether a proposed building height clears the district maximum — and you have to dig through a 300-page PDF to find out. By the time you have the answer, you've spent 45 minutes on a question that should have taken 30 seconds.
The PDFs are long. The answer is in a table on page 312. The table has footnotes. The footnotes reference other sections. And even after all that, you're still not certain you read the right table for the right district.
"What if the system just showed you the sentence in the ordinance — not a paraphrase, not a summary — the actual sentence, with the section number, and a clear pass or fail?"
That question started Codecheck. I began with Westmont, Illinois — the municipality where my employer is based — extracted the entire zoning code into a structured schema, and built a checker against it. Then I kept going. Today, 505 jurisdictions are live, covering 6,784 zoning districts across 10 states. The national expansion starts next.
The methodology is rigorous: every field cites the exact ordinance section, every gap is documented honestly rather than silently omitted, and every jurisdiction's depth score is published openly on the Coverage page. Because real compliance requires knowing what you don't know just as much as what you do.
These aren't aspirations — they're the design constraints the entire system was built under. Every architectural decision in Codecheck flows from one of these principles.
A paraphrase is an interpretation, and interpretations can be wrong. Every result includes the exact article, section, and table it came from — because that's what holds up in a plan review meeting.
Every jurisdiction publishes a depth score. Every missing category is documented as "not yet sourced," not silently omitted. We'd rather show you what we don't know than hide it behind false completeness.
A compliance check that takes 45 minutes is one that doesn't happen. Codecheck returns the same answer you'd get after 45 minutes of PDF research — in under 30 seconds.
Designed by someone who does the work. Every field in the checker, every category in the schema maps to a real question a real contractor asks before a real permit submittal.
Compliance checking belongs inside the tools professionals already use. The REST API and Revit add-in exist so the best compliance tool is the one you never have to open a new tab to reach.
Illinois is the proof of concept. The same extraction methodology that covers 505 jurisdictions works for any municipality in any U.S. state. The architecture was always national.
Codecheck's architecture is grounded in peer-reviewed research on AI-BIM integration for MEP contractors. My Auburn M.S. thesis — "Integrating AI with BIM for HVAC Contractors: A Practitioner-Centered Framework for Workflow Enhancement" — was based on 12 IRB-approved interviews with VDC and BIM professionals. Compliance checking emerged as the single highest-value application of AI in the pre-construction phase.
A co-authored systematic literature review on AI in construction pre-construction has been submitted to Automation in Construction, one of the field's leading peer-reviewed journals. The review covers PRISMA methodology, bibliometric analysis, and the landscape of AI tools across the pre-construction workflow.
Codecheck's data schema, extraction methodology, and API architecture represent an original engineering contribution to the U.S. construction industry's efficiency — not a derivative tool, but a purpose-built compliance intelligence system.
The reference jurisdiction — all 18 districts, all 18 compliance categories, every field sourced and cited from the actual ordinance PDF. The template all subsequent jurisdictions follow.
DuPage (17/18), Cook (16/18), McHenry (16/18), Boone (16/18), Kane (14/18), Will (14/18), Lake, Winnebago, Champaign, McLean, DeKalb — all extracted from official PDFs.
Elgin, Glen Ellyn, Arlington Heights, Bolingbrook, Collinsville, Chicago Heights, Chillicothe, Clarendon Hills, Carlyle, Crete, Gilberts, Brookfield, Calumet City, and more — each with real zoning district structures and local building code amendments.
Closing the remaining category gaps across all existing jurisdictions — ADU rules, MEP extended, loading requirements, landscaping. Targeting 16/18+ for all live jurisdictions.
Enter a project address and Codecheck automatically identifies the correct jurisdiction, zoning district, and applicable rules — no manual selection required.
Extending beyond Illinois to serve contractors working across state lines in the greater Chicago metro and the broader Midwest construction market.
Codecheck was architected for national scale from day one. The same methodology that covers 505 jurisdictions works for any municipality in the United States.
Full multi-jurisdiction compliance checking — free to use, no account required. Every result cites the source ordinance section.