Find the right source before putting a permit timeline or fee into a project decision.
A practical source desk—not a generic permit estimate. Pick a city, open the current municipal document, and keep the date beside your decision.
Every record identifies the municipal document, the signal worth reading, and the next change that should make you recheck it.
Use a published timeline as context—not a promise.
Official entry point for development-permit requirements, applications, and process material.
Next change: Application stream, submission requirement, bylaw, policy, or permit-process update.
Use it to: Confirm whether a development permit path applies before assigning a schedule or consultant scope.
Official building-permit information is maintained separately from the development-permit route.
Next change: Application checklist, building bylaw, review stream, or digital-service update.
Use it to: Map the building-permit stage separately from land-use or development approval.
The City publishes a dated schedule; fee amounts, credits, deposits, and agreement charges belong in the current document, not a generic pro forma default.
Next change: New annual schedule, fee bylaw amendment, charge update, or application-form change.
Use it to: Replace placeholder permit and application allowances with the current applicable line items.
The June 2026 fact sheet reports 2025 processing indicators and a streamlined multiplex application stream; these are reported outcomes, not a service guarantee for a new file.
Next change: New permit-performance release, process change, or published application-stream update.
Use it to: Use as context only; obtain a file-specific sequence, completeness review, and risk schedule.
Official planning, zoning, permit, and development material is organized through the City portal.
Next change: Council decision, zoning bylaw amendment, policy update, area-plan change, or new bulletin.
Use it to: Record the current governing planning source beside the parcel and date checked.
The City describes formal initial-application, development-permit, rezoning, and subdivision routes, including circumstances where an initial application is a precursor step.
Next change: Application procedure, zoning bylaw, OCP, development-permit-area, or intake requirement update.
Use it to: Determine the actual municipal route before treating a concept as submission-ready.
The City states an initial application is typically completed within 6–8 weeks once all required documents have been submitted; complexity and applicant response can change a broader project schedule.
Next change: Published process-time revision, intake-process update, or council-approved service change.
Use it to: Use only as a dated early-stage reference, then build a project-specific critical path.
The City’s permits and construction service area is the official starting point for building, trade, and related construction approvals.
Next change: Permit checklist, online-service, building-bylaw, inspection, or submission update.
Use it to: Keep building and trade permit requirements separate from planning or rezoning assumptions.
The development-planning source identifies the current consolidated fees and charges bylaw among the governing local records.
Next change: Consolidated-fee bylaw amendment, development-charge schedule, works-and-services update, or waiver change.
Use it to: Use the current bylaw and the applicable development class before entering a fee allowance.
The City notes that R1 SSMUH lots can still require a streamside protection and enhancement development permit where the parcel is near a qualifying stream or within the streamside development-permit area.
Next change: Development-permit-area map, guideline, environmental condition, or zoning update.
Use it to: Do not convert an SSMUH zoning signal into a no-permit assumption.
The City publishes application-submission guidance, intake confirmation steps, fee-estimate resources, and portal-based status access.
Next change: Submission guideline, fee bylaw, portal, environmental-report, or intake change.
Use it to: Build a complete-application checklist before relying on any timing estimate.
Surrey states that building-permit timing depends on completeness, response to City comments, and application volumes across review groups.
Next change: Digital-review, checklist, process, building-bylaw, or service-level update.
Use it to: Avoid treating a general timeline as an issuance promise for a particular application.
The City provides a fee estimator and says a non-refundable processing fee is due at application; applicable development and utility charges may be required before permit issuance.
Next change: Fee-schedule, estimator, DCC instalment, utility-charge, or building-bylaw update.
Use it to: Estimate only from the current City tool or schedule, then confirm the intake summary and permit-stage payment conditions.
A January 2026 council report records then-current review and permitting timelines. It is a dated operating snapshot rather than a guaranteed future duration.
Next change: New council performance report, permit-process update, service standard, or published timeline revision.
Use it to: Use the report to identify a source to refresh, not to promise a schedule to a buyer or builder.
The City publishes process-improvement and incentive changes separately from a project file’s actual approval path.
Next change: Pilot, policy, process, task-force, incentive, or program announcement.
Use it to: Check whether a published improvement applies to the actual application type and date.
Richmond’s official building-approvals page maintains permit forms and includes current SSMUH new-construction application material.
Next change: Application form, building regulation, submission process, checklist, or bulletin update.
Use it to: Use the current application package and verify whether the project triggers registered-professional or specialist inputs.
The City describes application documents, plan-processing fees, professional involvement in some circumstances, and payment before building-permit issuance.
Next change: FAQ, permit requirement, professional-review, payment, or issuance-condition update.
Use it to: Separate the complete-application requirement from the later issuance and payment steps.
Richmond directs permit applicants to the consolidated fee bylaw and identifies a credited, non-refundable plan-processing fee in its public guidance.
Next change: Consolidated-fee bylaw amendment, building-regulation fee change, or new fee schedule.
Use it to: Use the current consolidated bylaw rather than carrying a prior application’s fee into a new scenario.
A City council report documents development-application and building-approval fee changes and supporting rationale; verify the current enacted bylaw before applying an amount.
Next change: Council fee decision, bylaw adoption, implementation date, or schedule replacement.
Use it to: Track the distinction between a report, an adopted bylaw, and the fee that applies on the application date.
The current public FAQ is a requirements and application source; this tracker does not treat it as a published universal permit-issuance timeline.
Next change: Published service standard, performance report, permit-process, or application-requirement update.
Use it to: Request a file-specific sequence and confirm dependencies instead of inserting an unsupported duration into a pro forma.
We will not turn an address into a zoning, overlay, licence, permit, or development verdict using partial municipal data.