A harvest log is one line each time a crop comes out of the ground: the date, the crop and variety, the field or bed, the quantity, who picked it, and where it went. It takes a minute at the wash station and it answers three questions a farm otherwise guesses at. How much did each bed give? What did we have to sell each week last year? And if a buyer calls about a problem, which bed, which day, and who else got some? The last one needs a harvest lot, a short code written on the bin and on the invoice. Below is a log for a made-up market farm, how to code a lot, what the log tells you after a season, and the file.
The short version
- One row for each crop from each bed, each harvest day.
- Record the quantity in the unit you sell: heads, bunches, pounds, dozens.
- A harvest lot can be the date and the bed: 1116-B4.
- Write the lot on the bin, and on the invoice when you sell to a shop or a restaurant.
- Note what was culled, and why.
- Add up by bed at the end of the season for yield.
- TaroStack keeps each harvest as a lot and traces where it went. More below.
An example log
Three days at a small market farm.
| Date | Crop | Variety | Bed | Quantity | Picked by | Harvest lot | Where it went |
|---|---|---|---|---|---|---|---|
| Nov 16 | Lettuce | Green butterhead | B4 | 96 heads | KS | 1116-B4 | Farmers market |
| Nov 16 | Carrots | Nantes | B7 | 60 bunches | KS | 1116-B7 | Farmers market |
| Nov 17 | Kale | Lacinato | B2 | 45 bunches | ML | 1117-B2 | CSA boxes |
| Nov 17 | Lettuce | Green butterhead | B4 | 48 heads | ML | 1117-B4 | Restaurant order |
| Nov 18 | Tomatoes | Sungold | H1 | 38 lb | KS | 1118-H1 | Farm stand |
| Nov 18 | Eggs | Coop | 14 dozen | ML | 1118-EGG | Farm stand |
Quantity goes in the unit you sell in. If you pick into bins and sell by the bunch, count bunches after washing and packing, because that's what you have to sell.
Culls. The tomato row has a note: split after rain, 4 lb culled. Record what you threw out beside what you kept. A bed that gives 38 lb to sell and 4 lb to the compost is telling you something about the variety or the timing.
Where it went can be as plain as "farmers market". For a shop, a restaurant or a CSA, it's the start of knowing who received what.
The harvest lot
A lot is a batch of produce that shares a history: the same crop, the same bed, the same day. The code only has to be unique and easy to write on a bin with a marker.
| Code | Reads as |
|---|---|
| 1116-B4 | November 16, bed 4 |
| 1117-B4 | The same bed, picked the next day: a different lot |
| 1118-EGG | Eggs collected November 18 |
Write it on the harvest bin, keep it on the box, and put it on the invoice or delivery slip for wholesale customers. Then the restaurant's question has an answer: its lettuce was lot 1117-B4, bed 4, picked on the 17th by ML, and none of that lot went anywhere else. The lettuce from the same bed sold at the market the day before is a different lot. More on coding is in how to create lot numbers and traceability lot code.
If you're certified organic or audited for food safety, your certifier or auditor decides what a harvest record has to hold, and this log is a place to start. See organic system plan template and GAP certification.
What it tells you after a season
Add the log up by bed.
| Crop | Bed | Bed feet | Harvested so far | Per bed foot |
|---|---|---|---|---|
| Lettuce | B4 | 100 | 144 heads | 1.44 |
| Carrots | B7 | 100 | 60 bunches | 0.60 |
| Kale | B2 | 100 | 45 bunches | 0.45 |
Three days is too little to judge a bed. A season isn't. Yield for each foot of bed, set beside the price you got, is how you decide what to plant more of. And last year's log by week is next year's sales plan: you'll know roughly when the tomatoes start, peak and stop.
What's in the cooler and the shed between harvests is a different sheet: farm inventory template. For the stand itself, see farm stand inventory sheet.
Get the template
Download the harvest log template. Two sheets and a read-me: the log, with room for a season of rows, and a sheet for totals by bed. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. Print the log and keep it on a clipboard at the wash station if a screen there isn't practical.
Where this stops working
A clipboard at the wash station works until the pages have to be typed up, and in August nobody types. By October there's a stack of damp paper and no totals. The lot is on the bin and not on the invoice, so the day a buyer calls, tracing a box of lettuce means matching handwriting to delivery slips. And the log knows what was picked. It doesn't know what's still in the cooler.
How TaroStack does it
TaroStack keeps each harvest as a lot of stock.
A harvest comes in as a lot, with its date, its quantity and where it's stored.
What ships is recorded by lot, so a sales order to the restaurant knows which lot filled it.
Every lot is traced to the customers that got it. The recall report is one screen.
Stock goes out first-expired-first-out by default, so Monday's lettuce leaves before Tuesday's.
It works on a phone with no signal, in the field or the packing shed.
| The question | Clipboard | In TaroStack |
|---|---|---|
| Which lot did the restaurant get | Match slips by hand | On the order |
| Who else got that lot | Unknown | The recall report |
| What's in the cooler now | Go and look | Stock by lot and date |
| What did bed 4 give this season | Add up the pages | Lots received, by item |
TaroStack doesn't map your fields or plan your plantings. Lots, stock, customers, sales orders and the recall report are on every plan, from $9.99 a month. The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
