Check your plans against the code before you file
Enter what the National Building Code asks for and see every finding beside the clause it came from. A reviewer decides the outcome, not the software.
Rendering shown for illustrationFind the problems before the City does
Run a pre-check against the same engine a reviewer uses, then fix what it finds before you submit. Every result names the clause behind it, so you know what to change.
Start an applicationEvery finding arrives with its citation
Applications reach your queue already assessed, with a deterministic result and an audit trail on each one. Reviewers accept, override, escalate, or send back.
See how review worksCode checking your reviewers can actually trust
CACCP runs every submitted fact through a deterministic rules engine, then hands the findings to a human reviewer to accept, override, escalate, or send back — with a citation trail to the code on every result. Nothing is approved without a reviewer saying so.
Who this is for
Municipal & AHJ permit review offices
The deterministic engine applies the same approved rules the same way to every submission, so building and development permit reviews stay consistent across officers — and every approve, refuse, or override is a recorded, reviewer-made decision, never an automated one.
Policy & compliance analysts
Every finding carries a citation, an evidence trail, and — when a reviewer overrides it — a required rationale. Nothing is approved without a recorded, defensible reason.
Civil engineers
Rules are published as data, not opaque logic: RASE-structured (Requirement / Application / Selection / Exception), reviewable against the exact code provision they implement.
House & building developers
Plain-language findings tell you what's missing and why, with a clear revision path from a flagged submission to final approval — no guessing at reviewer intent.
How it works
Submit
An applicant creates a project, declares the governing code part, and enters the facts a rule needs — or extracts them from an uploaded drawing.
Evaluate
A deterministic rules engine checks every approved rule against the submitted facts. Every result traces back to a specific fact and code citation.
Review
A reviewer works each finding: accept, override with a documented rationale, escalate, or request more information from the applicant.
Decide
Approval is blocked while any critical finding is undispositioned. Only a reviewer's own action sets approved or refused.
Governed at every layer
Deterministic rules engine
Rules are data, not code. Evaluation uses three-valued logic and always resolves to one of four states — Meets, Does Not Meet, Information Not Available, or Uncertain. No hallucinated verdicts.
Human governs every rule and decision
Rules are authored offline and start as drafts; a reviewer must explicitly approve one before it can affect a live assessment. Final approval works the same way.
Four national model codes
The National Building Code — Part 9 (houses & small buildings) today, with Part 3 (larger buildings) in progress and not yet validated — plus rules from the National Fire, Plumbing and Energy codes, which apply alongside it rather than instead of it. Fire separations, means of egress, spatial separation, barrier-free access, and more.
Most of the corpus is still in draft — deliberately
An encoded rule does nothing until a named reviewer approves it. The counts above show both figures because the gap between them is the governance, not a shortfall: nothing reaches a live assessment on the strength of having been written.
Municipal zoning, as a separate development permit
Zoning is not in the National Building Code, and the gap is real: in the validating case the driveway width, parking and setback problems were raised by a development officer, not the building-code reviewer. A development permit is its own submission, judged against the municipality's bylaw by a development officer, and it can gate the building permit. Zoning rules are scoped to the municipality that made them — a bylaw is one city's, and a zoning rule that reached another city would be invented law.
Validated against a real case
The Part 9 rule set was checked against an actual City of Whitehorse permit review — real correspondence, real citations, not just hypothetical test data.
AI-assisted, never AI-decided
Upload a drawing and get suggested fact values back, with a confidence score and source reference. Suggestions are reviewed and saved by a human, like any entered value.
Full audit trail
Every review action, override rationale, and revision is recorded against the exact rule version and submission version that produced it.
The homes behind the applications
Ready to see it in action?
Sign in with an applicant or reviewer account to walk through the full workflow.
Building or planning department? Write to us at info@tangerinespace.com