Permit approval speed is one of the most visible measures of a planning department’s operational health. City council cares about it. Developers talk about it when they choose where to build. Provincial governments are increasingly making it a compliance metric. And yet, most BC municipalities have only a rough sense of how their approval times compare to other cities in the province.
That is not because the data does not exist. Permit data is captured by every municipality. The challenge is aggregation, consistency, and comparison across systems that were not designed to talk to each other.
Benchmarking permit approval speed across BC municipalities is possible, but it requires a clear methodology: which metrics to track, how to define them consistently, and what the comparisons actually tell you.
Why approval speed matters more now
BC has been direct about its expectations for municipal approval timelines. Legislation tied to housing supply, including rules around secondary suites and small-scale multi-unit housing, has made it harder for municipalities to use slow approvals as an informal constraint on density. The Housing Accelerator Fund (HAF) rewards municipalities that streamline approvals. The BC Building Code sets baseline standards that affect review complexity.
Beyond policy pressure, approval speed affects housing supply in practice. Projects that take longer to permit cost more to develop. Carrying costs accumulate while a permit application sits in review. Extended timelines can kill marginal projects, particularly infill development and smaller residential builds that have less financial cushion than large commercial projects.
Planning departments that track and publish their approval times signal to developers, applicants, and council that they take operational efficiency seriously. Those that do not know their own numbers are at a disadvantage when those questions come from above.
The core metrics for approval-speed benchmarking
Effective benchmarking starts with defining metrics consistently. Across BC municipalities, the most useful metrics are:
Application to approval (total processing time). The full elapsed time from submission date to permit issuance. This is the number applicants experience and the one most often cited in public discussions. Tracking median rather than average prevents outlier projects from distorting the picture.
Stage durations. Total processing time obscures where delays occur. Breaking the timeline into stages: intake and completeness review, technical review, referral coordination, approval and issuance, reveals which stages accumulate time. A municipality where technical review is consistently fast but completeness review is slow has a different problem than one where referral coordination is the bottleneck.
First-pass completion rate. What share of applications pass completeness review without being returned? High return rates inflate processing times and frustrate applicants. Tracking this by permit type reveals whether certain categories have unclear submission requirements.
Processing time by permit type. Residential versus commercial, new construction versus renovation, single-family versus multi-unit. These categories have different review complexities, and comparing apples to apples requires segmenting by type before comparing across municipalities.
Volume and pipeline depth. Processing time depends partly on capacity. A municipality handling double its typical application volume in a quarter may show longer times simply because of queue depth, not because of process inefficiency. Volume context is necessary to interpret time trends correctly.
How cross-municipality comparison works
Comparing approval times across BC municipalities requires consistent definitions. If one city measures application date from when the complete application is received, and another measures from when the initial application (incomplete) is submitted, the numbers are not comparable.
Provincial data programs and municipal associations have made some progress on standard definitions, but consistency is still uneven. In practice, useful benchmarking comes from:
Agreeing on a definition of “application date” (typically the date a complete application is received, not the initial intake).
Segmenting by permit type so comparisons are within-category.
Using median processing times, not averages, to reduce the effect of large or unusual projects.
Noting jurisdictional differences that legitimately affect timelines: population density, development mix, referral agency requirements, staffing levels. A small municipality with two planning staff is not comparable to a city with a dedicated permits department.
With those caveats in place, cross-municipality comparison reveals a useful range. Most BC residential permits fall somewhere between a few weeks and several months, depending on complexity and municipality size. Seeing where your city falls within that range tells you something meaningful about your relative performance, even if it does not tell you exactly why.
What benchmarking reveals that internal tracking misses
Internal tracking tells you how your numbers change over time. Benchmarking tells you how your numbers compare to peers.
These are different questions. A municipality where processing times have been steady for three years might interpret that as stability. But if peer municipalities have reduced their times over the same period, steady is actually falling behind.
Benchmarking also reveals which categories of permits are outliers in ways that internal data cannot surface. If your commercial renovation permits take roughly the same time as comparable municipalities but your secondary suite applications take twice as long, that asymmetry points to something specific in your secondary suite review process. Without the peer comparison, you would not know to look.
The practical use of this information is process prioritization. Planning departments have limited capacity for improvement work. Benchmarking data tells you which categories are furthest from the provincial range, which is where targeted improvement effort has the most leverage.
Integrating benchmarking into planning department reporting
The goal is not a one-time comparison but an ongoing visibility layer. Benchmarking that gets run once and filed away does not drive improvement. Benchmarking that is embedded in regular reporting creates accountability and tracks progress.
For planning departments, this means:
A quarterly or semi-annual review of median processing times by permit type, compared to the previous period and, where data is available, to peer municipalities.
A stage-level breakdown that identifies where delays are accumulating, so improvement effort can be targeted.
A volume trend view that shows whether processing time changes are driven by application volume or by genuine process improvement.
This kind of reporting does not require a large investment. It requires clean permit data, consistent definitions, and a tool that can aggregate and present the numbers without manual effort.
For a broader view of how permit analytics fits into municipal compliance obligations, see our posts on Housing Accelerator Fund reporting requirements and FIPPA-compliant permit analytics for planning departments.
Starting with your own data
Before benchmarking against other municipalities, the first step is understanding your own numbers. Many planning departments find that the exercise of defining and measuring their own processing times surfaces issues they did not know existed: stages that are not being date-stamped, permit types that are not being categorized consistently, or completeness review returns that are not being tracked at all.
Cleaning up your own data model is prerequisite work for any benchmarking exercise. It is also work that pays off independently, because the same clean data that supports external benchmarking also supports internal reporting, council presentations, and HAF compliance.
Steller provides permit analytics for BC planning departments, including processing-time benchmarking, stage-level breakdown, and peer comparison. FIPPA compliant, data stays in Canada. Start for free.