〜 Fig variety verification board 〜
Articles|Varieties|Board|About|[Log in]|
← All articles

Fig Cultivation Record-Keeping|Logging Harvest Dates and Yields to Stabilize Next Year's Crop

Updated: 2026-10-21

Fig harvest timing and yield can vary considerably from year to year, even when the plant appears to be grown the same way. Memory alone rarely preserves the details needed to explain the difference. Keeping a simple cultivation record can provide the information needed to make harvests more consistent in later years. This article outlines an easy-to-maintain method for keeping such records.

Figs beginning to ripen
© Emőke Dénes, CC BY-SA 4.0

Why Harvest Records Are Useful

The ripening time of figs varies from year to year depending on temperature, sunlight, watering, and the severity of pruning. Keeping records makes it possible to notice differences such as "this year is 10 days later than last year" and to consider their causes. Likewise, problems such as small fruit or weak flavor are easier to address when compared with the previous year's care.

Minimum items to include

Don't try to do too much at once, or you won't keep it up. The following items are enough to start with.

  • First harvest date and last harvest date (record summer crop and fall crop separately)
  • Number of fruit harvested, or approximate weight
  • Fruit condition (size, sweetness, and presence of splitting or rot)
  • Weather notes (prolonged rain, extreme heat, typhoons, etc.)
  • Dates of fertilizing, pruning, fruit thinning, and other tasks performed

Choosing a Record-Keeping Method

Smartphone notes and photos

The easiest method to sustain is to take one photo at each harvest. Photos keep the date, so you can review the timing and fruit size later. Adding a single line to a notes app, such as "3 fruit harvested, sweet," is also useful enough.

Spreadsheet software and planners

To compare results from year to year, it helps to organize the records in a table with columns for the date, the number of fruit, and notes. A paper growing journal works just as well. What matters most is keeping the records in the same format each year.

When growing multiple trees or varieties

Fruiting time and yield differ between varieties and between containers. Always record the variety name (or the container's label number) alongside each entry. For a plant whose name you cannot confirm, write "variety unknown (source: ○○)" so you will not confuse it when you review the records later. If you are unsure how to identify a variety, you can look up its characteristics in the variety guide or ask for advice with photos on the forum. However, a photo alone cannot establish a variety with certainty, so it is practical to record such identifications with a qualifier such as "probably this variety."

Using Records to Guide Next Year's Management

  1. Check the first harvest date from the previous year, and review fertilizing and watering from about two to three weeks before that date.
  2. Review pruning position, sun exposure, and fruit set on branches or in years where yield was low.
  3. In seasons with heavy splitting or rot, review rainfall records and consider rain protection and harvest timing accordingly.
  4. Repeat the tasks that worked at the same time of year the following season, and if a task had no effect, change only one thing and compare the results.

Changing only one condition at a time makes it easier to judge what caused the difference in results.

Summary

Growing records do not need to be elaborate. Keeping the same five items each year (harvest date, number of fruit, condition, weather, and tasks performed), using photos or brief notes, will gradually reveal the habits of your fig. To begin, record one photo and a single line of notes for the remaining harvest this season.

Not sure what your fig is?

Post a photo of the leaves and fruit and see what other growers think. "Maybe" is a perfectly good answer here.

Post your fig

Not going the way you hoped?

Ask other growers on the board. A photo gets you a faster answer.

2views
Share:𝕏LINEf

Reply0

Log in to comment