Skip to main content
Planning & Building

Cleaner applications. Traceable answers. A number a council can prove.

TrueNorth checks a planning or building application before it is submitted, answers zoning questions with a citation instead of a guess, and shows how long applications actually take. It does not decide anything — a staff member makes every call.

Canadian data residency for stored records, DLP redaction of applicant PII, and a contractually guaranteed zero-training policy. Applicant drawings are never used to train a model.

Built to sit next to the system you already run

BC municipalities run Tempest, AMANDA and EnerGov, and the Province publishes the open-source Building Permit Hub. TrueNorth does not ask you to replace them. Scoped /api/v1 keys turn screening, extraction and cited answers into endpoints your permitting system can call.

  • Upload a plan set and poll a screening run asynchronously.
  • Fetch a redacted, structured extraction once it is ready.
  • Ask a cited zoning question or list verified zones.
  • Push application timeline CSVs for descriptive analytics.

Keys are sha256-hashed with a server-side pepper, tenant-scoped, scope-checked and rate limited to 60 requests/minute. Full examples in the integration docs.

Integration surface · /api/v1
Tempest
MyCity / eApply
AMANDA
Granicus
EnerGov
Tyler
Building Permit Hub
Province of BC
POST/v1/screening/runs
GET/v1/screening/runs/:id
GET/v1/documents/:id/extraction
POST/v1/answers
GET/v1/zoning/zones

Four things the platform does

01

Pre-submission completeness screening

Intake & validation

An applicant or intake clerk uploads a plan set. TrueNorth reads the project data / zoning summary sheet, checks it against a city-authored checklist, and lists what is missing or non-compliant — with the sheet, page and quoted value for every finding. It cannot refuse an application.

02

Cited zoning answers, not determinations

Zoning intelligence

Ask what a bylaw requires and get the section, page and verbatim source quote back. Only human-verified rule sets are used. If no verified rule set exists for a municipality, the tool says so and shows the bylaw text — it never invents a rule value or decides what can be built at an address.

03

Turnaround time you can prove

Application analytics

Import a permit-system CSV or connect the API. Median and 90th-percentile Intake, Decision, Issuance and Total days are computed with their denominators shown, so a council that promised 60 days can measure it. Descriptive only — no forecast.

04

An integration surface, not another silo

Integration API

Scoped API keys let your existing permitting system call /v1 endpoints for document upload, extraction, cited answers, verified zones and asynchronous screening runs. The tenant is resolved from the key; every call is scope-checked and logged.

What it deliberately does not do

The last generation of automated compliance review was cancelled on cost-benefit by the city that piloted it. We built the defensible layer instead, and we say plainly what is out of scope.

  • Decide, approve or refuse an application
  • Determine zoning compliance for a whole municipality
  • Review the BC Building Code or the Vancouver Building By-law
  • Guess a zone from an address without a verified lookup
  • Forecast approval timelines or score applicant risk
  • Build a 3D digital twin or a bespoke workflow engine

Fundable as a project, not a subscription

UBCM's Local Government Development Approvals Program funds bylaw digitisation and Building Permit Hub compatibility; the CMHC Housing Accelerator Fund and the federal e-permitting stream back approvals modernisation. A citation-backed screening and integration layer fits that shaped work — and it is the cheapest way to get a defensible number in front of council.

This is a completeness screen, not a determination. Staff review every application. See the AI governance & decision register.