01 · Intake
The exact documents, fingerprinted.
Drawings, building models, forms and reports are received, scanned and fingerprinted, so it is provable which documents were checked.
Product · SaaS · In development
Building-permit packages checked against Canadian building codes, item by item, with fixed and tested rules. Every finding shows the provision, the evidence and where in the drawings it came from. A qualified person makes the decision.
Every provision checked returns one of four results
The verified information satisfies the provision.
The verified information does not satisfy the provision.
Something the check needs is missing from the package.
The answer needs interpretation, conflicts, or depends on the site — a person decides.
FIG. 01 / Four results, never a silent pass
CodeCheck never turns missing or uncertain information into a pass, and it states what it did not check, so a partial check cannot be mistaken for full compliance.
The problem
A large share of a plans examiner's time goes to routine checks that come out the same way every time — dimensions, areas, counts, ratings — before the work that needs judgement can start. Applicants learn about omissions only after submission, and each round of corrections costs both sides weeks.
A general-purpose AI chatbot is not the answer: it can give a convincing reply that changes when the question is asked differently. Code compliance needs answers that are repeatable, explainable and defensible to an applicant, a council and a court.
How it works
01 · Intake
Drawings, building models, forms and reports are received, scanned and fingerprinted, so it is provable which documents were checked.
02 · Evidence
Information from drawings, models and documents is brought into one description of the building, each fact linked back to its page, drawing area or model object. Extracted facts stay suggestions until confirmed.
03 · Classification
The building is classified — use, size, height, storeys — to decide which part of the code applies. When that is missing or open to interpretation, CodeCheck asks a qualified reviewer instead of guessing.
04 · Checking
The rules in force for the location and date are applied to the verified facts. Rules are version-controlled and approved by qualified people before use; the same inputs and versions always give the same result.
05 · Review
Reviewers work a queue of findings, each with its provision, evidence and reasoning. They confirm, disagree, request information or accept with conditions; their decision is recorded beside the machine result, never over it.
06 · Revisions
A corrected submission becomes a new version. CodeCheck shows what changed and rechecks the provisions it affects, with who submitted each version and when.
Built for Canadian authorities
CodeCheck is a jurisdiction-agnostic engine. A province, territory or municipality's adopted code or by-law is loaded as a document and becomes checkable provisions under that document's own citations. Adding a jurisdiction is a reviewed content step, not a development project.
It is designed for English and French codes, with the relationship between the two language versions reviewed by bilingual code specialists rather than assumed from machine translation. It is designed so that permit data stays in Canada, with a private installation for authorities that need one. It connects to an existing e-permitting system through open interfaces rather than replacing it.
CodeCheck will be offered as a hosted service that we operate, so a building department does not have to run it. It is in development, runs on our own infrastructure today, and is not yet offered for production permit review.
CodeCheck · In development
If you run a building department or a design practice and want to talk about automated compliance checking, tell us about your permit volumes, your codes and the systems you use today.
Talk to us