TreeBossPro Blog — Arborist Software

Recording Tree Height: Practical Estimates Arborists Can Rely On

Height is the number clients ask about most and arborists measure least. "How tall is that thing?" is a reasonable question, and the answer shapes everything from rigging to price. Yet height on most job tickets is a guess written as a round number.

After Measuring and Recording DBH: Habits That Make Arborist Records Useful, which covered DBH, this article looks at height: how to estimate it consistently and how to keep it useful on the record.

Why Height Belongs on the Record

Height tells a crew whether the work can be reached from the ground, needs a climb, or needs a lift. It tells an estimator how far a limb can travel if it is dropped. It tells you whether a tree that is 20 feet from the house could reach it. Recording height in feet on the property record means everyone starts with the same picture, rather than the office pricing a 40-foot tree that the crew finds is 75.

Height also matters to clients in ways they may not say out loud. Someone worried about a tall tree near the bedroom wants to know you took its size seriously. Telling them you recorded the height and how you estimated it is a small sign of professionalism that builds trust before any work begins.

Field Methods That Are Good Enough

Arborists have several practical options for estimating height:

• A clinometer or hypsometer with a measured distance from the tree gives a solid estimate
• A laser rangefinder with height function is fast and repeatable
• The stick or similar-triangles method works in a pinch when you have nothing else
• Comparison to known heights, such as a two-story roofline, is a rough check

Whichever method your practice uses, the important part is consistency. If one person always uses a clinometer and another always eyeballs, the numbers will drift apart over time.

Crown spread is another useful dimension for some jobs, especially clearance and reduction work. If you find yourself writing it in the notes often, consider a custom field so it is captured in the same place every time.

Note the Method and the Tree

As with DBH, TreeBossPro stores height at the property level. Write a short note saying which tree the height refers to and how it was estimated: "Height of backyard tulip poplar, laser rangefinder." A future reader will know to trust it. If you estimated from a distance because of access, say so.

The same discipline applies when a client volunteers a height. Homeowners routinely overestimate the height of trees near their homes. Record what you measured, not what you were told, and if you did not measure, write that the figure is approximate.

Height and Risk Conversations

Height and distance to targets drive many of the conversations arborists have with clients. Be careful not to overstate what a single height number means. A tall tree is not automatically a hazard, and a short tree can still fail onto a target. Use height to frame the discussion, then rely on your assessment and notes for the actual recommendation. If your client needs a formal risk assessment or written report, produce that separately; TreeBossPro keeps the property data, notes and photos, but it is not a report generator.

Height and Scheduling

Height affects how long jobs take and what crew and equipment you send. A property with several tall trees probably needs a full day and an experienced climber. Recorded heights help the office schedule realistically and help crew leaders see what they are in for on the crew app before they arrive. Combined with drop-zone notes, it is the difference between a smooth day and a long one.

It also helps with seasonal planning. Tall trees that need climbing work can be grouped onto days when your most experienced climbers are available, and the office can see at a glance which upcoming jobs are likely to run long because the recorded heights are on the property.

Update Height With the Cycle

Trees grow and they get reduced. After a crown reduction, the height on file is out of date. Make updating height part of closing out the pruning job, and use the service history to show how the tree has changed over cycles. That history is a quiet selling point when you propose the next round of work.

Reductions should be recorded with care. Note how much was taken off and from which part of the crown, along with the new approximate height. When the tree pushes new growth over the next few seasons, that note helps you judge whether the response is normal and how soon the next reduction cycle should come.

For how height, DBH and notes feed the rest of the workflow, read more on the arborist software page.