How to Keep a Sake Tasting Journal That Actually Teaches You Something

My first tasting journal was a disaster. Three months into my apprenticeship at a kura in Nada, the toji walked me through my first real sensory evaluation of a moromi sample—the fermenting mash that eventually becomes sake. He asked what I smelled. I wrote “good.” He asked me to be more specific. I wrote “very good.” He glanced at my notebook, said nothing, moved on.

I still have that notebook. Embarrassing, but it taught me something: a tasting journal is only as useful as the language you put into it. “Good” tells future-you nothing. “Ripe pear, faint lactic tang, finishes cleaner than yesterday’s sample” gives future-you a roadmap. The gap between those two kinds of notes is where actual learning lives.

What follows is the system I’ve refined over the years—first as an apprentice scribbling in a kura basement, then as an educator running tasting sessions for English-speaking professionals and enthusiasts. Not the only way to keep a sake journal. But one that’s proven useful for people who want to get better at tasting, not just record what they drank.

Why Most Sake Notes Fail (And Mine Did Too)

The problem with most tasting notes isn’t laziness. People try to capture too much, too fast, in a format that doesn’t serve them later. You taste something interesting, write a stream of consciousness, and three months later—trying to remember whether that Junmai from the izakaya in Kyoto had more umami than the one from the shop in Tokyo—your notes are useless. A pile of adjectives with no structure.

My Nada notebook was full of this. Pages of unstructured impressions I couldn’t cross-reference. I’d taste a sake and write “smooth, nice.” A week later, something similar: “smooth, nice” again. Were they actually similar? No way to know, because “smooth” meant nothing specific.

The fix isn’t more words. It’s better scaffolding. A structured journal gives you consistent reference points so you can compare across tastings, notice patterns, and—most importantly—catch yourself when your vocabulary drifts.

The Four-Part Structure I Use for Every Entry

After about a year of bad notes, I developed a template I still use today, both for my own drinking and in the tasting classes I teach. Four sections, filled in this order:

1. Context before flavor. Before writing anything about what’s in the glass, I note the date, the sake’s name (in Japanese and English if both are available), the brewery, the region, the grade (Junmai, Ginjo, Honjozo, etc.), the rice variety if listed, the polishing ratio (seimaibuai), and the serving temperature. Also where I’m drinking it—a bar, a friend’s house, a brewery tasting room—and whether I’m eating anything with it. Thirty seconds. Saves enormous frustration later. Sake changes with temperature, food, and context. Taste the same Junmai at 5°C in a wine bar alongside oysters, then again at 40°C at home with grilled chicken? Two different experiences. Your notes should reflect that.

2. Aroma first, in three tiers. I smell the sake before tasting it, breaking notes into three categories: primary, secondary, and what I call “background.” Primary aromas are the obvious ones—fruit, floral, grain. Secondary aromas are subtler, often emerging after the sake sits in the glass for a minute—spice, nuttiness, lactic notes. Background is what I detect underneath everything: mineral, earth, sometimes a faint alcohol warmth that tells me about structure. This tiering forces me to keep smelling rather than grabbing the first descriptor and moving on.

I also note intensity. A sake with a massive ginjo-ka (the aromatic ester profile typical of Ginjo-grade sake) that hits you the moment the glass approaches your nose is different from one that whispers its aromas and rewards patience. Intensity matters.

3. Palate in plain language, then in specific terms. When I taste, I do two passes. First: my immediate, honest reaction in whatever words come naturally. “This is bright.” “This coats my tongue.” “This disappears too fast.” No jargon, no trying to sound knowledgeable. Just the raw impression.

Then I go back and sharpen those notes. “Bright” becomes “high acidity, clean finish, almost tart on the front palate.” “Coats my tongue” becomes “full body, noticeable umami, viscosity higher than the Junmai I had last week.” “Disappears too fast” becomes “short finish, low sweetness, the sake doesn’t linger and I’m not sure if that’s a flaw or the intended style.”

The two-pass approach exists because the first reaction is often the most honest, and jumping straight to technical language can lose the thing that made the sake interesting to you. But the technical language is what lets you compare and learn. You need both.

4. One question for next time. This is the section most people skip, and it’s the one that turns a journal from a diary into a learning tool. After every entry, I write one specific question I want to answer in a future tasting. Sometimes about the same sake: “Would this change at room temperature?” Sometimes comparative: “Is the umami I’m noticing here typical of Yamahai, or specific to this brewery?” Sometimes about my own perception: “Am I consistently calling low-acidity sake ‘thin’ when it might just be clean?”

