Submission and document reading
The resident submits documents the way they do today. The system reads them: plans, certificate of location, proof of ownership, and the pieces specific to your by-law.
Use case · Automation
The complete permit file, before it reaches your desk.
The resident submits their documents. The system checks the file against your zoning by-law and produces the list of what's missing, in plain language, before the inspector opens the file. The inspector keeps the decision.
The starting point
Half the analysis time goes into back-and-forth.
A permit application starts with a stack of documents: plans, a certificate of location, proof of ownership, sometimes a complementary study depending on the zone. In most urban planning departments, half of an inspector's analysis time doesn't go into the analysis itself. It goes into back-and-forth over missing or incomplete pieces.
- The resident submits their file without knowing if it's complete.
- The inspector opens the file, spots a gap, and sends it back.
- The resident waits, tracks down the document, resubmits.
- The inspector starts the analysis over, sometimes weeks later.
What we built
Completeness checked before the inspector, not by them.
Built on request for cities, on a bank of hours, integrated with Munia.
The completeness check
Each piece is compared against the zoning by-law requirements for that zone and that permit type. The list of missing items comes out in plain language, for the resident, not regulatory jargon.
A complete file for the inspector
The inspector receives a file ready to analyze, with up-to-date pieces. They keep the decision: approve, refuse, ask for more. Nothing gets granted without them.
How it happens
From the workshop to going live.
- 1
The workshop, half a day
Free, on your real permit files. We map the pieces your by-law requires and where the back-and-forth happens most.
- 2
Development, in weeks
We configure the check against your zoning by-law and validate it with you on real files, iteration by iteration.
- 3
Integration with your Munia
The automation lives in the tool your team already uses, connected to your online submission form if you have one. Training for the people involved is included.
- 4
Follow-up
We measure the number of back-and-forths before and after with you, and adjust. Connections to other systems are added on request.
Who it's for
The people who receive the file.
Urban planning
The first sort happens before the file reaches your desk. You analyze complete files, not piles to sort.
See the urban planning page on munia.aiGeneral management
Fewer files stuck in limbo, a more predictable processing time to report to council.
See the general management page on munia.aiCommunications
The plain-language list of missing items becomes the basis for the reply to residents, without rewriting regulatory jargon for every file.
See the communications page on munia.aiQuestions
What we get asked about this case.
Never. It checks the completeness of the file, nothing more. The inspector remains the only person who analyzes the substance and makes the decision: approve, refuse, ask for more.
It's your by-law that gets configured at the workshop, not a generic one. Your zones, your requirements per permit type, your exceptions.
No. We connect to it on request, on a bank of hours. If you don't have one yet, we can also provide the submission step.
Let's talk
One demo. 20 minutes. No commitment.
Tell us about your municipality and one pain point you'd like to solve. We'll show you how Munia (and Carange around it) handles it. Reply within 48 hours.