Records
How Long Until an Apple Fruits After Coppicing or Pollarding?
One trial page gives no measured answer, so here is what it does say and a per-tree record to find the answer for your own trees, season by season.
Updated November 18, 2026 · 8 min read
A reader comment under a post about apple coppicing asks the question many growers have about cutting a fruit tree hard back: after a coppice or pollard cut, how long is it before the tree produces fruit, and would it be three years? Nobody can give you one number that holds for every tree. This article reports what one published trial does and does not say, then gives you a per-tree record so you can find the answer for your own varieties, rootstocks and site.
Where the question comes from
The post is "An apple coppice system for forest gardens, orchards and hedgerows", published on 30 April 2026 on The Woodland Orchard, a Substack. It summarises a presentation by Chris Evans to the 2nd International Forest Garden / Food Forest Symposium (20 to 24 February 2023) about a coppice and pollard trial at Waterloo Farm, a 20 acre smallholding in North Herefordshire, UK. Near the bottom, a commenter writes that they are not a fan of wood fuel and asks how long it takes after a coppice or pollard cut before the tree produces fruit, suggesting three years. The page lists one reply from The Woodland Orchard, but the text we could read does not include it, so we do not know what the answer was and we do not guess.
What the trial page actually says
The page is careful to say that the primary function of these trees is firewood, with fruit described as an additional benefit, a "stacked function". Fruit was a secondary aim, and the page reports no measured time to fruit after a cut. Here is what it does report.
- Design: three plantings of four trees each. Bramley on a small rootstock, Bramley on M25, and ungrafted M25 rootstock grown as a tree in its own right.
- Layout: 2 m spacing, planted as two year whips. At the time of the video the trees were coming up to five years old.
- Plan: a first coppice at year seven, followed by a five to ten year rotation.
- Pre-trial test: a Sweet Coppin cider apple in the farm's established 25 year old orchard was pollarded. It showed strong growth in the first year. Evans was anticipating a stem of 3 or 4 inches in diameter about three years after pollarding, at which point the tree would be ready to pollard again, a three year rotation "potentially with a fruit crop in the intervening time". A Stoke Red cider apple was coppiced and also showed strong growth in its first year.
- Fruit so far: the ungrafted M25 trees fruited in their fifth year, and the page says the fruit was very nice. The page describes the first coppice as planned for year seven, so this reports fruiting before the planned first coppice, not fruiting after a cut.
- Growth: the ungrafted M25 grew much more slowly than both the Bramley on M25 and the own-root Bramley, and there was little difference between grafted and own-root Bramley. The results mention own-root Bramley although the planting list gives Bramley on a small rootstock; the page does not explain the difference.
One more detail matters for anyone hoping for both wood and fruit. In the Q&A, Evans said they had considered removing fruit to maximise wood, because trees put a lot of energy into fruit at the expense of biomass. The author closes by asking whether the trees will deliver significant fruit as well as useful timber, and says they look forward to finding out. The post's author leaves that question open.
Careful with the three-year figure. In the page, three years is Evans's anticipated time for a pollarded Sweet Coppin stem to reach 3 or 4 inches across and be ready to cut again, with fruit possible in between. It is an expectation, not a measured time to first fruit.
What we can and cannot say
From this page alone, we cannot say how long any apple tree takes to fruit after being coppiced or pollarded. The page gives no measured fruit-after-cut result, and twelve trees on one farm in Herefordshire cannot stand in for your climate, soil, variety and rootstock. For local advice on cutting back established fruit trees, ask your regional extension service.
A per-tree record that answers it for your trees
You do not need a trial of your own to get a useful answer. You need to write down the same few things for each cut tree, every time. Copy this onto paper or a spreadsheet, one block per tree, one line per visit. Our piece on pruning records covers the general habits; these are the fields specific to a hard cut.
Fields to record once, on the day you cut
- Tree ID: a stable code that matches the tag, your plan and every later line. Never reuse it.
- Variety and rootstock: written the same way each time, as recorded at planting (our scion provenance piece explains keeping this straight). Note if it is ungrafted.
- Age of the tree at the cut, and its crop the season before, even if only "none" or "light".
- Cut date.
- Cut type in your own words: coppiced to near the ground, or pollarded, and the height of the cut from the ground in centimetres or inches.
- A photo of the whole tree from a marked spot, and a close photo of the cut surface.
- Whether you remove any fruit or blossom in later seasons. This changes how you read the result.
Fields to record on each later visit
- Visit date.
- Regrowth: number of new shoots, length of the longest shoot, and the diameter of the thickest shoot, measured at a marked point so you measure the same place each time.
- Blossom: the date you first see blossom on the tree after the cut, or "none seen" for that season.
- Fruit: the date you first see fruit set, and whether it stayed to harvest. Write "none" rather than leaving it blank.
- Harvest: pick date and a count or weight, with the unit. Even a rough bucket count is better than a blank if you say what it is.
- Problems and a same-spot photo.
When to record
- On the cut day: the once-only fields and both photos.
- Mid and late in the first growing season: regrowth and a photo.
- In spring each year, when blossom is due, so a missing blossom is recorded as missing rather than forgotten.
- At harvest each year, even in years with no fruit.
If you cut several trees, keep one or two uncut trees of each type as a comparison and record them with the same fields. Without that, differences in the log could come from anything.
Reading the record after one season
One season shows you the recovery pattern of the tree this year, not a rule.
- Compare regrowth across your cut trees using the same measurement point. Large differences between trees of the same variety and rootstock are worth a note about the site, shade and soil before you blame the cut.
- Check blossom and fruit for the first season after the cut. If you saw none, write "none observed" (or "not checked" if you did not look), and treat it as one data point. It does not tell you the tree will not fruit in year two.
- Compare against your uncut comparison trees. If they also had a poor year, a weather or cropping pattern may explain it, not the cut.
- Look at the photos side by side before the numbers. They catch things you did not measure.
Reading the record after several seasons
- Time from the cut to the first observed blossom and the first observed fruit. This is the number the commenter asked for. Compare by variety and rootstock once you have a few trees.
- Fruit versus regrowth. Put each year's harvest next to that year's regrowth. If fruit years tend to be weak growth years on your trees, this is where you would see it.
- Second cut. Start a new cut block with its own date and keep the old one. The interval between cuts is also a result.
- Cut surfaces. A reader on the same post wondered whether repeated coppicing leads to decay around old cut surfaces. The page does not answer that. Your photos of each cut over the years will at least show what is visible from outside, which is a reason to keep taking them.
After several seasons you will have a record of whether and when each tracked tree was first seen to blossom and fruit after its cut, with the trees that have not fruited yet written next to the ones that have. Our flowering and fruit-set piece and the per-tree harvest records piece cover the blossom and harvest lines in more depth.
Paper first, an app if you want it
A notebook with one page per cut tree and a photo from the same marked spot each visit is enough, and so is a spreadsheet. If you would rather see your trees on a map and keep the photos and notes attached to each one on your iPhone, CanopyTwin does that, with a 30-day free trial. It is a convenience, not a requirement, and the record works the same on paper.
Turn your orchard into a digital twin
CanopyTwin does the survey-to-map pipeline for you — QR tree tags, a live satellite map, and AI fruit counts from your photos. Start free, no card required.
Keep reading
- Pruning Records for Fruit Trees: What to Log, and Why the Photos Matter More Than the Prose7 min →
- Tracking Flowering and Fruit Set, Tree by Tree7 min →
- How to Keep Per-Tree Harvest Records: A Copyable Sheet for Pawpaw, Persimmon, Nut and Backyard Orchards8 min →
- Scion Provenance Records: What to Write Down When a Cultivar's Identity Is Uncertain8 min →