Arborist reports for development permits

Whether you’ve been told you need an arborist report or you’re wondering if your project will, this page explains what’s required, what the report contains, and what separates a report that gets approved from one that comes back with questions.

When is an arborist report required?

Arborist reports are triggered at several stages of development and permitting. The exact requirement depends on your municipality, your project type and the trees on or near the site. The most common triggers:

Development applications

Site plan approval, minor variance, consent and rezoning applications that affect trees on the property or next door will usually need a report in the application package. Urban forestry staff at most municipalities are consulted during site plan review.

Building permits near protected trees

In most municipalities, construction that may injure a protected tree needs a permit, and that permit needs an arborist report. What counts as protected varies. Toronto protects private trees 30 cm in diameter and larger. Burlington protects trees from 20 cm. Oakville and Mississauga protect trees from 15 cm. In Hamilton it depends on where the property is. The threshold matters, because trees just outside your building footprint can fall inside regulated protection zones.

Tree removal permits

Removing a tree above your municipality’s size threshold needs a permit, and the application needs a report documenting the tree’s condition and justifying the removal.

Committee of Adjustment and appeal hearings

If your application goes to the Committee of Adjustment or the Toronto Local Appeal Body, arborist evidence becomes part of the record. Decision-makers give tree preservation real weight when they evaluate minor variances and consents.

Infill and intensification

Laneway suites, garden suites, additions and lot severances on urban lots almost always encounter trees. A typical 7.5 to 15 metre Toronto lot may have several protected trees on or next to it, and all of them need assessment before construction starts.

When in doubt, assume you need one. A report costs very little next to a stop-work order or a forced redesign.

What’s in a compliant arborist report?

A report for a development application isn’t an opinion letter. It’s a technical document prepared to municipal requirements, ISA standards and the specific conditions of your project. A complete report includes:

  • Tree inventory and survey. Every tree on the property, and every neighbouring tree within the zone of influence, is identified, measured and assessed: species, diameter at breast height (DBH), condition and structure. In Toronto and Mississauga, that means trees within 6 metres of the property line.
  • Construction impact assessment. How the proposed work affects each tree: tree protection zones (TPZs), where construction conflicts with them, and root impacts from grading, excavation and underground services.
  • Preservation and removal recommendations. Each tree gets a recommendation: retain with protection, retain with mitigation, or remove. Removals are justified by condition, structural defects or an unavoidable conflict with approved development.
  • Tree protection plan. Hoarding locations and specifications, staging areas and mitigation measures, usually alongside or inside the report. In Toronto it’s part of most applications. See tree protection plans.
  • Mitigation specifications. When work has to happen inside a TPZ: root pruning method, grade change techniques, soil aeration, timing and supervision.
  • Replacement and compensation. Most municipalities require replanting when removal is approved, calculated from the removed tree and the municipality’s compensation ratios.

The report has to come from a qualified arborist, and each municipality defines that in its own terms. ISA certification is the usual baseline. For complex sites, or reports likely to face scrutiny at committee, a BCMA brings a higher standard of documentation.

What makes a report hold up to municipal review?

Urban forestry staff read reports critically. They look for gaps, inconsistencies and boilerplate applied to site-specific situations. Imprecise protection language generates comments and revision requests, and in a development timeline those cost weeks. Reports that get through review share a few traits:

  • They’re site-specific. Every tree is assessed and addressed individually. “Trees will be protected” doesn’t satisfy staff who need to see exactly how each tree will be protected.
  • They’re written by someone with credentials and field experience. The BCMA reflects a depth of knowledge that shows up in report quality. Just as important, recommendations have to be achievable during construction. A consultant who has designed and installed protection writes a different report from one who never has.
  • They meet the municipality’s own requirements. Toronto, Hamilton, Oakville, Mississauga and Burlington each expect different content. A report written for one city and submitted to another without adjustment is a common source of delay.
  • They anticipate staff concerns. Dealing with likely questions up front, instead of waiting for a comment letter, shortens the review.

Common mistakes that delay approvals

  • Submitting before the arborist has seen the drawings. The arborist needs the grading plan, servicing and building footprint to assess impacts. Reports prepared without them often come back once the drawings are submitted.
  • Missing neighbouring trees. Trees next door within the zone of influence must be assessed, and missing them is a common reason for incomplete application notices.
  • Vague protection specifications. “Tree protection fencing will be installed” isn’t enough. Staff need to see exactly where the hoarding goes.
  • The wrong credentials. Some municipalities set minimum credentials. Submit a report from someone who doesn’t meet them and expect it back before anyone reviews the trees.
  • Bringing the arborist in late. Trees that could have stayed with a small design change become removals because the design never accounted for them. Involve an arborist at concept stage, before drawings are final.

How the process works

  1. A short conversation

    We cover the project type, municipality, stage of approval and what you know about the trees. It’s free and usually takes about 20 minutes.

  2. Site assessment

    I survey and assess every tree in the zone of influence, review the design drawings, find the conflicts and work out the options. For most urban infill projects that’s half a day to a full day on site.

  3. Report delivered

    The report is checked against the municipality’s submission requirements and delivered, typically five to seven business days after the site visit.

  4. Support through review

    If urban forestry staff send comments, I respond directly. Tree protection plans, pre-construction pruning and construction monitoring fit into the same engagement.

Common questions

How long does an arborist report take?

For most residential and infill projects, five to seven business days from the site visit. Larger sites take longer. Urgent timelines can often be accommodated, so tell me at the start.

How much does an arborist report cost?

It depends on the number of trees, the municipality and how complex the site is. I give a fixed quote after a short conversation about your project, so you know the cost before any work starts.

Do trees on my neighbour’s property need to be in the report?

Yes, if they are within the zone of influence of your proposed work. Missing neighbouring trees is one of the most common reasons applications come back incomplete.

Need a report for your project?

Send me the address, the municipality and where you are in the approval process. I will tell you what the report needs to cover and how quickly I can deliver it.

CallText a photo