Who owns the next permit step when the company owner is on site?

Make the responsibility gap visible

“The office is handling it” does not identify a person or a commitment. Name the next action, then ask the intended coordinator to acknowledge it. Until that happens, describe the gap plainly: “No responsible person confirmed” or “Handoff awaiting acknowledgement”. These are suggested company descriptions, not new PermitLane statuses. An assignment on a list is not proof that its recipient has read it.

Keep the responsibility small enough to understand. “Check whether the requested drawing has arrived” is clearer than “Sort out the permit”. One person can coordinate the follow-up while someone else prepares a document or answers a technical question. State those separate contributions so the coordinator does not become an assumed designer, applicant or decision-maker.

Hypothetical example: two people assume the other will reply

Imagine a renovation company whose owner is on site while its usual coordinator takes a day off. A question about a supporting document arrives. The office administrator believes the site lead will answer; the site lead assumes the office has it covered. Nobody has acknowledged the action. This is an invented example, not a customer story or a claim about a particular municipal file.

Before leaving, the coordinator could name Alex as the backup for checking incoming correspondence. Alex confirms availability and agrees to locate the requested document, while the company owner remains the contact for an unresolved scope question. If Alex cannot obtain the document, the handoff calls for a clear update about the blocker. It does not call for an invented answer or a claim that the authority accepted anything.

Hand over the evidence with the action

Give the backup the project and permit reference, the exact request, the relevant document revision and the latest recorded event. Include the next action and any open question. A forwarded message without its attachment or a file called “latest” can leave the recipient reconstructing the situation. Point to a record that they are already authorized to access, and retain the original correspondence.

Agree where the acknowledgement and later update will be recorded. Use the company’s existing working process; this checklist does not require a new tool. Do not share passwords to make an absence easier. If the backup lacks appropriate access or authority to perform an action, record that limitation and arrange an authorized route before relying on the handoff.

Check the external contact route separately

Calgary’s residential ePermit FAQ lists contact information among the details that can be updated without pulling a project for revision. It directs users to the project’s contact-information area and its edit control. That is a specific portal instruction, not evidence that an internal task assignment updates the City’s records. Check the current application instructions separately when external contact details need attention.

City of Calgary: residential ePermit contact-information FAQ

Agree when the backup takes over

A backup needs an agreed trigger, such as a planned absence, and a defined task. Confirm their availability rather than assuming it from a copied email. If both people are unavailable, say “Backup unavailable” and identify who will arrange cover. Internal delegation alone does not establish permission to act as the applicant, change a permit or provide a professional opinion. Resolve that question through the appropriate process.

Separate company targets from authority deadlines

Your team may agree to check a missing document on Thursday. Label that as a company follow-up target. If an authority communication supplies a deadline, keep its actual date and source separately; do not replace it with the team’s preferred date. An unknown deadline stays unknown. If instructions conflict, preserve both and assign someone to seek clarification instead of choosing the more convenient version.

A six-step company handoff checklist

Use these steps to coordinate responsibilities. They are company practices, not municipal application requirements or a decision that construction can proceed.

1. Name the action. Identify the project, permit and next observable task, including the question still waiting for an answer.
2. Confirm the primary person. Record who accepted the task and what they agreed to do; leave unacknowledged assignments visible.
3. Confirm cover. Name an available backup, the trigger for taking over and the limits of that person’s responsibility.
4. Connect the evidence. Provide the request, relevant document revision and latest recorded event through an authorized access route.
5. Label the dates. Keep the company follow-up target separate from any authority deadline and preserve the deadline’s source.
6. Close the handoff. Record acknowledgement, the actual later action and the next follow-up; unresolved questions remain visible.

Keep the next commitment easy to find

PermitLane organizes responsibilities, evidence and recorded permit events. The backup and acknowledgement practices above are suggestions for your team, not automatic delegation features. Its AI determines permit applicability from the selected playbook and its recorded official-source revisions; an authorized person can override that determination. Municipal submission and review remain external, and PermitLane does not guarantee approval. A useful handoff ends with an accepted action and an honest update about what is still missing.