Use this log to record vineyard identification details, harvest conditions and laboratory-style must measurements for each block or lot. Enter values as measured or estimated, and note the method used wherever precision matters. Fields marked as required must be completed before the record is considered complete.
This template is informational and general in nature. It does not replace laboratory analysis, bench trials, or advice from a qualified winemaking or laboratory professional. Any acid, nutrient or processing decisions should be verified through your own trials and local guidance.
Tip: the estimated alcohol by volume (eABV) column is calculated automatically from the measured sugar content using a simple conversion factor of 0.552.
Vineyard or estate name
Block or parcel identifier
Grape variety
Is the planting material or rootstock documented for this block?
Yes, fully documented
Partially documented
No documentation available
Unsure
Please record the clone and rootstock details
What information is available, and what is missing?
Vine age (years)
Harvest date
Harvest start time
Harvest ambient temperature (°C)
When was the ambient temperature recorded?
Before picking began
During picking
At the end of picking
Not recorded at a specific moment
Was the temperature reading taken in the shade?
What instrument was used?
Please describe where and how the temperature was measured, including any sun exposure.
Weather conditions at harvest
Approximate fruit weight harvested (kg)
Was the fruit harvested mechanically?
Please note machine settings or any sorting steps applied after harvest.
How was the fruit handled after hand picking?
Placed directly into bins or lugs
Field sorted before loading
Destemmed in the field
Other
Record how the sample submitted for analysis was collected. Sampling approach can influence measured sugar, acidity and pH values, so note any deviations from your usual routine.
Sampling method used for this lot
Composite sample across multiple rows
Whole-cluster sample from several picks
Individual berry sampling
Sample taken from the receiving bin or press pan
Other
Please describe the sampling method used.
Number of sampling points or vines included
Sample collection date and time
Was any visible mould, rot or shrivelling observed in the sample?
Which conditions were observed?
Surface mould on a small share of berries
Rotten or burst berries
Heavily shrivelled or raisined berries
Split skins
Off-odours in the sample
Unsure of the cause
Roughly what percentage of berries appeared affected?
Please describe the odour and when it was noticed.
Thank you. No visible condition issues are recorded for this sample.
Which ripening or condition indicators were noted in the berries?
Even ripening across the sample
Uneven ripening within clusters
Sunburned or bleached berries
Green or herbaceous berries
Bird or insect damage
None of the above noted
Other
Please describe the additional indicator observed.
Average berry weight (g)
Was the sample kept cool before analysis?
Approximate holding temperature (°C)
How long was the sample held before analysis, and under what conditions?
Additional notes on fruit condition or sampling
Enter one row per block or lot. The estimated alcohol by volume (eABV) column is calculated automatically from the measured sugar content.
Estimated alcohol by volume conversion used in this log
The 0.552 factor is a simple, widely used approximation. Actual alcohol outcomes depend on many factors, including fermentation behaviour and any additions or removals, so treat the value as an estimate only.
Must Analysis
Block ID | Sugar Content (Brix) | Titratable Acidity (g/L) | pH Level | Estimated Alcohol By Volume (eABV %) | ||
|---|---|---|---|---|---|---|
A | B | C | D | E | ||
1 | Block 7A North | 26.40 | 5.20 | 3.92 | 14.57 | |
2 | Block 3B Terrace | 23.10 | 6.40 | 3.45 | 12.75 | |
3 | 0.00 | |||||
4 | 0.00 | |||||
5 | 0.00 | |||||
6 | 0.00 | |||||
7 | 0.00 | |||||
8 | 0.00 | |||||
9 | 0.00 | |||||
10 | 0.00 |
The rows above are illustrative examples only. Replace them with your own measured values; the eABV column recalculates automatically.
How were the sugar, acidity and pH values determined?
Refractometer for Brix with laboratory titration and pH meter
Density or hydrometer-based estimate with bench titration
External laboratory report
Field estimate only
Other
Please record the laboratory name or report reference
Please describe how the estimates were made and the likely margin of error.
Were the pH readings temperature-compensated or calibrated before use?
Which calibration buffers were used?
Please note any known limitations of the pH readings in this record.
Sample temperature at the time of measurement (°C)
Interactive logic summary: this block is designed to appear automatically whenever any row in the Must Analysis table shows a pH level above 3.8 together with a sugar content (Brix) above 25. When both conditions are met, the recommendation text labelled "Acidification Strategy" is displayed below.
Acidification Strategy: Your recorded must values indicate a higher pH combined with high sugar. This combination can be associated with a finished wine that tastes softer or flatter in acidity and may be more sensitive during storage. Consider evaluating a modest tartaric acid adjustment through bench trials before committing to a full-lot addition. A common starting point for trials is to test small incremental additions in the range of roughly 0.5 to 2.0 g/L of tartaric acid, measuring the resulting pH and tasting each trial. Because responses vary with buffering, temperature and must composition, treat these figures as illustrative trial steps only, not as prescriptions, and confirm any final addition through your own bench results and qualified guidance.
If no row meets both conditions (pH above 3.8 and Brix above 25), no acidification recommendation is triggered and this section can be left as a general record of the decision made.
Acidification Strategy — Bench Trial Worksheet
Block ID | Current pH | Current Brix | Trial dose of tartaric acid (g/L) | Must volume for trial (L) | Total tartaric acid for trial (g) | Observed pH after trial | Tasting and observation notes | ||
|---|---|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | G | H | ||
1 | Block 7A North | 3.92 | 26.40 | 0.50 | 1.00 | 0.50 | 3.86 | Slightly brighter acidity; fruit still reads as ripe | |
2 | Block 7A North | 3.92 | 26.40 | 1.00 | 1.00 | 1.00 | 3.78 | Noticeable lift; check balance against tannin perception | |
3 | 0.00 | ||||||||
4 | 0.00 | ||||||||
5 | 0.00 | ||||||||
6 | 0.00 | ||||||||
7 | 0.00 | ||||||||
8 | 0.00 | ||||||||
9 | 0.00 | ||||||||
10 | 0.00 |
Which acidification approach are you considering for the affected lot?
Incremental tartaric acid bench trials
Addition calculated from laboratory titration results
Assess cold stability before deciding
Blend with a higher-acid lot
No acidification at this time
Other
Please outline the trial increments and how each trial will be evaluated.
How will cold stability be assessed, and what result would change your decision?
Which lot are you considering blending with?
Please record the reasoning for deferring any acidification.
Do you have bench trial facilities available for this lot?
Which trial tools will you use?
Analytical balance
Calibrated pH meter
Titration setup
Small-scale blending cylinders
Tasting panel or group evaluation
How do you plan to evaluate the adjustment, and who will assist?
How confident are you in the accuracy of the pH and Brix values that triggered this recommendation?
Not confident
Slightly confident
Moderately confident
Confident
Very confident
I understand that this recommendation is informational only and that any acid addition should be confirmed through bench trials and qualified advice.
Decision and follow-up notes for the Acidification Strategy
Intended fermentation approach for this lot
Spontaneous or ambient fermentation
Inoculated with selected yeast
Co-fermented with another variety
Whole-cluster or carbonic-style handling
Not yet decided
Other
Which yeast selection or rehydration protocol is planned?
What factors are still being considered?
Which vessel types are planned for this lot?
Stainless steel tank
Oak barrel
Concrete vessel
Amphora or clay vessel
Open-top fermenter
Other
How many barrels are planned?
Estimated lot volume (L)
Target fermentation temperature (°C)
Is any pre-fermentation adjustment under consideration?
Which adjustments are being considered?
Acid adjustment
Sugar adjustment
Water addition
Nutrient addition
Enzyme or tannin addition
Other
Please describe the acid adjustment being considered and the trial evidence supporting it.
Please describe the sugar adjustment being considered and the target level.
No pre-fermentation adjustments are recorded for this lot at this time.
Please rank the following priorities for this lot, from most to least important
Aroma retention | |
Colour extraction | |
Tannin structure | |
Acidity balance | |
Alcohol management | |
Fermentation reliability |
Planned processing steps between harvest and fermentation
Record every addition or correction applied to this lot, including the date, product, stated purpose and dose rate. Keep units consistent so the log can be reviewed later.
Additions and Corrections Log
Date | Product or addition | Stated purpose | Dose rate | Unit | Lot volume treated (L) | Applied by | Notes | ||
|---|---|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | G | H | ||
1 | 4/18/2027 | Tartaric acid | Acidity adjustment after bench trial | 1.000 | g/L | 1200.0 | Cellar assistant | Dissolved in a small volume of must before addition | |
2 | |||||||||
3 | |||||||||
4 | |||||||||
5 | |||||||||
6 | |||||||||
7 | |||||||||
8 | |||||||||
9 | |||||||||
10 |
Was any addition verified by a second person before application?
Who verified the addition?
Please note how the addition was checked and recorded.
All additions listed above were recorded at the time they were applied.
Capture a short sensory snapshot of the must or early wine, and note any further analysis you plan to request.
Please rate the following characteristics of the sample
Very low | Low | Moderate | High | Very high | |
|---|---|---|---|---|---|
Fruit aroma intensity | |||||
Perceived acidity on tasting | |||||
Sweetness impression | |||||
Tannin or texture impression | |||||
Overall balance |
Overall impression of fruit quality for this lot
How do you feel about the acidity balance at this stage?
Will additional laboratory analysis be commissioned for this lot?
Which analyses are planned?
Yeast-assimilable nitrogen
Malic and lactic acid
Volatile acidity
Microbiological plating
Mineral or elemental analysis
Other
Please specify the additional analysis requested.
Please note why further analysis is not planned at this time.
Date results are expected
Sensory and analytical observations
Review the entries above for completeness and internal consistency before signing. This record is intended as a working log for your own use and does not constitute certification or approval of any kind.
I have reviewed this record and confirm the entries reflect the information available to me.
Recorded by
Role or position
Date and time the record was completed
Signature
Would you like a copy of this record sent to you?
Email address for the copy
No copy will be sent.
How will this record be retained?
Saved in a digital cellar management system
Printed and filed in a paper logbook
Shared with a laboratory or consultant
Attached to a batch record
Other
Please describe where the record will be stored.
Analysis for Viticulture & Wine Chemistry Log — Harvest and Must Analysis Record
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
This form is a comprehensive harvest and must-analysis record designed to capture vineyard and block identification, harvest conditions, sampling methodology, laboratory-style must measurements, conditional acidification planning, fermentation intentions, processing additions, sensory impressions and record sign-off. Overall, the form demonstrates a strong grasp of the practical workflow involved in harvest assessment, combining free-text detail with structured numeric inputs, calculated columns and conditional follow-up logic. Its layered design supports both quick data entry and deeper documentation where precision matters.
The log is organised into clearly named sections that follow the natural sequence of a harvest and early-cellar workflow: identification, harvest conditions, sampling, must chemistry, conditional acidification planning, fermentation planning, processing additions, sensory follow-up and sign-off. This chronological arrangement helps a user move through the record in the order the information is naturally generated, which reduces back-tracking and supports consistent documentation across multiple lots.
The form collects a mix of identification data, environmental observations, quantitative chemistry values, qualitative condition notes and decision records. Numeric fields specify decimal precision, which promotes consistent units and improves the reliability of any later aggregation or comparison across blocks. Because the record may include personal identifiers (recorded-by name, optional email address) alongside production data, basic privacy considerations apply: retention method is captured at the end of the form, and users should ensure that any stored copies are handled in line with their own internal data practices.
The form is detailed, which suits a technical logging context but does impose a meaningful completion effort. Conditional follow-ups help by hiding irrelevant detail, and the use of yes/no gates with targeted branches keeps the path focused. Potential friction points include the overall length of the record, the number of optional descriptive fields, and the reliance on accurate numeric entry for the calculated columns. Placeholder text and example rows mitigate these points well, and the inclusion of a clear purpose section at the top sets expectations before the user begins.
This identifies the origin of the record and allows multiple logs to be grouped by property. It is a practical anchor for any later retrieval, comparison or reporting across harvests.
Recording the specific block supports lot-level traceability and allows chemistry results to be linked back to a defined area of the vineyard, which is useful when comparing performance between plantings.
Variety context is central to interpreting sugar, acidity and pH values, since expected ranges and processing responses differ between varieties. The placeholder examples help users enter a recognised variety name in a consistent format.
This question captures background planting information that can help explain vine performance and fruit composition. The conditional follow-ups gather detail only where documentation exists, which is an efficient use of screen space.
Vine age is a useful contextual variable when reviewing yield and composition trends over time. It is appropriately left optional, since it may not be known for every block.
The harvest date anchors the record in time and allows the log to be ordered and compared against other lots picked in the same season.
Capture of picking time adds context to temperature and fruit condition observations, since conditions can change noticeably across a picking day.
Ambient temperature at harvest can influence fruit condition, handling decisions and early processing choices. The field specifies one decimal place, which is proportionate for an ambient reading and supports consistent entry.
Specifying the moment of measurement improves the interpretability of the temperature value, since readings taken before, during or after picking may differ.
This follow-up addresses a common source of variation in field temperature readings. The branching questions collect instrument detail or exposure description only where relevant, which is a thoughtful design choice.
A short free-text weather note adds useful qualitative context to the numeric temperature and can help explain fruit condition observations recorded later in the form.
Yield information supports volume planning for fermentation vessels and helps relate chemistry results to the scale of the lot. The approximate framing is appropriate for field estimates.
Harvest method can affect fruit integrity and subsequent handling needs. The conditional follow-ups capture either machine settings or hand-picking handling steps, which keeps the detail relevant to the answer given.
Documenting how the analytical sample was collected helps others judge how representative the chemistry values may be. The option list covers common approaches and includes an open description for less typical methods.
This adds a simple measure of sampling coverage, which can be useful when reviewing consistency between lots or seasons.
Fruit condition observations can influence processing decisions and help explain unusual chemistry results. The nested follow-ups gather specifics such as affected percentage or odour description only when a condition is reported, which is efficient and reduces unnecessary prompts.
Qualitative ripening notes complement the numeric Brix and acidity values and can help explain uneven results. The multiple-choice format with an open option balances speed with flexibility.
Sample holding conditions can affect measured values, so recording temperature or holding time supports later interpretation of the results.
This table is the analytical core of the form, collecting block identifier, sugar content, titratable acidity and pH alongside an automatically calculated estimated alcohol by volume. The formula column applies a stated conversion factor of 0.552 to the Brix value, and the surrounding text appropriately describes the result as an estimate rather than a measured outcome. Decimal precision is defined for each numeric column, which supports consistent and comparable entries across rows.
Recording the measurement approach helps others assess the likely precision of the values. Follow-up prompts gather a laboratory reference or a description of field estimation methods where applicable.
Calibration and compensation details strengthen confidence in pH readings, which are used as an input to the conditional acidification logic elsewhere in the form.
Measurement temperature provides helpful context for interpreting pH and acidity values and is captured with one decimal place for practical consistency.
This section is designed to surface automatically when any Must Analysis row shows a pH above 3.8 together with Brix above 25. The recommendation text is framed as informational and suggests evaluating modest tartaric acid adjustments through bench trials, with clear language that the figures are illustrative trial steps rather than prescriptions. This conditional approach keeps the guidance targeted to relevant lots.
The worksheet supports structured trial planning, with a calculated total tartaric acid column derived from trial dose and must volume. Including observed pH after trial and tasting notes alongside the calculations creates a compact, reviewable trial record.
This question captures the decision pathway chosen, with follow-ups that gather trial increments, cold stability plans, blending candidates or reasons for deferral. It supports consistent decision documentation without prescribing a single approach.
Asking about available facilities helps record how a proposed adjustment will be evaluated, and the follow-ups capture either the tools to be used or an alternative evaluation plan.
This rating adds a useful self-assessment layer to the conditional recommendation, helping reviewers judge how much weight to place on the triggering measurements.
Recording the planned fermentation method, vessels and target conditions creates a forward-looking plan that can be compared with actual outcomes later. Conditional follow-ups gather yeast protocol details or open considerations only where relevant.
The ranking prompt surfaces the winemaking priorities guiding decisions for the lot, which can help explain choices recorded elsewhere in the form.
This table provides a structured record of every addition applied, including date, product, purpose, dose rate, unit, treated volume and responsible person. The calculated or clearly specified units support later review, and the accompanying verification question encourages basic double-checking of additions.
The matrix rating captures a concise sensory snapshot across aroma, acidity, sweetness, texture and balance, providing qualitative context alongside the measured chemistry values.
This question records planned follow-up testing and, through its follow-ups, either the specific analyses requested or the reason no further analysis is planned, which supports continuity of the record.
The sign-off section closes the record with a review confirmation, recorder identity, optional role, completion timestamp and signature. The accompanying retention question captures where the record will be stored, which supports orderly record-keeping practices.
This form is a well-structured and practically oriented harvest and must-analysis log. Its principal strengths are the logical workflow alignment, the use of calculated columns to reduce manual arithmetic, the conditional acidification block that surfaces guidance only when relevant thresholds are met, and the consistent attention to measurement method and sample handling. The inclusion of clear disclaimers appropriately positions the content as informational. Areas to consider for refinement include the overall length of the record, which may benefit from optional sections being clearly marked as skippable when time is limited, and the possibility of using conditional logic more widely to hide rarely used descriptive fields. The illustrative example rows, placeholder text and defined decimal precision all contribute positively to data consistency, and the form is likely to produce a detailed, reviewable record when completed with care.
Mandatory Question Analysis for Viticulture & Wine Chemistry Log — Harvest and Must Analysis Record
Important Note:
This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.
Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.
Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
Question: Vineyard or estate name
Recommendation: Requiring this field supports basic record identification and helps ensure each log can be associated with a property when records are later grouped or retrieved. In a multi-site or multi-vintage context, a consistent estate name reduces ambiguity during review. The form creator may wish to confirm whether a standardised naming convention is preferred so that entries remain comparable across submissions.
Question: Block or parcel identifier
Recommendation: Marking the block or parcel identifier as mandatory supports lot-level traceability and helps link chemistry results to a defined area of the vineyard. Because the Must Analysis table also references block identifiers, capturing this value at the start helps keep the record internally consistent. The necessity of this field depends on how granularly the form creator intends to track lots.
Question: Grape variety
Recommendation: Requiring grape variety helps ensure that recorded sugar, acidity and pH values can be interpreted in an appropriate varietal context. It is a relatively quick field to complete and materially improves the usefulness of the record when comparing lots. If the form is used for single-variety operations, the form creator may consider whether this field could be pre-filled rather than manually entered.
Question: Harvest date
Recommendation: A required harvest date anchors the record in time and supports ordering and comparison of lots within a season. It is a low-effort field that provides clear operational value for record-keeping and later review. Where records are created retrospectively, it may be helpful to note whether the date refers to picking, delivery or analysis.
Question: Harvest ambient temperature (°C)
Recommendation: Requiring the harvest ambient temperature supports the form’s stated purpose of capturing harvest conditions alongside must measurements. Since the value is used as contextual information rather than a calculation input, its necessity depends on how the form creator intends to use harvest-condition data. The defined one-decimal precision helps keep entries consistent.
Question: Recorded by
Recommendation: Requiring the recorder name supports accountability and helps clarify who supplied the information if questions arise later. It is a standard record-keeping practice for working logs of this kind. Form creators should consider how this identifier will be stored and whether any data protection notice is appropriate for their context.
Question: Signature
Recommendation: A required signature supports the review and confirmation step described in the sign-off section and helps signal that the record has been checked before submission. Its practical value depends on the form creator’s internal review process; where a simple confirmation is sufficient, a checkbox may be an alternative worth considering alongside or instead of a signature.
The form currently designates seven fields as mandatory, concentrated at the beginning of the record (vineyard name, block identifier, grape variety, harvest date and harvest ambient temperature) and at the end (recorded by and signature). This placement is generally sensible: it captures essential identification and context early, then closes with accountability, while leaving the detailed analytical, sensory and planning sections largely optional. This balance is likely to support reasonable completion rates without sacrificing the core identifying information needed for the record to be useful.
Note: The recommendations above are general operational observations intended to support the form creator’s own design decisions. Required-field choices should reflect the specific data needs and workflows of the intended use, and may vary between organisations and contexts.
To configure an element, select it on the form.