Contractor changes
Changing contractors? Keep the permit record connected
Connect the incoming contractor to the right permit references, authorised records and unresolved updates before a change of team becomes a gap in the project history.
General workflow guidance
A contractor change can leave two different pictures of a job. The incoming team knows the work it has agreed to discuss, while the office still has correspondence and permit references associated with the previous contractor. A new name on the company schedule does not explain which external records have been updated. Before the handoff disappears into messages, connect the people, permit references and open administrative questions in one dated company note. The aim is continuity of evidence, not an assumption that every responsibility has transferred.
Identify the record before replacing a name
Start with the application or permit reference, property reference and the particular work being discussed. Then identify the outgoing and incoming businesses separately from the people coordinating the handoff. A familiar first name or project nickname is not enough to tell a colleague which contractor and which permit record the update concerns. Keep the earlier correspondence available instead of replacing its identity with the new contractor’s name.
Separate three questions: who is coordinating the company’s next action, who is named in the available permit correspondence, and what external update remains unconfirmed. Those answers may differ during a transition. If the record is unavailable, date the last confirmed observation and name the person who will check it. Do not use a company assignment to settle a contractual, professional or municipal responsibility that needs appropriate clarification.
Hypothetical example: the new team has a schedule but no record link
Imagine a fictional renovation on Pine Court. Sam is coordinating an incoming contractor, while Lee in the office holds the earlier permit correspondence. The company schedule has the new business name, but the handoff message contains only the project nickname. Neither person has confirmed whether an external contractor update is needed or completed. This is a hypothetical coordination example, not a customer account; it assumes no loss, enforcement action or eventual approval.
Lee connects the message to the actual permit reference and retains the earlier correspondence. Sam is assigned to confirm the applicable update process through the appropriate external channel. The company note distinguishes the incoming contact from the contractor named in the last confirmed record and leaves that discrepancy visible. Wednesday is a company check-in, not a municipal deadline. The team can explain who is checking the record without claiming that changing its schedule completed an authority process.
Calgary’s update instructions depend on the stated project category
Calgary’s residential ePermit guidance describes different contractor-update steps. For new house permits, it refers to updating the contractor’s business identification number, or BID. For residential improvement projects and demolition permits, it instructs the applicant to email the City with the new contractor’s name. These are Calgary’s stated ePermit categories and instructions, not a universal Canadian contractor-change process.
Check the current instructions for the actual application rather than choosing a category from this article. If the relevant record or process is unclear, seek confirmation from the appropriate authority. An administrative update does not by itself establish approved scope, permission to proceed or the responsibilities of the incoming business. This article does not interpret building code or decide permit applicability for a property.
City of Calgary: residential ePermit contractor-update guidance
Hand over relevant evidence without handing over credentials
Prepare a short index of the records the incoming team is authorised to receive: the relevant permit references, correspondence and unresolved questions. Identify where each record came from and what it actually shows. A document proving an earlier event should retain that event’s date and context. Avoid sending an entire project folder simply because it is easier than identifying the material needed for the handoff.
Use an appropriate authorised sharing method and verify the intended recipient. Do not share another person’s portal password or treat access to a folder as authority to act for a business. If records are missing or two versions of the contractor identity disagree, state the gap and assign a follow-up. When confirmation of an external update arrives, add it as a later observation while preserving the earlier position. These are company information-handling suggestions, not a claim that PermitLane transfers permits or manages municipal accounts.
A six-step company contractor-change check
Use this suggested coordination checklist when preparing a contractor handoff. Follow the authority’s current instructions and obtain appropriate professional or contractual clarification separately.
- Match the permit. Identify the application or permit reference and the particular work; avoid relying only on a project nickname.
- Separate the identities. Record the outgoing and incoming businesses, their contacts and the contractor shown in the last confirmed correspondence.
- Assign the external check. Name who will confirm the applicable contractor-update process and what remains unverified.
- Index authorised records. Identify the relevant evidence and unresolved questions the incoming team may receive; preserve their original context.
- Check access and recipients. Use authorised sharing, confirm the intended recipient and keep personal portal credentials out of the handoff.
- Record the later confirmation. Add evidence of the external update separately, retain any remaining discrepancy and label company check-ins honestly.
Keep company coordination distinct from authority decisions
PermitLane organises permit work and records human-observed external submissions and review outcomes. Its AI determines applicability from an applied playbook snapshot and the exact cited official-source revision; the recorded decision is applied automatically and an authorised person can override it. That is not a municipal decision, professional advice or a guarantee of approval. Municipal submission and review remain external. A clear company record helps preserve continuity while the appropriate people confirm the actual permit position.
Official sources
Source checked October 18, 2026. The Calgary example concerns residential ePermit contractor-update instructions. The company handoff checklist is a suggested practice, not a municipal requirement or permission to build.