TORONTO PERMIT APPLICATION CHECKLIST
A Toronto permit application checklist helps you catch mismatched drawings, missing signatures and unreadable files before submitting an already prepared package. Elmid Design Inc. provides engineering design and permit support for Toronto projects, including coordination of the documents within the agreed scope. Use this guide for a practical final check, while the City determines completeness and compliance.
[toc]
Quick links: Scope · Versions · Signatures · PDF quality · Pre-Check · Final checklist
Key Takeaways
- Check that every document describes the same property, project scope and design version.
- Confirm the applicable requirements first, then check the prepared package against them.
- Ask each responsible designer to resolve technical conflicts and confirm their issued documents.
- Open the actual submission PDFs to check signatures, page order, dimensions and legibility.
- Treat Toronto’s optional AI Pre-Check as advisory feedback, not a permit or formal submission.
- Keep a dated copy of exactly what was submitted and the City’s acknowledgement.
What This Toronto Permit Application Checklist Checks
This checklist starts when your team has identified the project requirements and prepared the application documents. Its purpose is to test whether those documents work together. A complete folder can still contain an old site plan, an unsigned form or two different layouts for the same floor.
First establish what belongs in the package using the City’s building permit application guide for your project type. The relevant guide is the starting point for required drawings, forms and supporting material. Additional requirements can depend on the property and proposed work.
Then perform the quality check described here. Keep a simple record of each concern, who will resolve it and the evidence needed to close it. “Someone is checking” is less useful than identifying the responsible designer and the exact sheet or form involved.
The checks below are practical coordination advice, not a City-issued certification or a substitute for professional review. An owner can identify inconsistent information without taking responsibility for engineering calculations. The professional responsible for that design must resolve the technical question.
Toronto Permit Application Checklist: Confirm the Project Scope
Write a short description of the work you intend to submit. Be specific enough that someone who has never seen the property can distinguish the proposal from a different project. Include the affected building area, the proposed use and major changes shown in the drawings.
For an interior renovation, “renovate house” may hide the important distinction between replacing finishes and changing the structure. For an addition, the description should agree with the footprint, storeys and use represented in the design. Have the design team confirm the wording where those distinctions affect the application.
Permit package checklist: compare shared project facts
Read the application description beside the drawing cover sheet, site plan and relevant technical reports. Check the address, unit identifiers and description of existing and proposed work. Where areas or unit counts appear in several places, identify differences for the team to resolve.
Do not assume every different number is an error. Drawings can legitimately report different types of area or measurements from different reference points. Ask what each value means before replacing it. A useful correction clarifies the basis of the measurement as well as the number.
Keep proposed later work separate from the current application. If you are undecided about a larger window or another bathroom, tell the designer before the package is issued. A pencilled preference should not quietly become part of a submitted plan.
Mark what is known and what needs checking
Existing-building information can come from measured conditions, previous drawings or owner recollection. Those sources are not interchangeable. Identify information that has not been confirmed, especially where it affects the proposed design.
For example, a floor plan may show a wall accurately while revealing nothing about the framing above it. A neat drawing does not prove that concealed construction has been verified. Ask the responsible professional what investigation is needed before relying on that condition.
Permit Submission Checklist for Document Versions
Start this part of your permit submission checklist with one submission folder and appoint one person to assemble it. This can be the owner, an authorized agent or a member of the design team, depending on the agreed responsibilities. The important point is that everyone knows which package is being checked.
Collect issued files directly from the responsible authors. Ask whether each file is the intended submission version, rather than selecting the attachment with the newest download date. File-copy dates can change when a document is moved between computers.
For your Toronto permit application checklist, prepare a short document register showing the filename, document title, issue date, revision identifier where used, and author. For a drawing set, record the sheet numbers it contains. This is a coordination aid for your team; it is not presented as an additional universal municipal form.
Record the evidence that closes a question
Give each open item a short, factual description. Identify the document, page or sheet where it appears, the person responsible for the answer and the next action. Keep the record focused on the problem; it does not need to become a long account of every discussion.
When an answer arrives, check what changed. A message saying “updated” is less useful than a replacement file and a clear reference to the corrected information. Note the issue date and confirm that the replacement reached the submission folder. If other documents depend on that change, ask their authors whether an update is also needed.
Separate confirmed corrections from owner decisions that are still pending. For example, an unreadable note can be sent back for a clean export. Choosing between two different layouts requires a decision before the designer can complete the coordinated issue. Treating both as minor file problems can hide the real reason the package remains unfinished.
Keep superseded files out of the submission folder
Retain earlier versions in a separate archive with a clear label. Do not delete the project history merely to make the current folder look tidy. An older issue can help explain a decision, but it should not be accidentally submitted alongside its replacement.
Watch for combined PDFs assembled from mixed issues. The first page may carry the current date while a structural or mechanical sheet inside still shows an earlier arrangement. Open the combined set and compare its contents with the register, page by page.
After any late correction, repeat the affected checks. Replacing one sheet may change page order, references or other documents. A package that passed yesterday’s check does not automatically pass after a new design decision today.
Present in the folder
A document exists, opens and appears relevant. This is a useful first check, but it does not establish that the document is current or consistent with the proposal.
Ready for submission review
The author has confirmed the issue, the package uses the same coordinated design, and identified gaps have an appropriate resolution. The City still decides whether the application meets its requirements.
Toronto Permit Checklist for Signatures and Responsibility
Use the City’s current Toronto Building forms index when checking forms. A form saved from an older project may have a familiar title but no longer reflect the current questions or applicable declarations.
Use your Toronto permit application checklist to review the completed forms as finished documents. Check that names, contact information and project details are consistent. Confirm that required signature and date fields have been completed by the appropriate people. Do not infer authority to sign from someone being the main contact for the project.
The City’s review-stream guidance includes an application signed by the property owner or authorized agent among the conditions for a complete application. Clarify who is acting as agent and who receives correspondence before submitting.
Check engineering responsibility without altering the design
Where engineering documents are included, ask the engineer to confirm the final issued files and the extent of their responsibility. Do not copy a seal or signature onto another document, edit an issued engineering drawing yourself, or assume one professional has reviewed another discipline’s work.
Toronto’s Reliance on Professional Engineer’s Seal guidance states that, for projects within the program’s stated house and accessory-structure scope, permit drawings or documents bearing an engineer’s seal require an Assumption of Responsibility for Engineering Content form. Its expedited-review program has eligibility and scope limits. A seal does not create a blanket promise of faster approval.
For the final check, have the responsible professional confirm that the relevant form, identified documents and submitted issue agree. The owner’s role is to flag an apparent mismatch. The engineer’s role is to determine and document the engineering responsibility.
PEO Certificate of Authorization
Elmid Design Inc. holds a Certificate of Authorization from Professional Engineers Ontario (PEO). This supports the firm’s provision of professional engineering services to the public. Read PEO’s Certificate of Authorization information for the distinction between a firm’s authorization and an individual engineer’s licence.
The engineering scope and responsible professionals should be clear for the project. A Certificate of Authorization does not guarantee permit issuance or represent PEO endorsement of a proposed design.
Permit Package Checklist for Drawing Coordination
A useful permit package checklist tests the drawings as one proposal, rather than reading each discipline in isolation. Start with a small number of locations where designs meet: the edge of an addition, a new stair opening, a structural support or an exterior doorway. Ask whether each relevant sheet describes the same arrangement.
This review is about finding questions for the design team. It does not ask owners to assess structural adequacy, select equipment or determine Code compliance. A drawing conflict needs an answer from the professionals responsible for the affected work.
Follow a change through every affected drawing
A moved wall can affect the floor plan, framing, services and room dimensions. A changed exterior door can affect the elevation, landing and relationship to outside grades. Ask the coordinator to identify which documents should change together.
Compare references as well as graphics. If a plan directs the reader to a detail, confirm that the detail exists and uses the same label. Check that notes describing existing, removed and new work remain distinguishable in the final PDF.
Where two sheets disagree, record both references in your issue list. “A2 and S1 show different opening locations” is a more useful question than “the drawings look wrong.” Avoid resolving the difference by choosing whichever sheet looks newer or easier to build.
Match the building design to the site information
Where site, grading or drainage documents form part of the package, compare the building location and key elevations with the architectural drawings. Ask the designers to review differences in entrance levels, foundation references or the footprint used for their work.
Make the reference point explicit. An elevation based on a local project datum cannot simply be compared with a geodetic elevation as though they share the same basis. The relevant designer or survey professional should explain and reconcile the information.
Permit package checklist: confirm the Code basis
Toronto administers the provincial Ontario Building Code; there is no separate technical “Toronto Building Code” replacing it. Ask the designers to confirm the applicable edition and amendments for the application. The Ontario Building Code regulation is the governing reference, supported by the provincial Code documents.
For a current application, do not reuse old notes simply because a similar project was previously approved. Existing permits, older designs and changed scopes can require project-specific interpretation. A readiness check should flag the question rather than invent an answer.
Toronto Permit Application Checklist: Match the Approval Evidence
An approval-related document is useful only if it relates to the work now proposed. Compare the property, description and referenced plans with the current package. If the design changed after an earlier review, ask whether that change affects the evidence you intend to rely on.
Toronto describes the Zoning Applicable Law Certificate as a preliminary review supporting a complete building permit application. The City requires a Declaration Form for its use. Check the certificate, declaration and relevant supporting information together rather than treating the certificate’s presence as the whole test.
The City’s review-stream criteria also identify satisfied applicable law and paid fees, alongside the required application and plans. Its published review periods apply to complete applications; they are not an unconditional date for receiving a permit. Ask Toronto Building about the route and completeness status that apply to your submission.
Keep conditions and open questions visible
If correspondence identifies a condition, note the evidence needed to address it and who is responsible. A statement that someone has “contacted the authority” does not demonstrate that the necessary outcome has been obtained.
Keep different approvals in their own categories. Planning, heritage, tree, conservation-authority and other requirements can apply depending on the property and work. The project team should identify their relevance; this preflight guide does not declare every approval necessary for every site.
When a decision is pending, avoid marking the application fully ready on your internal checklist. Record the outstanding item plainly and ask the City how it affects submission or review. A transparent unresolved item is easier to manage than an unsupported assumption.
Toronto Permit Application Checklist for PDF Quality
Toronto’s Electronic Submission Guidelines require PDF documents that are unsecured and not password protected. They also address flattened layers, comments, page sizes, drawing scale and document grouping. Check the current guidance for the exact files and submission route involved.
Key published requirements include black-and-white drawings and specifications, with colour images used only as supplements; a maximum ARCH E page size; and properly labelled filenames. HVAC and plumbing drawings are submitted as separate electronic documents for their respective applications. Structural drawings belong in the building-permit set as described by the City.
Permit submission checklist: inspect the exported PDF
Open the PDF that will actually be submitted. Look at every page in sequence, including blank-looking pages near the end. Check for cropped titles, missing detail edges, substituted symbols and faint lines. Confirm that page rotation makes the text readable without repeatedly turning the screen.
Zoom in on dimensions and small notes. Then view the full page to see whether the reader can follow the drawing’s hierarchy. A document can look attractive at a reduced size while critical measurements are unreadable at a practical viewing scale.
Have the document author verify page size and scale after export. The scale statement must describe the issued sheet correctly. Merely typing “do not scale” does not fix an incorrectly exported drawing or replace the required dimensions.
Flatten deliberately and recheck signatures
PDF processing can change what appears on the page. After the author flattens layers or resolves comments, reopen the final output and check that the intended notes, signatures and seals remain visible and correct.
Do not strip security or alter signed engineering documents on your own to make them pass a file check. Ask the issuer for a suitable submission copy. Keep any required author verification separate from your administrative file-opening test.
Where scanning is unavoidable, inspect the weakest page rather than judging the whole set by its clearest sheet. The City provides scanning requirements in its electronic guidance. Request a better source file when necessary; repeatedly enlarging a poor scan does not recover lost information.
PROJECT SUPPORT
Not sure which service you need?
Elmid Design Inc. provides engineering consulting and design for building and land development projects. We can discuss the engineering support your proposal needs and the information required to define that scope.
Explore building permit design and site grading design where site levels and drainage require coordination with the building proposal.
Permit Submission Checklist for Filenames and Records
Include descriptive filenames in your Toronto permit application checklist so each document and issue can be identified clearly. Follow any naming instructions in the applicable City submission route. Avoid ambiguous labels such as “final-final” or several attachments that all look like the latest drawing set.
Your internal register should point to the files being submitted, not merely to a folder containing multiple alternatives. If a combined PDF contains several sheets, check its page order against the drawing list. Resolve duplicate sheet numbers and missing references with the author.
Before sending, confirm the current submission route through Toronto’s official Before You Apply page. Initial applications, document resubmissions and different project services may use different instructions. An old email thread is not enough to establish today’s route.
Identify who will complete submission, monitor acknowledgements and handle payment instructions. Verify the applicable charges against the City’s current building permit fee schedule. Engineering fees are separate from municipal fees; this checklist does not estimate either from the file count.
After submission, retain an unchanged copy of the issued package with the submission date and acknowledgement. Keep later working changes elsewhere. This gives the team a clear answer to the practical question: “Which documents did the City receive?”
Where Toronto’s Optional AI Pre-Check Fits
The City offers a voluntary Building Permit Application Pre-Check for eligible residential applications. It can flag missing or inconsistent information and selected issues within the pilot’s scope. Eligibility includes specified residential projects, with further limits on the zoning and technical checks available.
The tool is hosted on the third-party CivCheck website. Review the City’s current eligibility, terms and privacy information before creating an account or uploading documents. Use the official City page to reach the service.
Treat the findings as questions to assess with the responsible designer. The pre-check does not approve the project, replace staff review, guarantee timing or formally submit the application. The City explains the separate submission step and the use of a pre-check ID and report.
If you use the tool, keep track of which document issue it assessed. A report on an earlier design should not be mistaken for feedback on a revised package. Apply the same version discipline to automated feedback that you apply to professional correspondence.
How Elmid Design Inc. Can Help Coordinate Your Toronto Permit Application Package
Elmid Design Inc. prepares building permit design drawings and provides engineering coordination for Toronto application packages. The agreed assignment can include scope-specific plans and details, coordination with related engineering documents, and technical responses concerning that work.
Share the proposed scope, available drawings and any City comments so Elmid Design Inc. can identify the engineering deliverables and remaining inputs. Confirm who prepares each document and who assembles the submission before using the checklist to check the final package.
Typical Permit Package Scenarios
The following typical scenarios illustrate how to turn a coordination concern into a specific check before submission.
An addition moves after the site plan is issued
The architectural plan shows a revised rear wall position, while the site plan still uses the earlier footprint. Both files open correctly and carry professional-looking title blocks.
Pause the package. Ask the relevant designers to confirm the intended footprint and review every affected document, including any zoning or grading information. Resume the check with a coordinated issue rather than selecting one drawing as the winner.
A PDF export loses important notes
A source drawing contains clear annotations, but the exported PDF shows faint text and omits several notes that were stored as comments. The owner notices the issue while checking the actual submission file.
Return the file to its author for a corrected export. Reopen the replacement and check the affected details, page order and visible signatures. A successful file upload would not prove that the lost information had been restored.
Two versions describe different interior layouts
The main drawing set shows a moved kitchen, while a related service drawing still uses the previous arrangement. The filenames give no clear indication of which issue belongs in the application.
Ask the team to confirm the current layout and coordinate the affected design. Update the document register and replace superseded submission files. Do not manually move equipment symbols on someone else’s issued drawing.
Toronto addition project references
Elmid Design Inc.’s public project portfolio lists 58 Karnwood Drive, 24 Deepglade Crescent and 46 Gordon Street in Toronto as building-permit projects for additions to existing houses. These references show a project category where package coordination matters. For an addition, use the checklist to compare existing-building information with the proposed footprint, drawings and related supporting documents.
Your Final Toronto Permit Application Checklist: Go or Pause?
Use a final review meeting or short documented handoff to close the package. The owner should understand the proposal being submitted, while each designer confirms the documents for which they are responsible. Record unresolved items instead of treating silence as agreement.
Proceed with submission when these checks are resolved
- The scope and property information agree across the prepared package.
- The applicable document requirements have been checked, with no unexplained omissions.
- Responsible authors have confirmed the submitted issues and resolved identified design conflicts.
- Necessary signatures, declarations and supporting approval evidence are in place for the chosen route.
- Final PDFs are legible, correctly assembled and checked against current City file requirements.
- The applicant, submission method, fee arrangements and record-keeping responsibilities are clear.
This is an internal readiness decision. It does not certify municipal completeness, Code compliance or permit approval.
Pause when an important design decision remains open, approval evidence relates to a different proposal, a necessary signature is missing, or technical information is unresolved. Assign the next action and repeat the relevant check once the revised evidence arrives.
If the City later requests corrections, move to a controlled response process. Keep the submitted baseline, identify the comment and coordinate the necessary changes. Detailed examiner responses and changes to issued permits are covered separately.
Frequently Asked Questions
Does a Toronto permit application checklist guarantee acceptance?
No. A checklist helps organize the package and identify avoidable problems. The City determines completeness and reviews the proposal against applicable requirements. Professional review remains necessary for the design matters involved. Keep the distinction clear when planning a construction start or discussing an expected review date.
Is a missing document the same as a coordination problem?
They are different checks. A missing-document check asks whether required information is present. Coordination asks whether the documents describe the same proposal. A package can contain every expected file and still show conflicting dimensions, layouts or design issues. Both checks matter before submission.
Can the owner do the final permit package check?
The owner can use a permit package checklist to review scope, contact information, filenames, obvious inconsistencies and whether documents open properly. Technical compliance, design changes and professional responsibility belong with the appropriate qualified professionals. Agree on who assembles the package and who confirms each part so that an administrative check is not mistaken for engineering review.
Should I submit an old approval with new drawings?
First ask whether the approval still applies to the revised proposal. Compare the referenced plans, scope and conditions. Keep the difference visible and obtain guidance from the appropriate designer or authority. Including an older approval does not establish that a changed design satisfies the same requirements.
Does passing the AI Pre-Check mean my permit was submitted?
No. The City explicitly separates its advisory pre-check from formal application submission. Follow the current City instructions for the subsequent submission step and retain the acknowledgement. An automated result should also be associated with the document version it actually assessed.
How can Elmid Design Inc. help prepare a coordinated package?
Elmid Design Inc. provides professional engineering design and permit support for Toronto projects. The agreed scope can include engineering drawings, coordination of related information and technical responses concerning that work. Share your proposed scope and available documents so the team can identify the engineering services and remaining information needed.
Geographic Locations That We Service:
Our Licensed Professional Engineers provide building permit design and related engineering support for Ontario projects. Related services include site grading plans, drainage design and erosion and sediment control plans, where required by the project.
We provide engineering services across a wide range of municipalities, each with its own requirements and review processes.
Toronto and Surrounding Areas
We provide engineering services in Toronto and provide grading engineering resources through our Toronto grading plan page.
Our service area also includes Oshawa, Pickering with our Pickering grading plan resources, and Clarington.
We also provide engineering services in Ajax through our Ajax grading plan resources, Whitby, Brock, Scugog, and Uxbridge, including our Uxbridge grading plan resources.
Halton Region
Within Halton Region, we provide engineering services in Burlington, including projects requiring Burlington grading plans.
We also provide engineering services in Halton Hills, supported by our Halton Hills grading plan resources.
Our service area also includes Milton and Oakville, including our Oakville grading plan resources.
Peel Region
Within Peel Region, we provide engineering services in Brampton, including projects requiring Brampton grading plans.
We also provide engineering services in Mississauga through our Mississauga grading plan resources and Caledon through our Caledon grading plan resources.
York Region
Within York Region, we provide engineering services in Vaughan and provide information about Vaughan grading plans.
We also provide engineering services in Aurora through our Aurora grading plan resources and East Gwillimbury through our East Gwillimbury grading plan resources.
Additional service areas include Georgina with our Georgina grading plan resources, Markham with our Markham grading plan resources, and Newmarket with our Newmarket grading plan resources.
We also provide engineering services in Richmond Hill with our Richmond Hill grading plan resources, Whitchurch-Stouffville through our Whitchurch-Stouffville grading plan resources, and King through our King grading plan resources.
Our service area also includes Bradford West Gwillimbury.
Other Southern Ontario Cities and Towns
We provide engineering services in many additional Southern Ontario communities, including Hamilton, St. Catharines, Niagara-on-the-Lake, Brant, Cambridge, Kitchener, Waterloo, and Woodstock.
We also provide engineering services in Guelph, Centre Wellington, Shelburne, Orangeville, New Tecumseth, Essa, Collingwood, Wasaga Beach, and Barrie, including our Barrie grading plan resources.
Additional service areas include Midland, Orillia with our Orillia grading plan resources, Ramara, Minden Hills, North Kawartha, Kawartha Lakes, Peterborough, Selwyn, and Brighton.
