Roadmap
What's shipped, what's next, and what you can vote on
Van Permit Audit publishes its roadmap in public. Everything shipped is listed below, everything planned for the next four quarters is listed below that, and the community voting board at the bottom drives the order we build things in. Vote for the features your firm needs: the ones with the most votes move up the queue.
Shipped
Every feature below is in production right now. The "Shipped" tag on the voting board below tracks newer shipped items as they land.
- Full City of Vancouver zoning bylaw coverage (RS-1, RT, RM, CD-1 districts)
- Vancouver Building By-law 2025 Volumes 1 & 2 indexed
- Parking By-law No. 6059: sections 1 to 8, 15 to 17
- Noise Control By-law No. 6555
- QR-verified public certificate links (scan-to-verify)
- CoV Application Pre-Fill (18 fields auto-populated from the analysis)
- Senior Official's Regulatory Assessment PDF (expanded bylaw rationale)
- Permit Vault: saved report history per account
- 7-day money-back guarantee on paid reviews
- Shadow audit: every analysis double-checked by a second model pass
Planned: next four quarters
Directional commitments, not dates in stone. The Q4 2026 and Q1 2027 items reshape significantly based on voting. Recent vote history is the best predictor of what actually ships on schedule.
- Laneway-house specialized analysis flow (different bylaw emphasis)
- Heritage-zone overlay awareness for First Shaughnessy, Gastown, Chinatown
- Multi-document upload (drawings + site plan + survey combined)
- Burnaby Zoning By-law No. 4742 full coverage
- Richmond Zoning By-law 8500 full coverage
- BC Building Code 2024 Part 3 (large buildings) indexing
- BC Building Code 2024 Part 9 (houses and small buildings) indexing
- Multi-factor authentication for accounts
- North Vancouver (District + City) zoning coverage
- West Vancouver zoning coverage
- BC Energy Step Code analysis
- Permit-timeline prediction: predict how long a Vancouver permit application will take based on complexity and historical data
- Architect / P.Eng. collaboration workspace: share reports with team, comment inline
- SSO / SAML for Enterprise customers
- SOC 2 Type I audit
- City of Surrey: Zoning By-law No. 12000 coverage
- City of Coquitlam: Zoning By-law No. 3000 coverage
- Application-layer encryption on stored documents
- API for approved integration partners (architectural firms, permit expediters)
How we decide what to build
We ship what users vote for
The order below is driven by customer votes, not internal priorities. If your firm works in a municipality we do not yet cover, vote for it: the municipalities with the most votes get built first. One vote per person per feature.
We publish in quarters, not sprints
Weekly roadmaps slip. Quarterly commitments survive. We publish a rough commitment for the next three quarters and let the fourth quarter remain directional. When a Q ships, we retrospect what moved, what slipped, and why, publicly, in a post.
No vaporware
A feature moves to "In Progress" only when there is a tested prototype on the staging environment. It moves to "Shipped" only when at least one paying customer has successfully used it end-to-end. The "Not planned" tag is used honestly: if we are not going to build something, we say so rather than leaving it in permanent limbo.
Coverage beats cleverness
Most roadmap requests are about "please add my municipality" rather than "please add AI feature X". That matches our view of where the real product value lives: in the bylaw encoding work, not in the model. We invest accordingly.
Community voting board
Upvote the features you want most. Suggest new ones. Every idea is reviewed. One vote per person per feature: we use browser fingerprinting (not accounts) so you can vote without signing up.
Know someone who works with Vancouver permits?
Share this page: the more votes a feature gets, the faster we build it.