What should I record in my harvest history?

Log the harvest date, crop name, variety, bed location, weight, quality rating (Excellent to Poor), and any notes. This complete record reveals patterns that memory alone cannot captureu2014identifying your best-performing varieties and beds, and enabling accurate year-over-year comparisons of your garden's productivity.

How can detailed harvest records help you plan your garden?

By tracking yields and timing across seasons, you discover which crops thrive in which beds, when to expect peak production, and which varieties consistently deliver. Use this data to estimate how many plants you needu2014for example, if broccoli averages 500g per pick and you want 1kg weekly, you need two harvests per week.

When should I start comparing my harvests year-over-year?

After 12 months of consistent logging, seasonal patterns emerge showing whether crops are earlier or later than last year, which varieties are more productive, and how your garden's conditions affect yield and quality. These insights replace guesswork with evidence-based planning for the next season.

What patterns can I spot from tracking harvest history?

Detailed harvest records reveal peak production weeks, average yields per pick, seasonal timing, quality consistency, and which beds perform best. This evidence shows whether varieties are worth repeating, when to expect harvests, and which planting strategies deliver the best results.

How do I know if a vegetable variety is worth growing again?

Compare total harvests, average yield per pick, and quality ratings across seasons. If a variety consistently produces healthy yields of excellent quality, it's worth repeating; if yields are consistently light or quality is poor, try a different variety next season.

Harvest history — every kilo, every crop

Running your garden5 min read

Every harvest you’ve ever logged, in one table — not just the totals but every individual pick with date, weight, and quality. The kind of granular log that, multiplied across a real season, lets you compare year-over-year and spot patterns no single-season memory can.

All-timeFull history

CSVExport format

SortableAny column

FilterableBy crop

On this page

The columns
Sorting and filtering
Running totals per crop
Export
Archiving vs deleting

The columns

Column	Shows
Date	When you harvested
Crop	Plant name (e.g. “Broccoli”)
Variety	The variety you entered (e.g. “Calabrese”)
Bed	Where it came from
Quantity	Weight in kg (stored internally; displayed in g where appropriate)
Quality	Excellent / Good / Fair / Poor
Notes	Any free-text notes from the harvest form

Sorting and filtering

The table is sorted by date descending by default (newest at top). Click any column header to sort by that column. Click again to reverse the sort direction.

The filter input at the top takes a crop name or keyword:

Type “broccoli” — only broccoli harvests show
Type “front” — only harvests from beds with “front” in the name
Type “first” — matches harvests with “first” in the notes (e.g. “first pick of season”)

Running totals per crop

Below the table, a mini-summary shows total kg harvested per crop in the current season:

Crop	Total this season	Harvests	Avg per pick
Broccoli	1.95 kg	4	487 g
Silverbeet	1.40 kg	5	280 g
Kale	0.85 kg	3	283 g
Bok choy	0.55 kg	1	550 g

The “Avg per pick” column is useful for planning — if broccoli averages 487 g per pick and you want 1 kg per week of broccoli, you need 2 picks per week, implying enough plants that two will be ready on consecutive days.

Export

The Download CSV button (top-right of the table) saves the full history as a CSV file. Useful for:

Archiving end of season. Download, rename to “autumn-2026.csv”, keep locally.
Custom analysis. Paste into Google Sheets or Excel for charts, pivot tables, moving averages.
Backup before pulling plants. When you archive a plant, its harvest records stay but feel more secure with an off-site copy.
Sharing with a cooperative. If you’re in a seed-saver or swap network, sharing harvest data helps the group plan collective plantings.

CSV format

date,crop,variety,bed,quantity_kg,quality,notes
2026-04-12,Broccoli,Calabrese,Front raised bed,0.450,Excellent,First pick of season
2026-04-15,Silverbeet,Fordhook Giant,Front raised bed,0.280,Good,Outer leaves
...

Multi-season view

The history shows everything you’ve logged since you joined. After 12 months you’ll start seeing season-over-season patterns — last autumn’s kale harvest was heavier than this autumn’s; broccoli performs better in the front bed than the back. Keep logging.

Archiving vs deleting

When a plant is finished (pulled out, gone to seed, dead), mark it archived rather than deleted. Archived plants stop appearing in your active list, but their harvest history stays in the record.

Delete only:

Genuine duplicates (you accidentally logged the same harvest twice)
Test entries from when you were learning the system
Entries where you realised the crop or weight was wildly wrong and you’d rather not see it in the record

Historical data has value even when imperfect — one season’s less-than-optimal harvest is useful context for next season’s planning. Only delete when you’re confident the record shouldn’t exist.

Year-over-year comparison

After 12+ months of consistent logging, the real value of the harvest history emerges — you can compare this autumn’s crop to last autumn’s at the individual crop level. Our demo garden’s first year of data is about to enable this for the Dayboro plot.

Things you can compare year-over-year from the history:

Total kg per crop per season
First-harvest date vs expected (earlier or later than last year?)
Peak harvest week
Season length (first-to-last harvest)
Quality distribution (more Excellent/Good ratings this year?)

← PreviousRead your ROI report Next →The weekly Gardener Digest