What to keep with your Bedford tree-work permission

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

Before you make arrangements

Save the complete decision and attachments, not just the email announcing an outcome. Identify the tree, relevant plan and specified operation. Confirm the correct authority if necessary through which council handles your tree enquiry. This guide is about organising records; it does not interpret a particular decision's legal effect.

Create one project folder with a clear index

A simple folder can contain the application, decision, plans, supporting reports, correspondence and final quotation. Use dates and plain filenames so another person can identify the current documents. A short index can explain what each file does and which version the contractor should read.

Keep the complete originals alongside any working notes. Do not alter a decision notice to incorporate your own interpretation, even if the change seems minor. A summary can be useful for household planning, but it should point back to the actual document. If you cannot tell whether an attachment belongs to the same application, ask the council before treating it as part of the authorised proposal.

Connect the tree label to the garden

Check that the identifiers in the application, plan and decision refer to the same feature. Our tree-location-plan guide explains how to match labels without assuming an informal sketch is an official survey.

Add a safe ground-level photograph if it helps the contractor identify the intended tree. Caption it with the confirmed label and viewpoint. Keep uncertainty visible: a guessed species or an old garden description should not replace a clear tree position. Where several trees stand together, ask the professional to resolve identification before the work date. A tidy filing system is only useful when the documents can be connected confidently with the tree on the ground.

Read the decision with its conditions

A decision can include limits or requirements that affect how the proposal proceeds. National guidance explains that tree-work consent may have conditions, including replacement planting in relevant circumstances. Keep the wording and referenced documents together rather than reducing the decision to “permission granted”.

Ask the council about any condition you do not understand. Do not infer a universal timetable, validity period or exemption from a different property's approval. If the tree work relates to development, read planning conditions and tree work too. The presence of one decision does not necessarily settle every requirement affecting a wider building or landscaping project.

Give the contractor the complete relevant set

Share the decision, specified operation and identification material before the final quotation is accepted. Ask the business to confirm that its scope corresponds with the documents. The person pricing the job and the team carrying it out should receive the same final instruction.

If a quotation uses different wording, ask why. A shorter commercial description might be harmless shorthand, but it might also conceal a different operation. The quotation checklist helps you compare the intended finish and inclusions. Keep evidence of what you supplied and when. This is a practical communication record, not a substitute for the contractor's own responsibility to understand the job it accepts.

A hypothetical version-control problem

Imagine a homeowner obtains a decision for a specified pruning operation, then forwards an earlier contractor email that proposed more extensive work. The email sits above the decision in a conversation thread, and the homeowner assumes the attachment makes the final intention obvious.

A safer handover identifies the approved specification explicitly and asks for a matching quotation. This is a hypothetical example, not a report of an actual Bedford incident. It shows why keeping a long email chain is not enough: the contractor needs to know which instruction is current. A brief cover note can state the decision reference, tree identifier and attached final documents while asking that superseded proposals are not used as the work order.

Record a changed recommendation separately

If a later inspection changes the proposed operation, retain both the old and new descriptions with dates. Ask the relevant authority how the change should be handled before assuming the earlier decision covers it. The contractor's recommendation and the authority's position are different parts of the record.

Use changing approved tree work to prepare the questions. Do not overwrite the old specification so that the sequence becomes impossible to reconstruct. A clear record might show original application, decision, subsequent concern, revised recommendation and written clarification. Keeping those stages visible helps a professional understand what has happened without having to infer it from file modification dates or incomplete forwarded messages.

Retain completion information proportionately

After the visit, keep the final invoice, any agreed variations and relevant photographs of the result. Ask the contractor for aftercare or follow-up advice in a form you can retain. Record who will undertake any separately arranged replacement planting or later work.

Our end-of-visit checklist helps you review the scope once the area is safe. Avoid treating a photograph as proof of every technical or legal point. Its purpose is to support the project history. If a condition requires further action or evidence, ask the authority what it needs rather than assume a general garden image will be sufficient.

Make future enquiries easier without oversharing

A later contractor may need to know what operation was carried out, while an estate agent or new owner may need relevant planning records. Keep the documents available, but share what is necessary for the specific purpose. Remove unrelated household contact details from a working copy if appropriate, while preserving the original securely.

If you cannot locate an old decision, start with the authority's official records rather than recreating its wording from memory. Ask for the relevant reference or document and identify any gap honestly. A project history can remain useful even when incomplete, provided it distinguishes known facts, missing evidence and personal recollections. The aim is clarity for the next decision, not a large folder whose status nobody can explain.

Your next step

Before booking, compare the decision, plan and quotation as one document set. Resolve mismatched tree identifiers or operation descriptions, then keep the accepted version and completion record together. The Bedford protection resource provides the official starting points when you need to find or clarify the underlying record.

When preparing to move, our selling with protected trees guide explains how to organise these records for your conveyancer.

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.