Changing a tree-work proposal after permission

General guidance, not a professional assessment. Confirm site-specific advice and current requirements before work.

Before you arrange the work

Keep the decision, original application, tree schedule and photographs available. Describe what would change: the tree, operation, amount of pruning, timing or access arrangement. Ask the relevant authority how the revised proposal should be handled.

Make the difference easy to understand

Write the old and new descriptions side by side. For example, removing one identified limb differs from reducing an entire crown. Replacing pruning with felling is a substantial change in the intended result. The contractor should explain the reason for a recommendation without treating that recommendation as permission.

Read crown reduction versus thinning if terminology is making the comparison difficult.

Ask before relying on an earlier decision

Check the decision’s scope, conditions and validity. There is no universal promise that a council can accept a change informally. The appropriate route depends on the original control and the revised work. Ask for written confirmation of what is required and retain it with the project record.

If the work relates to a development, our planning-conditions guide helps identify other documents to check. A change to a tree proposal may also affect the wider site plan.

Update the quotation and site instructions

Once the position is settled, ask for the quotation to match the authorised specification. Include the tree identifier and decision reference where relevant. Make sure the person attending the site receives the final version, not an early email with superseded instructions.

A new concern about tree condition should be assessed on its own facts. Our dangerous-tree permissions guide explains why urgency should not become an assumed blanket exemption. Keep people away from an immediate hazard and seek appropriate help; a routine enquiry form is not an emergency service.

Write a change note with a visible version

Give the proposed revision a date and a short title. Identify the tree, the original operation and the new recommendation. Add the reason for the change and who supplied it. This makes the question clear without requiring the council or contractor to reconstruct a long email conversation. Keep the original document intact rather than editing it until its history is unclear.

Attach a marked photograph or plan where the location might otherwise be ambiguous. Describe whether the change affects one branch, the whole crown or the tree’s retention. Avoid replacing a precise specification with a phrase such as “more reduction”. Ask the professional to express the proposed result clearly enough for the authority to consider and the contractor to quote. Our protected-tree application guide explains the value of identifying the actual tree and operation, even when your immediate question concerns a revision rather than a new proposal.

A hypothetical change after inspection

Suppose a homeowner’s original proposal concerned clearance above a path. During a visit, the contractor recommends a different operation because the desired clearance and the tree’s structure do not fit the first idea. That recommendation deserves a proper explanation, but it does not establish that the existing decision covers it.

The homeowner can send the original and proposed descriptions together, ask what process is needed and wait for the answer before confirming the revised work. Meanwhile, the business can explain the practical and price implications without carrying out the substituted operation. This is a planning example, not an assessment of a real tree. If a newly observed defect changes the urgency, seek an appropriate assessment rather than using the routine revision exchange as an emergency response. Keep any assessment and the authority’s response in the same record so the eventual job is tied to the actual information considered.

Check changes that appear purely practical

Not every change is a different pruning operation. The proposed date, access route or surrounding works may also matter to the project. Ask whether the existing decision or associated documents contain relevant conditions before assuming those changes are administrative. A new route through a neighbour’s garden also needs that person’s access agreement, regardless of the tree-control position.

Explain the practical reason for the change. For example, say that a gate is unavailable rather than simply asking whether a different machine can be used. The contractor should assess the method; the homeowner’s useful contribution is the changed constraint. If access depends on disturbing a structure, surface or protected working area, identify that separately. Planning conditions and tree work covers the wider document check. Keep one list of unresolved points so a revised tree description is not approved while a second change remains hidden in the access arrangements.

Agree the commercial effect before work

A changed operation may affect the scope, price and programme. Ask for a revised quotation or a clearly identified written amendment that explains what replaces the earlier description. Record whether a deposit already paid is carried forward and whether any separately commissioned assessment remains payable. Do not infer those terms from the fact that everyone agrees a change is needed.

If the business recommends extra work on the day, ask it to distinguish an immediate safety concern from an optional improvement. Keep out of the working area while that is assessed. Where the change requires further authority or information, a postponement may be necessary; do not solve the timetable problem by giving an instruction beyond what you can authorise. The quotation checklist helps you compare the final scope, material handling and access assumptions after the revision, rather than concentrating only on the difference in price.

Give the attending team one final instruction set

Before the visit, confirm that the contractor has the current decision, specification and site notes. Ask how superseded versions will be kept out of the team’s working instructions. A message sent to a salesperson may not explain what a different person attending later has been told.

Keep the final documents available for a ground-level discussion before work starts, but do not direct technical operations yourself. If there is a discrepancy between what the team expects and the agreed scope, ask for it to be resolved before the affected operation proceeds. At handover, compare the completed work with the current version and note anything deferred. Do not use an old quotation as the sole completion checklist after a material change. Retaining a short version history also makes it easier to explain a later query without presenting an early idea as though it was the final agreed job.

Your next step

Confirm both the authority’s position and the contractor’s revised scope before work proceeds. Keep a dated record of the agreed version for the end-of-visit check.

Keep the final version with the documents described in your Bedford tree-permission records.

Sources & further reading

• GOV.UK: Tree Preservation Orders and conservation areas
• Bedford Borough Council: protected trees

Sources checked 31 October 2026. How we prepare guidance.