When a permit upload fails, make the next attempt deliberate

Keep an attempted upload separate from a confirmed result

Start with what you actually observed: the application reference, the intended document category, the file version and the message shown by the external service. Record the time and the action that produced the message. Avoid a broad note such as “documents submitted” when all you know is that an upload was attempted. A file selected on a computer is not evidence that the authority received it.

If the screen stops responding or the result is unclear, leave the outcome unconfirmed. Check the available external record through an authorised account before creating another attempt. A colleague should be able to tell the difference between a known failure and an unknown outcome. Do not invent a successful result to make a checklist look complete, and do not delete the earlier observation when later information clarifies it.

Hypothetical example: the office retries the wrong drawing file

Imagine a fictional renovation on Birch Avenue. Jordan is preparing an external permit document upload while Taylor coordinates the company’s office work. Jordan sees an error and messages Taylor that the file did not go through. The shared folder contains two drawing versions with similar names. Taylor is ready to retry, but the message does not identify which version Jordan used or which document category was selected. This is a hypothetical example, not a customer story or a claim of an actual delay.

Instead of guessing, Taylor asks for the reference, selected file and observed message. The company confirms which version was intended and gives Jordan the next check. A company follow-up is set for Monday; it is not a municipal deadline or an approval estimate. Their note keeps the failed attempt visible. After another attempt, they record only the result they can verify through the external service, leaving any remaining uncertainty explicit.

Use the upload rules for the service you are actually using

Calgary’s residential ePermit troubleshooting FAQ says documents must be uploaded under the correct document type and identifies a 10 MB file-size limit. Those are instructions for that City service. They are not PermitLane upload settings and should not be copied into a general rule for every municipality or every submission channel. Check the current official instructions for the particular service before preparing another attempt.

A technical upload check does not establish that a drawing is adequate, that the selected application covers the proposed work or that a permit will be approved. If resolving the error would require changing substantive document content, obtain the appropriate clarification rather than removing material simply to get past a technical message. This article does not interpret building code, decide property-specific applicability or instruct readers how to design the work.

City of Calgary: residential ePermit document troubleshooting

Check the file without losing the evidence

Compare the selected file with the intended version before changing anything. Note its name, date or company version reference and the category you intend to use. Keep the original evidence of the failed attempt connected to the application. If you create a different submission copy, label it clearly so the next colleague can distinguish it from the source document. Avoid a folder full of identically named replacements with no explanation.

Share only the information needed to investigate the problem with an authorised recipient. A screenshot can contain addresses, account details or unrelated projects, so check its contents before sharing it. Never send passwords or sign-in codes to let somebody retry on your behalf. If the issue cannot be resolved from current guidance, prepare a concise question for the appropriate support channel and preserve the actual response without assuming it confirms unrelated matters.

A six-step company upload-retry check

Use these suggested coordination steps around an external upload problem. Follow that service’s current instructions separately.

1. Identify the attempt. Record the application reference, action, time and observed message without calling an attempt a submission.
2. Name the file. Match the selected document to the intended company version and category before another attempt.
3. Check the current rules. Use the relevant official service guidance and keep technical limits separate from content adequacy.
4. Protect the context. Preserve the failed or unconfirmed observation and share only authorised troubleshooting material.
5. Assign the next action. Name who will check, retry or ask for help, with a clearly labelled company follow-up date.
6. Verify the later outcome. Record what the external service actually confirms and retain any unanswered question.

Keep document work and authority decisions 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 is not a municipal decision, professional advice or a guarantee of approval. Municipal submission and review remain external. A useful company record preserves the problem, the next action and the evidence of what happened afterward.