Submitted is not issued: keep the permit evidence clear

A receipt answers a narrower question

Start by asking what the record proves. It might show a payment, a document upload or a completed submission step. Those are different events. Read the confirmation rather than relying on its filename or the sender’s short message. A receipt labelled “permit” does not, by that label alone, establish issuance. Keep the application reference and the relevant correspondence beside it so a colleague can check the same evidence.

When you report the event, use a concrete sentence: the application was submitted, the receipt is saved and the current authority response is still being checked. Do not fill the last part with an optimistic guess. These are suggested company notes, not new PermitLane statuses. If the evidence is missing, record who will retrieve it and keep the gap visible. If the current record cannot be checked, keep the last observation labelled with its date and assign another check. If two records disagree, preserve both and ask the authority to clarify the discrepancy rather than choosing the more convenient status.

Calgary separates submission and issuance

Calgary’s residential ePermit guidance identifies pre-screen and project review as statuses showing submission to the City. Its status descriptions say that pre-screen involves document review before bylaw and code review, while project review is with the City for that review. The same page describes approved for construction as a permit that has been issued. These descriptions concern Calgary’s residential ePermit workflow; they should not be treated as universal labels across municipalities.

The distinction helps explain why a submission record is not an issuance record. It does not answer whether a particular property’s work can begin, which permit applies or which conditions must be addressed. Check the actual permit documents and seek the appropriate authority or professional clarification for those questions. This article supplies a recordkeeping practice, not a construction decision.

City of Calgary: residential ePermit submission and status descriptions

Hypothetical example: a receipt becomes a scheduling assumption

Imagine a fictional contractor preparing a Willow Lane renovation. Jordan submits an application externally and saves the confirmation. Casey sees the message “paperwork sent” and starts drafting the crew schedule. Neither has recorded evidence of issuance. This is a hypothetical coordination example, not a customer account, and it assumes no loss, enforcement action or eventual approval.

Before finalising the company plan, Casey asks Jordan to identify the application reference, the current authority status and the document supporting the update. Jordan records the submission event and leaves issuance unconfirmed. Tuesday is set as the company’s next check-in, not an authority deadline. Any question about permission to proceed goes to the appropriate authority or qualified professional. The team avoids treating its own schedule as proof.

Check the permit, not just the project nickname

A project nickname can hide several separate conversations. A message about one application does not establish the position of another. Match each receipt or response to the permit or application reference it actually names. If the reference does not match your record, keep both documents and investigate the discrepancy before copying the status into a team update.

Keep the date of the observed event distinct from the date someone checked it. Yesterday’s receipt might be valid evidence of yesterday’s submission without describing today’s status. When a later response arrives, add that event and preserve the earlier record. Your history should make it possible to see how the understanding changed rather than presenting every document as evidence of the same outcome.

A six-step company evidence check

Use this before distributing a permit update or committing the team to a company schedule. It does not replace official instructions.

1. Identify the event. Read whether the record confirms an upload, payment, submission or issuance; do not infer the event from a filename.
2. Match the reference. Connect the receipt or response to the correct application and permit, rather than only to a project nickname.
3. Preserve the supporting record. Keep the original confirmation and the version of the documents associated with that event.
4. Record what remains unknown. If issuance or a condition is unconfirmed, name the person who will obtain the missing evidence or clarification.
5. Write a precise team update. State the confirmed event, its date and the unresolved question. Label your next check-in as a company commitment.
6. Add later outcomes separately. Preserve the submission history when the authority responds, and review company scheduling assumptions against the new evidence.

Keep software decisions and authority outcomes distinct

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 determination is not a municipal decision, professional advice or a guarantee of approval. Municipal submission and review remain external. An organised record helps the company explain what happened, while the authority’s actual documents remain essential to understanding its response.