The batch log, and the fields that matter
Updated
On this page6
Why it matters more here
A quick pickle can be checked in the finished jar. A ferment cannot be re-run, and by the time softness or an off smell shows up, the four warm afternoons in week two are history. Without a record, the honest answer to why a batch failed is that you do not know, and the next batch is a guess.
The fields
- Batch code, and which craft: fermented or quick.
- Cucumbers: grower, date picked, date brined. The gap between those two is a named cause of two different failures.
- Brine: salt weight, water weight, vinegar strength.
- Temperature, as a daily maximum rather than a spot reading.
- Tending: when scum was removed, when the weight was reset.
- Finish: date judged done, and on what basis.
- The pH reading, with the date and the meter.
- Yield, and what went to seconds.
Write it during, not after
A log reconstructed at the end of a packing day is a log of what you intended. The value is entirely in it being contemporaneous, which means it has to be physically where the work happens and simple enough to fill in with wet hands.
Then actually read it
The point is comparison across batches, which only happens if the fields are the same every time and somebody looks. One afternoon at the end of a season spent lining up the soft batches against the temperature column is worth more than any single page on this property.
It is also the regulatory record
For a commercial acidified food the log stops being a private diagnostic and becomes evidence that the filed process was followed. That changes what it has to contain and how long it has to be kept, and it is worth asking the process authority what they expect to see rather than designing a form and hoping. A log built for both purposes from the start is one log; a log built for curiosity and later retrofitted is two.
Keep it legible and keep it. The season you will most want to look back at is the one you were too busy to write up properly.