What a Tree Survey
Costs to Deliver

Most "tree survey cost" content online is written for the homeowner or developer shopping for a survey, comparing quotes with no idea what goes into one. This guide is written the other way round — for the arborist or surveyor building the quote, trying to figure out what to charge without either lowballing the job or scaring off the client with a number that doesn't obviously match the work.

If you're the one shopping for a survey rather than delivering one, the honest answer is that price depends heavily on tree count, site complexity, and whether risk assessment or category grading is part of the scope — get a quote based on your actual site, not a rule of thumb.

A tree survey job has three phases, and only one of them scales cleanly with tree count:

Site time is the phase most practitioners already price reasonably well, because it's the part they can watch a clock on. It depends on tree count, site density, whether risk assessment or category grading is in scope (both add time per tree — you're not just measuring, you're assessing), and access (a wooded slope takes longer to walk than a mown residential lawn).

Track your own site-time-per-tree across a few jobs of different types rather than borrowing someone else's number — a solo residential assessment, a dense wooded BS5837 site, and a flat municipal street inventory all have genuinely different per-tree rates, and only your own past jobs tell you what yours are.

Weather and season affect this more than most quotes account for. A winter survey of deciduous trees without leaf cover moves faster for some observations (easier sightlines into the crown for deadwood and structure) and slower for others (species ID without foliage is harder, and cold, wet conditions slow down data entry and photography). Build a small buffer into winter-season quotes rather than assuming site time is season-independent.

Office time is where quotes usually undercharge, because it's invisible at the point of quoting. Transcribing handwritten or notebook data into a spreadsheet, matching photos to tree numbers from a camera roll, marking up or redrawing a site plan, and assembling the final report package all happen after the site visit, off the clock the client sees.

For a manual paper-and-spreadsheet workflow, this phase is often close to the site time itself, and on complex jobs — large tree counts, risk assessments, disorganised photos — it can run longer than the walk. If your quote only accounts for site time, you're pricing half the job.

A day rate (or hourly rate × estimated hours) covering all three phases — prep, site, and report — is more defensible than a flat per-tree number for most jobs, because it actually reflects where your time goes. Reserve per-tree pricing for large, uniform jobs (a municipal street inventory of consistent, easily accessed trees) where tree count really is the dominant cost driver.

A simple build: estimate site-visit hours from tree count and site complexity, estimate office hours separately (don't assume they're proportional — they scale with photo count and report complexity, not just tree count), add prep and travel, multiply by your rate, then add a contingency for the unknowns you can't see from a client's initial description (access issues, an unexpectedly dense site, a scope that turns out bigger once you're walking it).

Decide separately whether risk assessment, category grading, or appraisal work is in scope — each adds meaningful time per tree beyond a basic species/size/condition record, and each is worth its own line in the quote rather than being absorbed into a single blended rate. A client comparing your quote to a cheaper one that skips risk assessment entirely needs to see that difference explicitly, not guess at why the numbers don't match.

For repeat clients — a property manager with several sites, a firm that sends you regular referral work — a standing day rate agreed once removes the need to re-quote from scratch every time, and it's usually worth the small early discount to lock in predictable, recurring work over one-off jobs priced individually.

A single illustrative number is more useful than another paragraph of "it depends," so here's one worked example with its assumptions stated plainly. Change any assumption and the number moves — that's the point of showing the build, not just the total.

A few patterns show up repeatedly in underpriced tree survey jobs:

"Just the trees in the front" becomes "and also the ones out back" more often than not. Put the scope in writing before you start — which trees, which diameter threshold, whether risk assessment is included or a separate line item — and quote additional trees discovered on site as a change order, not absorbed silently into the original number. This isn't about nickel-and-diming a client; it's about the quote staying honest to the work actually done.

The same applies to revisions after delivery. A client asking you to re-check one tree a month later is a quick favour; a client asking for a second full pass because their plans changed is a new job. Deciding in advance where that line sits — and saying so in the original quote — avoids an awkward conversation about scope after the work is already done.

The office-time phase — transcription, photo sorting, report assembly — is the part LogLog is built to shrink. Data and photos are recorded once, at the tree, on the pin. The export produces the spreadsheet, the annotated plan, and the organised photos in one ZIP, which means less of your quote has to cover re-typing your own field notes. It doesn't make the site visit faster — walking the site still takes what it takes — but it recovers the desk hours a manual workflow quietly burns after you've already left.