Diy Soap Making Logbook

Why I Track Every Batch of Soap I Make

Three years into cold process soap making, I finally stopped guessing why one batch turned out different from another. The answer wasn't more research. It was a spreadsheet. My soap recipes varied by humidity, water discount, fragrance oil load, and whether I had poured during trace or let it sit too long. Some of those variables made tiny differences. Others—like using too much liquid fragrance from a cheap supplier—guaranteed a separated mess. But without recording what actually happened, I couldn't tell the difference between "this one was slow" and "this one will never harden." So I built a Diy Soap Making Logbook. Not some fancy app. A Google Sheet with columns I actually use. Here's how it works and what the fields should be.

Diy Soap Making Logbook: The Columns That Matter

I start every entry with the date. Then the recipe name, which for me is usually just a shorthand like "OBS-BS-PO" for a bar using olive, beef tallow, and sweet orange fragrance. Don't overthink naming. You'll regret it when you have 40 entries and can't remember which one used the higher lye discount. Next come the superfat percentage and water discount. These two numbers alone explain more variation than almost anything else. A 5% superfat gives you a softer bar that dissolves faster. A 7% superfat feels luxurious but may not harden properly in humid climates. I track both because I've hit both problems. The fragrance load goes next. Milliliters per pound of oils. This is where people slip up. Most fragrance oils accelerate trace at 6% or higher in cold process. I learned that the hard way when a batch of cedarwood-bergamot soap turned to pudding in the pan. My logbook records the exact amount so I can see the pattern.

Then I log the pouring temperature, ambient room temperature, and whether the molds were pre-warmed. These feel minor until you're comparing winter batches to summer batches and wondering why the summer ones sat soft for eleven days instead of six. The trace type column is simple: light, medium, or heavy. Or just note if you added anything at trace—colorants, exfoliants, swirls. I stopped trying to standardize this. Every pour looks different, and trying to force identical trace just wastes time.

The Edge Case That Changed How I Log

Early on I only recorded ingredients and amounts. That worked fine until I had two batches with identical formulas that came out completely different. One batch developer's soda formed instantly. The other stayed fluid for twenty minutes. Same oils. Same lye. Same temperatures. The difference was the distilled water source. One batch used filtered tap water with trace minerals. The other used truly distilled water I'd bought in bulk. I wouldn't have caught that without logging the water type as a field. Now my logbook includes a column for water source, and I rarely get that surprise again. Here's another counter-intuitive thing beginners miss: lye batch variability doesn't matter nearly as much as tracking your curing time against hardness results. I measured half a dozen bars at day seven, fourteen, twenty-one, and thirty-five. The correlation between cure length and hardness was stronger than any difference from switching lye suppliers. If you're going to log anything obsessively, log when you cut and when you test hardness.

Practical Entry Template

My sheet has these columns in order: Date | Recipe | Oils (weighted) | Lye | Water source | Water discount % | Superfat % | Fragrance (ml) | Pour temp °C | Room temp °C | Trace level | Add-ins | Mold type | Unmold day | Cut day | First hardness test | Notes The first hardness test column is the one most people skip. Write down when the bar first feels solid enough to handle without denting. For me that's usually day 4 to day 7 depending on the tallow content. Recording it makes it stupidly easy to spot patterns later.

Notes is where I put anything weird. "Batch smelled like crayons after 24 hours." "Colors separated despite good emulsification." "Used too much titanium dioxide, looked chalky." Those notes sound pointless now. Six months later they're the only reason I stopped using certain color combinations.

What This System Doesn't Fix

A logbook won't save you from bad formulations. If your recipe is fundamentally unbalanced—too much coconut, not enough stability oils—no amount of tracking will make it wash well. The logbook shows you the failure pattern. It doesn't replace learning basic soap chemistry. It also won't help if you change variables without logging them. I once swapped from silicone mats to wooden bread-loaf molds and forgot to record it. Two months later I couldn't explain why my unmolding times had shifted by a full day. The logbook is only useful if you actually fill it in, which sounds obvious until you've had a long day and just want to move on. If you want something simpler than a spreadsheet, there are free templates online. Search for a cold process soap making journal template. The structure matters less than the habit of recording. I've seen people track their batches on index cards and still pull valuable patterns from the data. The format is secondary to consistency.

One thing I recommend against: don't try to log every micro-decision. I used to record the brand of each oil, the bucket size, the stirrer speed. That level of detail was exhausting and produced almost no useful signal. Stick to the variables that actually move the needle. Everything else is noise. After a year of entries, my logbook told me exactly which fragrance oils accelerated trace, which ones didn't, and which recipes needed a water discount adjustment for summer versus winter. That information saved me probably thirty pounds of failed batches. Worth the fifteen seconds per entry.