A scope change deserves a permit conversation

Start with what is still unknown

Treat the request as a proposed change until its status is clear. Record what the client wants and what your team still needs to confirm. Agreement on the design or price does not establish municipal acceptance. A useful next action names the person who will check the relevant process, the information they need and an internal follow-up date.

Hypothetical example: the layout changes on site

Imagine a renovation where the property owner requests a revised room layout after drawings have been approved. The site lead sketches the proposal on a copy. The office receives a photo of it, while another team member still has the earlier drawing saved on a phone. This is an invented coordination example, not a customer story or a decision about which permit action the change requires.

The coordinator can record the proposed change, identify both drawing versions and assign someone to confirm the next step with the appropriate authority or project professional. The affected team needs to know which details remain unresolved. Avoid distributing the sketch as though it were an approved instruction merely because it is the newest file.

Give each drawing a precise description

Use descriptions your team can understand: “Earlier revision — retained for history”; “Proposed change — not submitted”; “Submitted revision — authority response pending”; and “Authority-approved revision — linked to the recorded approval”. These are suggested company labels, not new PermitLane document statuses or municipal terminology. Use “Approval status unconfirmed” when the supporting record is missing.

Keep the earlier approval with the drawing it actually concerns. A later proposal does not rewrite that history. Give the files distinct revision identifiers, retain the original record and make the relationship between revisions explicit. If two files conflict, record the conflict and assign its resolution; do not use the filename, upload date or a colleague’s recollection as proof of approval.

Check the authority’s change process

For Calgary, the City’s application-change guidance says that changing an approved plan may affect permit validity and that revised plans need to be submitted for review. Its instructions distinguish residential building permits, commercial or multi-residential building permits, and development permits. Check the section relevant to the application and contact the City when the route is unclear.

Keep that municipal guidance beside the project question. The checklist below is a company coordination procedure; it does not decide whether your proposal needs a revised plan, another permit or a particular technical solution. If current instructions cannot be confirmed, leave that gap visible and seek clarification rather than treating the absence of an answer as permission.

City of Calgary: permit changes and revised plans

A six-step company checklist

Use this short record before briefing the people affected by the change. It can be maintained in your existing project records; it does not depend on a new form or an automatic workflow.

1. Record the request. Describe the proposed difference, who requested it and when. Separate what is agreed commercially from what still needs external confirmation.
2. Identify the affected records. Note the drawing revisions and permit references involved. Keep earlier files and correspondence so another person can trace the change.
3. Assign the next enquiry. Name the person who will confirm the applicable change process and the authority or project professional they will contact.
4. Write the next action and blocker. Set an internal follow-up date, label it as the company’s target and state what answer or document is still missing.
5. Record external steps separately. Preserve what was submitted, its actual date and any acknowledgement. Keep a later authority response attached to the submission it addresses.
6. Brief the affected team. Identify the exact revision and its recorded status, explain unresolved questions and ask recipients to acknowledge the update. An acknowledgement is not a municipal approval.

Finish with a clear next action

A useful update might say: “The revised layout is a proposal. Morgan will confirm the change process and update the team tomorrow.” That is an illustrative internal commitment, not an authority deadline. Replace it with the actual response when one arrives, preserving the earlier record. An unanswered enquiry stays open; sending it does not complete the review.

Keep the change connected to the permit record

PermitLane helps organize requirements, responsibilities, documents and recorded permit events. Its AI determines permit applicability from the selected playbook and its recorded official-source revisions; an authorized person can override a determination. A project note does not revise a municipal permit, and an earlier determination is not confirmation that changed work is covered. Municipal submission and review remain external, and PermitLane does not guarantee approval.