Review the new use before treating it as the old building.

Describe the business activity in ordinary language

Write what happens in each space, who uses it and what is stored or installed. “New tenant” or “same floor area” is too broad to explain a restaurant, exercise studio, workshop or warehouse change.

Use known descriptions instead of choosing a code classification yourself. Include the existing approved use when documented, the proposed activity and the rooms affected. Mark uncertain history as uncertain.

Build the before-and-after record

This is a briefing table, not an occupancy classification or a code assessment. Send it with the current plan revision.

Copyable use-review enquiry: “At [property], the documented existing activity is [description/source]. We propose [plain-language activity] in [identified rooms], with [layout, equipment or storage changes]. Available plans are [revision], and [specific history] remains unconfirmed. Please identify the appropriate local review pathway, information needed and responsible roles for determining the applicable building and protection questions.” Replace the brackets with actual facts. Attach the before-and-after schedule through the authority’s appropriate process and keep the response with that version. A proposed opening date is scheduling context, rather than evidence that the use is accepted.

Ask the authority about the whole pathway

Vancouver’s listed change-of-use development checklist asks for a proposed-use statement and plans showing room uses and changes. Calgary’s assembly tenant guide explains that such a tenancy can require building reclassification. These are local examples of why the use question belongs early in planning.

Ask the responsible jurisdiction which planning, building, fire and professional reviews apply. Record who coordinates the responses so one permit enquiry is not mistaken for every required decision.

Give the sprinkler team the actual change

• Current layout and available installation records.
• Proposed use description and drawing revision.
• Storage and equipment changes.
• Known access or occupied-work constraints.
• Authority correspondence and outstanding questions.

Ask what the existing protection assessment must establish and what information is still missing. Do not decide from the count of visible heads or a prior inspection result.

Keep decisions separate from the opening date

An intended opening date is useful scheduling context. It does not establish approval or technical suitability. Ask the project team to identify prerequisite reviews and which decision gates remain open.

If the proposal changes, update the use record and route the new version to the responsible team. Preserve the previous answer with its original assumptions.

Work through a use change with the same walls

Imagine a commercial suite that previously held a small office and is proposed for a group activity business. The floor area and most partitions remain. The owner may see a modest fitout, while the project team still needs the proposed use, activities, intended occupants and equipment information. The useful first step is a clear description of those changes and a request for the applicable review pathway. This example makes no occupancy classification or statement about which upgrade is required.

Prepare a marked plan showing which rooms change use and which remain as documented. Add a separate activity note for areas that cannot be explained by a room label: classes, storage, preparation work or gatherings, for example. Include existing permits or correspondence when available, but do not treat a lease description as an authority-approved use record. Ask the project team to identify the significance of incomplete history and the information needed to resolve it. A narrow proposed-change statement helps the authority answer a specific question.

Keep each answer with its jurisdiction, issuer and scope. A planning response about permitted business use may leave building or fire-protection review unresolved. A sprinkler provider may address its defined system scope while another professional handles wider building questions. Assign the coordination role that connects those answers. This prevents one favourable email from being treated as approval for every part of the opening plan and gives the owner a practical list of what still needs to be established.

Create decision gates that can survive a revised proposal

Break the planning record into questions to be resolved before major commitments. The gates may include confirming the authority pathway, establishing the design-review scope, coordinating the proposal and obtaining applicable completion or occupancy records. The project team determines the actual requirements and sequence. The record should show what evidence moves each gate forward, who supplies it and which assumptions the answer depends on. A target opening date belongs beside that record as scheduling context, not as a substitute for the required decision.

When the business plan changes, identify which parts of the brief changed: activity, room use, equipment, storage or layout. Send the update to the coordinator and ask which earlier answers need reconsideration. Keep the original version so the team can compare the proposal it reviewed with the current one. Do not change a room name in the final drawing and assume the earlier assessment automatically covers the revised operation. Even when the effect is ultimately limited, the review and explanation should be visible.

Before opening or completing the handoff, assemble a short decision index. It should name the accepted proposal, the relevant drawings and the records supplied by each responsible party. List outstanding limits and who owns them. Give the operating manager the accepted use description so future business decisions start from the completed record. This administrative continuity is useful long after the construction contact has left, especially when a later owner sees only the same walls and has no account of the review that supported the operation.

Retain the accepted use and protection record

Keep the resolved use description, accepted drawings, relevant authority correspondence and final system records together. Tell the building contact which changes were completed and which future changes require review.

Start with the property pathway for the relevant conversation, then use a project brief to prepare the record.

When several parties are involved, keep one named coordination contact for the owner. Ask that contact to identify the next decision and its supporting response after each material revision. This does not transfer every professional duty to one person; it gives the owner a clear administrative route for bringing the separate answers together.

References and scope

1. Change of use: development permit checklist — City of Vancouver. September 2021 checklist, still listed in the municipal document directory on review. Local submission example; confirm the current pathway and required documents with Vancouver for actual work. Link reviewed 2026-10-02.
2. Tenant improvement application: assembly occupancies — City of Calgary. Calgary assembly-occupancy application and professional-design guidance. It is not a national tenant-improvement rule or a determination for an individual project. Link reviewed 2026-10-02.
3. Provincial and territorial code adoption — Canadian Board for Harmonized Construction Codes. Explains adoption and enforcement responsibilities. Provincial tables carry different reference dates; obtain current information from the responsible authority. It is not a ruling for a particular building. Link reviewed 2026-10-02.

Review dates identify source-link checks, not professional certification or a building-specific determination. Confirm current jurisdiction and exact-model requirements for actual work.