A fermentation log sheet has a row for each reading of each batch: the date, the batch number, the day of the ferment, the temperature, the pH, the target pH for that product, what the batch looked and smelled like, and anything you did. The sheet compares the reading with the target and says At target or Not yet. For fermented vegetables, the drop in pH is what makes the food safe, so this log is the record that the drop happened, on which day, for which batch. Below is a sheet with two batches in it, and the file.
The short version
- A row every time you take a reading, usually once a day.
- Batch number, day number, temperature, pH.
- The target pH on the same row, so the sheet can say whether you're there.
- Calibrate the meter before use and note it.
- TaroStack holds each reading on the batch record and keeps the batch on hold until it's released. More below.
An example: kimchi over five days
Brightwater Ferments is a made-up Portland ferment maker I use in these examples. Batch KC-1109 is napa kimchi, salted at 2.2% by weight, with a target of pH 4.2 inside five days:
| Date | Day | Temp | pH | Target | Status | Look and smell | Action |
|---|---|---|---|---|---|---|---|
| Nov 9 | 1 | 68°F | 5.9 | 4.2 | Not yet | Fresh, no activity | Packed in crocks, weighted |
| Nov 10 | 2 | 68°F | 5.3 | 4.2 | Not yet | Bubbles starting | |
| Nov 11 | 3 | 69°F | 4.7 | 4.2 | Not yet | Active, sour smell | |
| Nov 12 | 4 | 68°F | 4.3 | 4.2 | Not yet | Active | Keep going |
| Nov 13 | 5 | 68°F | 4.1 | 4.2 | At target | Sour, crisp | Packed and moved to the cooler |
A sauerkraut batch, SK-1110, runs on the same sheet with its own target of 3.8. On day 8 it reads 3.9: Not yet, keep going.
What the log is for
The curve. Read the pH column down: 5.9, 5.3, 4.7, 4.3, 4.1. A healthy ferment at a steady 68°F drops like that, fastest in the first days. A batch that sits at 5.3 on day 3 is telling you something: too cold, too much salt, a dead starter. You see it on day 3, not on day 6.
The decision. Day 4 read 4.3. That's close, and it's not 4.2. The row says Not yet and the action says keep going. The batch was packed on day 5, at 4.1. Close enough is how a soft limit becomes no limit.
The proof. The target and the number of days come from your own process and whatever supports it. They're an example here, not a rule for your kimchi. But once you've set them, the log is how you show a buyer or an inspector that every batch met them. A fuller plan around these readings is in kimchi HACCP plan.
Good habits
Take the reading the same way every time: same depth in the crock, brine and solids blended if that's your method, meter calibrated with fresh buffer. How to do that properly is in pH testing for acidified foods.
Write the temperature. A ferment that took five days at 68°F will take longer at 62°F, and the temperature column is what explains a slow batch.
Don't skip the look-and-smell column. Mold on the surface, a slimy brine or an off smell belong on the record with what you did about it.
Get the sheet
Download the fermentation log sheet. The log, with a status that works itself out, and a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. How long the finished jar keeps is in kimchi shelf life.
Where this stops working
Six crocks at different days, two products, readings on a clipboard that get typed in on Friday. The batch that's ready and the one that isn't look the same on the shelf. And nothing stops a helpful person from jarring KC-1109 on day 4.
How TaroStack does it
TaroStack keeps the readings on the batch and the batch off the shelf until it's ready.
The batch is on hold while it ferments. A new batch can be held, kept out of what's available to sell or pack, until you release it.
Readings are fields on the batch record. Each day's pH and temperature go into fields of your own, with initials. Print the batch-record form for the clipboard if that's how the kitchen works.
The cabbage has a lot too. Recording the batch takes the napa, the salt and the chili flakes off stock and notes which lots went in, automatically.
From crock to customer. Each order records the lots it shipped. If a batch has to come back, one report shows every store it reached.
| The job | Clipboard | In TaroStack |
|---|---|---|
| Today's pH for each crock | A sheet, typed up later | Fields on the batch record |
| A batch that isn't ready | A note on the crock | On hold until released |
| Which cabbage lot is in a batch | Not recorded | On the batch record |
| Proof for a buyer | Find the right page | The batch's own record |
Recipes, batches, lots and holds are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). 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.