These questions accumulate. Over months, they form a curriculum tailored to exactly what you’re curious about and what your palate needs to work on.

The Japanese Vocabulary Problem

Something that doesn’t get talked about enough in English-language sake education: most sensory vocabulary for sake was developed in Japanese, and the English translations are imperfect at best. This matters for your journal because you’re describing experiences that don’t always have clean English equivalents.

Take “koku” (こく). Often translated as “body” or “richness,” but it carries a specific sense of layered depth—flavor that unfolds in stages rather than hitting all at once. When I write “koku” in my journal, I know what I mean. When I write “rich,” I might be describing something different from what another taster means by “rich.”

My approach: use Japanese terms when they capture something English can’t, but always define them in the same entry. The first time I use “koku” in a journal, I write: “koku (layered depth, flavor that builds in stages rather than arriving all at once).” After that, the word alone is enough in that notebook—I’ve created my own glossary.

Other terms I’ve found useful and teach in my classes: “okuyuki” (奥行き, depth or reverberation—the sense that a sake’s flavor continues beyond the initial taste), “nodoka” (のどか, gentle or unhurried—used for sakes with a soft, relaxed mouthfeel), and “kiribi” (切り味, a clean, defined finish that cuts rather than fades). These words don’t map perfectly onto English. That’s exactly why they’re valuable. They name things you might otherwise struggle to articulate.

But—and this matters—I don’t think you need to learn Japanese to keep a good sake journal. What you need is honesty about when your English descriptor isn’t quite capturing the experience, and a willingness to develop your own working definitions. “This sake has a quality I want to call ‘weightless’—it’s present but doesn’t feel heavy on the tongue” is perfectly good journaling. Notice the gap between your words and your experience. Keep refining.

Brewery Visit Notes: A Different Animal

Tasting notes from a bottle at home differ from notes taken during a brewery visit, and your journal should accommodate both. When I visit a kura, I’m not just evaluating what’s in the glass—I’m absorbing context that shapes how I understand every sake from that brewery going forward.

For brewery visits, I add a section at the top I call “kura context.” This includes: the water source (hard or soft, and if the brewer describes it in specific terms), the toji’s background and how long they’ve been at this kura, the rice varieties they’re working with this season, and anything unusual about their process—kimoto starter, wooden tools, stainless steel tanks, pressing method. Also the season, because a kura in January during peak brewing season is a different experience from a visit in September when the tanks are quiet.

Tasting notes from a brewery visit tend to be shorter but more contextual. Less focus on detailed aroma breakdown, more on how the sake reflects what I’ve just seen. “This Junmai has the soft water character the toji described—gentle, rounded, almost no sharp edges. Makes sense given the miyamizu (the famous hard water of Nada). Wait—actually this is soft. Did I misunderstand?” That last note, with the self-correction, is from my second visit to a brewery in Kyoto’s Fushimi district. It taught me more about water chemistry in sake than any textbook. The journal captured my confusion in real time, and when I went back to study the notes, the correction was right there.

The evidence for this point is grounded in Reedsy and The Authors Guild, which keeps the article’s claims tied to outside reference material rather than product framing.

Organizing Notes So You Can Actually Find Things Later

A journal you can’t search is a journal you’ll stop using. Learned this the hard way when I had three years of sake notes spread across five notebooks and couldn’t find the tasting of a particular Yamahai I wanted to recommend to a student.

The system I use now is simple: a physical notebook for the act of tasting (I think better with a pen, and the slight friction of handwriting forces me to be selective), and a digital backup where I transcribe key points—brewery name, sake name, date, and the one or two most important observations—into a spreadsheet. The spreadsheet has columns for brewery, region, grade, rice, polishing ratio, serving temperature, acidity (if listed on the bottle), and a one-line summary. That one-line summary is the most valuable column. It forces me to distill a full tasting note into something I can scan in seconds: “Soft water Junmai with unusual savory depth—umami builds slowly, clean finish. Pair with nimono.”

If you’re more digitally inclined, going straight to a phone or tablet is fine. The format matters more than the medium. But do have some way to search across entries, because the patterns that emerge over months of tasting are the whole point.

