How to Keep a Cooking Journal

September 30, 2026

A cooking journal can be three lines written after dinner. The trouble is that most attempts go wrong in one of two directions. Write a full page about every meal and the habit becomes a chore you start skipping. Jot down dish names and nothing else, and a year later you have a list that can't answer a single useful question.

This guide is about the middle: what to record, when, where to keep it, and how to make the entries findable when you need them. None of it requires an app, though we'll get to where one helps.

What a cooking journal is for

A cooking journal records what happened when you cooked. That sounds obvious until you notice how many nearby things get called the same name.

A recipe collection holds instructions, most of them for dishes you haven't made yet. A food diary tracks what one person ate, usually for health reasons, and doesn't care who cooked it. A meal planner is a set of intentions for next week. All three are useful, and none of them will tell you that the dal took forty minutes instead of twenty-five, or that your daughter picked out every piece of red pepper.

That second kind of fact is what the journal keeps. Its job is narrow: make the next time you cook something a little better informed than the last.

What to write in a cooking journal

An entry that earns its place usually has four parts, and none of them takes long.

The dish and where it came from. A name you'd actually use, plus the source if there is one: the cookbook and page, the website, the person who taught you. You're not copying the recipe. You're leaving a pointer to it.

What you did differently. The swap, the shortcut, the extra ten minutes. If you followed the recipe exactly, say so; that's information too.

How it went at the table. Who ate it, who didn't, who asked for more. Reactions fade faster than anything else, and they're the part a recipe can never hold.

One thing for next time. The sentence your future self will actually read.

Put together, an entry can be as short as this:

Four lines, and three of them would be gone by the weekend without it. There's a longer list of what's worth writing on a recipe after you've made it if you want to go deeper on that last line.

When to write it

The best moment is short and specific: after the meal, before the dishes are done. Wait until the next morning and you'll remember the dish but not the details. Wait a week and you'll remember that you made something, roughly.

This is why long entries fail. If writing one feels like homework, you'll postpone it, and postponed entries don't get written. Aim for something you can finish before the kettle boils. You can always add a line later; you can't recover one you never wrote.

Paper, notes app, or something else

Paper is pleasant and easy to start. A notebook in the kitchen, entries in date order, a pen that stays with it. Plenty of good cooks have kept exactly that for years.

The weakness of paper shows up later, when you want to find something. Date order is the order you wrote in, and it is rarely the order you search in. Nobody asks "what did I cook on the ninth of March?" They ask "how did the dal go last time?", and a notebook makes you flip back through every page to answer.

A notes app has the opposite problem: searchable, but easy to let drift into a pile of untitled fragments. If you use one, start every entry with the dish name, spelled the same way each time. That single habit does more for retrieval than any folder structure.

Some people speak their notes instead of typing them. A voice memo recorded while you clear the table captures more than you'd bother to type, and it costs nothing in the moment.

Keep the entries for one dish together

The first entry for a dish is a note. The third is a small history. By then you can see things no single entry shows: that the lentils always run long, that the dish went down better in winter, that you stopped adding the pickle and nobody noticed.

That's the point where a journal starts paying you back, and it only happens if the entries can find each other. On paper, that might mean an index at the back, or a page per dish instead of a page per day. In a file, it means consistent names. Recipes you've saved from elsewhere get the same treatment: what matters is connecting each saved recipe to what actually happened when you made it.

Reading it back

A journal nobody reads is just a tidier way of forgetting. Three habits keep it useful.

Look before you cook. Before making something you've made before, read its last entry. Thirty seconds, and it saves you repeating the same mistake.

Look when you're stuck. On nights when nothing comes to mind, skim back a couple of months. You'll find dishes that went well and simply fell out of the rotation.

Notice what keeps coming back. The dishes with five entries are telling you something. Over time they become the repertoire you actually cook from, which is rarely the one you'd have predicted.

Kept for long enough, a cooking journal also turns into something you didn't set out to write. A household's ordinary food, recorded as it was actually eaten, is most of a family cookbook already.

Where MealEncore fits

MealEncore is a cooking journal you can speak into. After a meal you say (or type) what you cooked and anything that stood out, and it becomes an entry: the dishes, what you said about them, and room for each person at the table to add their own reaction. It's built to keep what you said, not to fill in what you didn't.

When you've made the same dish more than once, you can tell it those entries belong together. From then on the dish carries its own history in one place: every time you made it, the notes you left for next time, what each person thought. The part a paper journal makes hard, finding last time, is the part it's built around.

MealEncore is invitation-only while we open it up. If this is how you'd like to keep yours, the list is the way in.

Join the early-access list →

Common questions

← Back to Blog