The Tree on the Line: Whose It Is, and Who Pays
Quick answer: The Tree on the Line: Whose It Is, and Who Pays — The crew that answers the phone is the crew that climbs the tree: locally based, insured, and working to the industry standards rather than to whatever the last job allowed. That matters most where the work is delicate — over a roof, beside a wire, or on a slope where the wood has to be lowered rather than dropped.
Field note. What we see is that the questions worth asking are the same on every property: who is climbing, what happens to the wood, and what the tree looks like in five years — so we answer those before we talk about dates.
On the other hand, credentials are a floor rather than a guarantee: what a tree gets is the judgment of the person in it, which is why we keep the same small crew on this coast.
Nothing on a residential property generates more bad feeling per dollar than a tree on the boundary. Two neighbours, one tree, and usually no document saying who is responsible for what. By the time a crew is being asked for a quote, the disagreement is already two years old and the tree is being discussed as an insult rather than a structure.
So the first useful move is not arboricultural. It is to establish what the tree actually is, on paper, before anyone spends money.
Ownership, in three cases
A trunk that stands entirely on one side belongs to that owner, along with everything it grows into. The neighbour’s remedy is limited and old: in California they may cut back the parts of the tree that encroach over their side, up to the property line, provided doing so does not kill the tree. That right is exercisable without permission and without notice, and exercising it clumsily is where liability begins.
A trunk that straddles the line is generally treated as owned in common by both neighbours, and neither may remove it unilaterally. This is the case that ends up in letters and, occasionally, in court, because the tree cannot be felled without both owners agreeing on the day, the crew and the bill — and in Cambria that agreement usually has to satisfy a permit as well, as set out in heritage trees and the paperwork.
Roots and branches that cross the line are the parts most people actually care about — the limb over the roof, the root under the patio. These can be severed up to the boundary by the affected owner, but the test that matters afterwards is whether the tree survived the remedy.
Kill someone’s tree by cutting its roots and you have converted a nuisance claim into a damages claim, and California’s timber-trespass statute, section 3346, provides for enhanced damages when trees are wrongfully destroyed.
Who is liable when a limb comes down
Less often than people assume. A healthy tree that drops a limb onto a neighbour’s fence during a storm is generally nobody’s liability — it is an act of nature, and the neighbour’s own insurance handles their damage. What changes that is knowledge.
If the owner knew, or should have known, that the tree had a defect — a cavity, a crack, a dead leader overhanging a structure, a letter from an arborist naming the problem — then failing to act on that knowledge is negligence, and the exposure transfers with it.
Which is why the notification matters more than the opinion. A recorded, dated expression of concern that names a specific defect is the document that changes who pays. What counts as a defect worth naming is the subject of judging a dead limb from the ground. A vague remark at the fence line achieves nothing.
The inspection, and who commissions it
An arborist inspecting a boundary tree needs to see the whole tree, which may mean stepping onto the neighbour’s land. There is no general right to enter someone’s property to inspect a tree, even your own — so the polite request is not a formality, it is the mechanism.
In practice this is where a joint inspection is worth the money: one arborist, engaged by both parties, produces a report both will accept, and it removes the obvious objection that the report was bought by the interested party.
What the report should contain is specific: the defect, its size and position, the target it threatens, an estimate of failure likelihood over a stated period, and a recommendation with a timescale. A report that says the tree is ‘of some concern’ is unusable. One that says a twenty-foot dead leader over the roof should come off within ninety days is a document two neighbours can act on.
The sequence that keeps it out of a dispute
Write down the location from the survey, or if there is none, commission one for the tree alone rather than the whole yard. Get the joint inspection, with the report addressed to both owners. Send the recommendation in writing, dated, by a channel that leaves a record, and offer to share the cost of the work if the tree was jointly owned — because the offer, even if declined, establishes that you acted reasonably.
Then do the work on the schedule the report sets, and keep the invoice with the report. If the tree later fails, that file is the reason the conversation stays civil and administrative rather than personal.
One more piece of practical economics. The cost of removing a jointly-owned tree is usually shared, and it is almost always cheaper than the alternative: a joint inspection, a shared invoice and a stump, versus two insurances, an emergency call-out at a premium and a neighbour who no longer waves. The tree is the same tree either way. The file is what differs.
And if the tree is healthy and the complaint is that it drops leaves in the gutter, the honest answer is that leaves are not a legal nuisance worth a letter. Buy a gutter guard, keep the file empty, and save the paperwork for a defect that has a target.
