Replacing a Driveway Near Trees: Decisions to Make Before Demolition

Published 2026-09-19 · By Reagan Carrier · 1209 words

Before replacing a driveway beside a mature tree, have the pavement work and tree concerns reviewed together. Explain which trees you hope to retain, ask whether an arborist should assess the conflict, and agree on what happens if demolition reveals roots. Do not make root cutting an automatic part of a driveway replacement order. The useful first decision is who will evaluate the site, not which material will cover it.

Define the problem without deciding the cause

Start with what you can actually see: a lifted edge, an uneven slab, a narrow driveway, or a surface that needs replacement. Mark each location on a simple sketch. Photograph the pavement and nearby trees together, then take closer views of the affected areas. Include the garage entrance, walking route, planting beds, and any place where the proposed driveway would expand.

Describe the result you want in practical terms. Perhaps you need room to open a car door, want to keep a shaded sitting area, or need a more usable route from parking to the house. Separate those goals from proposed solutions. A wider driveway is one possible response to an access problem, but the project discussion should establish whether that footprint is appropriate before treating it as fixed.

For a Middle Tennessee homeowner planning work around an established landscape, a short written brief can keep the conversation focused: what is wrong now, what must remain usable, which trees matter to you, and what you are willing to reconsider. Bring any previous repair records, but do not label a tree as the cause solely because it is nearby.

Why roots are not just demolition debris

University of Georgia Extension explains that roots provide both support and the movement of water and nutrients. Its discussion of surface roots warns that cutting them can damage or destabilize a tree. That makes a root encountered during paving a reason for assessment, not an invitation to trim whatever is in the way.

The same resource explains that roots can damage driveways and sidewalks. This supports taking a suspected root conflict seriously, but it does not diagnose your pavement from a photograph. Ask the paving contractor what the visible condition establishes and what remains uncertain. Ask an arborist to address the tree's condition and the implications of the proposed work. Those are related questions with different responsibilities.

Avoid asking either professional for a blanket promise that the tree will survive or that new pavement will never move. Request a description of the specific uncertainties instead. If the assessment changes your preferred layout, make that decision while the driveway is still intact whenever possible.

Put the pavement contractor and arborist on the same drawing

Use one dated sketch or plan for both conversations. Show the current driveway edge, proposed replacement limits, trees to be considered for retention, and any planned widening. Add the locations of other proposed work, such as a drain connection or a new walkway. Do not let separate sketches quietly describe different projects.

Ask the pavement contractor to identify the expected demolition and preparation area. Ask the arborist to identify protection needs and explain whether the proposed footprint raises concerns. If the recommendations conflict, request a coordinated review before accepting the final scope. The owner's role is to make sure the conflict gets resolved, not to select a root-pruning method from general online advice.

Useful questions include: Can the layout be reconsidered? Which dimensions are essential to the way the driveway will be used? Is additional evaluation needed before a firm scope is possible? Who records the agreed decision? Any alternative should be reviewed for the whole project rather than accepted because it appears to avoid one visible root.

Discuss the work area, not only the finished driveway

UGA Extension's construction-damage guidance identifies soil compaction, grade changes, trenching, and equipment contact as potential sources of tree injury. It also notes that damage may not become apparent immediately. A plan that discusses only the final pavement edge therefore leaves an important part of the work unaddressed.

Have the project team identify where vehicles will travel, materials will wait, and removed pavement will be loaded. Ask how any tree-protection boundaries will be marked and communicated before equipment arrives. These arrangements should reflect the site assessment, rather than a homeowner's guess about a universal safe distance from a trunk.

Walk through the proposed setup with everyday use in mind. If the usual parking spot becomes a protected area, where will household vehicles go? If deliveries normally use that side of the property, who will redirect them? Put the answers in the project notes so a later delivery or separate landscaping crew does not have to improvise.

Agree on a pause-and-review process for unexpected roots

A written scope can describe how a discovery will be handled without pretending every underground condition is already known. Ask the contractor to identify the person who will notify you if roots or other unanticipated conditions affect the agreed work. Decide who needs to review the discovery before the affected portion proceeds.

For example, the project notes might call for photographs, a marked location on the plan, and a discussion with the arborist before revising work near a retained tree. This is a suggested communication process, not a direction to expose, cut, or treat roots. The professionals responsible for the site should determine appropriate methods.

Also decide how a change will be documented. Request the revised work limits, any added evaluation, the effect on access, and any schedule or price adjustment in writing. A homeowner should be able to distinguish a previously agreed item from a newly proposed one without reconstructing several phone calls.

Compare proposals using the same tree-related assumptions

Before comparing totals, check whether each proposal describes the same driveway footprint and the same assumptions about retained trees. Ask whether arborist evaluation is included, arranged separately, or still outstanding. Identify who is responsible for communicating protection measures and who will receive questions during demolition.

Keep a small closeout file containing the final plan, approved changes, and photographs. If tree follow-up has been recommended, record who will provide it and how to arrange the visit. Keep pavement care instructions separate from tree-care advice so each question goes to the appropriate professional.

Milliken Corporation's published services include asphalt driveway installation and repair, as well as concrete driveways and walkways. When requesting a proposal, mention nearby trees at the outset and ask how the pavement review should be coordinated with any needed arborist assessment. Do not assume a paving proposal includes tree evaluation unless that responsibility is expressly described.

Frequently asked questions

Does a tree beside the driveway mean it must be removed?

No automatic conclusion follows from proximity alone. Ask for an assessment of the tree and proposed work before deciding whether retention, a layout change, or another approach is appropriate.

Should I cut visible roots before the contractor arrives?

No. Leave root decisions to a site-specific professional assessment. Cutting first removes the opportunity to evaluate the conflict with the tree and pavement conditions still intact.

Can I choose asphalt or concrete before the tree review?

You can state a preference, but keep the footprint and scope open for review. Material selection does not answer who will assess nearby roots or how unexpected conditions will be handled.

Sources and further reading