Drawing identification
Before a drawing reaches the site, check which permit record it belongs to
A file called “latest” does not explain its relationship to the permit record. Preserve the drawing’s identity, source and unresolved differences before the handoff.
General workflow guidance
A drawing can lose important context between the office and the site. Someone downloads a file, another colleague renames it and a printed copy arrives with only the project nickname on its cover. The sheet may be perfectly readable while its connection to the permit record is unclear. Before handing it to another person, identify which document it is and where it came from. The purpose is a traceable handoff, not a promise that a filename, company stamp or printing date makes the document suitable for the proposed work.
Treat “latest” as a label that needs an explanation
Start with the project and the particular application or permit reference. Identify the drawing title, any revision information actually shown and the source from which the company obtained it. Keep the date of retrieval separate from a date printed on the drawing. Downloading an older document today does not change the document’s revision, and a later company filename does not establish a later external review.
If the company cannot connect the sheet to the relevant record, leave that connection unconfirmed. If two copies differ, preserve both and identify the difference for clarification. Do not choose one merely because its name sorts first in a folder. This check concerns document identity and context. It does not decide which design is adequate, what work a property requires or whether a crew may proceed.
Hypothetical example: two copies carry the same project nickname
Imagine a fictional renovation on Spruce Walk. Kai is preparing a drawing package for a company site handoff. The folder contains a downloaded plan set and a separately named working copy. Both filenames include the project nickname, but the handoff message does not identify a permit reference or explain the working copy’s changes. Jules, receiving the package, asks which record the printed sheets belong to. This is a hypothetical coordination example, not a customer account or a report of an actual construction error.
Kai keeps the two copies separate and records their visible identifiers and sources. The company does not relabel either copy as approved merely to complete the handoff. Kai takes responsibility for locating the relevant external record and asking the appropriate person about the discrepancy. Friday’s company check-in is a follow-up target, not a municipal deadline. Jules receives an honest explanation of what is known and what still needs clarification rather than an unsupported instruction to use one set.
Keep the external document source visible
Edmonton’s page about changes to existing buildings says the permit holder can find reviewed plans and permit documents through SelfServe. That is a specific description of access in Edmonton’s process. It does not establish the status of a different file in a company folder or show that a locally edited copy matches the reviewed record. Check the current official instructions and the particular external document being discussed.
This article does not determine which drawings are required on a site, interpret a review mark or decide that a document covers a proposed change. Seek the appropriate authority or professional clarification where that question matters. Keep the answer connected to the exact document and question it addresses. A response about one sheet should not silently become an answer about an entire project or a later revision.
City of Edmonton: reviewed plans and permit documents in SelfServe
Carry the identity into the handoff
Prepare a short index that connects the supplied document to its title, visible revision information, permit reference and source location. Note who assembled the package and when. If a printed copy is involved, make it possible for the recipient to identify the corresponding file without relying on a personal memory of the folder. Avoid obscuring existing identifiers while adding the company’s own administrative context.
Share only the relevant documents with an authorised recipient. Keep working material, unrelated private files and portal credentials outside a broad forwarding chain. If later information changes the company’s understanding of a copy, update the affected colleagues and preserve the earlier handoff note. These are company document-handling suggestions, not a legal retention schedule, a technical drawing-control standard or a claim that PermitLane validates construction drawings.
A six-step company drawing-handoff check
Use these suggested checks to make a document handoff understandable. Confirm technical and authority questions through the appropriate channels separately.
- Match the record. Identify the project and the particular application or permit reference associated with the document.
- Read the identifiers. Record the actual title and revision information; keep the retrieval date distinct from document dates.
- Preserve the source. Explain where the copy came from and avoid treating a company filename as evidence of external review.
- Expose differences. Keep conflicting copies identifiable and name who will obtain the necessary clarification.
- Check the recipient. Provide the relevant authorised material and an index that connects printed sheets to their files.
- Record later clarification. Add the dated answer within its scope and update the people relying on the earlier handoff.
Keep document context connected to permit work
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. Clear document context helps a company explain its evidence without presenting a local file label as an authority decision.
Official sources
Source checked November 5, 2026. The Edmonton example concerns finding reviewed plans and permit documents through SelfServe. The drawing-handoff checklist is suggested company practice, not a determination of technical adequacy or permission to build.