Quick Summary
- Before the check runs, you see every building code the AI will use
- Confirm, add, or remove codes—catch wrong code year (e.g. 2019 vs 2025) before it runs
- Upload project-specific PDFs (campus guidelines, municipal requirements, MIT code, etc.)
We added a step before the plan check runs: the system shows you all the building codes it's going to check against. You get a chance to confirm, add, or edit that list. Why? Because sometimes the drawing set references one code year and the team actually needs another—or the project has jurisdiction- or owner-specific requirements that aren't in the default list.
Confirm and Edit the Code List
Previously the checker would automatically run against a set of codes. Now you see something like: “Here are the 10 codes I'm going to check. Are you OK with this?” You might catch that the drawings say 2019 and you need 2025, or that a local amendment is missing. You can add or remove codes and add a short note or instruction before the check runs, so the results align with what the AHJ or owner actually expects.
That one extra step has already helped teams avoid running the wrong code set and wasting a run or missing the right jurisdiction.
Project- and Campus-Specific Standards
Many projects have custom standards beyond the base building code: campus design guidelines (e.g. MIT), municipal requirements, owner standards, or institutional PDFs. You can upload those as PDFs and the checker will consider them in the same run. So if you're on a university or government job, you don't have to choose between “code only” and “code plus our guidelines”—you add the guidelines and run one check.
Best practice: confirm with your PM or design team which codes and standards apply before you hit run, especially for jobs in specific jurisdictions or with strict owner requirements.
Custom Guidelines & Jurisdictions
Deep dive on uploading custom codes and project-specific standards.
Custom Guidelines