Put Unresolved Tree Work Questions in a Decision Register
A tree work conversation can end with agreement about the main job and uncertainty about several smaller matters. One person remembers discussing the stump. Another thinks the contractor will confirm disposal later. A neighbour has mentioned a shared gate, but nobody has checked who can give permission to use it. These loose ends become harder to resolve when they live in separate messages. Before accepting a proposal, give each unanswered question a place in a short decision register.
This is a planning record, not a technical assessment of a tree. It helps distinguish information you have received from choices you have actually made. Its purpose is to make the next conversation specific: what remains unknown, who can answer, and which commitment depends on that answer. A useful register can fit on one page, even when the project involves more than one visit.
Record a question before it becomes an assumption
Start with issues that could change what you book. Write them as questions, rather than predictions. “Will the proposal include removing the stump?” is more useful than “Stump probably included.” The question invites a verifiable response. The prediction can quietly turn into a belief that nobody remembers agreeing to.
Keep observations separate from conclusions about tree condition. You might record that you noticed a changed branch position from a familiar viewing point. That does not establish a diagnosis or the appropriate work. The International Society of Arboriculture explains in its guidance on why to hire an arborist that tree work should be undertaken by people trained and equipped to work safely in trees. Use the register to ask for professional input, not to replace it with an entry in a spreadsheet.
For each issue, record five things: the question, the person or source expected to answer, the evidence needed, the commitment affected, and the present status. A date is helpful when information may change. A question without an answer owner tends to circulate. A question without an affected commitment tends to look equally important to every other question, even when only one of them should stop a booking.
Decide which unanswered matters should hold up approval
An unresolved question does not always require the whole project to stop. Separate matters that affect the proposed work from preferences you can decide independently. An unanswered question about permission for access may affect whether the described arrangement is possible. Choosing where to store your own garden furniture may be a separate household task. Letting these sit in one undifferentiated list creates unnecessary urgency around minor details and too little attention to consequential ones.
Use plain statuses such as “awaiting information,” “answer received,” and “decision recorded.” Add “closed without action” when you deliberately decide an issue needs no further work. Avoid calling an item approved merely because someone replied. A reply may supply information while leaving the actual choice open. For example, an additional service being available does not mean you have asked to buy it.
The affected commitment column makes this distinction practical. It might say “Do not accept the proposal until the debris description is clear” or “Confirm this before agreeing the visit arrangement.” Write only a commitment you control. Do not assign a contractor responsibility for a neighbour's consent, a local authority's decision, or an owner's preference unless that responsibility has genuinely been agreed.
A fictional register for a mixed proposal
Imagine a fictional homeowner, Marta, reviewing a proposal after a site conversation. The proposal describes tree work and debris removal, while a follow-up message refers to an optional stump service. Marta also remembers discussing a gate that opens onto a neighbouring property. Rather than combining these into “confirm everything,” she writes three separate entries.
The first asks what the written debris removal scope includes and excludes. The expected answer comes from the proposer, and the evidence is an updated description in writing. The affected commitment is acceptance of that scope. Marta does not use a general comment about leaving the property tidy as a substitute for the specific answer. She wants the decision to be understandable later without reconstructing the conversation.
The second asks whether the stump service is part of the present offer or a separate option. Even if the answer is “separate,” the entry stays open until Marta records her choice. She might proceed with the original offer while excluding that option, or request a revised offer before deciding. Neither choice should be inferred from the fact that she asked about it.
The third asks whether the proposed access depends on permission Marta does not yet have. She records who can provide that permission and asks the contractor how the visit arrangement would change if it is unavailable. She does not tell the contractor the gate is available while waiting for a response. The entry shows a dependency that needs resolving, without pretending that a planning note itself grants access.
Keep answers attached to the version they describe
When a response arrives, copy a short factual summary and point to the original message or proposal version. “Included in revised proposal dated Tuesday” is stronger than a bare tick beside “included.” You need enough context to tell whether a later change has made that answer obsolete. Keep the full correspondence somewhere retrievable; the register is an index to the evidence, not a replacement for it.
If a new proposal changes the scope, revisit only the entries it could affect. Do not silently carry forward every old answer. A different access arrangement may change a previous assumption about household preparation, while leaving an unrelated decision intact. Mark the affected entry “needs reconfirmation” and say why. This keeps a revision from wiping out useful work while also preventing old certainty from attaching to a new arrangement.
Broader tree work planning resources can help you identify the questions to bring into these conversations, including scope, local checks, and access. Use that preparation to improve your questions. The answers for your property still need to come from the relevant professional, actual proposal, or responsible local source. A general guide cannot confirm a particular offer's contents.
Choose between a short register and a complete specification
A register works best when the main purpose is closing a manageable set of uncertainties. It is quick to share and makes dependencies visible. Its limitation is that several resolved entries can give a false impression that the whole job has been specified. Ten answered questions do not establish that every necessary question has been asked. Read the final written scope as a whole before relying on the list.
For a more involved project, use the register alongside a separate work brief and the provider's written proposal. The brief describes the intended outcome and known constraints; the register tracks what is not yet settled. This adds some administration but avoids making one document perform incompatible jobs. For a small project, a simple numbered note may be sufficient if each issue still has an answer source and a clear decision.
Resist recording every passing thought. An item deserves a place when its answer could change a choice, clarify responsibility, or prevent a misunderstanding about the agreed work. Archive resolved items rather than repeatedly discussing them, and reopen one when new information affects it. Before your next conversation, select the few entries that govern your next commitment. Ask those questions, retain the answers, and record the resulting choices in words that another reader could follow.
What did you think?