How to track multiple ferments at once (without forgetting any)
One jar, you can keep in your head. The trouble starts with the second — and blows up with the third. A water kefir finishing its F1 tomorrow, a kombucha started… Tuesday? Wednesday?, two bottles of ginger F2 in the cupboard for an unknown number of days. Add a tasting whose verdict you meant to write down, and there it is: you're no longer tracking your ferments — they're tracking you.
This isn't a discipline problem, it's arithmetic: three asynchronous batches, each with 2-3 phases (the F1 in an open jar, the F2 in a sealed bottle, the cold rest), means six to nine staggered deadlines to hold in your head at all times. No brain is built for that — and the stakes aren't just flavour: an F2 forgotten three days in the warmth ends as a geyser, sometimes as shattered glass.
Let's look at the existing methods, honestly.
Method 1: the paper notebook
The classic. One page per batch: start date, recipe, observations, verdict.
What works: the tasting notes. Writing down what you tasted by hand is pleasant and it sticks. For the history of a recipe you repeat identically, a notebook does the job.
The limits: a notebook doesn't warn you. You have to remember to open it to learn that an F2 is ready — and remembering is precisely the thing that's failing. As for finding "the mango kefir version that was perfect" across 40 handwritten pages: good luck.
Method 2: the spreadsheet
One row per batch, date-phase-notes columns, maybe a formula computing the end date.
What works: the overview. A spreadsheet sorted by date shows what's in progress, and the data is reusable.
The limits: everything is manual — every phase change is an entry, and one missed entry makes the whole sheet a lie. No reminders either (or you build a notification system on top… and you've reinvented an app, only more fragile). On a phone, in a kitchen with sugar on your hands, the experience is rough.
Method 3: sticky notes and jar labels
Date in marker on the lid, sticky note on the cupboard door.
What works: the info lives on the object — no mixing up two jars. Keep that habit no matter what.
The limits: the label says when the batch started, not when to act. It can't see the bottles inside the closed cupboard, keeps no history, and peels off at the first wash.
What you actually need
Cross-reference the limits and the spec writes itself. You need a system that:
- knows the phases of each recipe (F1 → F2 → cold), with their durations;
- tells you when to act, without you having to think about it;
- keeps a history per recipe, so you can reproduce what worked;
- updates in two taps, wet hands included.
You can rig this up with a spreadsheet + alarms + a notebook. It's doable — and it's exactly the rig that FermPal replaces: every batch moves phase by phase along its recipe, with durations and temperatures; the home screen shows where each jar stands and what's coming due; you log the tasting when you archive, and every recipe keeps its versions so you can find the ratio that fizzed every single time. The free plan covers 3 active batches — exactly the threshold where memory gives out.
Track my ferments with FermPal (free) →
The short version
| Method | Overview | Due dates visible | History | Effort |
|---|---|---|---|---|
| Paper notebook | ❌ | ❌ | 🟡 hard to search | Medium |
| Spreadsheet | ✅ | ❌ (DIY) | ✅ | High |
| Sticky notes / labels | 🟡 jar by jar | ❌ | ❌ | Low |
| Dedicated digital log | ✅ | ✅ | ✅ per recipe | Low |
Whatever the method: write the date on every container, set one weekly check-in day, and never start an F2 without knowing when you'll take it out. The rest is tooling.
Go further: the online fermentation tracker, and if you're just starting out, the water kefir guide (grains, F1, F2).