Keep the original submission when the City asks for revisions

Read the comment before assigning the answer

Keep the authority’s original message with its date, application reference and attachments. Read the complete request before splitting it into tasks. Preserve the wording and put your team’s interpretation in a separate note. If a comment refers to an unfamiliar drawing or seems inconsistent with another instruction, record the question and ask the appropriate authority or project professional to clarify it.

Give each comment a reference the team can use, retaining any reference supplied by the authority. Connect it to the correct permit and review round. A request about one application should not silently become a requirement for every permit on the project. An unanswered question remains a blocker, even when other responses are ready.

Hypothetical example: two comments, three attachments

Imagine a small contractor receives two requests for clarification during an application review. A designer prepares a revised drawing for the first. The coordinator is gathering a supporting document for the second. A colleague sees three attachments in the shared folder and assumes the response package is complete. This is an invented coordination scenario, not a customer story or a technical finding by a municipality.

The coordinator checks the two comments individually. The first has a proposed answer and an identified drawing revision; the second still needs confirmation from the person supplying the document. The useful update is specific: one response is prepared and one is waiting. Counting files, or marking the designer’s task complete, cannot establish that every requested item has been addressed.

Map each comment to a response

For each item, record the comment reference, responsible person, proposed answer, exact document revision and next action. For example: “Comment 2: Riley is obtaining the supporting document; office check on Thursday; blocked pending the supplier’s response.” That is an illustrative company follow-up, not a municipal deadline. Record any actual authority deadline separately, together with the notice that establishes it.

Make the answer easy for another team member to follow. A note saying “updated” is less useful than a reference to the relevant sheet and revision. If a document answers more than one comment, identify each connection. If no change is proposed, record the explanation being put forward rather than quietly removing the comment from your list.

Keep your copy and follow the portal instructions

Retain the original package in your company records, together with what you observed about its external submission. Save the authority’s response and distinguish the proposed replacement files from the files previously sent. This history helps the next person understand what the reviewer saw and what the team changed. It does not require adding duplicate documents to a municipal portal.

Calgary’s residential ePermit FAQ describes resubmission as supplying information or drawing/detail revisions needed before approval. It says changes to an existing document should update that document rather than add a new one. The FAQ also distinguishes “pre-screen” and “project review”, which indicate submission to the City, from “revision” and “re-submission”, which remain under the applicant’s control. Follow the current instructions for your application; these are Calgary portal terms, not PermitLane statuses.

City of Calgary: residential ePermit resubmission guidance

A six-step company checklist

Use this as a company coordination check before the next external submission. It is not a municipal requirement list or a substitute for the authority’s instructions.

1. Preserve the request. Save the complete authority response, its date, attachments and application reference.
2. Separate the comments. Identify each item and its review round; keep uncertain or conflicting instructions visible.
3. Assign the answer. Name the responsible person, the next action and an internal follow-up date clearly labelled as your company’s target.
4. Connect the evidence. Point each proposed response to its exact document and revision, and retain the earlier company copy.
5. Check the package. Review outstanding questions and follow the applicable portal instructions before the authorized person submits externally.
6. Record the actual event. Keep what was sent, when it was sent and any acknowledgement; assign the next follow-up without assuming acceptance.

A response sent is not a response accepted

Tell the team what you can support: the answer is being prepared, the response was sent, or an acknowledgement is still missing. These are suggested company descriptions, not new product statuses. When a later authority response arrives, connect it to the submission it addresses. Keep earlier messages intact so the sequence stays understandable. Do not turn an upload, acknowledgement or internal task completion into a claim of approval.

Keep the review history together

PermitLane organizes 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 that determination. This does not mean AI resolves a reviewer’s technical comment. Municipal submission and review remain external, and PermitLane does not guarantee approval. A clear record helps the team find the next action and the evidence behind it.