Does a Mixed Orchard Row Really Ripen Together? Keep a Harvest-Window Log

If you plant different varieties and species in the same row, the question you eventually want answered is simple: do they all come ready at once, or do they come in a sequence you can pick through over weeks? You will not know from the plan. You will know from a log. A harvest-window log records, for each tree, when you first picked and when you last picked, what you picked in between, and how much. After one season it shows you the shape of your picking calendar. After several, it shows whether that shape is stable or moves with the weather. This article explains the fields, then how to read the result.

The question people actually ask

It is a natural question for anyone planning a mixed planting, and it is one viewers put to Stefan Sobkowiak: his Q&A video series page on the Miracle Farms site (the post dated 8 August 2018) lists the viewer questions that the series set out to answer. Among them: which specific apple, pear and plum cultivars he has in each row and how he times his harvest by planting them together in the same rows, whether all the fruit trees in the same row ripen at the same time or only the apples, and, if some things ripen at different times in a given row, how he plans to coordinate harvest and how that rotation works.

That page, as we read it, is a list of questions and a link to the video; the text does not give the answers. So we cannot tell you what he plants or what dates he picks, and we do not. What the list does show is that growers ask it: whether the trees in one row ripen together or in sequence is not something a planting plan settles on its own. The only way to find out for your own row, soil and climate is to write the dates down.

The harvest-window log

Keep one row per tree per picking day, as you would in a per-tree harvest record, and then add a summary line per tree per season. Our piece on per-tree harvest records has the full daily sheet. The fields below are the ones that matter for ripening windows.

• Season (year) and Tree ID: a stable code that appears on the tag, the map and every row. Do not renumber between years.
• Cultivar and species: written the same way every year, including rootstock if it is a grafted tree.
• Row and position: which row and which place in the row, so you can see neighbours.
• Pick date: every date you actually picked from that tree, not just the first and last.
• Quantity for each pick: a count or weight, whatever you can do consistently. Even a rough bucket count is better than blank, as long as you say which unit you used.
• Ripeness note: a few words on what you were picking ("just coloured", "fully ripe", "windfalls only"). It is the most useful field and the one most often left out.
• Notes: weather, damage, birds, things that stopped you picking on a given day.

From the daily rows, work out a per-tree summary at the end of the season: first pick date, last pick date, number of picks, total yield, and window length in days (last pick minus first pick). Put the summary in its own table with one line per tree. That table is what you read.

Be honest about what counts as a pick

Two habits will quietly distort the log. First, if you start picking when you happen to have time rather than when the fruit is ready, your first-pick date measures your calendar, not the tree. Note when a pick was delayed. Second, windfalls are not the same as picked fruit. Record them in the same row but flag them, or keep a separate column, so a late tree that mostly dropped its fruit does not look like a long window.

Fruit that you leave unpicked also deserves a note. If a tree was never harvested because you were away, enter the season and the Tree ID with "not picked" so the gap is visible instead of the tree simply missing from the sheet.

Reading the log after one season

A single season gives you a map of one year, not a rule. It is still enough to answer some practical questions.

1. 1Sort the summary by first-pick date. This is your actual succession for the year, from first tree to last.
2. 2Draw it as bars on squared paper: one bar per tree, running from first pick to last pick, with the days along the bottom. Mark the days of heaviest picking. Overlaps and gaps are visible at once.
3. 3Look for gaps: stretches of days when nothing in the row was picked. Check your ripeness notes before you call it a gap in fruit, because a day with no picking can also mean you were busy or the crop was damaged. A confirmed gap is where your plan fell short for the year. Remember too that some fruit, European pears for example, is picked mature and ripened off the tree, so a pick date is a harvest date, not an eating date.
4. 4Look for overlaps: days when many trees were all ready together. Those are the days you will run out of buckets, time or storage, and the days when fruit is lost.
5. 5Compare neighbours in a row. If two trees you expected to ripen weeks apart have nearly the same window, the plan did not produce a succession. Look at the cultivar names before you blame the site.

Do not read too much into one year. A cold spring or a hot July can move everything earlier or later together, and a tree that is stressed or overloaded will behave differently from the same tree in an easier year. One season tells you where your orchard was this year.

Reading the log after several seasons

The value of keeping it grows with each year, because you can separate what is fixed from what moves.

• Order versus date: compare the sequence of the trees across years, not just the calendar dates. If the same variety is always first and another always last, the order is a property of the planting. If the dates all shift together, weather is the likely cause, but check your notes for a shared reason such as a delayed picking day first.
• Window length: a tree whose window is always short is easy to plan around. A tree whose window varies a lot from year to year needs slack in your plan.
• Persistent gaps: a gap that appears every year is a real hole in the succession, and the one to fix, either by adding a variety that ripens there or by planning storage across it.
• Persistent overlaps: if three trees always peak in the same week, that is a workload problem, and you may want to line up helpers, storage or processing for that week.
• Yield beside window: write the yield next to each window. A long window with tiny yield is not a succession worth planning around. A short window with a big yield is the one that needs a plan.
• Biennial or off years: if a tree's window or yield swings between alternate years, the multi-season table will show it, and you can plan the row around the average rather than the best year.

Keep the daily rows even after you have summarised them. They are what let you go back and ask a new question next year, for example how many days after the first pick half the crop was in.

From log to plan

Once you have two or three seasons, write the observed order for the row on one line and mark the stretches that stay empty or crowded. That is the evidence for a decision. You might plant to fill a persistent gap, start picking an overloaded tree at the early end of its normal harvest maturity, or decide that a variety whose window overlaps its neighbour's is not worth the space. The log will not tell you which to choose. It will tell you which problem you really have.

If a tree is replaced, keep its old rows under its old ID and start a new ID for the new tree. Our piece on replanting and gap-filling covers keeping the history straight when trees come and go.

Paper first, an app if you want it

A notebook with one page per row and a summary table at the back of the book is enough, and so is a spreadsheet with a Daily sheet and a Summary sheet. If you would rather see your trees on a map and keep the pick history 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 log works the same on paper.