Honey harvest records: what to track and why
You pulled supers, you extracted, and now there are buckets on the kitchen floor. Whatever you write down in the next hour is most of what you will ever know about this harvest. Here is what is worth recording, and what each field pays you back later.
The fields that matter
Harvest date. Not the extraction date (record that too if they differ). The harvest date tells you what was blooming, which is how you will name this honey later, and it anchors year-over-year comparison: "we pulled two weeks earlier than last season" is a sentence you can only say with dates.
Which yard and which hives. Even a rough list. If one colony out-produces the rest three years running, that is queen stock worth raising from, and you will never spot it without attribution. If you can, note ounces or frames per hive; if you cannot, at least record which hives contributed so the season totals stay honest.
Frames or supers pulled. A quick count. It turns "good year" into "41 medium frames against 28 last July", and it helps you sanity-check extraction yield (a medium frame typically gives roughly 3 to 4 pounds, but your own average, from your own records, beats any rule of thumb).
Total weight or volume. Weigh the buckets before they disappear into bottling. This is the number your season lives on: yield per hive, price-per-pound math, and how much you can promise the people already asking.
Moisture reading. Take it at extraction, per batch, with a refractometer. Honey above roughly 18.6% moisture can ferment in the jar; below it, it keeps essentially forever. One reading now saves you from discovering foam on a customer's shelf in January. (More on this in our moisture guide.)
Floral source, honestly. "Mostly wildflower, some clover" is a fine record. If you sell honey labeled "clover", the label is a claim, and your harvest note is the only evidence you have that it is true. Write what was blooming and what you actually believe the bees worked.
A batch identifier. Anything consistent: 2026-JUL-A works. Every jar you later fill should trace back through a bottling run to one of these identifiers. If a customer ever reports a problem, the batch id is the difference between pulling six jars and pulling everything.
Conditions, optionally. A line about the weather and the season ("dry June, flow stopped early") is what makes the record readable in three years. Skip it when there is nothing to say.
Why bother
- Blending decisions. When one batch reads 17.2% moisture and another 19.4%, records are what let you blend deliberately instead of hoping.
- Labeling and selling. Net weight, floral claims, and lot traceability all come from harvest and bottling records. See the records you need to sell honey.
- Better beekeeping. Yield per hive, per yard, per year is the feedback loop for every decision you make: queen sources, yard locations, when to super.
- Taxes. If honey income lands on a Schedule F, harvest and sales records are the paper trail.
A minimal template
If you keep nothing else, keep this per batch: date, yard, hive list, frames pulled, weight, moisture %, floral source, batch id. Eight fields, two minutes, once or twice a year per yard.
Where HiveMind AI helps
HiveMind AI has a harvest record with exactly these fields built in. Batch ids are generated from the harvest date so they stay consistent, per-hive ounces and frames are optional so the record never blocks you, and the moisture reading follows the batch through bottling, where a reading above 18.6% is flagged before it goes in a jar. Harvests connect forward to bottling runs, inventory, and sales, so a jar traces back to the hives it came from. The Free plan covers up to 10 hives; see what each plan includes.