Pour over brew log for V60, Chemex, Kalita, and manual drip methods

Lock the baseline

Start with a reference brew: 15g coffee, 250g water, 13 on the grind setting, 93 C, 30s bloom, 2:30 total time. Save every deviation from this baseline so you can trace cause and effect.

Change one variable at a time

A pour over log is most useful when you change one variable per brew: grind, ratio, water temperature, pour speed, or bloom time. Changing everything at once makes the log hard to learn from.

Describe taste with purpose

Instead of good or bad, use tasting language that points to a next adjustment: under-extracted suggests finer grind or hotter water; over-extracted suggests coarser grind or cooler water; bitter suggests channeling or uneven pour.

Note the pour structure

Save how many pours, pour weight per pour, pour speed, and whether you used a circling or center pour. Pour structure is one of the most under-recorded variables.

Build toward a recipe

After 10-15 brews with the same bean, you should have enough data to write a repeatable recipe: the exact settings that produce your preferred taste. Save it as a reference brew.

How this becomes an OmniSaver record

The practical output of this guide is not another long note. It is a compact record with enough structure to help you act later: the source, the situation, the important fields, the reason it mattered, and the next step.

For Taste, that means choosing the smallest Saver that matches the moment and saving only the fields that will help you compare, repeat, prove, decide, or reuse the context later.

A simple workflow

Start by saving one real example while the context is fresh. Review it after the outcome is visible. Compare it with the next similar record. Reuse the best version when the situation appears again.

This save, review, compare, reuse loop is the reason OmniSaver uses tiny apps instead of one giant database. Each Saver keeps the record close to the behavior it supports.