A clear planning report built around the real proposal
“Tree report” can mean different things depending on the project stage. It may refer to the survey information itself, a written planning report, an impact assessment or construction-stage documents. We start with the wording you have received and the live plans.
A council request for a “tree report” can be frustratingly broad. The sensible first step is to look at the exact wording and the drawings that are being submitted. That tells us far more than the report label on its own.
The written report should explain the tree resource, the planning relevance and the next action clearly. On a small domestic scheme that may be concise. On a larger or more constrained development it may need to draw together survey data, impacts, mitigation and supporting plans in much greater detail.
The important thing is that the document answers the project question. A planning officer should not have to guess which drawing is being assessed, which trees are retained or how a stated mitigation measure relates to the actual proposal.
What you receive
The exact output depends on the site and project stage, but the work should always be clear, coordinated and usable by the people making the next decision.
- Clear description of the site and development context
- Tree survey findings and retention categories
- Explanation of Root Protection Areas and crown constraints
- Recommendations on retention, removal and mitigation
- Cross-reference to relevant plans and drawings
- A route into AIA, TCP, AMS, TPP or supervision where required
The finished information should be easy for the client and design team to understand, technically defensible for the Local Planning Authority and practical enough to carry forward into the next project stage.
Delivered by Arbor Cultural: read the main BS5837 Tree Report service information →

