Use this guide to develop the reasoning behind tree risk assessment when preparing for the ISA Tree Risk Assessment Qualification (TRAQ). Each concept explains a practical distinction, illustrates it with an original example and identifies a mistake to avoid. Work through the foundations before applying them to inspection findings and management decisions.
Foundations of tree risk reasoning
1. Distinguish a hazard from risk
A hazard is a potential source of harm, such as a branch capable of breaking. Risk considers whether failure could occur, whether something could be struck and what harm could follow. A structural defect therefore starts an investigation; its presence alone does not establish the risk associated with every surrounding target.
Worked example: A dead limb over an occupied bench creates a different risk situation from the same limb over an inaccessible area with no identified target.
Mistake to avoid: Assigning risk solely from the appearance of a defect.
Context reference: Welcome
2. Separate the components of a failure event
Analyze failure, impact and consequences separately before combining them. Failure concerns the tree or part breaking or overturning. Impact concerns that failed material reaching a target. Consequences concern the resulting harm. Keeping these components distinct prevents frequent occupancy from being mistaken for evidence that the tree itself is more likely to fail.
Worked example: A crowded walkway increases potential exposure to a falling branch, but crowding does not weaken the branch attachment.
Mistake to avoid: Using a busy target to justify a higher likelihood of structural failure.
Context reference: Welcome
3. Define the assessment period
A likelihood judgment needs a stated period because opportunities for failure and exposure accumulate over time. The assessment period also determines which foreseeable changes matter. It is a boundary for the assessment, not a promise that the tree will remain unchanged or safe until that period ends.
Worked example: For an assessment covering the coming year, planned excavation during that year is relevant even if the tree currently shows no excavation damage.
Mistake to avoid: Reporting likelihood without explaining the period to which it applies.
Context reference: Welcome
4. Identify the tree part being assessed
Whole-tree overturning, trunk fracture and branch failure have different mechanisms and impact areas. Identify the specific part before interpreting defects or selecting mitigation. One tree may need several separate failure scenarios, because a sound trunk does not eliminate a hazardous branch and a healthy crown does not establish root stability.
Worked example: A tree has a cracked lateral branch and an apparently stable root plate. Assess branch failure separately from whole-tree failure.
Mistake to avoid: Giving one undifferentiated judgment that conceals which part could fail.
Context reference: Welcome
5. Compare loading with structural capacity
Failure becomes possible when loading exceeds the capacity of the relevant structure. Loading includes forces from wind, gravity and other site-specific influences; capacity depends on wood, geometry, attachments and roots. A defect can reduce capacity, while an environmental change can increase loading without creating a new visible defect.
Worked example: Removing neighboring trees exposes a retained tree to greater wind loading even though its trunk appearance is unchanged.
Mistake to avoid: Treating visible condition as the only influence on failure.
Context reference: Welcome
6. Build a specific failure scenario
A useful scenario links a part, a plausible failure mechanism, relevant loading conditions and an exposed target. This makes the assessment testable and the recommendation understandable. Describe foreseeable conditions rather than combining every imaginable event into an extreme scenario that provides little help with ordinary management decisions.
Worked example: A long branch with a damaged attachment could break under wind loading and reach the parking spaces beneath its outer crown.
Mistake to avoid: Describing danger without identifying how the tree part could reach a target.
Context reference: Welcome
7. Separate uncertainty from estimated risk
Uncertainty describes limits in knowledge; risk describes the potential harmful event. Poor visibility or missing history can lower confidence without automatically proving either high or low risk. Explain the uncertainty, its importance and whether additional information could change the decision. Avoid hiding uncertainty behind a precise-looking category or number.
Worked example: Dense groundcover prevents inspection of the root collar. Record the limitation and consider further access if root condition would affect the recommendation.
Mistake to avoid: Treating an unobserved defect as evidence that no defect exists.
Context reference: Welcome
Targets, occupancy and site conditions
8. Identify targets and their vulnerability
Targets include people, property and activities or infrastructure that could be harmed or disrupted. Identify actual targets within plausible impact areas and distinguish their vulnerability. A person, lightweight shelter and robust boundary wall can have different consequences from the same falling material, even when their distances from the tree are similar.
Worked example: A branch extends over both a picnic table and a stone wall. Record the people using the table separately from the wall.
Mistake to avoid: Listing nearby objects without considering whether failure could harm them.
Context reference: Welcome
9. Estimate occupancy over relevant times
Occupancy concerns how often a target is present in the potential impact area. Consider daily, weekly and seasonal patterns rather than relying on one site visit. An empty location during inspection may be heavily used at other times. Simple occupancy calculations can describe exposure, but they are not complete calculations of tree risk.
Worked example: A supervised area is occupied for 3 hours in a 12-hour operating day: 3 ÷ 12 equals 25% of operating time.
Mistake to avoid: Interpreting 25% occupancy as a 25% probability of injury.
Context reference: Welcome
10. Distinguish moving and stationary targets
A stationary target remains exposed while present; a moving target passes through an impact area for a limited time. Traffic counts alone do not describe exposure because speed, stopping behavior and route position also matter. Assess queues and waiting areas separately from uninterrupted movement through the same space.
Worked example: Cyclists pass beneath a branch quickly, but pedestrians waiting at the adjacent crossing remain beneath it. The waiting area needs its own exposure description.
Mistake to avoid: Assuming identical exposure for every person counted on a route.
Context reference: Welcome
11. Map plausible impact areas
Impact areas depend on the failing part, its position and possible movement. Consider falling, swinging, sliding or rolling where relevant, while recognizing uncertainty in direction. Tree height or branch length can inform geometry, but a simple circle does not resolve every failure scenario or establish a safe exclusion boundary.
Worked example: A downhill path may be exposed to material rolling after impact, even when it lies beyond the branch's initial landing area.
Mistake to avoid: Treating one distance measurement as a guarantee that a target cannot be struck.
Context reference: Welcome
12. Recognize changes in wind exposure
Buildings, topography and neighboring vegetation can alter wind exposure and turbulence. Changes to these features may change loading on a tree. Existing shelter should not be assumed permanent, and exposure should be assessed alongside structure and adaptation rather than used as a standalone prediction of failure.
Worked example: A tree beside a recently cleared development now faces open terrain. Record the changed exposure when interpreting an existing weak attachment.
Mistake to avoid: Assuming a tree's history under sheltered conditions predicts its response after clearing.
Context reference: Welcome
13. Investigate changes within the rooting area
Excavation, paving, grade changes and compaction can affect roots and their growing environment. Establish where work occurred, its extent and its timing. Crown symptoms may appear after underground damage, so the absence of immediate foliage decline does not settle questions about anchorage or future physiological stress.
Worked example: A trench was excavated beside a mature tree last month. A green crown does not establish that structural roots escaped damage.
Mistake to avoid: Limiting the site assessment to conditions visible above ground.
Context reference: Welcome
14. Interpret soil and drainage conditions
Roots and surrounding soil together resist overturning. Soil moisture, drainage, rooting depth and restrictions can influence this system. Saturated ground can affect anchorage, but wetness alone does not prove instability. Interpret it with root condition, soil movement, tree position and recent environmental conditions.
Worked example: Persistent waterlogging, shallow rooting and fresh ground displacement warrant more concern together than temporary puddles around an otherwise unchanged tree.
Mistake to avoid: Declaring a tree unstable solely because its soil is wet.
Context reference: Welcome
Tree biology and structural response
15. Understand compartmentalization
Trees respond to injury by restricting the spread of dysfunction and decay and by producing new tissues. They do not restore injured wood to its original condition. Successful wound closure can conceal an internal defect, so external closure and internal structural condition must be considered separately.
Worked example: A pruning wound has closed over, but the older wood behind it may still contain decay. Closure alone does not resolve the structural question.
Mistake to avoid: Calling a closed wound proof that the underlying wood has healed completely.
Context reference: Welcome
16. Connect decay with wood properties
Decay organisms alter wood components and can reduce mechanical performance. Strength loss depends on the decay process, its distribution and the structure carrying loads. Visible discoloration is not a direct strength measurement, and apparently modest deterioration can matter when it affects a critical attachment or load path.
Worked example: Decay concentrated at a branch attachment may be more consequential than a similarly sized decayed area in a less heavily loaded location.
Mistake to avoid: Estimating remaining strength from color or cavity size alone.
Context reference: Welcome
17. Separate vitality from structural integrity
Vitality describes biological functioning and growth; structural integrity concerns the ability to withstand loading. They interact but are not interchangeable. A vigorous tree can contain a serious structural defect, while a declining tree may retain substantial mechanical strength. Assess crown condition and structural evidence as separate lines of information.
Worked example: Dense foliage on a tree with a large trunk crack does not cancel the evidence of structural separation.
Mistake to avoid: Using a green crown as a general certificate of stability.
Context reference: Welcome
18. Interpret adaptive growth
Trees can add wood in response to mechanical loading and structural irregularities. Ribs, buttresses and uneven growth may show adaptation, but they may also draw attention to an underlying weakness. Interpret the location and form of growth alongside defects and loading; visible reinforcement does not establish that compensation is sufficient.
Worked example: A pronounced rib beside an old injury suggests a structural response, but the adjacent crack still requires assessment.
Mistake to avoid: Assuming every bulge proves either failure or adequate reinforcement.
Context reference: Welcome
19. Distinguish root functions and distribution
Roots provide anchorage, water and nutrient uptake, transport and storage. Root size alone does not completely define function, and root systems are often uneven because of soil and site constraints. Avoid assuming roots mirror the crown or extend equally in every direction when interpreting construction damage or stability.
Worked example: A tree beside pavement may have asymmetric rooting. Damage on its accessible soil side could therefore affect a disproportionate part of the root system.
Mistake to avoid: Inferring root distribution solely from the crown outline.
Context reference: Welcome
20. Use species characteristics cautiously
Species characteristics can inform expectations about wood properties, branching, decay response and environmental tolerance. They provide context, not a verdict on an individual tree. Condition, dimensions, management history and site exposure may outweigh a broad species tendency. Confirm identification when a species-dependent interpretation materially affects the decision.
Worked example: A species associated with brittle branches still requires inspection of this tree's attachments, defects and targets before a recommendation is made.
Mistake to avoid: Assigning an individual tree's risk from its species name alone.
Context reference: Welcome
21. Interpret crown symptoms in seasonal context
Leaf density, discoloration and shoot growth should be interpreted against season, species and recent conditions. Normal dormancy can resemble decline, while drought symptoms may indicate stress without identifying a structural failure mechanism. Crown symptoms help direct investigation but usually need corroboration before conclusions about roots or stability.
Worked example: Sparse foliage after drought suggests physiological stress. It does not by itself establish that the root plate is structurally unsound.
Mistake to avoid: Treating every sparse crown as evidence of imminent overturning.
Context reference: Welcome
22. Treat organisms as diagnostic clues
Fungal fruiting bodies and other biological signs can indicate conditions needing investigation. Their significance depends on identification, location, host and associated damage. Fruiting bodies do not directly reveal the full extent of decay, and their absence does not establish sound wood. Seek specialist identification when the interpretation depends on it.
Worked example: A fruiting body at the trunk base prompts investigation of basal and root condition; it does not alone define the remaining load-bearing structure.
Mistake to avoid: Making a final risk judgment from a photograph of an unidentified fungus.
Context reference: Welcome
Interpreting structural defects
23. Assess branch attachment geometry
Attachment form influences how forces transfer between a branch and its parent stem. Included bark can interfere with wood connection, but attachment assessment also considers cracks, relative stem sizes, growth and loading. A narrow angle alone is an incomplete diagnostic finding and should not replace inspection of the actual union.
Worked example: Two upright stems have a narrow union with included bark and a visible separation. The separation adds evidence beyond the angle itself.
Mistake to avoid: Equating every upright branch angle with the same likelihood of failure.
Context reference: Welcome
24. Interpret cracks as structural separation
A crack can interrupt the transfer of forces through wood. Its importance depends on location, orientation, extent, movement and the structure affected. Distinguish an open separation from a superficial bark feature, and document uncertainty when depth cannot be established. Fresh changes may be especially important when compared with reliable earlier records.
Worked example: A previously recorded trunk crack is now visibly wider and extends farther. That change warrants renewed assessment of the affected stem.
Mistake to avoid: Judging a crack solely by its visible length.
Context reference: Welcome
25. Differentiate deadwood and suspended material
Attached dead branches and already detached, suspended branches present different failure situations. Attached wood may break as deterioration progresses; suspended material has already lost its original support and may shift or fall. Assess size, support, position and targets. Inspection and response must avoid placing people beneath unstable material.
Worked example: A broken limb lodged above a seating area requires attention to its uncertain support, even if nearby attached dead twigs are much smaller.
Mistake to avoid: Grouping all dead material into one severity judgment.
Context reference: Welcome
26. Evaluate cavities through remaining structure
A cavity's significance depends on the location and continuity of remaining load-bearing wood, openings, cracks and loading. Hollow trees can retain substantial strength, but hollow appearance alone cannot establish adequacy. Simple geometric ratios may omit asymmetry and local weaknesses and should not be treated as universal pass-or-fail rules.
Worked example: Two trunks have similar cavities, but one also has an open crack through its remaining shell. Their structural situations differ.
Mistake to avoid: Using cavity diameter alone to decide retention or removal.
Context reference: Welcome
27. Distinguish established lean from recent movement
A long-established lean may reflect growth and adaptation. Recent changes in lean, root-plate lifting, soil cracking or displacement can indicate a different situation. Establish history where possible and interpret these signs together. A leaning trunk is neither automatically unstable nor automatically safe because it has stood previously.
Worked example: An old photograph shows the same lean, but newly lifted soil appears on one side. The fresh soil movement remains significant.
Mistake to avoid: Dismissing new root-plate signs because the trunk has always leaned.
Context reference: Welcome
28. Interpret structural root damage
Root damage can affect anchorage and biological functioning. Its significance depends on which roots are affected, their position, damage extent and the remaining root-soil system. Distance from the trunk alone is insufficient. Avoid fixed assumptions about an acceptable number or size of severed roots without a defensible individual assessment.
Worked example: Excavation damages several substantial roots on one side of a tree. Assess the resulting asymmetry rather than merely counting the roots.
Mistake to avoid: Declaring root damage harmless because it lies outside an assumed boundary.
Context reference: Welcome
29. Examine interacting defects
Defects can interact when they affect the same load path. Decay may reduce available wood while a crack further disrupts that wood's continuity. Assess their combined geometry and mechanism rather than counting defects or simply adding severity labels. Multiple unrelated observations do not necessarily have the same interaction.
Worked example: A cavity and a crack intersect at a heavily loaded union, creating a more consequential configuration than either finding described in isolation.
Mistake to avoid: Scoring defects independently while overlooking where they connect.
Context reference: Welcome
30. Use previous failures as contextual evidence
Previous branch or stem failures can reveal loading patterns, attachment weaknesses or site exposure. Establish what failed and under what conditions before extrapolating. The remaining tree may differ structurally after failure, and absence of previous failures is not proof of future stability.
Worked example: Several comparable limbs failed during ordinary winds. Investigate whether retained limbs share the same attachment characteristics instead of assuming identical outcomes.
Mistake to avoid: Treating past survival or past failure as a complete prediction.
Context reference: Welcome
Assessment methods and diagnostic limits
31. Understand limited visual assessment
A limited visual assessment screens for specified visible conditions within a restricted viewing or access arrangement. It can help identify trees needing closer assessment, but its conclusions must match what could actually be observed. Clearly state whether observations were made from a route, vehicle or selected viewpoints.
Worked example: A roadside screening identifies a large broken branch. The observation supports follow-up but does not establish that the unseen trunk base is sound.
Mistake to avoid: Presenting a screening observation as a comprehensive individual-tree assessment.
Context reference: Welcome
32. Understand basic individual-tree assessment
A basic assessment commonly uses systematic ground-based inspection of the tree and surrounding site, with appropriate simple observations or tools. It connects visible findings to targets and failure scenarios. It cannot resolve every internal or elevated condition, so identify limitations and questions that may require a more focused assessment.
Worked example: Ground inspection reveals an elevated union whose far side cannot be seen. Record that limitation rather than assuming the hidden surface resembles the visible side.
Mistake to avoid: Treating ground access as equivalent to complete visibility.
Context reference: Welcome
33. Choose advanced assessment to answer a question
Advanced assessment should address a defined uncertainty that could influence management. Possible approaches include closer crown inspection, root investigation or specialized measurements by competent practitioners. More equipment does not automatically create a better conclusion. Select the method according to the question, expected information and limitations.
Worked example: Uncertainty about internal decay at a critical trunk section may justify targeted diagnostic work if the result could change retention or mitigation decisions.
Mistake to avoid: Ordering a test without explaining what decision its result will inform.
Context reference: Welcome
34. Inspect from complementary viewpoints
Different viewpoints reveal different surfaces, attachments and relationships. Where safe access permits, examine the tree from multiple sides and relate crown, trunk, roots and targets. Obstructions and viewing angles should be documented. A defect hidden from one position may be obvious from another, while apparent features can change with perspective.
Worked example: A union appears intact from the path, but a second viewpoint reveals an open crack on its opposite side.
Mistake to avoid: Completing the assessment from the most convenient single position.
Context reference: Welcome
35. Interpret sounding and probing conservatively
Sounding and probing can provide local clues about cavities or deteriorated material when used appropriately by competent assessors. Responses vary with geometry, bark and wood condition. These observations supplement inspection; they do not map an entire stem or directly quantify strength. Avoid unnecessary injury or unsafe access during investigation.
Worked example: A hollow-sounding area supports further investigation, but neighboring solid-sounding areas do not prove that all internal wood is sound.
Mistake to avoid: Converting a local sound or probe response into a whole-tree strength estimate.
Context reference: Welcome
36. Understand tomography as an interpreted model
Tomographic methods infer internal conditions from measured signal behavior across a section. Results depend on measurement geometry, wood characteristics and interpretation. A displayed image is a model of the investigated section, not a photograph of decay or a direct statement of failure probability. Relate results to external defects and loading.
Worked example: An anomalous region in one trunk section prompts interpretation of possible deterioration; it does not establish conditions throughout the entire trunk.
Mistake to avoid: Reading a colored diagnostic image as a complete structural verdict.
Context reference: Welcome
37. Understand the sampling limits of resistance drilling
Resistance drilling records variation along a narrow sampling path and can help investigate internal wood condition. Interpretation requires suitable equipment knowledge and awareness of wood variation. Because it samples locally and is invasive, its use should be justified. A favorable trace does not exclude deterioration elsewhere in the section.
Worked example: One sampling path passes through apparently intact wood beside a suspected cavity. That trace cannot establish the cavity's full extent.
Mistake to avoid: Generalizing one narrow sample to all remaining load-bearing wood.
Context reference: Welcome
Integrating findings into risk decisions
38. Support failure likelihood with a mechanism
A defensible failure-likelihood judgment connects observations to the capacity and loading of a particular tree part during the stated period. Explain which findings support the judgment and which limit confidence. Avoid letting an alarming appearance replace analysis of the actual mechanism or expected loading conditions.
Worked example: An active separation at a heavily loaded union provides a clearer failure mechanism than an unexplained statement that the crown looks dangerous.
Mistake to avoid: Assigning likelihood without showing how the observed condition could cause failure.
Context reference: Welcome
39. Treat impact likelihood as conditional on failure
Impact likelihood asks whether a target would be struck if the specified failure occurred. It depends on the failure path, target location and presence. Keeping this conditional question separate prevents double-counting structural weakness and helps identify mitigation that reduces exposure even when tree condition remains unchanged.
Worked example: Moving a seating area outside a branch's plausible impact area can reduce impact likelihood without changing that branch's likelihood of failure.
Mistake to avoid: Using the same crack as evidence for both failure and target presence.
Context reference: Welcome
40. Describe consequences for the actual target
Consequences concern the harm that could follow impact, considering material size, impact characteristics and target vulnerability. Distinguish bodily injury, property damage and disruption where relevant. Do not infer exact injuries from branch dimensions alone or substitute an object's replacement value for every possible consequence.
Worked example: A falling limb could damage an empty shed; the same impact area occupied by workers introduces a separate potential for personal injury.
Mistake to avoid: Assigning consequences without stating who or what could be harmed.
Context reference: Welcome
41. Distinguish ordinal categories from probabilities
Ordered descriptive categories communicate relative judgments but do not automatically represent measured probabilities or equal numerical intervals. Use the definitions in the applicable official method consistently. Assigning arbitrary numbers to words and multiplying them can create false precision unless a validated method explicitly supports that calculation.
Worked example: Labeling two likelihood categories as 2 and 4 does not establish that the second represents twice the probability of the first.
Mistake to avoid: Turning descriptive categories into invented mathematical probabilities.
Context reference: Welcome
42. Keep combined judgments within one scenario
When combining failure, impact and consequences, ensure every component refers to the same tree part, target, conditions and assessment period. Mixing components from different scenarios can produce an incoherent conclusion. Use the applicable official framework for formal category combinations rather than inventing a matrix.
Worked example: Combine a lateral branch's failure judgment with consequences for the bench beneath that branch, not with consequences from whole-tree impact on a distant building.
Mistake to avoid: Selecting the most severe component from unrelated scenarios.
Context reference: Welcome
43. Assess multiple target scenarios separately
A single failure can expose several targets with different occupancy and consequences. Separate scenarios when those differences affect management, and identify which findings drive the recommendation. An overall summary should preserve important distinctions instead of averaging away a consequential target or implying all targets share the same exposure.
Worked example: A branch overlaps a permanently parked vehicle and a occasionally used picnic table. Assess property and people exposure separately.
Mistake to avoid: Averaging target occupancy into one value that obscures the people scenario.
Context reference: Welcome
44. Separate risk assessment from acceptance
Assessment describes the potential event and its estimated risk; acceptance is a management decision made within the responsible organization's criteria and obligations. The assessor should explain findings and options without assuming a universal acceptable-risk threshold. Any relevant legal or organizational requirements must be established separately for the setting.
Worked example: An assessor explains a tree's failure scenario and mitigation options; the responsible manager applies documented site criteria when choosing the response.
Mistake to avoid: Claiming that one assessment category is legally acceptable everywhere.
Context reference: Welcome
45. Prioritize action without hiding uncertainty
Management priority can consider assessed risk, exposure, available interim controls and confidence in the information. A poorly understood condition may justify prompt clarification, while credible signs of instability near people may warrant immediate site controls by responsible personnel. Explain why the chosen response fits the scenario and uncertainty.
Worked example: A fresh structural separation above an occupied entrance supports prompt access management and competent follow-up rather than waiting for a routine inspection cycle.
Mistake to avoid: Using uncertainty as a reason to postpone every protective decision.
Context reference: Welcome
Selecting and reviewing mitigation
46. Reduce exposure by relocating targets
Moving a target can reduce risk by changing the opportunity for impact. This may preserve tree benefits while addressing a specific scenario. Confirm the new location against all relevant trees and failure paths, and consider whether users will continue occupying the original area despite the relocation.
Worked example: A bench is moved beyond the assessed branch impact area, and the former seating space is redesigned so people do not gather there.
Mistake to avoid: Moving furniture while leaving the same pattern of human occupancy underneath.
Context reference: Welcome
47. Evaluate the reliability of access controls
Barriers, closures and access arrangements reduce exposure only when they are suitable, maintained and followed. Their effectiveness depends on site use and implementation. Temporary controls should have a clear responsible party and review condition. A sign alone may provide little exposure reduction where people routinely enter the area.
Worked example: A temporary closure protects a seating area while a damaged branch awaits specialist assessment, provided the closure is maintained and unauthorized access addressed.
Mistake to avoid: Treating the existence of a warning sign as proof that occupancy has stopped.
Context reference: Welcome
48. Balance pruning benefits and structural costs
Appropriate pruning may remove a defective part or reduce loading, but it also creates wounds and changes crown structure. Define the specific risk-reduction objective and use competent arboricultural planning. Excessive or poorly placed cuts can introduce future problems; an immediate visual reduction in crown size does not establish a lasting improvement.
Worked example: Selective work on an overextended defective branch addresses its loading more directly than indiscriminate cutting throughout the crown.
Mistake to avoid: Assuming greater foliage removal always produces greater or longer-lasting risk reduction.
Context reference: Welcome
49. Understand the limits of supplemental support
Supplemental support may help manage some structural configurations, but it does not restore decayed wood or eliminate every failure mechanism. Suitability, design, installation and inspection require appropriate competence. Assess the supported structure, possible failure outside the system and ongoing management responsibilities before relying on support as mitigation.
Worked example: A support system addressing a weak union does not resolve separate basal decay affecting whole-tree stability.
Mistake to avoid: Describing a supported tree as permanently safe or maintenance-free.
Context reference: Welcome
50. Evaluate removal as a scenario-specific option
Removal can eliminate future failure of the removed tree or part, but the decision should relate to the assessed scenario and feasible alternatives. It also changes the site and may alter neighboring trees' exposure. Removal operations introduce their own hazards and require qualified planning; the assessment should not become hazardous work instructions.
Worked example: Removing one unstable tree may address its identified risk while requiring review of newly exposed neighboring trees.
Mistake to avoid: Assuming removal leaves every surrounding risk condition unchanged.
Context reference: Welcome
51. Protect roots and address site causes
Mitigation can include preventing further root damage, managing harmful site activities and correcting suitable environmental problems. These measures may support future condition but do not instantly replace lost roots or repair existing structural weakness. Distinguish prevention of deterioration from immediate control of an identified failure scenario.
Worked example: Stopping repeated vehicle compaction protects the rooting area, but separate action may still be needed for a damaged structural root system.
Mistake to avoid: Treating improved growing conditions as an immediate cure for compromised anchorage.
Context reference: Welcome
52. Make monitoring a defined management action
Monitoring needs observable features, a responsible person and conditions that trigger reassessment or action. It gathers information; it does not physically strengthen the tree. Monitoring is useful only when compatible with the assessed risk and the organization's ability to respond. Significant storms, damage or site changes may justify earlier review.
Worked example: A recorded crack is reviewed for changes against dated photographs, with renewed assessment required if separation increases.
Mistake to avoid: Writing 'monitor' without identifying what to observe or what change matters.
Context reference: Welcome
Reporting, communication and professional conduct
53. Define the assignment and its boundaries
State which trees, targets, assessment period and methods the assignment covers. Explain access limitations and excluded areas or questions. Clear boundaries prevent a focused inspection from being interpreted as an assurance about an entire site. They also help determine whether the chosen approach can answer the client's actual management question.
Worked example: A report covers three trees beside a play area and explicitly excludes the adjacent woodland that was not inspected.
Mistake to avoid: Allowing a limited assignment to appear to cover every tree on the property.
Context reference: Welcome
54. Separate observations from interpretations
Record what was observed before stating what it may mean. Measurements, photographs and visible symptoms are evidence; conclusions about decay, failure mechanisms and likelihood are interpretations. This distinction helps another reader evaluate the reasoning and makes uncertainty visible without weakening a well-supported recommendation.
Worked example: Record 'open separation at the union' as an observation, then explain why its location and loading raise concern about stem failure.
Mistake to avoid: Recording a suspected internal condition as though it were directly observed.
Context reference: Welcome
55. Make tree records reproducible
Use sufficiently clear identifiers, locations, dates and images so another person can locate the same tree and compare the same features. Record measurement units and relevant viewpoints. Reproducibility supports follow-up and helps prevent recommendations from being applied to the wrong tree or apparent changes being caused by inconsistent photography.
Worked example: A tagged tree, mapped location and dated photograph of its western union allow the next assessor to examine the same feature.
Mistake to avoid: Identifying a tree only as 'the large one near the entrance.'
Context reference: Welcome
56. Write recommendations that support implementation
A recommendation should connect the identified scenario to a clear action, appropriate urgency and any necessary specialist input. Distinguish interim exposure controls from permanent work. Avoid vague phrases that leave the manager uncertain about what needs to happen, while keeping technical work specifications within the assessor's competence and assignment.
Worked example: Recommend restricting access beneath the damaged branch pending competent evaluation, and identify who should arrange that evaluation.
Mistake to avoid: Writing 'make safe' without specifying the risk being addressed or the next action.
Context reference: Welcome
57. Explain residual risk after mitigation
Mitigation changes a scenario but may leave risk from the retained structure, remaining targets or other failure mechanisms. Describe what the proposed action is expected to reduce and what still needs management. Avoid guarantees: a recommendation should communicate its practical purpose and limits rather than promise that no future failure can occur.
Worked example: Removing a defective limb addresses that limb's scenario, but the retained tree still requires management of other identified conditions.
Mistake to avoid: Stating that completion of one action makes the whole tree risk-free.
Context reference: Welcome
58. Recognize competence limits and refer appropriately
Professional judgment includes recognizing when a question exceeds one's knowledge, access or diagnostic capability. Explain what specialist input is needed and how it could affect the assessment. Referral should answer a defined question, not merely transfer responsibility. General ethical expectations support honest representation of competence and limitations.
Worked example: An unfamiliar fungal sign affecting a retention decision prompts specialist identification, while the assessor records visible structural findings independently.
Mistake to avoid: Presenting uncertain specialist identification as established fact to avoid referral.
Context reference: Code of Ethics; Welcome
59. Manage conflicts that could distort judgment
A financial or personal interest can influence recommendations or their perceived independence. Identify relevant conflicts and communicate them clearly. Keep the assessment's reasoning tied to evidence, and distinguish assessment advice from a proposal to sell work. ISA identifies its ethics policy as guidance for professional decision-making across credential programs.
Worked example: An assessor who also offers removal services explains that relationship and documents why removal is recommended over feasible alternatives.
Mistake to avoid: Allowing the value of a potential work contract to determine the assessment conclusion.
Context reference: Code of Ethics
60. Support an informed management decision
Communicate findings in terms the responsible decision-maker can understand: the scenario, important uncertainty, options and expected effects. Document the chosen response and any deferred recommendations without claiming the assessor controls every management decision. Clear communication also preserves continuity when responsibility passes to another manager.
Worked example: A manager chooses target relocation over pruning. The record explains which exposure it reduces and what monitoring remains necessary.
Mistake to avoid: Providing a category alone and assuming the manager understands its implications.
Context reference: Code of Ethics; Welcome
References
Reference dates:
Browse all study guides