Vineyard blocks, the spray diary and EU-compliant records

Blocks are the unit of record for everything in the vineyard module — sprays, scouting, soil, yield and the weather-driven forecasts. Set them up once and every record hangs off them.

Create a block

1. Go to /vineyard/blocks — the Block Register — and press + Add Block.
2. Enter the Block Name (required), plus variety, clone, rootstock, area in hectares, trellis system and certification status.
3. Give the block a location by entering its Latitude and Longitude in the Where is this block? fields — long-press the spot in Google Maps and copy the two numbers, or use the centre of the block. (The separate GeoJSON boundary textarea is optional — only for a polygon outline you already have from a mapping tool; its centre is used as a fallback if you leave latitude and longitude blank.) The block's coordinates drive the nightly per-block weather feed, which in turn powers phenology and disease forecasts, so don't skip this.
4. Press Create Block.

The free Cellar Hand plan includes 2 blocks; Winemaker (€19/yr) allows 3, and the Vineyard plan (€39/mo) and above are unlimited.

Log a spray

Sprays are logged as activities on a block:

1. Open the block, switch to the activities tab and press + Log Activity.
2. Set the Activity Type to SPRAY, with the date, operator and equipment.
3. Under Chemical Applications, press + Add Chemical for each product: chemical name, active ingredient, registration number, category, FRAC code, rate per hectare, total quantity, PHI (days) and REI (hours), and the target pest or disease.
4. Save. From the PHI, MakeWine calculates the withdrawal date automatically — the earliest safe harvest date is shown against the application. If you have applied the same FRAC group too often, the entry is flagged with a FRAC rotation risk warning for resistance management. That warning is a Vineyard-plan feature (Vineyard, Estate and Winery) — on Cellar Hand, Winemaker and Compliance you still log the spray and get the PHI withdrawal date, but not the rotation flag.

The spray diary and CSV export

/vineyard/blocks records roll up into the Spray Diary at /vineyard/spray-diary — one register across all blocks, filterable by block, category and date range. A second tab, FRAC Group Usage, summarises applications per FRAC group and flags groups worth rotating.

Press Export PPP register (CSV) to download an inspection-ready file. Regulation (EU) 2023/564 requires plant-protection-product records to be kept electronically from 1 January 2026; the export covers the mandated fields — product, authorisation number, date, dose, crop and area treated (ha) — plus the agronomic extras (FRAC, PHI, REI, withdrawal date, operator, weather) that buyers and inspectors ask for.

Scouting

On the block's scouting tab, press + Record Visit to record a walk. The record is the visit, not the finding — a clean walk that found nothing is saved with an outcome of Clean, and no pest or disease at all. That matters more than it sounds: a clean walk is exactly what IPM practice and certification audits want to see, and it is the record most systems make impossible to keep.

When there is something to report, you choose the pest or disease from a fixed vocabulary and record severity as a percentage of tissue affected — the standard SAD steps (1, 3, 6, 12, 25, 50, 75) rather than a vague band — plus the percentage of rows affected, whether the economic threshold was exceeded, the action taken, and photos. Visits appear on the block timeline and feed your decision record when a spray follows an observation.

One term in that vocabulary is deliberately broad: grapevine yellows covers Flavescence dorée and Bois noir together, because they cannot be told apart by eye and FD is a notifiable disease in much of the EU. Recording a suspicion as the specific one is a legal hazard; recording what you actually saw is not.