Conversational Intake: describe your project, get the right permit forms
The first hours of every permit application go to working out which forms apply. A conversation replaces them.
Read the guide →
Feature guides
Twelve features, one permit workflow that runs itself
Detailed guides to every Permits2Go feature: how the work gets done today, what that costs, how the feature works, and what your permit process looks like after.
Ontario has 444 municipalities, and one after another they are buying, building and maintaining their own online permit portals. The result is hundreds of disconnected approval systems with different forms, naming rules, reviewer contacts and data formats, all operating under the same provincial legislation. Writing in Residential Builder, Arash Shahi, CEO of LandLogic, summed up the outcome: after years of funding, pilots and promises, development approvals in Ontario still average 18.4 months.
Permits2Go was built for the applicant side of that problem. Instead of learning each municipality's paperwork from scratch, you describe the project once and the platform finds the right forms, fills them, reviews the drawings, packages the submission the way each city expects, and keeps every reviewer conversation on the application. As Shahi put it, instead of applicants managing the process, the process manages itself.
Each guide below covers one feature in depth: the current industry workflow without it, the cost of that workflow, how the feature works, and how it changes the process from here on. Read them in order or jump to the one that hurts most today.
Form Discovery & Uploads: the right forms, the right drawings, named the way the city wants
Building the document list for a permit is a research project. Keeping drawings named and current is a second one.
Read the guide →Auto-Analyze: machine-learning drawing review before the city sees your plans
Most first-round comments are about what is missing from the drawings, not what is wrong with the design. A pre-review catches them.
Read the guide →City Submissions: packages named to each city’s standard, delivered by email or portal agent
Every municipality wants the same package delivered a different way. The submission step is where that shows.
Read the guide →Send for Signature: pre-filled permit forms your clients sign in minutes
The owner’s signature is one line on one form and routinely costs a week. Signing links with pre-filled fields close that gap.
Read the guide →Automated Reviewer Calls: a voice agent that phones the city so you don’t have to
The phone is still how permit status really moves in Ontario. A voice agent makes the call, records it and proposes the update.
Read the guide →Review Comment Responses: turn a comment letter into an itemized, answered, tracked list
The comment letter is where most permits lose their second month. Itemizing, answering and tracking it by hand is why.
Read the guide →Dedicated Application Inbox: every permit gets its own email address
City correspondence goes wherever the applicant’s email goes. An address per application keeps it on the file.
Read the guide →Dashboard & Notes: status, fees, city comms and client updates for every application in one place
The permit spreadsheet is where good intentions go to become out of date. A dashboard that the file itself keeps current fixes that.
Read the guide →Notes: the running record your team writes to as the file moves
What the examiner said, what the owner agreed, what the engineer promised: today it lives in threads. A notes tab puts it on the file.
Read the guide →Site Inspections: who is coming, what passed, and the deficiency list before re-inspection
The permit is issued and the paperwork moves to the site. Inspections are where a project passes or stalls, and where records are thinnest.
Read the guide →Auto-Filled Permit Forms: government PDFs that arrive already filled in
The same address, owner and designer details typed onto a dozen forms, in a dozen layouts. Pre-filled PDFs make that a review, not a job.
Read the guide →