How we onboard codes and maintain accuracy over time
Our content team follows a systematic process to bring new jurisdictions into UpCodes and keep adopted codes accurate as they change. Because publication lifecycles vary by AHJ, our workflow is designed to stay current and auditable.
Accuracy is a lifecycle, not a one-time import
Codes don’t arrive as a single “final” PDF. They move through drafts, errata, supplements, and local amendment cycles. Our process tracks those stages so adopted requirements remain consistent inside UpCodes.
A unified library of codes, assemblies, and products
Maintaining adopted codes at scale isn’t just about collecting documents-it requires sustained effort, judgment, and verification. This is the work that keeps the UpCodes library usable in real projects, not just theoretically accurate.
Faster, smarter workflows
See the code in visual form
Confidence in the details
Clearer enforcement timelines
"Before UpCodes, I used to chase down state and local modifications myself, finding the actual code mod legislation on government websites, so I know how to get my information from primary sources. And I've had at least two experiences with other aggregators that left out changes or got them wrong. That shot my confidence in those sources forever. So when UpCodes came out, I double-checked it many times, and to date I have not found any substantive errors or omissions. I now have enough confidence in UpCodes that I go to it directly for accurate state code texts."
Paul Naprstek, Principal at PEN Architectural Consulting
How We Maintain Code Accuracy Over Time
Here's what we ask as we research each jurisdiction:
- Which AHJ governs which code? This helps us break down the regulatory and legislative authority for each city/state.
- How does the AHJ make code changes? This helps us determine how the AHJ adopts and amends code.
- How do codes from different AHJs work together? This helps us understand the intricate relationships between the various code-enforcing entities.
We coordinate with AHJs and work with code development staff on an ongoing basis. That coordination helps us resolve clarifications faster, identify typos or errors earlier, and share those findings back with the AHJ. It also allows us to anticipate upcoming adoptions. By tracking draft versions, reviewing adoption details, processing draft legislation, and addressing AHJ questions, we’re able to host future codes well ahead of their effective dates.
Once a code moves toward adoption, we follow it through every stage of its lifecycle. That includes obtaining final versions, reviewing adoption details, performing comparative analysis, and resolving outstanding AHJ questions. When the effective date arrives, the adopted code becomes the current code available on UpCodes for that jurisdiction. From there, we continue tracking supplements, updates, and intermittent legislation to ensure the content stays current.
Code accuracy doesn’t stop at publication. Our team combines technology with full-time, dedicated code reviewers to monitor AHJ-specific updates, addenda, errata, and TIAs as they’re released. We incorporate changes throughout the lifecycle until a code adoption is eventually superseded in that jurisdiction. This ongoing process ensures users are always working from the most accurate, enforceable version available.
A platform with depth and breadth
Trusted by 800,000 AEC professionals and teams who rely on accurate, current codes.
All your building codes in one organized library.
See the code with our detailed diagrams
Access a growing library of high-fidelity diagrams that clearly illustrate complex code requirements and help your team visualize how they apply in real projects.
Real results. Measurable impact.
Projects don’t just store information — they make it reusable. Quickly migrate insights, standardize documentation, and control project settings to save hours across teams and jurisdictions.
All your building codes in one organized library.
Simplify product discovery and selection
Browse compliant product options aligned with your project’s code requirements. Compare specifications, explore alternatives, and connect products directly to assemblies and diagrams for better decision-making.
Our most frequently asked questions
Got more questions? Read our full FAQ or contact us with your enquiry.
Copilot is included in the UpCodes Professional plan. Essentials users can try Copilot with limited access, but full capabilities are reserved for Professional subscribers.
Generic AI tools are trained on broad internet data and aren’t designed to handle the complexity of AEC compliance. UpCodes Copilot is purpose-built on a continuously maintained library of locally adopted codes, amendments, assemblies, and products, with clear citations back to the exact sections used.
That difference shows up in practice: in a recent expert-reviewed study, Copilot was 57% more accurate than leading generic AI tools when answering real-world code questions.
Yes. Copilot remembers your jurisdiction, building type and size, and code year - so you don’t have to start over every time. You can also upload project documents like AHJ comments or spec drafts for more tailored, project-aware answers.
Accuracy is where purpose-built AI matters most. In an independent study of 43 real-world code questions, responses from Copilot and several generic AI tools were evaluated by industry subject matter experts.
UpCodes Copilot earned a 93% weighted accuracy score across major code families-more than 2× the accuracy of generic AI tested. Every answer is grounded in adopted codes, includes verifiable citations, and often surfaces diagrams to support interpretation.
Yes. Copilot doesn’t stop at Q&A. It can generate project-specific checklists, and soon, full specifications - all tied directly to your projects. This enables collaboration across teams, centralizes compliance tracking, and replaces hours of manual QA/QC with automated, reliable workflows.
Your data is your data. Copilot does not train on your conversations or documents, and we use secure, enterprise-grade infrastructure to protect sensitive information. Conversations are private by default and cannot be seen by teammates unless you explicitly share them.