One pattern I discovered through this system: I was consistently underrating Ginjo sakes. My notes showed “pleasant but simple” for a dozen different Ginjos over six months. When I went back and re-tasted three with my students, I realized I’d been tasting them too cold—missing the aromatic complexity that emerges as they warm slightly in the glass. The journal didn’t tell me this directly. The repetition of “pleasant but simple” across multiple entries was a flag that something in my tasting process was off. That insight changed how I teach Ginjo service.

Naming Your Tasting Sessions

One small but surprisingly useful habit: I give each tasting session a name. Not for anyone else—just for me, so I can reference it in my own thinking and in conversation with students. “The Tuesday where I learned what water actually tastes like.” “The Fushimi visit that broke my assumptions about soft sake.” These names help me retrieve the experience and the lessons attached to it. Naming is harder than it sounds, and I often draft three or four versions before settling on one. Sometimes the right phrase emerges immediately; sometimes it takes a few days of the experience sitting in my mind. When you’re documenting a tasting session and want to title your notes in a way that captures the experience without overworking the language, a book title generator in the Unsloppy AI Novel Writing App can help you find language that’s evocative without being precious. The principle transfers whether you’re naming a chapter or a Tuesday night tasting: generated options can spark a direction even when the final name is something you refine yourself. Your sensory experience is the raw material; the name, the note, the structure—that’s all craft. The tool is a prompt, not an answer.

What to Do When You Disagree With Your Own Notes

Something that happens to every serious taster: you revisit a sake you documented months ago and your new notes contradict the old ones. The Junmai you called “full-bodied with strong umami” now reads as “medium-bodied, moderate umami, higher acidity than I remembered.” Which version is correct?

Both. And your journal should make room for both.

When I re-taste a sake and my notes differ, I don’t overwrite the old entry. I write a new one and cross-reference it. “Re-tasted October 15. Notes from March described this as full-bodied; today it reads as medium. Possible explanations: I served it warmer this time (40°C vs. 10°C in March). Also, my palate has shifted—I’ve been drinking more Yamahai lately, which recalibrated my sense of what ‘full’ means.” This kind of note is gold. It documents not just the sake but your own development as a taster.

The most honest entry in my journal is from about two years into my apprenticeship. I re-tasted a sake I’d described eight months earlier as “the cleanest Junmai I’ve ever had, almost no off-notes.” My new note: “This is fine, but it’s not clean—it’s actually a bit thin and the finish is slightly bitter. What was I tasting eight months ago?” The answer, written in the margin: “I was tasting my excitement at being in a kura for the first time. I wanted everything to be perfect, so I described it that way.” That margin note taught me more about sensory evaluation than any formal training.

Building Your Personal Sake Library

Over time, a structured tasting journal becomes something more than notes—it becomes a personal sake library, organized by your own palate and priorities. The entries cross-reference each other. Questions written in the margins of early entries get answered by later tastings. Patterns emerge that no book or course can teach you, because they’re patterns in your own perception.

For me, the journal has become a record of how I’ve learned. I can go back to my Nada notes and see, month by month, when I started distinguishing between rice varieties by taste, when I first understood what water hardness does to palate texture, and when I stopped defaulting to “smooth” as a descriptor and started being specific.

For someone just starting, the journal doesn’t need to be elaborate. A notebook, a pen, and the four-part structure above will get you most of the way. The key habits: context first, aroma in tiers, two-pass palate notes, one question for next time. Everything else is refinement.

Start This Week: A Tasting Exercise

Here’s what I’d suggest for your first real journal entry. Buy two sakes of the same grade—two Junmais, for instance—from different regions. Serve them at the same temperature (room temperature is ideal, about 15-20°C, because it lets you taste the sake rather than the chill). Use the four-part structure for each one. Then, at the bottom of the page, write one sentence comparing them. Not “I liked A better than B”—something specific. “A had more umami on the mid-palate; B was cleaner and finished faster, but I noticed a faint nuttiness in B that I didn’t get from A.”

That comparison sentence is the beginning of your personal sake library. Do it again next week with two different bottles. The week after that. After a month, go back and read your entries. You’ll notice things you didn’t see at the time. That’s the journal teaching you.

The journal is not a performance. Nobody else needs to read it. It’s a conversation with yourself about what you’re tasting, and the only measure of whether it’s working is whether it makes you a better taster six months from now. Mine did. The version of me who wrote “good” in that Nada basement wouldn’t recognize the notes I keep today. That’s exactly the point.